Once you have installed this device handler on your hub:
Go to the edit page of the master dimmer you want to control. Look up the Device Network ID.
Go to the edit page of the accessory dimmer you want to control that master.
Change the driver ("Type" in the picture above) to The Generic Z-wave Association handler.
Once the screen refreshes you should see this:
Type 01 in the Number field, and the Device Network ID of master you want to control.
Click on the Associate Group button to make the association.
If you want the master to update the accessory dimmer status, do the same from the master dimmer. This should set you up with a three-way situation.
If you have a four or five-way situation, it is similar. You just have to take into account each device will have to be associated to all of the other devices in the switching group. Let me know if you need more details.
Let me know if you want more information about the other method too. It isn't that difficult either.
Hi - I tried this driver with the Eaton RF9640. It successfully fully turn off the switch which is great (so far this is the only driver that does this)...
But using this driver means that I lose the z-wave + feedbacks to the hub when the switch is pressed physically (the hub does not detect and update any physical interaction).
Have you found a solution that allows z-wave+ feedbacks to the hub?
I have 16 of the RF9640 devices. I use the Generic Z-Wave Smart Dimmer driver. They faithfully report their state. Is there something more specific you are looking for it to report?
Remember that Z-Wave devices (that do not implement scene control) do not send a report if the switch is already in the state you are manually choosing (i.e., if it is ON, manually pressing the ON button will not cause it to send an additional (Basic nor Multilevel Switch) report.
Thanks for your answer. You are correct, the reporting is working correctly...
My issue is that when the switch is turned off from this hub / driver, there is still a residual current that keeps the light on at a very dimmed level (the switch does not turn off completely even when its state is changed to off in the app). This does not happen when is turned off physically : in this case, the switch completely turn off and there no residual current going through (and the state in the app is also changed to off). For this I think this driver is not fully compatible.
The only driver I found that is capable to fully turn off the switch is the one posted by kahn-hubitat in Sep '20 (above) ; Link here. But this driver does not support the reporting of the device state...
I am looking for a solution that allow both : full OFF (no residual current) from the hub command and state reporting... Hopefully there is one somewhere...
It sounds to me like it has been configured with a minimum dimming level other than zero.
-Choose one of your particularly troublesome dimmers and change the device driver to "Basic Z-Wave Tool". Here is the link to the code if you don't have it already.
-Now get the parameter report for parameter 11. This is the minimum dimming level. Normally this should be set to zero, unless you bulbs do weird things with it set to zero.
-If it something other than zero, set parameter 11 to zero (0).
-Change the driver back to the Generic Z-Wave Smart Dimmer.
Thank you for this... You are right, parameter 11 is set to 1... But it cannot be set to zero... I tried the Basic Z-Wave tool and I can change its value to any number but when trying to change to 0, nothing happens. I verified in the doc of the switch and it says the value of parameter 11 must have value between 1 to 99 (see picture of the doc below). The minimum nber I can set is 1...
Could you verify that your switches have parameter 11 set to 0? The only thing I can think about it the firmware version of the switch... Mine has the Firmware version 1.0. Could you check yours?
No problem... Here are the answers to your question :
1- The switch is connected to 2 leds wall lights that each has a wattage of 10.1W (so total is 20.2W)
2- Here is the screen shot
I can't find anything that would dictate the peculiar operation you are experiencing.
I know some other dimmers have separate minimum dimming settings for manual vs digital actuation. This one does not have that function programmed AFAIK.
As I said earlier, I have 16 of these (over 40 Eaton RF96XX devices of all types) and none of them have exhibited this behavior. At this point I would exclude the dimmer, perform a factory rest on it, then include it again.
I know. Not the easy answer you or I were hoping for. If the issue is within the dimmer, this is likely the only way to fix it. Let me know if this helps.
BTW, the differences you see between our logs is likely due to your device being connected to your C-7 hub with S2 security. I have a C-5, so I can't connect them that way. In the end, the actuator command is the same Basic Set (20 03) in both logs. It is in the 6c01 (Supervision Command) payload on yours.
First... @wayne.pirtle : Thanks for your help digging into the switch settings and configuration... I really thought you would get it through your detailed investigation... And that I would be able to use the generic driver... It seems to be a pretty common problem (I was just looking at some Amazon review on the RF9640 dimmer...So many complains on not fully switching off...). So it is amazing that you do not have this issue... Maybe linked with being with a C-5 hub... (?)
The good news... I found a solution to make it work properly by making a very small modification of a custom device driver... I am using a modified version of the "Any Z-Wave Dimmer Driver v1.1.8" written by @jvm33 found here : Link to Driver
The modification I made to the code is just on one line... I replaced line 1102 from the original :
Forcing the "dimmingDuration" to 1sec in that command is making this driver works properly for the EATON RF9640 on my C-7 hub (correctly removing the residual current and fully / properly turning OFF the switch).
Check-out this driver... Pretty complete... Impressive work by @jvm33 (Thanks!) !!!
(PS: And yes, I tried to play with the Dimmer ramp time parameter of the switch but no chance with that as well...)
Yea!!! Hi am so glad you found a fix. I hadn’t heard of this as an issue. I am surprised I didn’t encounter it too, since I bought my devices from 7 or 8 sources (all new devices) over several months.
I still wonder if a factory reset would straighten it out.
@willshieh were you ever able to get the Eaton 9540 master and 9542 accessory to work? My home was wired up for both to control my entry way lights but the Clarehome controller died and I just recently switched to Hubitat elevation. I can control the 9540 via hubitat but controlling the 9542 via hubitat or manually with the switch does nothing. Tried reading on the forums here but all of the device drivers people provided aren't doing the trick for me.
Thanks in advance if you figured it out.
If anyone else has any pointers for a Hubitat n00b (day 2) I'd appreciate it!
Hi @bcopeland, any leads on these dedicated drivers? I'm new and have read through a few threads on it already. I tried some custom drivers but never did I see the Association field that I could enter a value for (of the Master Unit).
Any help would be appreciate for this hubitat newbie.
