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).
You must log in or register to comment.
That’s strange, it usually does keep that, because the values are coming from the devices themselves. Like a switch is either on or off as soon as HA reconnects, it requests the state of the switch. Same for thermostats, at least in my case, because mine are connected via the router via DECT. It may helps to provide some more details on your installation (Docker, HASS OS, …) and devices
I’ve edited the post with some other information. About your configuration, how does HA ask for the state? This mean that your HA loses all the values too, but it repopulates them automatically. What about the entities that provides values FROM HA itself? For example the setpoint of the thermostat?
During restart all entities are in state unavailable. When the integrations are loaded all the entities with their current states become available again, but that’s something of seconds. The internal entities, like Helpers, are immediately available - that’s the closest to “value from HA itself” I have in my setup
The internal entities, like Helpers, are immediately available
This is my problem:in my main HA instancd the internal entities are in state “unknown” when I reload the configuration. In another instance of HA everything works fine and the thermostat goes back to their previous state when I reload the configuration, in the “main” instance they don’t :(
If you set up your HASS with docker, make sure that PATH_TO_YOUR_CONFIG is appropriately replaced with desired location.
I used to have kinda same problem, then I noticed that there was a suspicious directory named /PATH_TO_YOUR_CONFIG lol
Are you using Docker? Forgive me if you know and understand docker - I’m just checking to make sure, but if you’re using Docker are you sure you set up your volumes correctly? Docker is stateless, so on any restart it would lose all of your info and be a clean install if you did not set up your volumes correctly
Something’s wrong with your configuration. What hardware, OS and HA config are you running?
My HA install does not lose anything when restarted. All my wifi, Z-wave & Zigbee devices, various entities and thermostat come back in the same state as prior to restart. I’ve run HA Supervised on two HW platforms and 3 distros and they’ve all functioned this way.
I’m using HA OS on Proxmox. About the configuration, what do you need to know? Do you wanna see it all? All the sensors and switches slowly goes back to “normal” as soon as they publish their state.
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?
