52.X Hub V2/V3 Customer Beta Release Notes

Developer Programs Hub Firmware Beta
40

Hello,

I don’t know if it has anything to do with the new Beta 52.11 version, but I have observed the following on several devices with different drivers.

  • I have stopped receiving the 2 ZDO messages from the Basic cluster with each AttributeReport message on several devices with different drivers:

with 52.09:

2024-03-07T17:54:00.424525730Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xDD38, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xD0, rssi: -82, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x89 >, GenericBody:  00 00 00 00 00 00 00 00 00 00 > >
2024-03-07T17:54:01.390896771Z DEBUG Zigbee Motion Sensor Mc  Sensor Mov-1 device thread event handled
2024-03-07T17:54:01.401375355Z TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2024-03-07T17:54:01.414923980Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD38, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xBA, rssi: -61, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x75, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2024-03-07T17:54:01.420222230Z TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2024-03-07T17:54:01.424796771Z INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2024-03-07T17:54:01.434003896Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2024-03-07T17:54:01.444903605Z DEBUG Zigbee Motion Sensor Mc  Sensor Mov-1 device thread event handled
2024-03-07T17:54:02.633368043Z TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2024-03-07T17:54:02.674138752Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xDD38, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xD0, rssi: -82, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x8A >, GenericBody:  00 00 00 00 00 00 00 00 00 00 > >

with 52.11

2024-03-07T21:48:29.341479337Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 9b6380e3-7155-4d74-85f6-0878a92e0a85 [0xB389] (Sensor Mov-2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xB389, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xBC, rssi: -60, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x11, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2024-03-07T21:48:29.411513503Z TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2024-03-07T21:48:29.417151378Z INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2024-03-07T21:48:29.423116128Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 9b6380e3-7155-4d74-85f6-0878a92e0a85 [0xB389] (Sensor Mov-2)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}

  • Smoke detector Mc: The 3 paired devices only send AttributReport message.

  • Contact Sensor Mc: Some devices continue to send ZDO messages. I have re-paired one of them, resetting the device, WITH HUB SECURE MODE DISABLED, and it has been re-paired, configured correctly, they have a new network ID (DNI), it has not lost any routines and it has stopped sending messages ZDO of the Basic cluster.

  • Motion Sensor Mc: Identical to the Motion Sensor Mc. I also re-paired a device with the same result.

  • It is possible that since they are sleeping devices, they have not been reconfigured with the Hub reboot. Tomorrow I will re-pair all the devices with these drivers with this quick and easy method. Now it’s too late here.

  • Switch Mc: all but one of the controller devices have stopped sending ZDO cluster basic messages

  • Multi Switch Mc: one of two the driver devices have stopped sending ZDO cluster basic messages

  • Temperature humidity Mc: The two driver devices have stopped sending ZDO cluster basic messages.

If they have nothing to do with it, it doesn’t matter, it is good news for the zigbee network and for the batteries.

2 Likes