I wired in my first 4 way switch yesterday and was thinking I got lucky and it all worked. The switch is a GE 14292 with two add-ons. I noticed these on/off entries in the log that are not humanly possible to produce. I haven't seen this before and was wondering what it might mean.
To make sure I'm following this - if I disconnect the traveler at the main switch and I'm still seeing the problem, I'll know it's the main switch. The same applies to the add-ons - disconnect the traveler and see if the problem persists?
The funny thing is if I hadn't seen the log I would have thought they were working perfectly. This is going to take a while because it has happened hours apart.
I also reconfigured the switch because I did kill the power each time I put the wires back in a box and then tested the switch to make sure I didn't disconnect anything in the process.
Maybe related, maybe not but I had a Zooz S2 dimmer doing that to me today. Upon further investigation I had the driver as a Generic Zwave smart dimmer...changed it to a Generic Zwave dimmer and everything calmed down. When I first installed it it worked fine but as time went on it starting acting really screwy.
Thanks. I will also try that. It's a zwave plus GE 14292 toggle (non-dimmer) with two add-ons (12728) and it configured with the Generic Zwave Smart Switch driver.
The Zooz S2 dimmer is screwey, that's why currently it's not been fingerprinted nor added to our supported devices wiki.
It issues a constant stream of level change reports whilst a level change is in progress, these are of no value from an automation standpoint and do nothing other than load up your mesh with packets that just get thrown out by the driver.
I don't recomend this dimmer until they fix this, and I've not received any indication that they will.
Actually, they aren't behaving properly. They are spamming your zwave network with garbage when you change the dim level on the light.
But I understand what you mean. As long as your zwave network isn't too loaded, and there isn't a lot going on at the same time you are dimming, it can be fine.
I expect they will fix it sooner or later with a firmware update. I'm not sure I would rip out a working device, if everything else is OK.
It would be interesting to see what happened if someone had, say, 20 of these and triggered them all at once with a rule/automation - like what could happen on a mode change. I would guess the switches would still work, but nothing else on the zwave network would until dimming finished. I could be wrong, though.
I’ve been free of the rapid on/off events for 12 hours. I’m going to give it another 12 hours and then unpause a RM rule that notifies me every hour the basement lights are on.
I’m wondering if what I’m seeing in the log could be ghost events similar to what had been generated by RM polling even though the rule isn’t specifically using a RM polling routine.
Looking through my logs I do not have any events after I changed the driver to the generic dimmer from the smart dimmer. Before that I did have a bunch of on/off and change of level events. Hoping that was it for right now anyway.
They are spamming your zwave network with garbage when you change the dim level on the light.
As long as your zwave network isn't too loaded, and there isn't a lot going on at the same time you are dimming, it can be fine.
I might contact them then and see if they swap them out for the standard ones...last thing I need is a bunch of issues causing me headaches.
