I have several GE 46201 z-wave plus switches. I am trying to write a rule based on the physical switch being turned on. What I find in the logs is that even when one of the switches is turned on or off by a rule or Alexa, the logs show a both a physical and a digital on or off.
I'm using the system driver that I think should correspond to this device
I would like to use this driver instead of the generic because I plan on using some of the double tap and button features of these switches.
What am I doing wrong?
EDIT: forgot to mention that I have done the configure on each switch
Thanks, Mike - when the device was originally included (Dec 2019) the driver just showed "Device". I switched it to generic z-wave smart switch. When 2.1.8 was released in Jan it included a new driver for the 46201, so I switched to that one and did a configure under the new driver. Should I have done this differently?
Mike is right, if you want to use in-box drivers the correct one is:
GE Enbrighten Z-Wave Smart Switch
If you want to try a user driver, then it would be the one below. It is somewhat confusingly named very close to the in-box one (it is GE Enbrighten Z-Wave Plus Switch)... But since I made mine 5 months before they did, that isn't my fault. :
Both should support correct reporting of physical/digital events, though... So that is odd that the in-box driver is reporting both.
But if you can't get the in-box one to do what you want, try the user driver (the user driver also supports triple tap events and pre-loading the dimmer level which the in-box does not).
@JasonJoel@mike.maxwell Thanks for your responses. I have 10 GE 46201's, they all show both physical and digital on/off each time they are switched on or off, regardless of how the command gets there (app, Alexa, physical). This is using the new system driver. Here is one example of what happens when I turned one on via voice command:
I don't really know how to interpret the z-wave parsing but it looks like both drivers are reporting a physical and a digital "on" when I turn the switch on via voice command? Please help me understand what is going on here.
No, you would know if you changed associations. It takes manual steps to do it (and the in-box driver can't do it at all).
Sorry I can't be more help. Sure looks like the command is being sent to the device multiple times. You might want to pause all of your rules and groups and see if behavior changes. Make sure something isn't repeating the command to the device multiple times.
Pausing those simple lighting rules didn't have any effect. Still seeing digital and physical "on" commands in the log with a voice command. I turned the simple lighting rules back on, triggered them (using motion) , and I see same thing in the logs, both digital and physical "on".
There are definitely a few command classes I didn't put in my drivers (as you can see in the logs when you repair). Maybe I'll go back and add them at some point.
In terms of device functionality they aren't needed at all. They are just additional calls that @bcopeland makes on repairs. Side note, it would be handy if there were a list of these 'not needed for normal functionality' command reports that the hub makes during a repair so drivers authors would know to add them (if they are even really needed to be added).