Unless you install Home Assistant Supervised on Debian, it will not be an officially supported installation. You’ll discover that information, and more, after you read the installation requirements for Home Assistant Supervised.
The poster is kind of in a bind because they want to use the AirSonos add on, but still keep a Raspian OS. I’m running the Home Assistant container install and managing all the other containers, like Node Red, myself, without the add ons. But the issue here appears that the AirSonos Docker container is no longer being developed/working, and only works as a Home Assistant add on per this post/thread - AirSonos docker plugin - #9 by frenck. So, installing AirSonos as a separate stand alone container doesn’t appear to be an option here. And the only way to have the addon would be to run the Home Assistant operating system or a supervised install.
@123 would it be possible for them to install a virtual machine on the RPI running Debian, and then install the supported supervised install on the Debian VM? Or would it not be able to handle that?
Or just run the whole home assistant operating system in a VM like documented here? Linux - Home Assistant
You’re asking me to comment on the feasibility of something I didn’t suggest.
The OP should install Home Assistant Supervised on Debian (even if it’s an RPI3). That’ll allow for the installation of the AirSonos Add-on.
The OP advised
The supervised install instructions here architecture/adr/0014-home-assistant-supervised.md at 91ecbe4af814de6c06f3f98afc0920b2491a334c · home-assistant/architecture · GitHub specifically say “No additional software, outside of the Home Assistant ecosystem, is installed”
Based on that, I don’t think they can just replace raspian with Debian, install Home Assistant, run their other programs and call it a day. I was seeking an alternative through a VM to make everything work for the OP and was just wondering what your thoughts are on that based on your frequent posts in the community and expertise.
1 Like
This line represents the true concern:
The user is also responsible for not installing or changing anything on their system that will interfere with the Supervised installation. Examples are software that will update Docker containers managed by the Supervisor.
Plenty of users have other things running on the host that have no impact on Home Assistant’s operation and the system isn’t flagged as Unsupported or Unhealthy. Personally, I run ssh and samba services installed on Debian as opposed to Add-ons. Where you will run afoul is installing an impactful docker container like Watchtower.
I still believe Home Assistant Supervised is the appropriate choice. If you think it should be Home Assistant OS in a VM, you are welcome to guide Neilp down that path. Based on what has been posted so far, that might be a long path up a tall hill.
2 Likes
Ok thanks for the info. I wasnt sure how “strict” the guide was about other programs but your post clears it up. Based on that sounds like the supervised install is the best bet for the op.
Thank you all for the input over my nights sleep.
Going to be too much to read and digest on my phone, but this does look like a complex issue to resolve. It was what I was afraid of. 
I have outdoor work to do today ( farm/ horses/ grass mowing etc ) but will go through all your suggestions in more detail when I get a chance in the next couple of days
Many thanks
Thank you all
Did not want to go down the Debian route and then have to try and re create the system I currently have (HomeVisionXL, HA-Bridge, MQTT broker, VNC server etc) on a different OS, learn the differences fo the new OS Yes it could well be possible…and with a Pi running on a SD card, I can easily have a play on a fresh card then go back to my original system if it does not work.
Or the VM ware route…but this all then become another major project…I was very much hoping that I was missing something simple…and one of you knowledgeable people was login to tell me…yes here it is easy …just open a terminal, type this … to install …XYZ…which will add the Add-On package…but no
So looks liek this is dead in the water for me.
The only use I had for HA was going to be the Air Sonos, I coudl not see it being able to do anything else for me…as HV & HV-XL currently run all I need .
thank you all for trying to help…but I’ll bow out of this for now
Will head over to the
I agree with you supervised only run well if you are running Debian and not RaspiOS
If everything run on Docker then you should not have many issue since you can move all your config and reinstall your docker then all should run as is?
1 Like
If you are only want to use HA for AirSonos, did you try to install AirSonos directly on your machine without docker?
But as previously pointed out, Docker install does not provide the add-ons, and the AirSonos add on was what i was wanting
There was some Docker type stuff done in 2016 for AirSonos, but it no longer seems to work
Did you try AirConnect? It’s still actively developed and seems to have the same/better functionality than AirSonos
No, and No,
I assumed they were part of / need HomeAssistant, to run and were not standalone applications
Just about to light fire for midday farm BBQ, but tonight when I get home I’ll look them up, thanks
Back home now and looked at Air Connect…looks like what I need
thanks
“most of the addons can be replaced with just a regular docker container from dockerhub”
I am new to both HA and Docker and wondering how to do this. Can’t find any info for dummies. I am running docker on a synology NAS. Can you point me in the right direction?
3 Likes
I was in the same boat starting out and there really isn’t a comprehensive step by step guide “for dummies”. It is a tough way to start out but if you stick with it you’ll learn a lot about docker along the way which is definitely worth it. If you have docker running successfully that’s a huge step forward. If you haven’t already, I would first get the Home Assistant container running, and the official documentation is a good starting point
Then instead of installing add-ons through Home Assistant you install the equivalent add-ons as other docker containers. Currently I’m using Node-red, Portainer, ZwaveJS2MQTT, Zigbee2MQTT, Swag, and Wireguard all running in docker as separate containers. What add-ons are you looking for specifically to run? If you list the ones you want hopefully I/someone can post links to the install instructions/tutorials for them.
2 Likes
I tried it out by installing a Configurator container alongside with HA container. Now since Configurator in loaded as an iframe in HA, I need to expose Configurator’s container to the internet if I want to access HA from outside my network. I’m using a reverse proxy to make it work since the Configurator is not on SSL.
Not sure I am doing it right, but I suppose I will have the same issues with other “add-on containers”.
I don’t use the configurator, I usually just edit the yaml config files right on the machine running home assistant using the nautilus file explorer in Ubuntu. The machine has a keyboard and monitor. I can still ssh into it or access it on my windows laptop through a samba share. Ssh and samba are running on the “bare metal” of the ubuntu machine.
I do have zwavejs2mqtt and zigbee2mqtt’s config pages accessible through iframe pages through home assistant, and yes those need to be configured with a reverse proxy for external access. Home Assistant won’t proxy them for you. For a reverse proxy I use the Swag container which combines nginx, duckdns, letsencrypt (for secure ssl certs/access) and fail2ban. It sounds like you already know how to deal with reverse proxies, but if you’re interested in SWAG I set that up using the instructions from this post
Another option instead of or in addition to a reverse proxy is a VPN. Then when the VPN is connected all the local http addresses would work just like you’re in the network even though you are away. I have wireguard for that and wrote up this guide about installing it in a container
4 Likes