Where is the add-on store when running from docker?

Installation
42

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

43

Did you try AirConnect? It’s still actively developed and seems to have the same/better functionality than AirSonos

44

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

45

Back home now and looked at Air Connect…looks like what I need
thanks

46

“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
47

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
48

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”.

49

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
50

I know this is a very old thread… But I have been searching for 3 days now and it seems many talk about the ability to install the HA addons directly into docker, yet not a single person has posted a guide/tutorial on how to do it. Didn’t the team realize that some of the HA approved add-ons were going to be valuable moving forward, such as a text editor and terminal at the very least. What a PIA this has been. These, among a few others, are essential components we need to have installed and yet we have to “go figure it out”.

51

It’s not the exact HA “add-on” that you will install in docker. The “add-on” will only work in HA. Think of HA as an incompatible alternative to docker…

For instance, there is a adguard add-on for HA. You can’t install that add-on in Docker, however you can install a docker container called adguard from the docker hub in docker. Both are containers, both have the same name, but they are not compatible.

Terry

52

I think we understand that… Which is what makes HA even more confusing. HACS was a simplified way of installing add ons. Now we have nothing. There are no guides, no helps and no support in getting these essential add on back into our configurations. All I am trying to suggest is that when massive changes like this are decided upon, that perhaps a bit of help towards the users that will be impacted would be nice. I am sure the internal team knows what needs to be done to get these add ons, or something similar, installed. So why leave us in the dark?

And I do understand the issue/stance on provided support to these users. But HA has a HUGE community now. Perhaps someone from inside the community could be encouraged by HA to do the guides? That would remove the liability of needed support from the HA team itself.

53

I don’t think you do understand. If you want “Add ons” you install Home Assistant OS (aka HAOS), either on bare metal or as a guest in a VM. Once upon a time you could also install “HA Supervised” but that has been deprecated.

You have NEVER been able to install “Add Ons” through HACS, period. It even tells you so when you install HACS. HACS provides alternate sources for integrations, not add ons and that’s the way it’s always been.

If you want to install HACS on your docker hosted HA container, you can certainly do that. If I remember correctly from the HA container shell you pulldown the HACS install script with wget and install it manually. From that point it’s HACS as usual. Google is your friend for the exact instructions.

Terry

1 Like
54

Ok, So as usual the the internal team doesn’t understand it’s user base. It is years and years of constant breaking of workflows, installations and hacks. HA could easily become a commercial product generating a tremendous amount of wealth for all involved if it were STABLE. But the HA team is so thick headed in it’s stance about it’s user base needing to CONSTANTLY adapt to broken and half baked roll outs. Granted, you guys do great things. But you constantly ignore the fact that the end users are fixing things every month. There appears to be no consideration of backwards compatibility. Piss on me, a long time user, all you want. But this stance you are taking that we don’t understand HA is pure ignorance on your (HA’s) part. Not everyone who is using HA has the time or expertise to repair broken installs/updates. And removing HACS is a broken installation to many of us end users. I’m sorry that you don’t understand that. And few are willing to state it cause the HA team pisses on anyone who opposes, constructively I might add, their decisions.

Geeezzzz… All some of us wanted was access to a freaking text editor. Something absolutely essential to working with YAML files. But hey, I guess some of us have entire weekends to waste and need to go searching for a fix. When we all know, someone at HA has already figured out how to integrate a simple text editor. But hey, no worries if you don’t want to tell us how to edit the files. And please, don’t insult us by telling us we shouldn’t be installing a version we’re not ready for. That is another insult I have seen over the years where some who are eager to learn are insulted and pissed on for trying to learn by asking for help.

And if you think I am insulting you, you are again horribly wrong. I love HA and what it can do. I think it is one of the most amazing projects I have seen in my 50 years of tech. It has tremendous possibilities. But I also know that ignoring users and their needs is the kiss of death. The user base attached to HA is only loyal because there are no real alternatives. Once a competitor arrives on the scene, you will hear the sound of a rushing wind as people flock to give it a try. You can either receive that as encouragement to make adjustments or ignore it and find out the hard way. Personally, I hope HA makes the adjustments while they have the chance.

1 Like
55

You do realise that entire rant was directed at a fellow community member?

It’s very hard to understand from your posts what your specific issue is.

Can you explain the problem you are trying to solve? Include details of the type of HA nstallation you have, and what you have tried that doesn’t work.

Maybe a fellow user or volunteer developer (which comprises 99.9% of the people on this forum) will be able to help.

2 Likes
56

NEVER, NEVER, NEVER. You would see a mass exodus of users if this were to happen.

The core integrations are well tested in the monthly updates. It’s the user-generated add-ons and integrations that sometimes break. The devs focus on the core and will attempt to alert the user contribution authors of upcoming changes. Most keep up with the development schedule, some unfortunately, drop off the planet and no longer support their contributions.

There are literally many hundreds of these user-contributed tools, so to expect the devs to test every one of them with each update is remarkably unreasonable.

In my case, I run HAOS bare-metal on an Intel NUC i3, and I measure my uptime in years.

1 Like
57

Yes, as Chris stated, instead of ranting, what don’t you simply state what you are trying to accomplish?

I am not an employee of NC or a code contributor, just a regular user. I’m trying to help you but you are using mixed terms and seem to be here just to complain. If that’s the case rant on but know that it’s pointless because as stated above, the vast majority of people using this forum are users and community members.

Terry

3 Likes
58

Exactly! Nobody here wants that. If we did, we’d be on one of the many existing commercial offerings.

Terry

59

Are You telling me your Run HA in Docker, and don’t know how to “access and edit” yaml-files , easily ?

3 Likes
60

If you cant maintain a docker install then your best option is HAOS in a mini pc.

2 Likes
61

You don’t install the actual “add-on” with a docker install and would need to install/configure its equivalent. And that’s going to depend on which “add-on” you want.

The problem is you can’t really put together a comprehensive guide because the host OS and overall configuration is going to be very different from one Docker install to another. To get the added flexibility you have to trade off that it will be more complicated to manage.

This person has put together quite a few helpful guides, and would be a good place to start for setting up Home Assistant container -

My post above is old but still relevant for this. You can use the text editor in the host OS on the machine running Docker, you can setup a SAMBA share, and/or setup SSH to edit the file in host machine from another one.

If the host OS is Ubuntu here would be links on how to configure Samba and SSH- so you can edit files with either one. Once configured SAMBA is really nice because from any Windows machine on your network you just use the file explorer to go to you home assistant config on the Ubuntu machine and can edit it with notepad/wordpad.

https://ubuntu.com/tutorials/install-and-configure-samba#1-overview

There are other guides in this forum, such as how to configure SWAG - linuxserver/swag - Docker Image for secure remote access, and a guide I wrote up on how to install Wireguard in docker for a VPN - Wireguard Container

Zwave can be installed in docker by following these steps - scroll down to “Option 3 - The Z-Wave JS UI Docker container” - Z-Wave - Home Assistant

Zigbee2mqtt can be installed in docker following these steps - Docker | Zigbee2MQTT

An MQTT broker can be installed in docker following these steps - Configuring the Mosquitto MQTT Docker container for use with Home Assistant — Home Automation Guy

A guide for Node Red in docker and home assistant is here - Installing Node Red in Docker for Home Assistant

Container is definitely a harder install type to manage - that’s why the HASOS option is easier to manage. I feel your pain on the breaking changes. I’m not as able to be involved as I was a few years back due to job changes so have moved to more of a maintenance mode with my smart home, and get frustrated when things break. I try not to complain anymore though because I keep in mind I would rather use a solution that is actively managed and receiving updates from something that is no longer maintained. There’s really nothing else I’ve seen on the market that works better than Home Assistant, so I fix it and move on when something breaks. I also can understand why the developers are focusing on the two install types and no longer supporting supervised and core - No one likes to see their install type removed from support, but it is just too much to expect them to maintain all of these options and be able to fully support the product.