Zigbee Extreme Battery Drain

2024-02-21T18:03:03.763174166Z INFO Zigbee Contact Mc <ZigbeeDevice: d5c46aef-8f26-4442-a671-2f36f00e42e5 [0x2F64] (Puerta Casa)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0x2F64, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xCC, rssi: -82, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x9C >, GenericBody: 00 00 00 00 00 00 00 00 00 00 > >
2024-02-21T18:03:03.812428125Z DEBUG Zigbee Contact Mc Puerta Casa device thread event handled
2024-02-21T18:03:04.136161291Z TRACE Zigbee Contact Mc Received event with handler zigbee
2024-02-21T18:03:04.150468875Z INFO Zigbee Contact Mc <ZigbeeDevice: d5c46aef-8f26-4442-a671-2f36f00e42e5 [0x2F64] (Puerta Casa)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F64, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xBC, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x31, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, MeasuredValue:
1796 > > > >
2024-02-21T18:03:04.162569208Z TRACE Zigbee Contact Mc Found ZigbeeMessageDispatcher handler in zigbee_contact → Temp-Sensor
2024-02-21T18:03:04.167351541Z INFO Zigbee Contact Mc Executing ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
2024-02-21T18:03:04.184345Z DEBUG Zigbee Contact Mc Puerta Casa device thread event handled
2024-02-21T18:03:04.420104208Z DEBUG Zigbee Contact Mc driver device thread event handled
2024-02-21T18:03:05.744209875Z TRACE Zigbee Contact Mc Received event with handler zigbee
2024-02-21T18:03:05.750990958Z INFO Zigbee Contact Mc <ZigbeeDevice: d5c46aef-8f26-4442-a671-2f36f00e42e5 [0x2F64] (Puerta Casa)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0x2F64, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xC4, rssi: -88, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x9D >, GenericBody: 00 00 00 00 00 00 00 00 00 00 > >

Yesterday they released the beta 52.8 firmware version of the hub and changed something again in the Zigbee stack.
This time they have changed from version 6.0.9 to 5.7.4, it seems that they have gone back.

Well, looking at the CLI logs it seems that the devices are once again sending two messages from the Basic cluster, generic body, for each reportAtributte message of any attribute.
We return to what the previous firmware version 51.x and the zigbee stack 5.6.4 did.

If it was a good step to reduce battery consumption, it seems that this was not the correct step or something went wrong.

Maybe it makes some sense, but I don’t see it, it worked perfectly without sending the two Basic cluster messages.
They’ll tell us, if they want.

3 Likes