Joseph Doherty 5c88de078c fix(abcip): keep the ALMD last-told state across a re-subscribe so a still-faulted alarm is not re-raised (#641 review) ...

Now that ALMD transitions route, a re-subscribe (every reconnect, every alarm-set change)
started from an empty per-subscription record and re-RAISED every still-faulted alarm,
which the host projects as Active+unacked - un-acknowledging a condition the server had
just carried across the rebuild with its client ack. The record is now driver-owned and
pruned to the new set, mirroring MTConnect's _deliveredConditions.

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

2026-10-08 17:17:55 -04:00

..

Client

fix(client): alarm filter selected ActiveState/Id as ONE QualifiedName — every event read inactive

2026-10-08 16:19:27 -04:00

Core

fix(opcua): carry native alarm condition state across a full rebuild (#641)

2026-10-08 17:02:12 -04:00

Drivers

fix(abcip): keep the ALMD last-told state across a re-subscribe so a still-faulted alarm is not re-raised (#641 review)

2026-10-08 17:17:55 -04:00

Server

fix(abcip): report ALMD transitions with ConditionId = RawPath and a Kind (#641)

2026-10-08 17:08:47 -04:00

Tooling/ZB.MOM.WW.OtOpcUa.Analyzers.Tests

fix(archreview #10): wire CapabilityInvoker into prod dispatch via a Polly-free seam

2026-07-08 21:33:16 -04:00