Another thing I noticed was that including the bulb in a group, sending ON to the group turned the bulb on at 100% intensity. All other dimmers just restored their previous setting (even Ikea Tradfri ).
Ok - it may simply be that it’s not allowed by the device. The device doesn’t provide this function, so I’ve tried to support it though the binding - this works with the Zipato bulb as I’ve tested it but I’ve not tried it with the Aeon (although I do have one here, but I’ve not tried it).
Let’s see what the log shows…
It’s not a device parameter - it’s a configuration option in the channel.
If it works even once, then the setting is probably ok. If it only doesn’t restore the last value when using within a group, then it’s possible it’s something else causing the issue - I would take a look at exactly what command is being received by the binding.
This is the answer I got from Aeotec regarding the white level settings of the high-intensity non-RGB part of this bulb.
There are only 2 white level settings, Cold White and Warm White, which can also be changed within the color command class settings for Color Set command. The option is limited if you are not planning to use RGB to create a warmer white color in this case. The RGB color mixtures are possibly the only way to achieve a much warmer LED light.
These 2 white level settings are not controllable by OH2 at the moment, but what they call warm-white is far from it. Nothing warm about it, and going for RGB will yield a lot less intensity. It is not possible to mix RGB in with the white.
The way OH2 works is to control the two whites - scaling between the two of them. So, if you want cold white, then cold is 100% and warm is 0%. Something in between might be 50% each, and warm would set the warm LED to 100% and the cold to 0%.
This works with the Zipato bulb but I’ve not tried it on the Aeon but I think they may allow only 1 white LED on at once. I do have an Aeon bulb so will try and find some time to test it over the next week.