Few days ago, I decided to upgrade my home network from ZBDongle-P to the new ZBDongle-E. All was perfect excep my power strips. Two of them (_TZ3000_o005nuxx) decided to reboot each second. The solution was as simple as forcing the removal of those pesky power strips, reject the device and re-pairing them like long-lost friends.
During my troubleshooting I updated the dongle and setup ember driver.
'Ember' significantly improve the startup of my Z2M environment avoiding multiple reboot and errors. Furthermore, after resolving the stability concerns with my power strips, my network environment has achieved a newfound level of reliability.
Therefore and once again, thx a lot @Nerivec and @Koenkk for your work !
Setup:
Unfortunately, few hours later I check everything and discover I cannot set 'power_outage_memory' and get this error on logs for 1 powerstrip (_TZ3000_cfnprab5) :
For the other powerstrip (_TZ3000_o005nuxx), when I want to setup "restore" I get:
Debug 2024-04-01 08:46:26Received MQTT message on 'zigbee2mqtt/HappyAquaPower/set' with data '{"power_outage_memory":"restore"}'
Debug 2024-04-01 08:46:26Publishing 'set' 'power_outage_memory' to 'HappyAquaPower'
Debug 2024-04-01 08:46:26Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'genOnOff', data '{"moesStartUpOnOff":2}' from endpoint 1 with groupID 0
Info 2024-04-01 08:46:26MQTT publish: topic 'zigbee2mqtt/HappyAquaPower', payload '{"child_lock":"UNLOCK","linkquality":196,"power_outage_memory":null,"power_outage_memory_l1":"restore","state_l1":"OFF","state_l2":"ON","state_l3":"ON","state_l4":"OFF","state_l5":"ON"}'
Info 2024-04-01 08:46:26MQTT publish: topic 'zigbee2mqtt/HappyAquaPower', payload '{"child_lock":"UNLOCK","linkquality":192,"power_outage_memory":null,"power_outage_memory_l1":"restore","state_l1":"OFF","state_l2":"ON","state_l3":"ON","state_l4":"OFF","state_l5":"ON"}'
Debug 2024-04-01 08:46:26Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'genOnOff', data '{"moesStartUpOnOff":2}' from endpoint 1 with groupID 0
Info 2024-04-01 08:46:26MQTT publish: topic 'zigbee2mqtt/HappyAquaPower', payload '{"child_lock":"UNLOCK","linkquality":232,"power_outage_memory":null,"power_outage_memory_l1":"restore","state_l1":"OFF","state_l2":"ON","state_l3":"ON","state_l4":"OFF","state_l5":"ON"}'
Debug 2024-04-01 08:46:26Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 1 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 1 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 2 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 2 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 2 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 3 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 3 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 3 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 4 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 4 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 5 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 5 with groupID 0
I write in this request for 2 types (but similar) equipments. Logs are not the same but in the end we have the same problem.
What did you expect to happen?
I expect to setup the "Power outage memory" parameter on my power strips.
How to reproduce it (minimal and precise)
Click on Device > "DeviceName" > Expose and set **Power outage memory*** parameter.
Zigbee2MQTT version
1.36.0 commit: 86ed71c
Adapter firmware version
7.4.1 [GA]
Adapter
ZBDongle-E
Setup
Raspberry Pi4 with HA, EMQX and Z2M in a docker.
Debug log
Reboot with "Ember" driver and issue with _TZ3000_cfnprab5:
logs.txt
For the other powerstrip (_TZ3000_o005nuxx), when I want to setup "restore" I get:
Debug 2024-04-01 08:46:26Received MQTT message on 'zigbee2mqtt/HappyAquaPower/set' with data '{"power_outage_memory":"restore"}'
Debug 2024-04-01 08:46:26Publishing 'set' 'power_outage_memory' to 'HappyAquaPower'
Debug 2024-04-01 08:46:26Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'genOnOff', data '{"moesStartUpOnOff":2}' from endpoint 1 with groupID 0
Info 2024-04-01 08:46:26MQTT publish: topic 'zigbee2mqtt/HappyAquaPower', payload '{"child_lock":"UNLOCK","linkquality":196,"power_outage_memory":null,"power_outage_memory_l1":"restore","state_l1":"OFF","state_l2":"ON","state_l3":"ON","state_l4":"OFF","state_l5":"ON"}'
Info 2024-04-01 08:46:26MQTT publish: topic 'zigbee2mqtt/HappyAquaPower', payload '{"child_lock":"UNLOCK","linkquality":192,"power_outage_memory":null,"power_outage_memory_l1":"restore","state_l1":"OFF","state_l2":"ON","state_l3":"ON","state_l4":"OFF","state_l5":"ON"}'
Debug 2024-04-01 08:46:26Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'genOnOff', data '{"moesStartUpOnOff":2}' from endpoint 1 with groupID 0
Info 2024-04-01 08:46:26MQTT publish: topic 'zigbee2mqtt/HappyAquaPower', payload '{"child_lock":"UNLOCK","linkquality":232,"power_outage_memory":null,"power_outage_memory_l1":"restore","state_l1":"OFF","state_l2":"ON","state_l3":"ON","state_l4":"OFF","state_l5":"ON"}'
Debug 2024-04-01 08:46:26Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 1 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 1 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 2 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 2 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 2 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 3 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 3 with groupID 0
Debug 2024-04-01 08:46:27Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 3 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 4 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 4 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 5 with groupID 0
Debug 2024-04-01 08:46:28Received Zigbee message from 'HappyAquaPower', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":2}' from endpoint 5 with groupID 0
What happened?
Few days ago, I decided to upgrade my home network from ZBDongle-P to the new ZBDongle-E. All was perfect excep my power strips. Two of them (_TZ3000_o005nuxx) decided to reboot each second. The solution was as simple as forcing the removal of those pesky power strips, reject the device and re-pairing them like long-lost friends. During my troubleshooting I updated the dongle and setup ember driver. 'Ember' significantly improve the startup of my Z2M environment avoiding multiple reboot and errors. Furthermore, after resolving the stability concerns with my power strips, my network environment has achieved a newfound level of reliability. Therefore and once again, thx a lot @Nerivec and @Koenkk for your work ! Setup:
ZBDongle-E:
Z2M:
Unfortunately, few hours later I check everything and discover I cannot set 'power_outage_memory' and get this error on logs for 1 powerstrip (_TZ3000_cfnprab5) :
In the state part I get:
For the other powerstrip (_TZ3000_o005nuxx), when I want to setup "restore" I get:
When I get the state I have:
I write in this request for 2 types (but similar) equipments. Logs are not the same but in the end we have the same problem.
What did you expect to happen?
I expect to setup the "Power outage memory" parameter on my power strips.
How to reproduce it (minimal and precise)
Click on Device > "DeviceName" > Expose and set **Power outage memory*** parameter.
Zigbee2MQTT version
1.36.0 commit: 86ed71c
Adapter firmware version
7.4.1 [GA]
Adapter
ZBDongle-E
Setup
Raspberry Pi4 with HA, EMQX and Z2M in a docker.
Debug log
Reboot with "Ember" driver and issue with _TZ3000_cfnprab5: logs.txt
For the other powerstrip (_TZ3000_o005nuxx), when I want to setup "restore" I get: