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
I have 3,
Aeon GEN5
Hank
Aeon Bulb 6
I'm playing with the GEN5 and the LED driver. You know, cuz the past is always better, right? 
It seems the same, Not a ton of tests but after the config completed and again setting "Instant" transition, status is more of an "eventually" thing. It's not entirely consistent. But eventually, it shows. the extreme so far has been about 1 second behind the light. (I'm assuming instant means instant, and when I see any light or any lack of light out of the corner of my eye, while watching status.. that's when I begin evaluating responsiveness.)
Well, I'm ok with 1 second delay... 
What I wasn't ok with was dashboards and automations not being right because status didn't update without a manual poll or refresh.
Thanks for your work on digging into this @csteele!
The GEN 5 Bulbs won't work with the GEN 6 handlers so as long as you keep it on the handler it gets assigned when the device is joined everything should work as expected.
Thanks @krlaframboise - unfortunately, when those bulbs were joined (several firmware releases ago), they weren't properly assigned to that driver.
I'm not going to test if that's been fixed now, but I'll adjust those bulbs when I get back home. Appreciate your clarification on this though.
Speaking of I have 5 of the Aeon Gen 5s linked as AEON LED Bulb. They have got to b about the slowest responding zwave devices I have in my house. I have 4 of them across the front of my garage and when switching colors on all of them it's popcorn city with seconds of delays between each of them switching. Is this just common with this bulb? I have other zwave devices in and outside of the garage and a zwave outlet that respond instantly. multiple zwave repairs have been done since they have been out there. I just always assumed these bulbs "sucked" but just wondering if this is normal with these?
(I only got them because they were one of the only bulbs rated for outdoors when I got them)
Did you try setting them to Instant?
I sure have NOT! You had me so excited. I just changed all 4 then hit the "group" on button...still...takes about 4-8 seconds to turn all 4 on(same with manual each bulb at a time...slow). It's just so weird nothing else takes this long...including the homeseer zwave motion light which is just above and in the middle of them. Again...I thought that was the bulb. So are you saying yours respond reasonably quickly?
90% of the time it's instant, yes.
On, Off, On, Red, Daylight white, Red, Off, On, Daylight white, Off.
There was an ON that was delayed. But everything else was instant.
Do you have more than 1? So this thread made me look a bit deeper. Just turning on/off a SINGLE bulb seems relatively fast. But when I try to do them in a group (4) that's when things really slow down. Whether I create a group using the Groups/Scenes app or just a virtual switch with a rule that turns on/off all 4 bulbs. I get a 4-8 second delay turning them all on or off.
I do. I have the two Aeons on one of my Hubs and the Hank on the other, with Hub Link/Link to Hub between them.
I've never looked at Group/Scenes app.
I'd suggest opening a Live Logs tab and repeating your test. Then ask support or @bravenel to review the captured logs.
There you go!!! Turned on debug on them and flipped the switch. You can see the delays... guessing this is NOT what you see. Glad I clicked on this thread today!
Switch on at 1:39:22 and last light on at 1:39:37. 4 lights total. And the big delay at the beginning was
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:42.291 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:42.021 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:41.591 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:41.150 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:40.708 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:40.268 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:38.083 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:37.819 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[app:288](http://192.168.13.46/logs#app288)2018-11-20 01:39:37.466 pm [info](http://192.168.13.46/installedapp/configure/288)VIRT-LIGHTS: Garage Front Light 4 switch on
[dev:132](http://192.168.13.46/logs#dev132)2018-11-20 01:39:37.371 pm [debug](http://192.168.13.46/device/edit/132)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:36.951 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:36.680 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:129](http://192.168.13.46/logs#dev129)2018-11-20 01:39:36.503 pm [debug](http://192.168.13.46/device/edit/129)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:32.567 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:32.539 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:32.380 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[app:288](http://192.168.13.46/logs#app288)2018-11-20 01:39:32.347 pm [info](http://192.168.13.46/installedapp/configure/288)VIRT-LIGHTS: Garage Front Light 3 switch on
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:32.254 pm [debug](http://192.168.13.46/device/edit/131)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:32.205 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:32.048 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:32.042 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[app:288](http://192.168.13.46/logs#app288)2018-11-20 01:39:32.037 pm [info](http://192.168.13.46/installedapp/configure/288)VIRT-LIGHTS: Garage Front Light 2 switch on
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:31.899 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:31.850 pm [debug](http://192.168.13.46/device/edit/130)BasicReport(value:99)
[app:288](http://192.168.13.46/logs#app288)2018-11-20 01:39:28.627 pm [info](http://192.168.13.46/installedapp/configure/288)VIRT-LIGHTS: Garage Front Light 1 switch on
[dev:129](http://192.168.13.46/logs#dev129)2018-11-20 01:39:28.601 pm [debug](http://192.168.13.46/device/edit/129)BasicReport(value:99)
[dev:129](http://192.168.13.46/logs#dev129)2018-11-20 01:39:28.497 pm [debug](http://192.168.13.46/device/edit/129)BasicReport(value:99)
[app:642](http://192.168.13.46/logs#app642)2018-11-20 01:39:22.337 pm [info](http://192.168.13.46/installedapp/configure/642)AA-TEMP-Garage Lights is now True
[dev:132](http://192.168.13.46/logs#dev132)2018-11-20 01:39:22.272 pm [debug](http://192.168.13.46/device/edit/132)on()...
[dev:131](http://192.168.13.46/logs#dev131)2018-11-20 01:39:22.209 pm [debug](http://192.168.13.46/device/edit/131)on()...
[dev:130](http://192.168.13.46/logs#dev130)2018-11-20 01:39:22.153 pm [debug](http://192.168.13.46/device/edit/130)on()...
[dev:129](http://192.168.13.46/logs#dev129)2018-11-20 01:39:22.033 pm [debug](http://192.168.13.46/device/edit/129)on()...
[app:642](http://192.168.13.46/logs#app642)2018-11-20 01:39:21.969 pm [info](http://192.168.13.46/installedapp/configure/642)AA-TEMP-Garage Lights: AA-TEMP-Garage Lights switch on
[dev:514](http://192.168.13.46/logs#dev514)2018-11-20 01:39:21.874 pm [info](http://192.168.13.46/device/edit/514)AA-TEMP-Garage Lights was turned on@support_team I'm bringing this back up. I'm still seeing what I condsider to be significant delays for local processing. One of the reasons from switching from ST was the extra delay because of the cloud. However my delays are longer on HE and seem to all be related to zwave as my zigbee devices are fast and lights work well. Initially @bobbyD helped by seeing I had some device in secure mode (zooz motion sensors/door) but I've excluded and re-included those in insecure mode. The whole zwave network is just slow.
This is very consistent. Another example just now. Came home and a very simple rule that turns lights home when I arrive. But takes MINUTES for them to all turn on. Part of that rule is turning on a group here is the log from that:
Logs from the group:
[dev:392](http://192.168.13.46/logs#dev392)2018-12-02 09:45:52.831 pm [info](http://192.168.13.46/device/edit/392)GROUP-Christmas Lights Inside switch is on
Then logs from one of the devices:
dev:3902018-12-02 09:57:03.026 pm infoChristmas Tree - Family Room Switch is on
dev:3902018-12-02 09:56:59.097 pm infoChristmas Tree - Family Room power is 56.740 W
dev:3902018-12-02 09:46:16.243 pm infoChristmas Tree - Family Room Switch is off
Yep, that's right. It's part of the group and didn't turn on for 12 minutes after the group turned on. I'm getting very frustrated because it seems daily I'm tracking down a new problem. These are all devices and a network that was working previously on ST and MUCH MUCH faster. I know there are a few other threads out there discussing this and talking about "good night" routines that take 5-10 minutes to turn off all the lights? I've yet to see a response about what's going on?
I had, and to a lesser extent still have, similar issues but I've stopped collecting objective data - so it's just a subjective opinion that I have to offer. I have a ticket open with support but the last activity was a few months ago so I appear to have dropped off the system. I haven't complained because I just haven't had the time to pursue it.
A few months ago, I would broadly estimate that 25% of the time I'd see 1-2 minute delays in Z-Wave response. Now, it's 5%. So, I guess I'm happy(er).
Very similar to you. I'd be spending a lot of time scanning through past logs and piecing together what's going on. From what I can see there seems to be some type of backlog happening in the zwave stack. I only say that because sometimes it looks like it clears out and a flush of zwave events get sent all at once. There are definetly delays and I was hoping above to prove that out. A simple scenario of 4 devices. It's very consistent. Agreed sometimes it seems "better" and sometimes it's 12 minutes (not better). But the length of the delay and when and under what scenarios is it worst I can't tell. It seemed to get better after I removed the "secure" zwave zooz sensors and made them insecure... and everything seemed fine for a string of days. And then it's not. I've seen other threads with zwave delay issues so I'm hopeful there is a software fix in the future.
1 Like
There are lots of these around the forum.
3 Likes
I have problems with AEON RGBW-Z bulb GEN5, when I reacal a scene it dose not change dimmer level. Never. But if I dose change color.
If change dim level another way it works perfect.
I have try it using Aeon Bulb Gen6 driver and Hank RGBW LED Bulb driver, and got same resluts, no way fore a SCENE to change dim level for this bulb.
Please help
