#After moving from Docker to HASS OS sensors stop updating after a while

1 messages · Page 1 of 1 (latest)

dusty ether
#

I recently migrated from Docker to a separate VM (with restoring a backup) to make updating easier. However, I've noticed that my Energy Dashboard stops updating after two days of uptime. I couldn't find any errors in the logs, and upon checking the sensors, it seems they simply stop updating. I've been running Home Assistant on Docker for over two years without any issues, but I'm currently out of ideas.

#

They start updating again after restarting Home Assistant from the UI. I'm currently running 2025.1.4 with supervisor 2024.12.3 and OS 14.2

trail oxide
#

so problem solved itself then?

dusty ether
#

Sorry, I should have been clearer. After a restart, they work for about 1–2 days, but then I need to restart again for them to update.

dusty ether
#

I gave it more memory, which it readily accepted. Home Assistant seems more responsive now. I'll update in a few days—hopefully, that was the issue, as my hass is packed with automations and sensors.

trail oxide
#

OS view is not accurate, that's just what it reserved. Not what it's actually using. 4GB seems like a lot

#

check http://homeassistant.local:8123/config/hardware for real usage

dusty ether
#

Still not working. Memory is 1.1 GB after restart

#

I just updated to 2025.2.0, curious to see if it makes a difference

trail oxide
#

is it p1 via wifi?

dusty ether
#

Yes, but it’s also my GoodWe inverter that stops updating around the same time and thats connected with Ethernet

trail oxide
#

Might be the wifi then

dusty ether
#

My inverter is connected with ethernet and they have it also

dusty ether
#

Okay so I figured out that my sensor are still updating but energy is not, these screenshots are before restart

#

This after restart:

#

Seems like they update but don’t store the history and that might be why?

trail oxide
dusty ether
#

After the restart the line became flat

trail oxide
#

the restart is at a different time

#

but still, its your watt sensor going flat. That's the input for your integral sensor

#

so your problem is whatever is giving input to the watt sensor

dusty ether
trail oxide
#

tried checking the logs of whatever integration you are using to read the sensor?

dusty ether
#

This is the only log with errors