What is the procedure for returning these outlets?
They are very unreliable and by your lack of updates I can only assume this will continue for longer than I am willing to go without them. I’ve already waited nearly 2 years for the ZEN 25 fixes and I’m not willing to do that again.
Please recommend replacement outlets that are know to work reliably with the Ezlo Secure.
Hello,
By taking a look at your controller’s logs, this is what I was able to find. Around 3 AM the ha-zigbeed service restarted, probably caused by a system re-initialization. The controller starts to look for all three devices you have paired as soon as the initialization of the service is completed.
2023-02-03 03:31:01.290350 DEBUG: Try to request attribute value: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, attributeName: OnOff
2023-02-03 03:31:01.304345 DEBUG: Try to request attribute value: nodeId: 0xd279, endpointId: 0x01, clusterName: on_off, attributeName: OnOff
2023-02-03 03:31:01.319697 DEBUG: Try to request attribute value: nodeId: 0xb9af, endpointId: 0x01, clusterName: on_off, attributeName: OnOff
The controller starts to update all nodes and finds out that it can’t get communication with all three of your devices.
2023-02-03 03:31:31.684473 DEBUG: Device is not longer reachable 61153
2023-02-03 03:31:31.684803 DEBUG: Device is not longer reachable 53881
2023-02-03 03:31:31.684973 DEBUG: Device is not longer reachable 47535
The controller tries to send commands multiple times during that same morning returning an unreachable status.
2023-02-03 06:03:13.458972 DEBUG: Skip rejoining of existing device: 0xd279 / 53881
Trust Center Join Handler: status = secured rejoin, decision = no action (03), shortid 0xD279
2023-02-03 06:03:14.771434 DEBUG: Try to request attribute value: nodeId: 0xd279, endpointId: 0x01, clusterName: on_off, attributeName: OnOff
2023-02-03 06:03:45.096395 DEBUG: Device is not longer reachable 53881
2023-02-03 06:14:20.363713 DEBUG: Try to send command: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, commandName: On, commandParams: null
2023-02-03 06:14:49.235232 DEBUG: Try to send command: nodeId: 0xb9af, endpointId: 0x01, clusterName: on_off, commandName: On, commandParams: null
2023-02-03 06:14:50.683499 DEBUG: Device is not longer reachable 61153
2023-02-03 06:15:12.343571 DEBUG: Try to send command: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, commandName: On, commandParams: null
2023-02-03 06:15:19.553721 DEBUG: Device is not longer reachable 47535
2023-02-03 06:15:42.662447 DEBUG: Device is not longer reachable 61153
Trust Center Join Handler: status = secured rejoin, decision = no action (03), shortid 0xB9AF
2023-02-03 07:06:46.119971 DEBUG: Try to request attribute value: nodeId: 0xb9af, endpointId: 0x01, clusterName: on_off, attributeName: OnOff
2023-02-03 07:07:16.533015 DEBUG: Device is not longer reachable 47535
2023-02-03 10:05:46.646119 DEBUG: Try to send command: nodeId: 0xb9af, endpointId: 0x01, clusterName: on_off, commandName: Off, commandParams: null
2023-02-03 10:06:16.995493 DEBUG: Try to send command: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, commandName: Off, commandParams: null
2023-02-03 10:06:17.008209 DEBUG: Device is not longer reachable 47535
2023-02-03 10:06:34.331847 DEBUG: Try to send command: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, commandName: Off, commandParams: null
2023-02-03 10:07:04.674091 DEBUG: Device is not longer reachable 61153
2023-02-03 10:08:16.945514 DEBUG: Try to send command: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, commandName: On, commandParams: null
2023-02-03 10:08:24.154383 DEBUG: Try to send command: nodeId: 0xeee1, endpointId: 0x01, clusterName: on_off, commandName: Off, commandParams: null
emberAfReportAttributesCallback(): 61153 / 0xeee1, ep: 1 -> 1, cls: 6 / 0x0006
2023-02-03 10:08:45.903874 DEBUG: Receive attribute report from node_id: 61153
ZigbeeAddon::attributeValueUpdated: 0xeee1 0x0001 0x0006 0x0000 false
2023-02-03 10:09:10.334096 DEBUG: Try to send command: nodeId: 0xd279, endpointId: 0x01, clusterName: on_off, commandName: Off, commandParams: null
2023-02-03 10:09:40.624432 DEBUG: Device is not longer reachable 53881
Could you please let me know why are the daily reboots at 3 AM necessary? And just in case, are there any important obstacles between the outlet’s location or anything that could generate interference?
Regarding the ZEN25, there’s a potential fix included in the firmware version 2.0.35.2167.3 (BETA release). Please let me know if you’d like to try it out on your controller to test its behavior.
The outlet is only ~18 inches from the hub with a direct line of sight.
It seems to me the outlet needs to be debugged to determine why it gets into a state where it doesn’t respond to the controller. We need logs on both sides to see if the outlet is even receiving anything from the controller while in this state. If the outlet can’t be debugged then perhaps you can use a zigbee monitor if such a thing exists, something like wireshark is for ethernet.
I decided to reboot the controller daily to try to fix the issue where Alexa says the device isn’t responding. What is your recommendation about rebooting? Don’t do it? Do it but with a ___ frequency (fill in the blank).
I will accept the BETA release of 2.035. We should determine if the potential fix will work before it gets released, no?
Hi @slapfrost,
Any updates?
I’m still on 2.0.33.2116.2. It sounded like you were going to update me to the BETA version.
Hello @chuckf2 !
Your controller has been upgraded to firmware version 2.0.35.2156.5. Would you mind testing the ZEN25? And also let us know how the responsiveness with your outlets is.
Hi @slapfrost,
Not there yet:
• Tested on 2/15/2023 between approximately 10:30 to 10:42am EST.
• I plugged the ZEN25 into an outlet in the same room as the hub, about 10 feet away.
• I did a factory reset on the ZEN25
• I paired it as a Generic Z-Wave device, selecting S2 security. Install went fine.
• I toggled the switches in the Vera Mobile app (3.63) in various combinations and I fairly quickly confused it. The app shows port 2 being on but the led on the device indicates it is off.
• In another test I was able to get it into a state where the main switch shows it is off but the two port switches indicate they are on. However, while I was writing this up the app showed the main switch and port 2 on which is correct.
• In another test I was able to get the app to show the main switch on while the port switches are off even though port 2 is on on the device.
• I've noticed the "wait cursor" appearing in the app when I play with the switches. It may be that the app needs to wait a little longer before allowing the user to interact again.
• I won't bother moving the device away until it is stable close up.
• Hopefully you can grab some info from the logs.
I’m still having trouble with the Centralite outlets. They almost always say “Device failed to communicate” but they still work sometimes.
Currently, the app says that for one I use for a lamp even though I’m able to control it from the app.
Hello @chuckf2 ,
How was the experience with moving one outlet closer?
When was the last time the outlets reported they were online? I’ll try to gather logs from when they lost connection.
I’ll test the connection and let you know the results.
Hello @chuckf2 ,
This is a follow up to your situation.
It was reported and fixed on firmware version 2.0.35.2167.3 and your controller is currently running 2.0.50.2444.3, could you confirm if everything is working fine now?
We’ll be attentive to your response.
Looks like they are working fine now. thank you!
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules