Kakifrucht
commented
2 years ago The 'Glow' effect just uses the alert function the Hue bridge exposes, and I have no idea how compatible 3rd party lights are with that feature. If you have problems with it you will have to just disable the Glow effect in advanced settings, you are right that there is really nothing I can do to fix it I'm afraid. What it does it set the brightness high, then low, and back to previous setting after completing it, so if 3rd party lights have issues with that going too fast it would be a hardware limitation.
I'll leave this open for now.
This is probably not an issue with Lightbeat. It's probably more of an issue with the lights capabilities. But, I'm honestly not totally sure. (But it does seem likely since Glow works find with Hue bulbs.)
First of all, I don't know if it's gonna be an issue with ALL non Hue Zigbee lights and controllers. But it is for my CMARS and Seedan ones. But, I figured it would be good to put it here since I've talked about Non hue light compatibility in another issue.
I know Lightbeat was made specifically for Hue bulbs so Dev if you just want to close this, it's cool. :-) It would just be great to have it in the issue tracker for people to see in case they want to buy non hue bulbs.
The issue: Glow causes the Non Hue lights to seemingly go into a repetitive flashing cycle of fully turning off and back on every now and then. Then they will resume normal LightBeat behavior.
I think the Glow function IS working though.
I'm not sure why. But, I seem to remember reading something about either Refresh Rates or # of commands the Non Hue lights being able to take per second being less then Hue lights. Maybe that is the cause, maybe the lights are just getting overwhelmed and freaking out/ maybe it's some kind of error code.
It could also be that Glow makes the brightness of the lights sometimes go down below the mininium so they just shut off.
I'm not sure whats up. But again, it's probably not a LightBeat issue since Glow works fine on Hue bulbs.