I test HA for a while on Win 11 VirtualBox VM. I just let HA find my devices and did very little customizing. I made a few dashboards and built three automations. One automation flashes a light via my ISY when I get home. The other two play an MP# on my Sonos when my Ubiquiti doorbells are pressed.
My HA started locking up. It would be fine for a few hours and then just freeze. The console cursor would freeze and I would have to reboot the VM.
I built a new Intel NUC, installed Proxmox and then HA. I restored my HA config to this instance. Everything was fine for a few days. Now, this VM is freezing up. The only way I can get it back is to reset the VM in Proxmox.
Does anyone have similar issues or any ideas what the problem might be? Could one of my automations be causing this?
Not sure I can help you for two reasons. My Home Assistant server has never “frozen”, and I have never used ProxMox or VM’s. My Home Assistant is running native X-86 HAOS on it’s own Intel NUC.
“Freezing up” is about as nebulous a statement as possible. What do the logs show? The last few lines in config/home-assistant.log may be revealing.
Why install it so deep? just more to have to figure out if problems arise. As for troubleshooting the old adage of “keep it simple stupid” comes to mind. Or the most incredible and inspiring statements ever made by an actor James Doohan in a engineering role comes to mind. “The more they over think the plumbing the easier it is to stop up the drain”
So reboot and disable all your automatons, let it run for a couple of weeks if it doesn’t “freeze” you found the answer is your automatons is the problem. If it freezes before that, than it is VM related which points to something the VM uses (Hard drive, memory) regularly check the health of the VM.
Maybe a compatibility issue of the VM (Virtual Box) and Windows 11
Stevemann - Here’s the logs just before the last “freeze”. By freeze I mean HA ceases to work and cannot be accessed via the app or local IP. The console looks normal except the cursor stops flashing. The console will not accept any commands.
I don’t know what the custom integration “HACS” is.
2023-04-01 11:40:36.776 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-04-01 11:40:38.186 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2023-04-01 11:40:38.223 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=40 from 2023-04-01 13:47:39.427567)
2023-04-01 11:40:41.803 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry richard for rachio
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File “/usr/src/homeassistant/homeassistant/components/rachio/init.py”, line 63, in async_setup_entry
webhook_url = await async_get_or_create_registered_webhook_id_and_url(
File “/usr/src/homeassistant/homeassistant/components/rachio/webhooks.py”, line 139, in async_get_or_create_registered_webhook_id_and_url
cloudhook_url = await cloud.async_create_cloudhook(hass, webhook_id)
File “/usr/src/homeassistant/homeassistant/components/cloud/init.py”, line 186, in async_create_cloudhook
hook = await hass.data[DOMAIN].cloudhooks.async_create(webhook_id, True)
File “/usr/local/lib/python3.10/site-packages/hass_nabucasa/cloudhooks.py”, line 40, in async_create
raise ValueError(“Hook is already enabled for the cloud.”)
ValueError: Hook is already enabled for the cloud.
2023-04-01 11:40:43.291 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-01 11:40:49.240 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-01 11:40:49.354 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-01 11:40:49.615 ERROR (MainThread) [pyisy] ISY Reported an Invalid Command Received /networking/resources
2023-04-01 11:40:50.402 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 24 DF DD 1
2023-04-01 11:40:50.416 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 6 DC 1
2023-04-01 11:40:50.437 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 B E8 1
2023-04-01 11:40:50.450 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 9 2A 1
2023-04-01 11:40:50.488 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 7 B6 1
2023-04-01 11:40:50.499 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 9 E5 1
2023-04-01 11:40:50.501 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 7 F3 1
2023-04-01 11:40:50.503 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 49 6 AB 1
2023-04-01 11:40:50.506 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 4A 36 A3 1
2023-04-01 11:40:50.507 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 4E 6B DE 1
2023-04-01 11:40:50.509 ERROR (MainThread) [pyisy] ISY Could not communicate with device: 53 28 A2 1
Do not worry about HACS error that is normal for that addon. I get upon every start up of HA.
You have a database error from it not being shut down cleanly. That may need to be repaired. Which then messes up the recorder which writes to the database.
You have a issue with an entry for rachio (water irrigation), it is causing the rest of the errors. That crashes the network/internet.
So lookup how to repair the database.
Get your rachio setup correctly without errors. See: Rachio - Home Assistant
Please be advised that instructions are sometimes not correct due to being out of date. Also check the changes notices for “Breaking Issues”, there are usually instructions on how to fix/repair those because of changes to the parts of HA.
I removed the Rachio integration. HA, of course, re-discovered it, but I 'll just leave it in that state for now. I can’t think of a reason to control that with HA anyway.
I moved (if that’s the correct terminology) the database to SQL using MariaDB.
The errors you noted are now gone. I do still have some ISY errors. I can’t find anything explaining if I should worry about these or not.
2023-04-02 20:04:36.081 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-04-02 20:04:42.250 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-02 20:04:48.111 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-02 20:04:48.254 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-02 20:04:48.518 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-02 20:04:49.532 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-02 20:04:51.548 ERROR (MainThread) [pyisy] Client Response Error from ISY: 400 Expected HTTP/.
2023-04-02 20:04:51.548 ERROR (MainThread) [pyisy] Bad ISY Request: (http://192.168.10.236:80/rest/networking/resources) Failed after 5 retries.
Which talks about docker ( just another VM on Linux) and a reverse proxy issue
Then it could be other items (devices) or from Alexa so check each integration/add-on. It can be something that is misconfiguration in the config.yaml.
Did you do some cloud setup for nabucasa? That could be the issue too.
That error is showing an incomplete web or IP address. The last line that has the address, can you identify that?
As for rachio, leave controlling of it out but monitoring data collection of operation should be no problem.