I maked the reply as “Solution” to tag the entire post as solved, since the problem has been solved without doing anything (and maybe that is what someone should do when this problem occurs).
One possible explanation is given by ludeeus on the GitHub issue that I linked in the reply:
I’m guessing that the message you see is due to Wi-Fi is not connected during startup.
This is fixed in the Supervisor version that is currently on the beta channel.
Anyway, since doing nothing is not a “real” solution to the problem, I removed the solution mark.
Hello, I’m having a similar issue. It says I’m running an unsupported version. Seems to be a problem with network-manager.
I followed this link, https://www.home-assistant.io/more-info/unsupported/network_manager, and added the mentioned code into the proper files but I’m still getting same problem.
Here you have some screen shots with some info from my system.
In that case, I don’t know why it is reporting that it’s “Unsupported”.
You can wait until someone else, with more knowledge about this issue, responds to your question or you can report it as an Issue in the Supervisor repository.
21-03-28 22:59:10 WARNING (MainThread) [supervisor.core] System running in a unsupported environment!
21-03-28 22:59:10 WARNING (MainThread) [supervisor.resolution.evaluations.base] NetworkManager is not correctly configured (more-info: https://www.home-assistant.io/more-info/unsupported/network_manager)
21-03-28 22:58:55 WARNING (MainThread) [supervisor.dbus.network] No Network Manager support on the host. Local network functions have been disabled.
21-03-28 22:59:00 WARNING (MainThread) [supervisor.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
I believe the unsupported software problem happens when a standalone container is installed as explained here: Unsupported software
In my case, I’ve installed HomeBridge to my Home Assistant as a Container via Portainer as explained here to get my Nest Thermostat to work with Home Assistant since the Nest Thermostat plugin for HomeBridge works without any problems when Google Account - Refresh Token is used.
I believe that to be the reason why I’m having an unsupported installation problem.
There will be a link in Supervisor that will show you what the issue is. Also the supervisor log. Portainer itself is unsupported now and withdrawn so it could be Portainer as well as homebridge causing the error
Such a shame since I believe that is the only stable way to get the Nest Thermostat to integrate into Home Assistant and the Nest plugin for HomeBridge is still maintained and updated. That is the only solution I had a no issue integration for the Nest Thermostat. I also have the Google/Nest hello doorbell and that works with the google integration but not the Thermostat.
If someone manages to create a community / custom add-on version of the same HomeBridge, so that in the end the HomeBridge comes to HA via Supervisor, instead of via Portainer…
… would the Supervisor still declare our HomeBridge add-on being an “Unsupported software”?