All lights and covers turned on and off around 10pm

Configuration
1

Please help on how I can figure out what's happening. I have about 60 lights and about 6 covers. Yesterday, they turned on around 9:57pm and kept going off and on for about 15 minutes till I shut down my miniPC. Today, the same thing happened again around 10pm. I've checked logs and can't find anything that points to the culprit. I'm wondering if I might be hacked or if it's something else. I'm very lost.

I use MatterHub to share my devices (lights and covers) to Alexa. I also use emulated hue to share my lights and covers to Harmony Hub in case. I'm curious if the issue might be coming from one of them but don't know how to check. Any guidance at all would be very appreciated. My wife is about to ask me to get rid of HA completely!

2

Choose one or more of the affected entities. What do the History and Activity logbook show for those entities?

If this is a new behavior, what changes have you made recently?

3

Also check if you're using any of the following in your automations & scripts. These target all homeassistant entities if you don't specify which ones should be targeted:

homeassistant.toggle
homeassistant.turn_on
homeassistant.turn_off
4

Also explain the matterhub <> emulated hue <> ha relation. Is it new? As Drew said did it change recently?

Does Amazon talk to the same emulated hue devices directly by chance?

(what your describing is something switching lights unexpectedly and another system fighting equalibrium triggering a race as they try to sync.)

5

It happened the first time 2 days ago and then happened again yday.
"Dimmer turned off triggered by action Home Assistant Core Integration: turn_off"

This was the message all the lights had on both days. I've only seen that message from the emulated hue Harmony integration so I'm leaning towards that. But not clear why that would that configuration would be causing issues. I've had it for the last 6 or so months without issues. 2 days ago, I assumed someone touched the remote and that caused it to go haywire (no logs to check on the Harmony side). However yday, noone touched the remote and it happened again. So I'm lost.

Any chance it could be something else other than the Harmony integration via emulated hue? Anything else I should check?

6

It's not new. I use Matterhub to expose some of my devices to Alexa so I can use voice control via my echos. I also use emulated hue to expose my devices to the Harmony remote so I can use the home control buttons on my Harmony Elite remotes.

I just remembered that my Matterhub wasn't actually working yesterday so it couldn't have been that. Must have been the Harmony but not clear how/why it's causing issues.

7

Then it's 100% what I told you yesterday. You have a homeassistant.turn_off action being called and the targets are either not defined, or else they're defined too broadly (like targeting an entire floor or label).

I just tried this by calling the homeassistant.turn_on & homeassistant.turn_off actions in Dev Tools & can confirm that's exactly what is reported in the Activity log.

image
image1018×191 17.7 KB

Usual suspects for this are (poorly coded/misconfigured) blueprints. Search both the automations.yaml file & the blueprints folder for any reference to an action starting with homeassistant.turn