Difficulty in Migrating to HAOS from Container Install - integrations not loading

Installation
1

I have been running home assistant on a container for a few years, but I am needing to move it off of my main server. Due to the complexity of the system I had thought that using an Intel NUC would give me a bit more headroom and keep the automations quick as compared to a raspberry pi 4.

Although I am able to get HAOS installed on the NUC, even the brand new version of the install comes with issues with integrations not loading properly. For example, the Met.no and radio browser integrations both fail to set up properly. Sample logs are below. If I try to do a partial restore then although my lovelace dashboards come across nicely, 90% of the integrations do not load properly, and it is not necessarily limited to those that require a remote connection, but also includes those that communicate on the local network. I have tried disabling the wifi and bluetooth.

Appreciate any insight into this issue.

Logs below

2023-08-22 22:15:48.831 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-08-22 22:15:48.852 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=2 from 2023-08-23 02:03:35.814032)
2023-08-22 22:15:49.787 WARNING (MainThread) [homeassistant.config_entries] Config entry '58:CE:2A:F1:8B:09' for bluetooth integration not ready yet: Bluetooth adapter None with address 58:CE:2A:F1:8B:09 not found; Retrying in background
2023-08-22 22:15:54.017 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Radio Browser' for radio_browser integration not ready yet: Could not connect to Radio Browser API; Retrying in background
2023-08-22 22:15:58.752 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:15:58.758 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Home' for met integration not ready yet: Update failed: ; Retrying in background
2023-08-22 22:16:03.771 ERROR (MainThread) [homeassistant.components.homeassistant_alerts] Error requesting homeassistant_alerts data: Cannot connect to host alerts.home-assistant.io:443 ssl:default [Try again]
2023-08-22 22:16:03.781 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:16:05.998 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.1.182 (192.168.1.182). Requested URL: '/auth/token'. (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.203)
2023-08-22 22:16:11.016 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.1.182 (192.168.1.182). Requested URL: '/api/websocket'. (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.203)
2023-08-22 22:16:19.148 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:16:44.370 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:17:29.832 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:18:55.124 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:20:20.362 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:21:45.776 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:23:11.211 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:24:36.593 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:26:01.888 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:27:27.102 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2023-08-22 22:28:52.349 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2

Your recorder database backup seems to be corrupt. You can either delete the home-assistant_v2.db file and restart HA to begin again or copy the home-assistant_v2.db file directly from your old system to your new one (while HA is stopped for both the copy and paste on both systems).

ha core stop

Copy / paste

ha core start

Did you restore the entire /config directory including the hidden .storage directory?

The other errors seem to be long lived access token related. You either have to copy these across from your old system or generate new ones and set the integrations up again.

3

So this log is actually from a new install. So I had done a restore previously, and then just wiped the drives and did a whole new install.

I do admit I did an unclean shutdown when I was rebooting it, which you can see in the logs, but otherwise it’s like there is some baked in glitch that is causing these services not to load.

I can try copying over the config directory. What is the best way to transfer these files to HAOS when HA is stopped? I had been using the SSH add on and using SFTP, but that only works if HA is running. I’m unfortunately not exactly a linux guru.

4

The SSH addon will keep running even if home assistant is stopped. You could use WinSCP.

5

Any insight as to me getting the clientconnectorerror for metno weather integration?

6

Alright so I actually figured this out, and it is actually a bit obscure but I am putting it out there in case it may help someone else in the future.

So in order to put the OS on the NUC, because there is unfortunately no installer yet, I decided to use the method of running a trial of Ubuntu off a usb stick and then using balena etcher to flash the OS image onto the disk.

So if you’ve done this then you know you have to run some commands in terminal in order to get Balena installed along with the propery dependencies. So I used a guide to do this and it seemed to do it properly, though I thought it was a little weird that etcher automatically exited when the flashing was complete.

But hey, take out the ubuntu boot media and haos starts normally, but weird errors with the integrations.

Finally went back and used a different guide with only slightly different commands in order to do this, and this time etcher didn’t automatically exit. Now boots into haos and all integrations working perfectly. Restore works perfectly.

So yeah apparently you can have the flash process fail in a way that will allow you to boot into haos, but will leave congenital defects that are hard to identify.

Anyway thanks for the help!