SmartThings fixed the bug that was preventing users from saving the drop down settings, but enabled/disabled settings with a default value are still broken.
You can fix this by changing one line of code, but I’ve written tons of DTHs so I’m waiting to see if they’re going to fix it.
Is Zooz still officially going to be making this product? I see it in stock in Amazon, but Zooz doesn’t list it on their (sales ) website.
I’m assuming this device will be lower down the priority list, but is this device planned to be added to an Edge driver at some point?
Since the product is still being sold I might write a driver for it, but it’s at the bottom of the list.
Hi Kevin,
First, Thank you so much for all the work you do.
Ideally, I would like to only use the parent device handler with my RGBW lights. The only issue I’m having is when I set the color to #FFFFFF, the color is off. Is it possible to modify your device handler so when the color is set to #FFFFFF, the white channel is on 100% and the other channels turn off completely?
Above is the typical setting I will use (just the warm white lights on), so this is most important to us.
If you could provide some input on how I might make this change on my handler, that would be awesome. Thanks again.
Changing the handler shouldn’t be necessary because the handler should create a child device for the white channel which you can use to turn white on/off and change its brightness.
I have an odd question about this DTH/ Smartapp. Will it continue to function properly once smartthings moves to full “edge” drivers? I don’t understand a ton about the subject so any enlightenment would be very much appreciated-- (this question may be way off base because of my lack of understanding of the subject)
All DTHs written in groovy, stock or custom, will stop working once the transition is complete. Only Edge Drivers (written in Lua) will work on the new platform.
Fortunately There is a community-created Edge Driver now in beta that supports this device. (The Zen31 is actually a rebadged Fibaro unit.)
(EDGE Driver-Mc): Z-Wave Edge Drivers and others with FIBARO devices:
Also, this community FAQ might help. It also includes links to several official announcements on Edge:
FAQ: I have no idea what Edge is. Is that a new developer tool? (2022)
Ok, now I follow. Oh my, so much is going to go to crap at some point That’s sad.
I thought something was fishy about this, I hadn’t put my finger on it yet but things were merging in my mind.
Thank you for this @JDRoberts , very helpful
Also, thank you for introducing me to @TAustin. He is helping me get that rgb addressable sign (running through the falcon pi player API) working within smartthings utilizing his EDGE web requestor driver
I’m having a strange issue. I have 3 Zen31 setup and working fine in ST. I purchased another to setup on the patio. Settings are set exactly the same as my other working Zen31 devices, but the new device I can’t change the color in the main device control. (I currently have main device, and white child on) I can control the colors using ST routines or through GA (google assistant), but changing the color in the main device through ST, looks as if it takes, but if I swipe down on the screen, it reverts the color back to what it was previously. I’ve been in contact with Zooz (SmartestHouse) to get a replacement because I thought the unit was bad. They sent a replacement and it’s doing the same exact thing. Bench tested with a different light strip and power supply just to make sure I wasn’t entirely crazy. Any thoughts? Suggestions to check? Thanks for any help and of course the awesome code!
I might be able to troubleshoot it if you open Live Logging from the IDE, attempt to change the color of the new device through the mobile app, wait a couple of minutes, change the color of an old device through the mobile app, wait about a minute, and post the live logging results.
That being said, this DTH will stop working once SmartThings retires the Groovy platform and it sounds like there might already be a functional driver for this device. The info is a few posts above…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:17:40 PM: debug power is 0W
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:17:32 PM: debug colorSwitch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:17:31 PM: debug switch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:17:31 PM: debug blueSwitch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:17:31 PM: debug greenSwitch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:17:31 PM: debug off()…
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:27 PM: debug colorSwitch is off
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:27 PM: debug switch is off
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:26 PM: debug blueSwitch is off
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:26 PM: debug redSwitch is off
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:26 PM: debug off()…
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:20 PM: debug power is 4.8W
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:16 PM: error groovy.lang.MissingMethodException: No signature of method: static java.lang.Math.round() is applicable for argument types: (null) values: [null]
Possible solutions: round(float), round(double), find(), rint(double), find(groovy.lang.Closure), random() @line 1981 (huesatToRGB)
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:16 PM: debug setColor([hue:68.53])…
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:11 PM: debug switch is on
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:11 PM: debug colorSwitch is on
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:11 PM: debug blueSwitch is on
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:10 PM: debug redSwitch is on
b4f00513-5adb-4c90-83c2-1a340056b42f 6:17:10 PM: debug on()…
4f43644f-07ca-40f7-a0aa-8c4428c1b3a4 6:16:21 PM: debug 'zw device: 2C, command: 8201, payload: ’ parsed to [name:hail, value:hail, descriptionText:Switch button was pressed, displayed:false, linkText:OS Front Porch Lights, isStateChange:false]
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:16:20 PM: debug power is 12.5W
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:16:19 PM: error groovy.lang.MissingMethodException: No signature of method: static java.lang.Math.round() is applicable for argument types: (null) values: [null]
Possible solutions: round(float), round(double), find(), rint(double), find(groovy.lang.Closure), random() @line 1981 (huesatToRGB)
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:16:19 PM: debug setColor([hue:67.88])…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:16:11 PM: debug switch is on
3be68307-6233-4d30-8e4d-54b709bd5bcb 6:15:43 PM: trace Harmony - Sending data to Living Room Harmony
6:15:22 PM: info Waiting on events…
Red is new device that ISN’T working properly.
Blue is an old device that IS working properly.
I did look at some of the Edge drivers in this thread above, however, I’m not 100% sure how to include these drivers and attach them to the devices. Also, not super clear on which driver is for the Zen31. I did get as far as ‘Enrolling’ in Mariano Shared Beta Driver link. I a few drivers that I thought might affect some of my current devices. That’s as far as I got. I believe the “Z-Wave Bulb Mc” I installed is supposed to work for the Zen31.
Appreciate any help you can give!
Both of the devices are logging errors so that shouldn’t be working for either of them.
Can you send the logs after changing the color of the new device using an automation?
Both of the color changes below are from two different automations.
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug redSwitch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug redSwitch is on
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug saturation is 100
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug hue is 34
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug color is #00FF0A
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug blueLevel is 4%
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug greenLevel is 100%
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug redSwitch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug redLevel is 0%
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:10 PM: debug setColor([saturation:100, hue:34.12698745727539])…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:09 PM: debug setLevel(100, 3)…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:57:09 PM: debug on()…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:55 PM: debug power is 9.2W
4f43644f-07ca-40f7-a0aa-8c4428c1b3a4 6:56:53 PM: debug 'zw device: 2C, command: 8201, payload: ’ parsed to [name:hail, value:hail, descriptionText:Switch button was pressed, displayed:false, linkText:OS Front Porch Lights, isStateChange:false]
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:50 PM: debug redSwitch is on
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug redSwitch is off
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug saturation is 97
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug hue is 68
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug color is #1B07FF
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug blueLevel is 100%
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug greenLevel is 3%
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug redSwitch is on
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug redLevel is 11%
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug setColor([saturation:96.8253936767578, hue:68.3060073852539])…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug setLevel(100, 3)…
02caf9f4-fdfa-4bd6-9e6d-0dd21cd15f23 6:56:49 PM: debug on()…
6:56:41 PM: info Waiting on events…
Check both a working and a nonworking device to see if they are using the same DTH or if either of them is using an edge Driver.
It has happened when somebody says “I had three working just fine, I added a fourth one, now it just won’t work “is that the three are using a previous DTH, and there is now an edge Driver including that fingerprint and the person has subscribe to that channel (even if it was for a different device) and now whenever you add a device of that model, it’s picking up the edge Driver. Which might have a glitch.
I’m not saying for sure that’s what’s happening here, but it’s the next thing to check. 
@krlaframboise Some of the recent updates to the Android app have changed how the colorControl capability works. The color controls in the app now generate two separate setHue and setSaturation commands instead of the previous setColor command with Hue and Saturation as arguments. Routines remain unchanged though, so what @groundzero2010 is seeing matches what I’ve seen in other drivers/DTHs.
Thanks, I noticed the same thing and I think I’ve fixed the issue so I’m sending @groundzero2010 a new version to test.
I do believe you have me fixed up! I’ll test a bit more this afternoon/evening and make sure everything works properly.
