I picked up a cheap (Nanoleaf) Matter bulb recently to see what they're like in comparison to my current Hue setup. The bulb behaves quite strangely. When I turn it on with an automation, the bulb turns on at a very low level half of the time, even though it displays as 100%. If I check the event log, I can see the On level control is randomly changing. I think the bulb is doing this and is not HA instructing it to change. No amount of setting the On level back to 255 seems to help. Any thoughts?
#Matter bulb randomly changing 'On level'
1 messages · Page 1 of 1 (latest)
what's the firmware version?
This is a known firmware bug in Nanoleaf devices. I've complained about it to them directly in the past.
I'd expect you to see this on the 4.1.3 firmware on thread Essentials devices (that's the current latest available, as far as I know)
The current bulb firmware should usually turn back on at the same level as it last was at before it turned off, but handling of fade-outs is incorrect and can result in it writing an incorrect low On level value before turning off. I recommend having your automations turn the bulb on with a specific brightness set whenever possible.
by spec, the bulb should never be updating the on level value on its own, that value is supposed to be purely for users to configure the bulb and should be "NULL" - represented by the value 255 in the home assistant UI - by default, which means "remember last used brightness and restore it when turning on"
nanoleaf has said (via a developer message on their discord) that they are still working on the matter/thread stuff so maybe this will get fixed at some point, but this is just one of several annoying issues their devices surrently have.
fwiw, the Aqara T2 bulbs seem to behave well; I haven't yet tried the newer Hue bulbs with Thread support (they've apparently lauched a lower-priced "Essentials" line which might be worth checking out)
I honestly didn't even think about firmware on a the bulb as the update feature is not exposed in Matter. I installed the app, updated and now the issue is fixed. Thanks all.
The issue with the onlevel is still present in the current firmware, I think, but restoring the level when turning on might be more reliable?