Climate turns itself on when network is lost

Configuration
1

I’ve noticed that sometimes when connectivity is lost, some of my entities get turned on.
The most problematic one are the “climate” entities which get unavailable and a minute later turns themselves on automatically
Here is a sample log for one of the climate entities (“Office”)

7:02:19 AM Office became unavailable
7:03:14 AM Office turned off
7:03:15 AM Office changed to Cool by service climate.turn_on

So I guess the question is why climate.turn_on is running?

2

Do you have some automations that control the climate entity? It’s probably one of those that does this, because the state changed to unavailable and then back to what it was before the restart, which may be a trigger in one of your automations.

3

I thought about this too. but I don’t see any automation running in logbook.
Plus, I don’t think I have any automation which its trigger can be triggered on that scenario

4

I’ve had similar problems caused by an automation running which often didn’t show in the logbook. I would suggest turning off your climate automations, then forcing a reconnect and see if the problem persists.

1 Like