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

oK- I wIll sTay A rETard caUse yOu sAid so… Stop insulting the user base for trying to learn. When HA functionality breaks, it creates problems. And users are simply looking for answers on how to fix them. Telling them they did it wrong doesn’t help them fix it. Dah!

You are proving my point! THANK YOU!

Again, my point is being proven. Telling users what they NEED to do, and HOW to do it are two entirely different things. Users are spending a ridiculous amount of time searching for the HOW TO do it guides. I would suggest searching outside this forum to hear/see the volume of users desperate for answers. This forum is simply an echo chamber of the experts of HA.

1 Like

Overall, I thank you for taking the time to assemble your reply. You were gracious to add a tremendous amount of information. I, and probably many others, will find this useful. But this is not the norm - and I wouldn’t expect it to be. Your willingness to help is a much different approach then what some of us are accustomed to receiving in this forum where we are discouraged from trying to achieve better and greater control of our HA setup.

1 Like

For a long time user, using an advanced install type (Docker) you seem very badly informed. HACS is not removed from anywhere.

HACS has never provided a text editor. HACS has never provided add ons. Docker setup never had an add-on store either. How did you edit files up till now? Why would you chose Docker advanced install if you do not have the skills to install a text editor?

Those guides aren’t there because you can’t. You use HAOS, you get add-ons (thich are docker files targeted to Supervisor, which manages the addons inside HAOS). If you have a Docker setup, you use Dockers to run the same software, not add-ons. You want Studio Code to edit files? Install a Studio Code server DOCKER.

If you don’t know how, well, why use Docker instead of HAOS? Docker is the Do It Yourself version, not the Show Me How Its Done version, nor the Autopilot version. You want to hold the flight stick? Then you need to know how to fly. Docker has no training wheels attached.

So my advice: Make a backup, make sure you have the recovery key, install HAOS, resture the backup, use add-ons. From the addon store, not from HACS. You get all the perks of update notifications, etc…

If you don’t want to do that, then learn how to install software in Docker for all the software packages that are also available in add-on form. Also make sure you know how to update and maintain the OS beneath it and how to update software. Which already includes the use of terminal services/SSH and editors.

But be advised all guides are targeted towards add-ons. There will be guides for Docker, but mostly not specific to HA. I’d advise to install portainer, which is a GUI to mange Dockers, and Watchtower, which manages updates for Dockers. All these things probably have guides, but they have nothing to do with HA.

2 Likes

Nothing will ever be as easy as having the editor built into HA. When I access my HA installation from any device, from anyplace in the world, the editor is right there in the interface. That is the easiest and most convenient solution.

Any other solution requires the assumption that I will be accessing the files from the same place(s), same environment(s), same equipment, etc each time. And even getting each one of those configured is simply more time consuming then I would like. It also creates more contingencies which result in more points of failure than I would like to have. I just prefer to stay away from that if at all possible - this is why having the text editor add on was/is so awesome.

Ohh, sorry i didn’t understand you also don’t know how to access your Linux server remotely
As for the rest of your requirements and concern, i as above also recommend you to install HAOS
You have ofcause not specified your reason to run/keep running in Docker, if you don’t feel comfortable with it

The editor for automations.yaml and scripts is called the automation editor. For scenes.yaml it is called the scenes editor. sensors are created in the helper section. Dashboards are edited in the dashboard editor. All built in. There’s little to no need to revert to yaml nowadays.

For the good old yaml way, it isn’t as logical to write and maintain editor software for that. There’s little to no other software that includes a text editor to edit its own startup files.

Those features you speak of are recent improvements to HA. For those of us who started some time ago, a lot of our configurations may still be in YAML. But thanks for the assumption that I am not aware of the improvements that have occurred over the years.

Lots and lots of times, and i have both Terminal(SSH&Web in UI), + Samba + File-Editor Add-ons ( ones had Visual, but i found to to crappy ), i prefer “simple” file-editors, i.e NPP in windows, But most in HA i do in the GUI/file-editor , So Yes i prefer HAOS, and have no need for HA in Docker … i went for Supervisor from first install, my own decision ( For simplicity ), first Supervised in Debian, but it was “to fragile” for my curiosity.

You get the answer you get to your question, bc of your way to “speak” about and to people you don’t know and you have no idea of how they think, why and what they do and or try to i.e help or create something for others to “play with” , Most People does not come to this forum to listen to your Problems, but many are willing to help or advice People here
I.E The Internal Team(in your words) first i thought you mend The International, but never mind, They Don’t actually have a User-Base (Some might see it that way now thou) They started with something, for them self, other people joined in, some more wanted to add-in, hardly anyone did it to “Serve” someone else ( Like i.e You )
They Had a vision, it grew, and new ideas/options turned up, and it grew more , some “found” their “Work” in Github (sounds familiar ? ) They download it and found it cool.
Now this was quite some years ago, as you know, now there are tons of users, And again Contributors, “internal” integrations, 3rd part of same, Official add-ons, and Community of same … Options are endless for the endless stream of users with their own ideas.
But You are stucked in your own “container” and insulting people who don’t agree to your BS , Install your ADD-ON of choice in a Container(next to HA, or under would be the right term) Then write a Guide/Tutorial, for other People, so they don’t end up in Your situation
It’s clearly stated in the DOC’s NO Support for Add-Ons, and not many of the users in this Forum are running Container so there haven’t been a stream of “requests” for a “Dummy” for this, People running Container, most likely choosed this for a specific purpose and with required knowledge, a few bc they think it was/is cool, with that decision they rejected the Benefit of Supervisor, Or thought they could live without it ( which 99,9% does )
Your best choice is Google, there are people there have dedicated their time to produce Tutorials for You