TIDUFK2 September 2026
The Zigbee functionality was tested using a Zigbee coordinator running Zigbee2MQTT. The TIDA-011030 joined the network as a Zigbee end device and completed the device interview successfully. It was identified using its model name and manufacturer information. The device interview detected the On/Off, Metering, Electrical Measurement, and Temperature Measurement clusters on endpoint 10. A project-specific Zigbee2MQTT external converter was used to expose the supported measurement, breaker-state, alarm, and service-disconnect attributes. This converter is included in the TIDA-011030 CC2340R53 firmware folder.
Figure 4-9 TIDA-011030 Device Information After Successful Zigbee Commissioning and InterviewDuring normal operation, Zigbee2MQTT requested the electrical measurement attributes at five-second intervals. The received data included voltage, current, active power, reactive power, apparent power, power factor, frequency, accumulated energy, and temperature. The breaker could also be opened and closed using the On/Off control exposed by Zigbee2MQTT.
Figure 4-10 Metering Values and Breaker Control Displayed in Zigbee2MQTTBreaker-state changes, protection alarms, and service-disconnect reasons were transmitted using Zigbee attribute reporting when their state changed. This event-driven path does not depend on the five-second measurement polling interval.
Figure 4-11 Zigbee2MQTT Status Following a Short-Circuit Protection TripThe reporting behavior was verified by initiating a short-circuit trip. After the protection function opened the breaker, Zigbee2MQTT displayed the breaker state as OFF, asserted the service-disconnect alarm, and reported Short circuit as the disconnect reason. The overcurrent alarm returned to False after the current was interrupted, while the latched service-disconnect alarm and trip reason remained available to identify the protection event.