I’m not sure what you mean by that. The install method this thread is about uses HA Core too - every install method does.
I mean it is possible to install HA core directly on Linux (without docker and supervised environment)
Thanks all the Home Assistant community of being reconsidering this. As you can see, there are lots of people using this method, and most of them without any issue. It is not fair that for a small number of users who “abuse” of this method we pay all the consequences. And let’s be realistic, virtual machines are not a solution, at least a good one.
Currently (and I hope it continues like this) there are 3 ways to install this great home automation software. Not all facilities are suitable for everyone. It depends on factors like server, computer skills and needs.
I have read some comments from people who, for whatever reason, this method has not worked well for them and they have used another type of installation. This is correct and I think it is as it should be.
I honestly believe that the solution is not to deprecate the method. Rather than deprecate it, you can simply maintain general aspects of the architecture, and those people who abuse of this method and get into trouble will be advised to use another alternative installation method, such as HassOS or Home Assistant Core. But please, don’t deprecate something that many people use without having any kind of issue and what is perfect for them
I merely stated my opinions on XML, INI(py) and YAML, from prospective of me being shutdown by devs regarding configuration templates. All what I am trying as a rest of folks on this thread is to raise issues around Linux installation, which I did in separate thread.
I do agree, that we went off topic.
best …
He he!
Yes, I had to do that too, forgot to mention it… --Slapping my forehead–
The nonsensical naming and associated changes don’t help either.
I’d just like to take the time to say thank you for the new Zwave component. While it is a pre-release I have not had any issues and it appears to be a top notch component.
I appreciate the response about this and the deprecation being put on hold for now. Thanks for listening to all the feedback!
Unfortunately, I already moved over to a Virtualbox-based HassOS setup and eliminated my supervised Linux installation in response to the original deprecation post. But I’m glad that the option still exists, and if it does end up sticking around I might switch back at some point to eliminate needing to run virtual machines on my server.
Reading your post I see many similarities to what I am going through (except I haven’t gone through them yet). I currently have an intel NUC that I purchased to try and install HA as a replacement for my smartthings. I currently have Ubuntu server installed and was going to install HA supervised, but don’t want to be using a discontinued product. If I go with HA Core in a venv I worry that updating and installing addons will be a pain. I tried proxmox and couldn’t get it to connect remotely for some reason - plus it seems infinitely more complex. So i’m trying to decide what the best route for my install is?
How is odroid N2 recommended as there is not an official released image? The latest documentations shows it is still in beta.
You have an Intel NUC so the simplest option is to use the Intel NUC image for Home Assistant. That includes HassOS, Home Assistant Core, Supervisor, and support for Add-Ons.
Thanks for the feedback. I’m thinking I will try this method for now. I was just hoping that I could use the NUC for other things as well. But now I’m thinking that I’ll get myself setup with the NUC image for HA, get used to it, then later switch to linux with a VM.
One more question - with that setup, can I still run Node- Red and mosquitto?
So grateful this has been put on hold!
Thanks guys
Yes, you can run them as Add-Ons.
The Add-Ons repository is here:
https://community.home-assistant.io/tags/hassio-repository
Yes, that’s one of the supported methods (the one I use). It’s “main stream” - all install methods use it. It’s tested too.
I gotcha! It sounds then like the VMDK was a different version than your ESXi was expecting. I’ve run into this with every VM I migrated to a new ESXi host, not always from ESXi (one was VMWare Server 1.0 with way too many disk snapshots!) and sometimes I had to clone exactly like that to ensure it was in the right format for that version of ESXi. Sounds like this is more VMWare’s fault with their inconsistencies, but I’m glad you got it working!
following your footstep… I’m actually using this method. Feel more convertible to run everything independently so the docker can be use for other thing
why would docker cares?
you can have HA core installed as a container, it’s not about this subject thread, supervised installation on linux is about something else.
Docker is about to run everything independently, if want to.
I don’t get it, maybe i’m looking at this wrong.
I first tried with the virtual image and felt like a fish out of water… what OS was it again? couldn’t do any of the configs that normally take me mins to do, was effectively useless for me… so I setup a VM with a fresh copy of debian and installed HA under python… perfect solution for me and I’ve not once asked for help because of using my own OS of choice for the past 20 years.
I would go on to say don’t dumb HA down to using preconfigured installed/environments, however for the manual installs fee free to put all manner of scary warnings in the documentation stipulating your on your own for that type of install.