BETA UPDATES
I have started doing beta updates for my drivers, see this post for more details:
1 Like
Hi.
One of my ZEN73 LR's is not syncing.
I can get it, eventually, to sync, but then I can perform only one action before it stops responding.
Another configure brings up 15 changes, again.
I've tried rebooting.
I've tried shutdown/power cycling and flipping the breaker.
I flip the physical switch-which can get it going-led blinks, but again, even if it eventually says 'synced' it doesn't stay that way.
I replaced the driver with Driver and cleared states.
I've removed the device from the HomeKit Integration app, which I just recently started fooling with (coincidence?).
Any other ideas?
Perhaps a factory reset of the ZEN73?
I'm not crazy about doing a cloud restore since it won't capture stuff I've been doing lately.
Thanks!
Edit: I’m sitting here in the little room at the doctor’s office and the thing seems to work over the cloud and app
Edit 2: right before I left the house I exercise the switch by removing the rules for motion, sensing actuation. It seemed to work, but I didn’t have time to fully test. Hopefully it will be still working when I get back home after golf.
Do not do a cloud radio restore, unlikely to help.
It should not just get out of sync by itself, unless you are changing the settings. Are you maybe changing the LED settings via rules? It could them possibly show it has 1 pending change. Running a configure at that point would just try to set that one parameter back to how it was.
If the device stops responding, running configure is not the solutions at all. The Sync Status is just for the settings, has nothing to do with the device being responsive.
If its showing synced and you run a Configure the driver attempts to set all the parameters again per your settings. It should normally sync back up within a few seconds. If this fails either the device is not responding, or the mesh/radio is jammed up and not sending or receiving the messages.
2 Likes
Makes sense.
And yes, it does now work normally.
I'm in the middle of re-adding several Zooz Zen devices and noticed some unusual behavior during the Configure step.
It appears that Zen77 (paddle switch) and Zen74 (toggle switch) behave differently when both using the ZEN Advanced Dimmer driver. Both dimmers were Off when added via SmartStart to the hub. During the Configure step the Zen77 will turn On, but the Zen74 will stay Off. See the logs below. Both dimmers are on the most recent firmware.
I observed this in a similar previous pair of devices (I'm adding a few at a time). I think I saw this the last time I configured this hub. I also think this happened with a ZAC36 Water Valve (went from open to closed during Configure). I'll continue to watch as I add devices.
Zen77:
Zen 74:
Some of the Zooz devices react when certain settings are set, which happens at configure. So there is not really any way around it.
1 Like
Hi.
I've been trouble shooting some rule issues.
In the process I noticed that the basement ZEN73's always have the three association groups set to 01.
When I go to a normally operating switch, which does not have associations showing on the preference page, and hit "Configure", lo and behold, I get the 01's.
I realize that 01 is the hub, but is this an issue?
Thanks.
For Zooz devices Only the lifeline needs to be set to the hub (01), all the other associations can be blank. It could possibly cause issues with duplicate reports if you have all the associations set to the hub.
There are some other brands where to enable certain features you have to set other associations to the hub but I have never seen a Zooz need that.
The thing is, I can't get rid of the 01's.
They seem to populate after a configure or a preference change.
Turn on debug logging, change them all to 0, then save. Post the resulting logs.
Also what is the firmware version? Maybe this is something new that I have not seen yet. I don't think I have any of the 800LR switches. Most of my house is the old ZEN27's
I think Jeff would also like to know what (Zooz) f/w version your Z73s are on.
2.10
I noticed this after restoration from a local backup, but I haven't been looking for this.
Same result with my one dimmer, ZEN74:
Just like the ZEN73, it started blank, but went to 01 after Configure.
Are you on Zwave JS? You can tell from Zwave details if the button says to switch back to legacy. If yes then that is probably the issue, I am not supporting anything on Zwave JS, too many bugs still.
I guess I should have said Trace logging, you can switch it to trace and do logs again but I am 99% sure its going to be a bug in ZWJS.
Just tested on a ZEN30 on ZwaveJS and I cannot set any associations. So you probably set those when on ZIP and are now on ZwaveJS and cannot remove them.
Trying to set the association does nothing and device kicks back that is empty / not set still.
Yes I am.
Is the general consensus that ZWJS is not yet ready for prime time?
It could explain some rule slowdowns and inops.
I've never used associations, only experimentally, and then, not with the LR devices I believe. This is with each device I've used Configure on. It changes from blank, or "Enable" or whatever, to 01.
Just from the feel, perhaps ZWJS reports the hub association, which don't all devices have, or perhaps LR, as it found it, and then does nothing with it.
In any event, I do believe I'll be going back to Zip I can't see any advantage.
Thanks.
