You can still use Raspbian Buster + VENV install which is pretty much the same thing as Hassbian, apart from Raspbian will recieve future updates. 
@flamingm0e
Was half of it wrong
My anger actually comes from people on this forum not being helpful
Check the list again with hassos and see if my agreements are right for Hassos
You need a specific plugin for root terminal access to the os which is needed for vlans which was buggy as hell for me
Hassos uses the red hat network manager. The Debian vlan pack imo is better.
Since the ssh package for Hassos has been super buggy for me winscp has been an issue which is what I use for modifying my config.
The comment about vlans was still for the guy that said they are all hardware and you said there is no need for them on a rpi with home assistant. Just cause you don’t have the same need I do, doesn’t mean there’s no need.
Props to @kanga_who who actually came up with useful info.
No. You don’t need a specific plugin. You follow the directions in the documentation for debugging HassOS and add the SSH file to the sdcard…
It uses nmcli
Winscp works fine.
But docker is so hard!! /s
I hope you realize your initial post warranted unhelpful responses. If you post with less attitude you’ll get good responses. You came in here looking for an argument and you got one.
3 Likes
But I did get a good response. It’s was to use raspbian and do the hass.io alt install which I looked at and should work great for all my needs.
I can still use ssh and winscp the way I’m used to. I can install vlans package in raspbian and use them the way I’m used to. I do not have to install the network manager. Also since it’s a docker, I shouldn’t have to worry about python updates.
I admitted I was talking about the wrong thing with the difference to hass.io and hassos when it was pointed out.
The key problem is I am far from the only ignorent person here. The difference is I’m in need of help usually, not “helping” people with wrong answers on how vlans work and just complaining because your a fan boy. All hardware haha.
And sure I get your point on attitude. I’m like that all the time. Why do people have to be so sensitive about everything?
as An outsider to the conversation, your initial post made it look like you knew nothing about vlans based on the phrases around it. It was so brief and full of errors that anyone reading it could easily miss interpret what you were laying down.
Still doesn’t change the fact that the person who actually got pissed off and was supposedly knowledgeable doesn’t realize what vlans are and also doesn’t realize that most Linux distros are either Debian based or red hat based at ground level in my experience. I used to actually prefer centos which is red hat based but mostly Debian these days.
But your right. I preach not posting in some else’s topic unless you have something helpful, but did it myself. On the other hand I wouldn’t have gotten a viable solution if I didn’t. And as someone else pointed out the whole issue with wrong termination between hass.io and hassos stems for bad documentation and the fact the website brings you to believe they are the same. IMO the alt docker install should b the go to.
At this point, none of this matters to me. I have a free SD card I can load up and swap with my current one to minimize downtime and should get everything I want with hass.io alt docker install on raspbian. Just wish this would have been brought to me a couple weeks ago when I was redoing it all.
3 Likes
@smbecker3673 I have learned a lot from your post and the following responses. Thanks for posting and for keeping a level head in the conversation. I didn’t really realize that hassos and hass.io were different either. I run a hassbian install and a lot of the posts and documentation are leaning in the hass.io direction so I have been wondering if I will be forced to switch at some point. I was concerned about losing ssh access and the ability to hack the system a bit to make it do some tricks.
The whole hass.io, hassbian, hassos, docker, virtual environment, yada yada yada is very confusing in my opinion. I am a software developer with 30 years experience and I find the terminology for hass very tricky to understand and get right when posting. Especially when you don’t really have a lot of time to dig through pages of forum posts to find the nugget that helps you understand. The docs are not terrible, for open source they are actually pretty darn good but there are still many things that are hard to understand if you don’t spend a lot of time researching.
I am just about to move my system from a raspberry pi to a retired computer which I plan to put ubuntu on and let it take over my home automation and several other servers I have running on various pi devices. I think this post is going to help me plan that out better.
3 Likes
For sure the alt docker install the the nice guy posted a link for, will work for any system, pi, inuc, old PC you have lying around.
Ultimately, I would like an esxi that can handle all my stuff but I got slot. 3 pis, a torrent pi, a Hass pi, a bind server running on a pi 1. A unifi cloud key gen 2 running protect and unifi, really wish I could run protect on my own box. A ubnt mfi x86_64 server running Ubuntu 14 and a Apache for other home automation tasks I have not moved to Hass yet, mfi only works on 14 due to it being a dead product line which sux and can’t run much else with it, but still very useful just not open to outside world. And another x86_64 PC running iredmail and unms.