If it's a Honeywell Z-Wave Plus switch or dimmer, you should be able to use that driver. I have never checked model numbers, every Honeywell and UltraPro (and GE) Z-Wave Plus dimmer or switch I have is running very nicely on those two drivers.
I particularly like the fact that his driver allows you to change a dimmer into a switch. Allows me to only purchase dimmers and then put them to use on any light(s) I want to. So I never have situation where I need to buy a switch 'cause I only have dimmers.
Just to clarify - you don't need to ID the specific models unless you are just generally curious. All you really need to know is if the switch is Z-Wave Plus or Z-Wave. I have installed all three types (GE, Honeywell, UltraPro) Z-Wave Plus switches over the past few years, and they all work w/the drivers I provided the links for.
Z-Wave Plus dimmers/switches inClusters data should start/include, as @neonturbo indicates 0X5E:
It asks the device for it's capabilities. Then the driver can understand what (in this case) the outlet can do. Your example of the indicator light is a good one, but it could be other basic things that make the device work correctly.
Yes, it is a good habit to do so, and may be required in many cases to make things work.
They were supported at one time. The locks were so problematic, they were causing a support nightmare. They removed these from the compatible list, but did not remove the driver. In fact, I think there has even been an updated driver since it was removed from the official list.
There IS an built-in Schlage driver. It should detect it correctly. You probably don't want the generic driver.
You can sort of tell by the InClusters. If it had a 0X25 in the cluster it would be an older Z-wave device, with 0X5E it is a Z-wave Plus.
I usually google the DeviceID number and see if it comes up. The better way is probably to pull the switch and look at the numbers. The number on the face of the switch can often also help ID it, and that is pretty easy and safe as you just have to pull the decorative plate.
I suspect this IS a Enbrighten due to being a Z-wave plus, and that it supports S2 security.
This part is incorrect. Cluster 0x25 simply means the device supports the binary switch command class. So any zwave or zwave+ device that is a binary switch will have this inCluster.
For example, here’s a binary zwave+ switch that has this inCluster:
Well I'm here for the Jasco 46562 issue where it shows up as a dual outlet and creates two child devices that don't do anything. The delete button is still greyed out for those child devices. I just installed six of these today, so now I have a lot of extra devices in the list now. If I choose the parent device and ignore the child devices that does appear to work though.
As for the driver, the box claims Z-Wave Plus so I figured they would update status quickly, unlike the old non-Plus GE/Jasco switches I have installed elsewhere. I tried a couple built-in drivers that controlled the device properly, but would not update the status (GE Enbrighten Z-Wave Smart Switch and Generic Z-Wave Plus Switch). For now I'm using the Generic Z-Wave Switch driver and added them to the Z-Wave Poller app so I can get decent status update times.
Can you test if switch can be controlled from the device page? If it can, can you test whether physical control of the switch is mirrored on the device page?
If that does not work, then can you download @JasonJoel's driver described in the thread linked below. Repeat steps 3 and 4 indicated above, but selecting @JasonJoel's driver instead of the built-in driver.
Removing the children worked. The built-in driver didn't work. Switching to @JasonJoel 's driver appears to work well for these. Polling of my old GE/Jasco switches seems to have stopped working right in the process of doing all this though. Guess I'll need to try rebooting and stopping/starting the polling again and hope it's fixed.
Do you have all of your Enbrighten Switches working with @JasonJoel's driver without polling? And if so, have you removed them from the polling app?
If you haven't, you should do that first.
After doing that, do a "Shutdown" from the menu (under Settings), and not a reboot. Then disconnect power - from the wall outlet side and not the hub's microUSB connector. Wait 30 seconds, then power up again.
Finally, how many non-zwave+ switches are you polling?
If they are Z-Wave Plus, then those are good drivers to use for the devices.
I think you know this already from the other thread, but you should only be polling for the older "Z-Wave" devices and not the newer "Z-Wave Plus" versions.
Removing the reconfigured "Enbrighten"-driver devices from the polling list seems to have fixed polling again. I had done a "Stop All Polling" and start again once I removed them and they started updating correctly again. I learned that devices don't get removed from that list automatically even though they aren't using one of the drivers that app requires.
I have 19 of the non-plus dimmers and three non-plus switches.
Yes I'm aware of that. Using the non-plus driver and enabling polling was a stopgap until I had a solution, and that stopgap actually worked with these switches, as suboptimal as it was.
This new driver having double and trip-press unique triggers is useful too. I have some plans for using that in a few rooms.
Just wanted to thank you for your help. I will put the new drivers in some new UltraPro's that I am ordering for a new install location - I want to use the Double Tap feature to try to tie in a second switch, but only "on demand".
I also want to thank you for the encouragement and info on my schlage lock. I got it installed and working. I did not get it working in the Lock Code Manager App - but from reading all the other threads, I am pretty sure its because I added a code at the device itself first (within Hubitat), before I tried lock manager. I think that if I wiped out all of the codes and started over with Lock Manager, it would work. But I needed it to work, so I will try that later. I did put in multiple users from the Device (using Hubitat). THis weekend or next I will start over and see if I can get it to work. I want to be able to set up temporary codes for a dog sitter in the future
Anyway - thanks again, really enjoying Hubitat so far!
You're very welcome...glad to hear that things are progressing and your lock is up and running. My Schlage is working well w/Lock Code Manager so I'm sure yours will as well.
Happy HA-ing, and in the future you can share your growing knowledge w/another forum member.
Yep. That’s the only way it works. I have two Schlage BE469ZP and they work fine with beaming repeaters near each one (Ring Alarm Extender v2 devices).
I e just installed one of these switches (Jasco 46562) and it still added it as a dual outlet. I did switch the driver to Generic Zwave Plus driver and the switch looks to be working, but I also now have two ghost child devices. So doesn’t look like the issue is fixed.
C8 hub running latest firmware.
