You are running an unsupported installation

[Lucart98]

I have the error “You are running an unsupported installation” on the Supervisor page since a while (I don’t know exactly how much time).
I wanted to know if this is important and if I can try something before reinstalling everything from scratch.

Below is a list of issues found with your installation, click on the links to learn how you can resolve the issues.

• Network Manager

That link brings to a page that says “If you have not already, install Network Manager on the host.”
How do I install Network Manager on Home Assistant OS?

Log:

2020-11-27 03:32:52 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for garbage_collection 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.
2020-11-27 03:32:52 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for 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.
2020-11-27 03:33:02 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for ctabustracker 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.
2020-11-27 03:33:11 ERROR (MainThread) [homeassistant.components.wled] Error fetching wled data: Invalid response from API: Error occurred while communicating with WLED device at x.x.x.x
2020-11-27 03:33:11 WARNING (MainThread) [homeassistant.config_entries] Config entry for wled not ready yet. Retrying in 5 seconds

Supervisor 2020.11.0
HassOS 4.17
Running on Raspberry Pi 4

[fanuch]

Try this on the host operating system (your Raspberry Pi 4):
sudo apt install network-manager

[123 (Taras)]

It’s running HassOS.

[nickrout]

Then surely it should not come up as unsupported?

[kanga_who (Jason)]

Go to Configuration—>Info and copy/paste the info from that page. Should look like this.

System Health

Home Assistant Core Integration

version: 0.118.3
installation_type: Home Assistant Supervised
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.6
os_name: Linux
os_version: 5.8.0-0.bpo.2-arm64
arch: aarch64
timezone: Australia/Brisbane

Home Assistant Cloud

logged_in: false
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok

Hass.io

host_os: Debian GNU/Linux 10 (buster)
update_channel: stable
supervisor_version: 2020.11.0
docker_version: 19.03.13
disk_total: 58.4 GB
disk_used: 4.0 GB
healthy: true
supported: true
supervisor_api: ok
version_api: ok
installed_addons: Visual Studio Code (2.8.2)

Lovelace

dashboards: 1
mode: auto-gen
resources: 0

[Lucart98]

System Health

Home Assistant Core Integration

version: 0.118.4
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.6
os_name: Linux
os_version: 4.19.127-v7l
arch: armv7l
timezone: Europe/Rome

Home Assistant Cloud

logged_in: false
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok

Hass.io

host_os: HassOS 4.17
update_channel: stable
supervisor_version: 2020.11.0
docker_version: 19.03.12
disk_total: 57.8 GB
disk_used: 22.7 GB
healthy: true
supported: failed to load: Unsupported
board: rpi4
supervisor_api: ok
version_api: ok
installed_addons: Samba share (9.3.0), File editor (5.2.0), Duck DNS (1.12.4), Mosquitto broker (5.1), Terminal & SSH (8.9.1), Google Assistant Webserver (0.0.4), Dropbox Sync (1.3.0), Node-RED (7.2.11), InfluxDB (3.7.9), Grafana (5.3.6), Plex Media Server (2.4.2), ESPHome (1.15.3)

Lovelace

dashboards: 1
mode: storage
views: 6
resources: 5

[anon43302295]

To be perfectly honest, if you’re running HAOS and it is showing as an unsupported installation, then it is a (pretty big) bug, and should be reported to the HAOS repo on github.

[Lucart98]

I see. Thank you!
I’ll open an issue there and avoid reinstalling everything to see if more tests are necessary to find the issue.

[123 (Taras)]

@nickrout

Then surely it should not come up as unsupported?

Lucart98 indicated it was running HassOS 4.17.

Subsequent post clearly shows the ‘unsupported’ message despite being HassOS.

So the answer to your question is “And yet it has.”

[anon43302295]

@123

So the answer to your question is “And yet it has.”

Yup, hence it must be a bug somewhere, be it in HAOS or in the way the supervisor divines an unsupported installation.

[Arnox (Arnaud)]

@Lucart98 probably already done, but just in case, have you rebooted your RPi ? I had the same message once, and a reboot fixed it.

[Lucart98]

@Arnox

have you rebooted your RPi ?

Yes, already tried multiple times but didn’t fix it.

[nickrout]

Yes. people sometimes don’t know what they have.

Has anyone noticed that it says os 4.17 in one place and 4.19 in another?

[123 (Taras)]

@nickrout

says os 4.17 in one place and 4.19 in another?

I’m seeing the same thing on my test instance (but it doesn’t indicate it is unsupported):

4.19 here

4.17 farther down the list:

I assume it’s due to some subtle difference in the version control scheme (or not).

In addition, despite a concerted effort to expunge the deprecated term Hass.io from all official documentation, there it is in boldface in the latest release. That section ought to be titled Supervisor or HassOS or something other than a term that is supposed to have been deprecated a half year ago.

[nickrout]

Actually I think 4.19 may be the kernel version?

Agree on hass.io sigh

[123 (Taras)]

Kernel version? That sounds right.

I think I read something somewhere (release notes??) that the next version of HassOS will be based on 5.4.

---

EDIT

FWIW, even the upgrade to 5.4 still renders my test instance incapable of being promoted to a production instance. An enhancement in 5.9 is why my production instance continues to be HA Supervised on Linux.

Community member jameshilliard added a patch that allows Linux to detect a certain USB-based device as a serial device (as it should be).

UPB lighting

My patches adding support for the Simply Automated USB PIM to the Linux kernel have landed in time for the v5.9 release(I think they will get backported to stable kernels as well fairly soon as well). Are you able to get notifications of switches changing state in message mode without polling for the state change?

Older version of the kernel don’t see it as a serial device and render it invisible to Home Assistant’s UPB integration.

[nickrout]

My advice to the OP: report to github, but don’t bother reinstalling, unless something else isn’t working.

[jameshilliard]

@123

Older version of the kernel don’t see it as a serial device and render it invisible to Home Assistant’s UPB integration.

Well my patches were backported to a number of older stable LTS kernel branches including 5.4, but it would only be later 5.4 point releases that would have it included.

[Lucart98]

Supervisor randomly stopped showing the error

GitHub issue: You are running an unsupported installation · Issue #2311 · home-assistant/supervisor

[123 (Taras)]

A “Solution” post explains how to solve the original, stated problem. What exactly did you do to make your system report it is now a supported installation?