RGBW device not responding to scenes unless manually turned on first

[AlbertStreet]

Recently started experiencing an issue where an RGBWW strip I have will not respond to any scenes, unless I manually turn on the strip in Homekit before running the scene (then it works fine). I have a separate RGB (no W) strip which is not experiencing the issue, so I suspect it may be related to the existence of the white LED and how that’s handled.

Solutions attempted:

• Pruning all MagicHome accessories from plugin
• Recreating scenes from scratch
• Power cycling LED strip and controller

I’m sure there’s more information needed, but I’m a novice at submitting big requests, so please let me know what other details I can provide.

Thanks!

[Zacknetic]

Hey, thanks for letting us know. We have been experiencing issues with scenes since the start of the project. The issue lies in the fact that some of these controllers, on a firmware level, are not programmed to respond to commands if they are "powered off" as in set to 0% brightness. We try to compensate by adding an 'on' command followed by a delay but the problem still persists intermittently which is frustrating for everyone and hard to debug.

Could you please go into the plugin's settings and set the logging level to trace> restart HomeBridge > try to reproduce the issue > and then upload the log file (please don't paste it) here? I can't promise it will be solved soon as again, this is an ongoing and known issue, but any information we get helps us greatly. Especially logs.

Thank you, -Z

[AlbertStreet]

Appreciate the reply. For what it’s worth, scenes have been working for this strip without much issue, it’s just in the last week or two that they’ve been having issues.

And my apologies, but I’m not seeing where the option to set the logging level to trace is located. Is that something I need to set in the config file?