HA in docker: hassio & raspberry-pi: invalid config

Configuration
1

Dear community,

a couple of days ago, I moved my HA-config-files from a raspberry pi to a docker container. I was surprised, how easily that was and that everything was working more or less at first try.

I do have two error messages, which cause is obvious, but I don’t know, how to get rid of them:

2023-01-06 23:41:24.302 ERROR (MainThread) [homeassistant.components.hassio] Missing SUPERVISOR environment variable
2023-01-06 23:41:24.304 ERROR (MainThread) [homeassistant.setup] Setup failed for hassio: Integration failed to initialize.
2023-01-06 23:41:26.725 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of raspberry_pi. Setup failed for dependencies: hassio
2023-01-06 23:41:26.725 ERROR (MainThread) [homeassistant.setup] Setup failed for raspberry_pi: (DependencyError(...), 'Could not setup dependencies: hassio')

I have deleted the raspberry pi integration, but the error seems to stay. Is there some configuration or code that I have to delete? Where?

Any help is very much appreciated.

2

Hi, anybody could help?

3

There are two other discussions about the same question. Both indicate a solution, without going into specific details.

I will try that and see, if I can provide some more details.

4

Container version doesn’t have supervisor so the hassio integration won’t load. Remove it.

5

Hi @petro,

thank you for your input. I have deleted the “integration” regarding raspberry (and hassio?), but the error keeps coming up. There must be something deeper down in the system.

grafik
grafik1920×879 109 KB

The other two discussions implied to search through /config/.storage folder. I wanted to do a quick backup, before doing that. Or have you got a better idea?

6

Shouldn’t be anything else. Just restart your system and the rrrors should be gone

7

The errors are still there. I did a quick search through all files in the storage-folder. Is one of those entries responsible for the two errors?

Suche "hassio|rpi|rasp" (48 Treffer in 4 Dateien von 33 gesucht)
  C:\Users\schneich\Documents\Docker\HomeAssistant\config\storage\core.config_entries (3 Treffer)
	line  58:         "source": "hassio",
	line 377:         "domain": "raspberry_pi",
	line 378:         "title": "Raspberry Pi",
  C:\Users\schneich\Documents\Docker\HomeAssistant\config\storage\core.device_registry (9 Treffer)
	line 615:             "hassio",
	line 627:             "hassio",
	line 639:             "hassio",
	line 651:             "hassio",
	line 663:             "hassio",
	line 675:             "hassio",
	line 687:             "hassio",
	line 699:             "hassio",
	line 711:             "hassio",
  C:\Users\schneich\Documents\Docker\HomeAssistant\config\storage\hacs.repositories (34 Treffer)
	line  2033:         "name": "RPi Monitor Card",
	line  2034:         "filename": "rpi-monitor-card.js"
	line  2037:       "description": "A Raspberry Pi status display Card for Home Assistant Lovelace",
	line  2041:       "full_name": "ironsheep/lovelace-rpi-monitor-card",
	line  2047:         "raspberry-pi"
	line  6232:       "full_name": "And3rsL/VisonicAlarm-for-Hassio",
	line  6342:       "full_name": "Antoni-Czaplicki/vulcan-for-hassio",
	line  7872:       "description": "hassio support for Airthings Wave BLE environmental radon sensor.",
	line  9914:       "full_name": "GuilleGF/hassio-ovh",
	line 13376:         "hassio-integration",
	line 13611:         "raspberry-pi",
	line 15894:         "raspberry-pi",
	line 17896:         "hassio-integration",
	line 19659:         "name": "Raspberry Pi GPIO",
	line 19666:       "description": "Home Assistant Raspberry Pi GPIO Integration",
	line 19667:       "domain": "rpi_gpio",
	line 19669:       "full_name": "thecode/ha-rpi_gpio",
	line 19674:         "raspberry-pi",
	line 19675:         "rpi-gpio"
	line 20124:         "name": "Raspberry Pi RF",
	line 20131:       "description": "Home Assistant Raspberry Pi GPIO RF Integration",
	line 20132:       "domain": "rpi_rf",
	line 20134:       "full_name": "markvader/ha-rpi_rf",
	line 20139:         "rpi-gpio",
	line 20140:         "rpi-rf"
	line 21056:         "hassio-integration"
	line 21237:         "hassio-integration",
	line 21355:         "hassio-addons",
	line 21356:         "hassio-integration",
	line 21695:         "hassio-integration",
	line 21997:         "name": "Raspberry Pi 1-Wire via sysbus",
	line 22012:         "raspberry-pi"
	line 22743:         "hassio-integration",
	line 25291:         "hassio-integration",
  C:\Users\schneich\Documents\Docker\HomeAssistant\config\storage\hassio (2 Treffer)
	line 3:     "key": "hassio",
	line 5:         "hassio_user": "7739eb1286284c94..."
8

It would be the config entry

9

Dear @petro,

Yesterday, I had a closer look into that json (… .storage\core.config_entries) and deleted the respective entries. Well, HomeAssistant gave me some errors afterwards and stopped working.

Here are the relevant parts of that file: there is the new mqtt-configuration, which seem to reference “hassio”. Because the mqtt-app doesn’t work in docker, I have set up an external mqtt-broker on 192.168.70.4. So this is nothing, I want to delete? Or do I have to reconfigure it?

{
  "version": 1,
  "minor_version": 1,
  "key": "core.config_entries",
  "data": {
    "entries": [
      {
        "entry_id": "6fec6457332d25e8931e528cdf7fxxxx",
        "version": 2,
        "domain": "openweathermap",
        "title": "OpenWeatherMap",
        "data": {
          "name": "OpenWeatherMap",
          "latitude": 47.xx,
          "longitude": 8.xx,
          "mode": "hourly",
          "language": "de",
          "api_key": "31f6e299e2c34cb5ee28f74bxxxxxxxx"
        },
        "options": {
          "mode": "onecall_hourly",
          "language": "de"
        },
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": "47.xx-8.xx",
        "disabled_by": null
      },
      {
        "entry_id": "39720229beb8d8ed9a1105bee948xxxx",
        "version": 1,
        "domain": "mqtt",
        "title": "192.168.70.4",
        "data": {
          "broker": "192.168.70.4",
          "port": 1883,
          "username": "hamqxx",
          "password": "xxxx322f3afc506e70b6850201d85780a3fff5e0axxx",
          "discovery": true,
          "discovery_prefix": "homeassistant",
          "birth_message": {
            "topic": "homeassistant/status",
            "payload": "online",
            "qos": 0,
            "retain": false
          },
          "will_message": {
            "topic": "homeassistant/status",
            "payload": "offline",
            "qos": 0,
            "retain": false
          }
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "hassio",
        "unique_id": null,
        "disabled_by": null
      },
      {...

Then, later on in line 377 and 378 of the same file, there is the reference to the raspberry. This is probably something, I could easily remove?

...
},
      {
        "entry_id": "8c6a9fc45ef3b35eac1eff5669e5729c",
        "version": 1,
        "domain": "raspberry_pi",
        "title": "Raspberry Pi",
        "data": {},
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "system",
        "unique_id": null,
        "disabled_by": null
      },
      { ...

All references to hassio in the core.device_registry are under the deleted devices. Can they stay there or should I remove those entries from that file?

What is the …storage\hassio file about? Should I remove the file or just its content?

{
    "version": 1,
    "key": "hassio",
    "data": {
        "hassio_user": "7739eb1286284c94xxx"
    }
}

Thank you very much and best regards,
Chris

10

I did some more testing: deleting this entry did it (see below). No more errors relating to raspberry or hassio in the logs after booting the HomeAssistant Container.

…/.storage/core.config_entries

      {
        "entry_id": "8c6a9fc45ef3b35eac1eff5669e5729c",
        "version": 1,
        "domain": "raspberry_pi",
        "title": "Raspberry Pi",
        "data": {},
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "system",
        "unique_id": null,
        "disabled_by": null
      }
3 Likes
11

I’m having similar issues. How do I remove the hassio integration? It’s not listed on the Integrations page.

12

Hi @ehn ,

I did not have to remove hassio, but I went to the …storage/core.config_entries and deleted the reference to the Raspberry pi. That solved the issue and removed the hassio error as well.

13

Yeah, that worked. Thanks!

In my case, I was migrating from a Home Assistant Blue and had to look for occurrences of “odroid” and “hardkernel”.

14

I had the same issue after moving from ha OS to a docker instance. Removing the raspberry_pi entry removed the error message for me. Thanks for the help.

15

I was doing some troubleshooting on my migrated system as well and had these exact same errors. Finding the raspberry_pi entry in the /config/.storage/config.config_entries was spot on. Maybe it makes sense to call this out in the documentation as a gotcha to go correct? I only needed to remove the one entry to remove both the raspberry_pi and the hassio log errors.