This one JUST happened. Went into upstairs bathroom. I looked up at the light it was barely on. I thought that's odd. It's not sunset so the mode can't be evening. So pulled up my phone with and looked at DH page. Saw this in the logs:
The ONLY other two rules that control this light are both mode dependent for NIGHT mode. (My night lights) One rule turns them on and now one rule turns them off. Both have in conditions that mode must be night. So that couldn't have effected this and that reflects with nothing showing in the logs.
The only other thing I can think is this light is added to Google for the Google Assistant. IF that's causing it would I see a log. I know no one sent a command to turn the upstairs bathroom light to 1. but at least it's possible that's where it's coming from???
Lol that’s one way round it. Unfortunately I still get the problem on Hue lighstrips and hue floodlight and if anything it’s worse now with the latest firmware and hot fixes. To replace 4 lighstrips with 6 extensions on each is going to be damn expensive. I also do find that when the Hue strips work they come on much quicker than local LIFX controlled bulbs
Necro'ing this thread rather than post a new one in the hopes that the original poster has some ideas. I too am having a single hue bulb come on at 1%. I have no rule that has it at that level. I've reset the Hue bridge, removing any previous rules that I had set through Hue Labs. I am using the awesome CoCoHue drivers from @bertabcd1234, although I had previously been using the standard ones and was experiencing the same problem.
Any recommendations? Is there any way to find out where the command to set the level to 1% is coming from? I did write a quick rule to set the bulb to a higher level if it ever went to 1%, but that only worked about 75% of the time.
