Continuing the discussion from Hub Update 1.1.0:
Did @mike.maxwell's driver for the Aeon RGBW Z-wave bulb make it into this release? Thanks.
Nope...
Bummer... I'll try to keep waiting patiently.. I know you folks are cranking through a ton of stuff.. 
Thanks for the effort... BTW - when released, will that driver likely work with the Aeon RGBW LED Z-wave strip? I've got three strands of those I'll be using for kick lights under new kitchen cabinets, and then one as an uplight on a ledge.
You might give the hank rgb driver a shot in the meantime.
The new “Hank RGBW LED Bulb” driver is able to successfully set colors, saturation and levels on my Aeotec LED bulb Model # ZW098-A52.
(Aeon Aeotec Z-Wave bulb)
The paired signature is:
- deviceType: 259
- zwaveSecurePairingComplete: true
- inClusters: 0x5E,0x26,0x33,0x27,0x2C,0x2B,0x70,0x59,0x85,0x72,0x86,0x7A,0x73,0x98
- outClusters: 0x5A,0x82
- deviceId: 98
- MSR: 0086-0103-0062
- firmware: 1.04
- manufacturer: 134
2 Likes
Yup, I concur with @rayzurbock - this driver does work for me. Will test it with the LED strips shortly.
Thanks.
Are you able to change color temperatures and does it remember the dim level after turning it off and then back on?
I need to do some more experimenting but it doesn't look quite right for the Aeon.. yet.
The Hank is a RGB-W bulb, while the Aeon (internally) is a RGB-W-w bulb.. it has three "rings" of LEDs. The same RGB ones as Hank's and a Daylight White "ring" plus a Soft White "ring". Only one "ring" can be active at a time.
Clearly, the RGB LEDs can mimic (poorly) the Whites, and from my early tests, that seems to be what's occurring. If I pick "Daylight White" from the dropdown, the color I see is quite obviously the RGB set (ring) of LEDs. At first, when I picked just White from the dropdown, when it came on at 100% it looked like it was from one of the two "W rings" - but at 20% it was much clearer it was also RGB.
This is one where I really hope I'm wrong, because this worked well on ST and I abandoned this bulb in order to power off my ST Hub, waiting patiently for a full featured Driver.
This is all I have as "evidence" thus far:
2018-06-28 12:08:48.503:info MasterBed RGBW Bulb colorName is Dark Violet
2018-06-28 12:08:48.498:info MasterBed RGBW Bulb RGB is [128, 0, 255]
2018-06-28 12:08:48.497:info MasterBed RGBW Bulb color is #8000ff
2018-06-28 12:08:48.492:info MasterBed RGBW Bulb saturation is 100
2018-06-28 12:08:48.490:info MasterBed RGBW Bulb hue is 75
2018-06-28 12:08:40.171:info MasterBed RGBW Bulb colorName is Light Cyan
2018-06-28 12:08:40.167:info MasterBed RGBW Bulb RGB is [207, 249, 255]
2018-06-28 12:08:40.163:info MasterBed RGBW Bulb color is #cff9ff
2018-06-28 12:08:40.156:info MasterBed RGBW Bulb saturation is 19
2018-06-28 12:08:40.154:info MasterBed RGBW Bulb hue is 52
2018-06-28 12:08:17.921:info MasterBed RGBW Bulb colorName is Dark Violet
2018-06-28 12:08:17.917:info MasterBed RGBW Bulb RGB is [128, 0, 255]
2018-06-28 12:08:17.916:info MasterBed RGBW Bulb color is #8000ff
2018-06-28 12:08:17.915:info MasterBed RGBW Bulb saturation is 100
2018-06-28 12:08:17.913:info MasterBed RGBW Bulb hue is 75
My Rules are setting the Bulb to "Purple" & 100% which seems to log as Dark Violet, and then to "White" & 20% which seems to log as Light Cyan, 19 saturation.
For all I know, the HankRGBW is also RGB-W-w, but the glance I had at the specs didn't make it clear.
As an RGB driver for the Aeon, I agree, it's great. 
Even this much will help.
I can change color temperature, but it doesn't retain color when I do. If I set my Hue to 50 (Cyan @ 100 Saturation) and I set color temp to anything the brightness of the bulb changes and the color changes to white immediately. It looks like the lower limit is 2000 and the upper level is 7000.
Yes, but I found that if you change the level and then turn the bulb off before the driver receives/refreshes the new level (shown in Current States in the driver) then when it turns back on it goes to the last state that it did actually save.
So, setLevel and call Refresh then wait a few seconds (my level in Current States changed within 10 seconds), I could then send Off and then back On and it returned to the level that I wanted.
Edit adding link to video. Order of events:
- Set Hue to 50, Cyan
- Set Hue to 80, Magenta
- Set color temp to 7000, Bulb changes to white.
- Set color temp to 2000, Bulb white softens
- Set level to 20, delays 7 seconds. Current State, level stays at 99 until refresh is clicked and 7 seconds pass
- Turn the bulb off with Current State > level at 20
- Turn the bulb on. It turns on at 20.
- Set hue back to 80 (magenta), 7 seconds pass before change.
- Set level to 100.
- Turn off, without clicking refresh. Current State > level still shows 20
- Turn on, bulb turns on dimmed at 20
- Set level to 100, bulb changes to bright
- Clicked refresh, waited 7 seconds until Current State > level showed 100
- Turned bulb off.
- Turned bulb on and it turned on bright at 100.
I think I'm swirling around a similar conclusion... my current impressions are:
- setting the Color is an RGB only action.
- setting the Color Temp will switch "rings" - 6500, 6800 and 7000 all seem to use the Daylight "ring"
Oddities in Color Temp = 10 does soft white, 100 does daylight, 400 does soft white
Given there's only two possible colors and there are plenty of specific values that selects a "ring", I'm good! - there's a noticeable delay in some commands but it's not consistent thus I'm thinking it's Hub "load" related.
I've been able to create rule(s) to control this bulb and get the result I'm wanting. It's jut lucky that what I want is covered by the driver. I save/restore but of course that's switch only, color is not saved/restored.
I use the Color for various status events, the most obvious is that Garage Door Open = purple.
I have a Rule for the GD sensor and it sets a Private Boolean in another Rule, or resets the Boolean. The 2nd Rule Captures the State (of switch - on/off), sets the Color to purple, 100%. A third rule is Triggered by Rule Truth of the 2nd Rule and turns the light on. This is related to the Capture State in that On/Off in the same Rule as Capture occurs first. I need to capture state first, set the color then turn it on. When the GD closes, I restore (the switch), then set the color back to Daylight "ring".
@mike.maxwell - I'm seeing strange behavior with the Aeon Bulb 6 multi-color DTH....
The bulb is Z-wave plus, so it should be reporting its state automatically, but, it appears that it is not - I still have to manually refresh it (or set an RM task for that). This is annoying for dashboards, but it also is manifesting itself in the Alexa behavior of 'sorry, device not responding' (even though the action does take place).
As I'm about to upgrade my two nightstand bulbs (both Z-wave not Z-wave plus) to the multi-white version of the Aeotec Bulb 6, to get better response time, I thought I'd ping you here, in case the code for those DTH's is from the same core code base. It looks like something is out of whack with the status reporting.
Thanks! 
Are you referring to manually turning the bulb on/off? If so, then when the power is cut the bulb has no way to report that it's off so there's nothing that can be done about that.
Sorry, should have been clearer - the bulb is in an 'always on' circuit... I know that the radio has to be on all the time... but, when using controls of any kind to turn it on/off (the light portion), it doesn't report state without an additional poll or refresh.
How are you turning it on/off?
The hub is the only way I have. I mean I have automations and Pico's that tell the hub to turn it on/off, but the actual commands come out of the hub. The hub knows the state. It just needs the command ack to know the command got there.
I have a Hank RGBW bulb in this room, I changed to using the Aeotec LED 6 bulb Multi-Color and status follows along. (this is just a test of the driver only. Hank might be sending status that Aeon isn't. I'll go get my Aeon into this room and test again.)
Well that's a mystery. @guywmartin is correct.
Aeon RGBW bulb using the Aeotec LED 6 bulb Multi-Color driver doesn't report status well. Switch to the Hank RGBW driver and status is reported.
Status is being reported at the end of the transition. I'd say "most" of the time, status is accurate, but due to the delay it does miss the occasional report. I've seen switch: off when the bulb is lit and switch: on when it's dark/off.
I did get a debug message that might shed a light (hehehehe)
dev:134 2018-11-19 11:41:29.236 am info MasterBed RGBW Bulb switch is on dev:134 2018-11-19 11:41:29.231 am debug BasicReport(value:35) dev:134 2018-11-19 11:41:28.966 am debug Unhandled Command: Hail() dev:134 2018-11-19 11:41:14.681 am debug on()... dev:134 2018-11-19 11:41:04.637 am info MasterBed RGBW Bulb colorName is Dark Orange dev:134 2018-11-19 11:41:04.626 am info MasterBed RGBW Bulb RGB is [255, 110, 5] dev:134 2018-11-19 11:41:04.622 am info MasterBed RGBW Bulb color is #ff6e05 dev:134 2018-11-19 11:41:04.616 am info MasterBed RGBW Bulb saturation is 98 dev:134 2018-11-19 11:41:04.615 am info MasterBed RGBW Bulb hue is 7 dev:134 2018-11-19 11:41:04.613 am debug setColor([saturation:98, hue:7, level:93])... dev:134 2018-11-19 11:40:58.432 am info MasterBed RGBW Bulb switch is off dev:134 2018-11-19 11:40:58.426 am debug BasicReport(value:0) dev:134 2018-11-19 11:40:58.177 am debug Unhandled Command: Hail() dev:134 2018-11-19 11:40:58.023 am debug off()... dev:134 2018-11-19 11:40:45.438 am warn description logging is: true dev:134 2018-11-19 11:40:45.437 am warn debug logging is: true
Unhandled hail ??
Difficult to pin down, but the Aeon bulb is reacting slower than the Hank. I set the transition time to zero (driver has an explicit selector = instant) and status leaves the bulb sooner. I don't see a difference between the drivers any more with transition at zero.
1 Like
Enable logging, open logging, toggle the switch and then post the logs
I'm not at home right now, so can't do that, but, I'll try @csteele's fix when I get back and see if that does it. Thanks everyone!
Are you using the brand new Aeon LED 6 or the old Aeon LED 5? The multi-white and multi-color drivers are meant for the GEN 6 bulbs that went on the market within the last couple of months.
Can't answer for @csteele, but I have the following bulbs (the multi-white's just arrived, so I haven't installed them yet):
The ZW098 is the GEN 5 model so you should be using the Aeon LED Bulb driver which explains why it's not reporting the status...
1 Like
