@tobycth3. Here is that thread.
1 Like
Is it possible to change the LED color based on a trigger using SmartLights App?
I installed @jbisson DTH, but no luck figuring it out.
@Scott_Barton this should be possible. However, It doesn’t work for me either. The event passed in to the device handler does not contains the actual color value. Here’s what I’m getting in the setColor event map:
[switch:on, hue:25, saturation:100, level:80]. Notice there is no color in there. Based on this documentation, it should: http://docs.smartthings.com/en/latest/capabilities-reference.html
Seems like a SmartLight app bug or a ST hub bug at this point. Someone from smartthing could maybe comment on this one on why the color attribute is not being passed in.
Also, you might want to update my code, I’ve added a bunch of useful stuff in the parameters section.
I believe that is the color. What you’re looking for and not finding is the “hex” key in that map, but the Hue/Saturation/Level defines the color; H25/S100/L80 should be in the neighborhood of #CCFF99.
The documentation is unclear, especially, around which attributes should be there and which one are optionals. Based on the documentation http://docs.smartthings.com/en/latest/capabilities-reference.html#color-control we should have 3 attributes: hue, saturation and color. Color Options should have: hue,saturation, hex, level, switch.
That being said, is there any helper function to contruct an RGB color value based on hue/saturation/level?
The color attribute is a map with the potential keys hue, saturation, hex, level, switch, which is consistent with the event map you are getting, except that it does not contain a k-v for “hex”. From context I am assuming that the k-v “level” is the “color” level component of a HSL tuple since there’s no reason to have a switch level value in a color map.
You may get some mileage from the pseudocode at this site with the caveat that ST gives you Hue as a percent value (0-100) not in degrees (0-359).
@Scott_Barton I’ve uploaded a new version which addressed the bug.
seems to be working now. I’ve used colorUtil.hslToHex which seems to have worked quite well. However, I couln’d find any documentation around it, hidden util class?
I’m using the Aeon Smart Switch, not the Smart Dimmer. This DTH seems to act as if it is a dimmer, not an on/off switch. On all my other on/off switches, when I turn it on, it immediately turns it on and changes the value to On. On my dimmers when I turn it on, it says Turning On first, takes a while to actually turn on and then after it is to the correct level it changes the value to On,
Your DTH for the Aeon Smart Switch says Turning On and takes a while for it to actually turn on. Sometimes it doesn’t actually turn on or off and then it gets confused as to what state it actually is. I experienced similar behavior when I first added the Smart Switch (before installing your DTH) and it came up with Z-Wave Metering Dimmer. When I switched it to Z-Wave Metering Switch, it fixed all the issues.
Can you update this DTH to act as an On/Off switch only. I see there is also a level settings which does nothing for the Aeon Smart Switch.
Smart Switch - http://aeotec.com/z-wave-plug-in-switch
Smart Dimmer - http://aeotec.com/z-wave-plug-in-dimmer
Look the same but are different.
Thanks!
This device handler works for the Smart Switch (I don’t have any Smart Dimmer to try it).
Do you have the smart switch or the smart dimmer? I’m a bit confused as you said that you switched to z-wave metering switch and it fixed your issue.
As for the level, it acts as the brightness and only works in energy mode. You can click on the energy icon to flip to energy mode. The level should now starting to work.
I have the SmartSwitch. However the DTH acts as if it is a dimmer.
Instead of turning on immediately when you use the ST app, it says turning on and then can take several seconds to turn on and sometimes it doesn’t actually turn on.
That’s the expected behavior. There is a delay between you press the button and the switch turn off. That delay should be pretty quick (1-2secs). However, this should always work.Everytime you press on the button, it sends a request in the cloud to smartthing, come back at the hub and send a z-wave to the switch. There is not much we can do about it at this point. Seems like a bad internet connection or z-wave interference.
You could try to load a difference device handler but I really dough it will change anything.
Why do you say it act as a dimmer?
I have the same problem as @Scott_Barton.
I configured the switch using your device handler which I need to get timely updates on the energy usage.
But actually turning the unit on or off does not work that well. Switching the device to zwave metering switch causes the on and off to work almost instantly.
Thanks!!!
@jbisson - I am having the same issue (they do not respond) with two units that were misbehaving using the device handler suggested by Aeon and therefore I was trying out your DTH.
This is the error messaage I see over an over in my logs:
4:27:21 PM: error groovy.lang.MissingMethodException: No signature of method: script1478206571997672127907.zwaveEvent() is applicable for argument types: (physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation) values: [SecurityMessageEncapsulation(commandByte: [33, 100, 0, 0, 0, 6, 0, 68, 0, 0, 0, 6, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)]
Possible solutions: zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicReport), zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicSet), zwaveEvent(physicalgraph.zwave.commands.configurationv1.ConfigurationReport), zwaveEvent(physicalgraph.zwave.commands.firmwareupdatemdv2.FirmwareMdReport), zwaveEvent(physicalgraph.zwave.commands.hailv1.Hail), zwaveEvent(physicalgraph.zwave.commands.manufacturerspecificv2.DeviceSpecificReport) @ line 197
Any idea what is causing the issue? I just can’t seem to find a DTH for the SS6 that will not mess up my zwave network.
Also, I noticed that the fingerprint seems incorrect for the SS6 I have…
The DTH has:
// Base on New Z-Wave Fingerprint Format
fingerprint mfr: “134”, prod: “259”, model: “96”
fingerprint type: “1001”, cc: “26,32”
But when I look at what the device reports I see:
zw:Ls type:1001 mfr:0086 prod:0103 model:0060 ver:1.03 zwv:4.05 lib:03 cc:5E,86,72,98 ccOut:5A,82 sec:25,26,33,70,27,32,81,85,59,7A,73 role:05 ff:8700 ui:8700
Therefore I believe 3 values should be changed to… mfr: “0086”, prod: “0103”, model: “0060” (initial zeros can be omitted) if you have the AEON branded version of this switch.
The data above is confirmed in part here:
http://products.z-wavealliance.org/products/1312
…and here:
0x0134 is the MFG ID for AT&T so you may have used a rebranded version for your development… I believe you can add the data I provided along with the data you used to make it work for both variants.
// Base on New Z-Wave Fingerprint Format
fingerprint mfr: “134”, prod: “259”, model: “96” //AT&T rebrand
fingerprint mfr: “86”, prod: “103”, model: “60” //Aeon brand
fingerprint type: “1001”, cc: “26,32”
Also I noticed something weird regarding class “32”. It is the METER class so it should be there but my devices are not reporting it (however they are also not working properly at the moment). The silly ST hub v2 insists on recognizing them as Aeon LED Bulbs… which I believe is also when I started having nightmares with my two SS6 devices.
I had one switch working yesterday and another refusing to respond. Then later I noticed the off command I had sent much earlier got issued because the switch was off when it should have been on. So I tested again and it’s working again. Typical ST phantom issues.
I edited the fingerprint to have ST v2 recognize the Aeon Smart Switch 6 both in regular inclusion and secure inclusion. The fingerprint code below seems to work however the DTH works correctly only if you do the insecure join. When joining secure, the DTH fails to control the on/off switch… maybe it is not implemented correctly in the DTH’s code. Can anyone check?
fingerprint mfr: “86”, prod: “103”, model: “60”
fingerprint type: “1001”, cc: “25, 26, 32”
fingerprint cc: “5E,86,72,98”, sec: “25,70,27,32,81,85,59,7A,73”, secOut:“5A,82”
@jbisson I get this error in Live Log using your DH.
groovy.lang.MissingMethodException: No signature of method: script1478191482637672127907.zwaveEvent() is applicable for argument types: (physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation) values: [SecurityMessageEncapsulation(commandByte: [], commandClassIdentifier: 90, commandIdentifier: 1, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)]
Possible solutions: zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicReport), zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicSet), zwaveEvent(physicalgraph.zwave.commands.configurationv1.ConfigurationReport), zwaveEvent(physicalgraph.zwave.commands.firmwareupdatemdv2.FirmwareMdReport), zwaveEvent(physicalgraph.zwave.commands.hailv1.Hail), zwaveEvent(physicalgraph.zwave.commands.manufacturerspecificv2.DeviceSpecificReport) @ line 197
@jbisson @simonselmer - Once I modified the fingerprint I was able to include the SS6 both in secure and non secure modes without having to tell it which DTH to use. However, in secure mode the SS6 no longer responds to any command and I am guessing that there is some issue with the DTH handling the secure messages. If I include the SS6 in insecure mode, then all works perfectly.
I had the same problem, with a new SS6. I added it in secure mode and it wouldn’t respond. Finally I tried just a single press when adding it, and now it works.
Even though I can from time to time find the SS6 a bit unstable.
@aruffell @simonselmer You are totally right about the fingerprint issue, I actually had the fix locally and didn’t check it in 
As far as the secure inclusion mode, it needed some significant tweak here and there, which I hope I fixed.
I don’t really want to hi-jack this thread, so I decided to start my own here:
let me know if you guys have issues with the latest one.
1 Like
@jbisson
When I try to add either of the aeon smart meters code using git integration I get the error:
Updated 0 devices and created 0 new devices, 0 published ( 1 skipped due to errors)
I am able to add the flic button from the same github repository, but not either of the aeon buttons.
Does anyone know what i am doing wrong?
