I’m pretty new to HA. I’ve set it up and I keep editing the confirmation and everytime I restart to apply the changes, all the switches, sensors and even the thermostat lose their values. The most annoying is the thermostat (classic thermostat entity) because I have to turn it on selecting heat/cool and set the temperature. Is there a way to keep all these values across restarts?
Edit: I’m using HA OS on Proxmox. All the sensors and switches slowly goes back to “normal” as soon as they publish their state, apart from some entities that have values provided by HA itself and not by the devices (like the thermostat).
When you restart HA, keep an eye on the Summary tab for the Proxmox guest. If you’re seeing CPU or memory spikes going into the red, you might need to assign more resources to the guest. Also take a look at swap and boot disk utilization - do they seem particularly high?
Also, over what period of time to the “go back to normal”? A few minutes, half an hour, more?
Nothing like that, the resources are more than enough, no peaks. It “goes back to normal” when all the sensors/switches have sent their status and when I manually turn the heater back on and set a new setpoint for the thermostat
How network-savy are you? I’m thinking you could run tcpdump on your HA server and capture network packets while restarting HA, then inspect in Wireshark.
Most devices don’t actually “send” their status to HA directly. It’ll (usually) be HA querying their status (the exception being devices that publish via intermediate services, like MQTT). Inspecting the network packets might reveal more about what’s going on.
All the devices (sensors and switches )sends their status via MQTT; I’ve manually configured them all via yaml. The problem is in HA itself since as soon as I reload the config, the thermostat (which is a HA entity by itself), loses the setpoint and the status (heater/cool/off).
@peregus @DeltaTangoLima I am not an expert by any means, but I think there is a state “recall” somewhere that tells mqtt and or ha to keep last state
For MQTT that’s the retain flag, but for HA I don’t know what that is and I really need it!!!
The retained flag simply tells the MQTT broker to keep the last message published for that topic, so it’s always available (rather than timing out and emptying the topic).
Like I said, you should probably do a packet capture to see what’s happening when HA queries states (either from devices or MQTT - it doesn’t matter).
HA doesn’t query any state. The thermostat is within HA, it doesn’t have to query anything from anything, that’s what I’m investigating. The setpoint is set in HA and HA retains that number.
That doesn’t make sense. HA doesn’t “own” the setpoint - the physical thermostat does. All HA is doing is telling the thermostat what setpoint to use, as if you were standing in front of the thermostat yourself.
What thermostat are you using?