[dependabot]

Bumps native/bacnet-stack from b4abcf1 to afcf114.

Commits

• afcf114 fix(bacfile-posix): platforms without fileno() and ftruncate() (#1557)
• 4196cfa Feature/bacfile posix file size set (#1556)
• 12e493f fix(dst): support Southern Hemisphere DST ranges and reject invalid calendar ...
• 0f84390 feat(ai): add read-only Min_Pres_Value and Max_Pres_Value (#1552)
• e9e4880 feat(nc): support dynamic Notification Class instances (#1553)
• See full diff in compare view

[gencto]

Closing: this submodule bump to afcf114 regresses our server-side Notification Class handling and is not safe to adopt yet.

The range pulls in two upstream changes that break our NC path:

• #1551 — Priority is reworked to a BACnetARRAY, and
• #1553 — dynamic Notification Class instances.

With the bump applied, the integration suite fails at runtime:

BacnetProtocolException: write 15:3 property 86 failed (Object: Unknown Object)

(object type 15 = Notification Class, property 86 = priority) — our server can no longer provision/write the NC object the way it did against b4abcf1. This is a real behavioural regression, not a build break, so it can't be papered over with a generator tweak.

We'll revisit adopting a newer bacnet-stack once our NC server path is reworked for the array-priority / dynamic-instance model. Until then we stay pinned at b4abcf1.

---

Generated by Claude Code

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.