So long story short, Google Nest thermostat just disconnects from HA every once in a while. It used to be when I did a reboot I’d get a notification in HA telling me an integration needs setting up again, always Nest and Google Calendar.
But now it seems to disconnect and not tell me. I realise when it’s fucking freezing and my heating hasn’t kicked on (I control it with HA rather than Nest because I get better results.)
So what I’ve done is have Node Red reload the integration every 4 hours, because when I manually do this it’ll come up that the integration needs reconfiguring.
So now all I need is to be notified when the integration needs reconfiguring. A Google just brings me up threads on how to send a notification. I can do this already, I just want a notification when I get a notification…
See, the problem is that it’s called “Notifications” in HA.
First thing I thought of, but it remains “connected” in HA as in it just reads as the same temperature and has API errors when It sends commands. It’s actually disconnected but not registering as such.
I haven’t had a disconnect since I started refreshing the integration in Node Red a couple of days ago, so to be fair I don’t know if it will become “Disconnected” when it refreshes and isn’t connected.
Basically what I’m saying is this may actually be the way to do it, I just don’t know yet if it will become “Disconnected” yet
Maybe look at something like a template trigger that checks the last_updated property of the state object? If it’s older than n hours ago it’s triggered?
Nice, I’d have to see how often the temperature changes during a normal day but I could make it work. Great idea thabks