tl;dr My Yeelight S1 suddenly started pulsing red (“Alarm” mode) today and I cannot figure out why.
The bulb is in our front door sconce and is controlled in HA using the Yeelight integration. It is turned on/off exclusively via a single Node Red flow (Big Timer turns it on at sunset and off at sunrise) and it’s set to a soft white color at about 50% brightness. That’s it. It is never toggled manually and no other colors are ever used. The S1 is actually overkill for this use case, but it’s what I had lying around when I decided to automate the front door sconce.
It has been working without any hiccups for months. Totally set and forget. Then suddenly today, hours before sunset, my wife was grabbing a package and asked me why the front door light was pulsing red. I opened the HA mobile app and checked the S1’s entity and sure enough, the light was sitting in “Alarm” mode (I’ve never even tried any of the Yeelight modes) and the History tab said that it had indeed responded to a light.turn_on call a few seconds before.
I can’t for the life of me think of any reason this would’ve happened. There’s only two mechanisms that can control this light: the node red flow above, and a single light card on my only dashboard. I haven’t even tinkered in HA in several weeks and I barely open the app anymore these days, as my automations are all pretty dialed in.
I checked the Yeelight app and all I see are some new message notifications (just marketing stuff) and a firmware update, which I’m not applying because I saw a thread somewhere about how they’re trying to remove LAN control, which I definitely don’t want.
Any ideas at all what would’ve caused this? I wouldn’t mind so much, except that it’s our front door light and I don’t want it pulsing bright red without me knowing. My instinct was that this was a Yeelight app issue, but I think the service call firing means something told HA to make it happen. Are there logs that would definitively ID the source of that call?
HA Blue 2021.6.5
OS 6.0
Node Red 9.1.4
Yeelight 3.3.04