HA restarted and 4:20 am and lights went on

This has happened 3 times in the past week.
HA restarted in the middle of the night (we were fast asleep) and then the lights in our bedroom went on.
I don’t know why HA restarted and why then also some lights went on.
Does anyone has an explanation and/or a suggestion on what to do ?
Thanks

Is there anything in the logs?

I am not very familiar with interpreting the log, but if Epson is the issue then I can delete the integration as I don’t use it anyway.

What is the light entity’s logbook saying? Does it say what turned the light on? If it doesn’t, then the light was turned on outside of HA. My first guess would be that you had a short power break at the time (which caused HA to reboot too) and the lights are configured to turn on after coming back from power off state.

But of course this depends on what lights you are using and what is your setup for them exactly. For example I have some lights managed by shelly and in the shelly I can configure behaviour for this. Similarly I can do this for Philips Hue (I use the Hue hub).

First of all, thanks for taking the time to guide me.
The lights are Zwave wall switches.
I noticed in the log that the Vizio and Epson were using URLs of my previous wifi router, and I deleted both integrations.

I’m not using Zwave, so I can’t help you with them specifically. But have you checked the light entity logbook to see what triggered the lights? Please do, as then you will know if it was some automation in HA doing it.

And if it’s caused by the lights themselves, and you get no further replies here, you could start a new topic specifically in the Zwave section.

Thanks for your input.
I was able to identify a specific Automation that appears to have been triggered when HA (unexpectedly) restarted in the middle of the night.
I don’t know why HA restarted and why this specific Automation was triggered. Until (if…) I find out the why, I have created a new Automation that disables the specific Automation during the night.

If you post the automation code, we can try to help.

In the meantime, you don’t necessarily need a separate automation to disable this one for the night, you could just add a condition (for example, after 8 am, before 10 pm). This will make sure even if the automation is triggered at night, it would not pass this condition and not run the actions.

1 Like

Thanks.
I have added the suggested time condition:

alias: "# MBR Fan-Light Remote ZEN32 (Z-Wave JS) ON"
description: ""
triggers:
  - type: turned_on
    device_id: 351e95c26c5lllc2aaee8e61160ec934
    entity_id: 419127b468nnn59d6c190ed4f29e3966
    domain: switch
    trigger: device
conditions:
  - condition: time
    after: "00:01:00"
    before: "10:01:00"
actions:
  - type: turn_on
    device_id: a12b6115ebc7b6hhhf71d5f9e5r79316
    entity_id: 824e5a9d59984jjj9354af806dber010
    domain: light
    brightness_pct: 40
  - type: turn_on
    device_id: f93a8a0b3dd4zzzd85e124f52bf5d6c
    entity_id: 39f1fa65ab56ebbbcb2b98dr60b3889
    domain: light
    brightness_pct: 40
  - type: turn_on
    device_id: 520d21fc5d02xxxdd9ao608ad68ce4b2
    entity_id: 7cbc910d45bdyyyeaa0cdy57a4cff529
    domain: switch
  - action: fan.turn_on
    metadata: {}
    data:
      percentage: 33
    target:
      entity_id: fan.14_21_mbr_fan
mode: single

For security I have slightly changed the entities’ id.

Alright, thank you.

Honestly, I don’t think I can really help you here. It seems weird to me that actions are called by the switch getting turned on, and that the switch gets turned on when HA restarts.

It seems to be ZEN32 Scene Controller, is that right? Have you tried using a blueprint instead? There is one for this device here:

BTW, the time condition you added will work such that the automation will only be allowed to do the actions if it is triggered between 1 minute after midnight and 10:01:00. Not sure if that’s what you wanted.

1 Like

What does the Logbook show? It’ll say what automation (if any) turned the lights on.

Thanks. I need the opposite and changed it already.
I do have the blueprint.