Model-specific alarm control and readback
Track Y811/Y812 alarm commands, capability limits and state readback for complete model configurations, with matched module data, gateway versions and real-device acceptance. Keep documentation, displayed state, simulation and field results distinct.
Timeline
Alarm handling was made dependent on the complete configuration model rather than treating similar-looking devices as one protocol. Module and existing-point model updates were reported for production and test data; uncleared list caches could still show older values temporarily. A gateway commit passed a reported 186 unit tests and two hardware-simulation tests. Missing or unknown alarm models were to be rejected while ordinary switches kept their existing path. Those checks do not establish acceptance on all real variants.
Daily entry · Alarm models, point contracts and client checks ↗