I don't have one of these and just wrote that one trying to help someone else who did, but I'm curious to know more about this problem. What values are you using for color? My driver just does the same numerical mapping HomeSeer does: 0=off, 1=red, 2=green, 3=blue, 4=magenta, 5=yellow, 6=cyan, 7=white. I can add a String (versus numeric) alternate to this command so either "Hubitat"-format (color string name) or HomeSeer's raw numeric values would work, but I guess neither would if this won't, so I'm curious where the problem lies.
...if anyone wants to try helping me figure this out, since I don't have one of these devices. Between switching drivers, it might also be a good idea to switch to the plain "Device" driver and run the "Delete All States" command, then do the for-real switch (HomeSeer's driver in paricular saved some things here that ruined LED calculations for both their own and other drivers that used the same state variable name).
That's me! I'd play around more if I had one of these devices. I'd definitely recommend the "delete all states" thing above if you haven't tried it (glaring bug in HomeSeer's orignal driver if you ever used it). But I'm sure Bryan will get Hubitat's sorted out soon enough.
The codahq driver would probably work on the C-7 if you pair without S2 or S0; I'm guessing it's old enough that Hubitat didn't have the built-in Z-Wave secure encapsulation methods available for driver authors yet.
Well, I don't know what refreshed, but both of mine are now working from the Device Menu controls without error. The debug log entry has the correct color/LED number specified, and the switches are lighting up correctly.
Not yet (just installed last week, going slow and letting the mesh settle).
But others reported that their drivers were working under some circumstances, and the debug log clearly showed a bug in the command, so I assume the automated rules will work.
Still trying to decide if I will go rule machine or try and bring Webcore over.
I reverted back to the build in driver.
I used a driver titled "Clean Device" by BoristheCat. It simply clears all state values, deletes any children and clears any scheduled events.
After this I could set the LEDs from the driver but my RM rule does not work yet. I'll have to check if there may be a spelling or capitalization difference in my RM entries.
Using the built in HS-WD200 driver I found I had to modify my setStatusLed to setStatusLED. Not sure which driver I created this rule in but the custom command was wrong for the built in driver.
No not now since I upgraded to the latest hotfix (v2.2.4.148. When I attempt to set any of the statusLED lights, I get the old error of:
2020-11-27 09:12:04.061 pm errorjava.lang.NumberFormatException: For input string: "red" (setStatusLED)
I'm still posting in the other thread ( @bcopeland ). I found two things:
It appears the LED and Color are reversed in the driver. You can see that by the errors.
It appears that the Status LEDs are never enabled. They go on an off with the dim function and they increase in number when the dimmer is bright and fewer when the dimmer is dim.
And OFF when the dimmer is off.
I'm really not going to worry about it for the weekend. I think the Hubitat guys deserve a much needed break, and they should enjoy the holidays with their families.
Hi all. Sorry to spam this thread, but I started a new thread trying to get this device to work in WebCore.
(I tried to use the Switch Dashboard code to make it work, but I have a lot of device logic to process and adding all those individual rules with priority was not manageable)
I have not tried Rule Engine yet, as I was hoping to be able to port my pistons over.
If any of you have experience with these in HE Webcore, I could probably use your help...
EDIT: NEVERMIND, there was a driver bug. All working now!
I determined the issue is with security. I removed and rejoined w/o security and the built in driver can control the Status LEDs. I may have missed this concept from an earlier post.
For me this the solution. I have no need to have my fireplace wall wash lights connected with security
We’re you able to get the status lights set? I just installed my switch today and the controls on the device page don’t work for setting the status lights, assuming I’m doing it correctly.
I had to join the dimmer to the hub without security to get the LEDs to work (or more correctly be able to control them). Even without security I feel comfortable the Russians won't hack my dimmer switch
Between switching drivers, it might also be a good idea to switch to the plain "Device" driver and run the "Delete All States" command, then do the for-real switch (HomeSeer's driver in paricular saved some things here that ruined LED calculations for both their own and other drivers that used the same state variable name).
