It gave an error in the ON/OFF function. As you told me it was pulled from github I didn't think it was worth troubleshooting. So I went to the built-in driver.
Ah. Yeah, the built in doesn't seem to work on the Leds at all.
I haven't looked at custom device handlers yet on this system. But probably something I'll take a gander at while I'm waiting for my mesh to settle.
@ArchStanton... when I ran v2.2.3, I was able to set/change the status LED from the Device page but now after upgrading to v2.2.4, I get the error below when I attempt to set the status LED using the built-in driver via the Device page. Is this a bug in the latest driver or am I missing something?
I've already notified Hubitat of the issue. bcopeland said he was on it so I'm confident it will get resolved shortly.
Huh. I actually got the same error with one of my simple lighting motion automation (using the stock automation app).
Might be that the new firmware has a bug defining some enums?
I used this and got them working
Hey, thanks for that! Looks like a well-written version of an ugly Webcore piston I have for ST!
But is it working on the 2.2.4 firmware? The notes said it uses the built-in driver, but that's apparently what's causing problems right now. (I could be wrong, I haven't set up a custom app like that yet)
I just updated the firmware prior to installing this. Working as expected so far.
edit:
C-7 on 2.2.4.145
Homeseer HS-WD200+ with the HS-WD200+ built-in driver
Using the Switch Dashboard app and child app from the link by MFornander- I haven't altered them. I actually haven't even looked into the code yet but they are working as expected.
I have what I think is a related issue. I have quite a few of these dimmers. I have a C7 hub and originally added them all w/o S2 as that didn’t work until 2.2.4 came out. Most of the switches are firmware 5.11. I can’t get double or triple tap to register. Nothing shows up in logs, nothing in events tab and nothing when a rule is defined. I’ve tried the following things (it’s pretty central to my set up to get this working)
Update to withdrawn driver (I found it on GitHub)
Switch back to build in driver
Upgrade firmware on switch to latest 5.14 (this was an epic pain, buy software from Homeseer, find a windows machine in my junk closet, set it up and flash them, but I did it)
Readied the switch with s2, tried both drivers again
Removed a switch from my network, added it to openHAB, verified that it sees all tap events right away.
Readied with S2
Try the new driver by @bertabcd1234 (this just this morning)
I swear that one of my switches did double tap at one point, but at this point none of my 2 and 3 tap rules are working. I noticed this morning that led color setting is not working either (which I think is mentioned here that @bcopeland is working on?)
It also seems like I don’t see events for on / off without hitting the device refresh button, but that may be normal and just an artifact of my staring at it too hard. I’m happy to help debug
This is fixed in the next hotfix build
1 Like
Just checking... I updated to 2.2.4.147 and it did not fix the issue. No problem, just checking in in case you were expecting it to be fixed with that update.
This update did ultimately fix both of my problems
- I can now set led colors as before with the HE driver, the withdrawn one and the new one
- I now see push 1&2 and double tap 1&2 with the HE driver. I see all the various push events I expect (double, triple and quad tap) with @bertabcd1234 driver.
It seemed like it did not work at first, but I rebooted and hit configure on the devices and that seems to have done the magic for me.
Thank you for these fixes, this round of “Rob automates the house” all kicked off with me trying to expand the double tap to start the kiddos nap playlist and turn on the white noise to accommodate a 3 tap for kid number 2 during my paternity leave. He’s 10 months today, but I’ve finally done the thing I’ve set out to do. On the way, I’ve swapped from smart things to hubitat, re-layed out my whole zwave network and added about 15 devices and automations.
Huh. I've rebooted 2x and hit configure, but I still see the same error when using the control on the device screen:
errorjava.lang.NumberFormatException: For input string: "magenta" (setStatusLED)
dev:182020-11-25 11:00:16.629 pm debugled:magenta color:5 blink:on
dev:182020-11-25 10:59:56.410 pm
[2.2.4.147] Still see error.
I've rebooted and configured multiple times.
When I attempt to set an LED via the device page I receive:
Like @rgkaufman I had to reboot and click Configure in the Device page. Once I did, I can successfully change the statusLED from the Device page but am unable to set the statusLED via a Rule. I tried with string "2,1,1" and "2,Red,1". @bcopeland Is the string format correct?
Ah, I see. With the HE driver I do see what you are describing. Both the codahq driver and the bertabcd1234 driver use a number and not a string for that value. The codahq driver does the status leds right at the moment, the bertabcd1234 driver appears to turn the whole thing white no matter what you put in or which led you target. All of them do the buttons now in my testing. That makes the codahq driver the complete one at the moment. I know you can get a copy of it from GitHub (that’s where I got it) but it’s not clear to me what the etiquette is for someone taking over maintenance or linking directly to a copy.
@rgkaufman... My selections are slightly different than yours (I'm using the HomeSeer WD-200 Dimmer driver from HE).
When I was running v2.2.3, my options where like yours but now in v2.2.4 it appears it only shows the colors without numbers but not sure if that has anything to do with the problem. I tried both in my rule and both failed (as you can see from the log in my previous post)
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).
I tried what I think is the driver you modified:
It did not throw an error but the LEDs did not change.
What's interesting is, I have a version by codahq that worked fine in C4 but when I switched to C7 this driver could no longer control the LEDs.
Also note, I could not change the LEDs using mike.maxwell Super basic Z-Wave driver.
So I'm just going to wait for bcopeland to sort it out.
