I’m not new to doing this…I’ve had it tagging up and running on my PI4 (Ubuntu) for years.
However, I can’t get anything to work on HA Yellow. None of these commands work. None of the traditional linux commands work.
I’m at a loss. Does anybody have any idea how to do this on Yellow???
As I don’t know how HA Yellow works, this is just a long shot question, but have you tried enabling ssh connection to the host OS and trying the commands there?
I started by doing this when HA was still HassOS and to be able to configure network you had to ssh into the host operating system, not the container. As ssh access to the host OS was disabled by default, you had to enable it first
Maybe these threads can help you
Good luck!
Yeah, I did.
I figured it out. I enabled the wrong SSH Add-On. You have to use the “community” one, not the “official” one.
Great work! 
Hmmm
Ok I got a question for you, do you know how to create virtual adapters in HAOS?
For example, I have vlans setup, and HA is on a trunk port and lives on an untagged network, and I’ve setup routing similar to you, but still only have one IP, on the untagged network of the trunk port.
However I have one integration, that I’d like to setup a virtual interface with an IP so HAOS ‘exists’ in that VLAN/subnet too. I’d prefer not to add a USB NIC or other Ethernet cable.
Its VLAN3 where I have media devices, namely my Samsung TV’s. And Samsung TV’s don’t allow control from outside a /24 subnet range.
If anyone has a guide how to make a virtual interface for a vlan to assign an IP in that subnet, I would greatly appreciate it.
Hi,
sorry for the late reply. What you are describing is exactly what’s implemented in the first tutorial: one physical network interface (eth0, as it all began from one rpi3b+ physical limitations) and not wanting to add usb network interfaces, nor use the wlan interface. You can create virtual network interfaces that are tagged with defined ids and that work at layer 3 level, having a unique ip and all other network configuration (you can also have multiple ips configured to a unique interface in linux with aliases, but they will travel the same “pipe”, so only with proper subnet masking could you segregate these interfaces from “seeing” each other. A bit more like a security through obscurity kind of thing. By adding vlans on top of that physical hardware, you are fully segregating networks.
Something like:
#nmcli con add type vlan con-name eth0@vlan3 dev eth0 id 3 ip4 "your_vlan3_ip_here/your_vlan3_subnet_mask_here" ipv4.dns "your_vlan3_dns_ip_here" gw4 "your_vlan3_gateway_here"
Hope this helps
Well I feel silly that I completely overlooked that reading through the post. Thank you very much @cr0muald0
It is me who should thank you Your last post is a living proof to other readers that the tutorial lives on!
Hi. I have my Home Assistant in other VLAN 10 than VLAN where is my Samsung QLED TV VLAN default.
Communication between this two VLANs is setu as access. From Home Assistant to TV and from TV to Home Assistant. But i can not add TV to HA because it is in ither VLAN. Is any solution for it ?
My network in home is build on Ubiquiti UDM pro and switches.
Home Assistant i have installed as Home Assistant operating system on my HP T630 termina. HA is connected by LAN. HP T630 also has wifi card but when i connect from HA by WIFI to VLAN SSID whee is TV it looks that works but sometime HA has a problem because try get from Ubiquiti the same address on LAN and WIFI. I have setup FIX IP on wifi from TV VLAN but it no working also…
Hi, a bit of a confusing setup, but why would you create two different VLANs to allow access between them? Sounds you are defeating the separation purpose. Do they have different networks / ip ranges?
My option would be to create/add a new network interface and proper VLAN in HA that matches whatever VLAN your Samsung TV already has and let them talk directly (via switch, obviously). In summary:
or…
You can use mDNS, just like explained here:
Vlan with HA has other adresses.
How on HA create other interface with VLaN ? I use Home assistant operating system 9.5
Wifi on TV i no use. Tv is connected by LAN wire.
Do i must in setup tv disable wifi?
Tutorial to create/add network VLANs in HA assistant is here (using the HA terminal addon and reading this whole thread might prove useful):
If wireless is not configured/enabled in Samsung TV, you are good to go 
Disable multicast DNS in Ubiquiti no resolve me my problem.
Create network terminal is not the same as connect from Home Assistant from Settings > Network ?
I installed addon terminal to my Home Assistant OS. I try login to root, hassos and admin and i can not. I dont know how i can do it to create this vlan.
But if i have in my terminal HP T630 also wifi card i can create interface with VLAN on this wifi card ?
First go to Settings / Add-ons and install “SSH & Web Terminal” from the HA repository, configure the add-on as per instructions in add-on documentation, then you’ll be able to have root access in terminal and proceed from the “nmcli” commands found in tutorial to create VLANs.
I think you should ALWAYS use cable connection whenever possible, but you can use wireless if no other option is available…
Here is my Terminal add-on output:
~ whoami
root
With root access you can proceed to create interfaces. If you have no root, something is wrong with add-on configuration.
Now i use wire interface LAN on my HP T630 terminal with Home Assistant operating system . But if i good understand i must create next interface on HA and connect it to vlan where is my Samsung TV ? And then Home Assistant will be use two interface one LAN interface to vlan IOT and second which now you suggest me to configure with VLAN Samsung TV?
yes, that’s about it
Remember, each VLAN and interface should have different networks (ex: 192.168.0.0, 192.168.1.0) and different gateways. HA is only a member of the network segment and not the gateway for the network clients!
Samsung should be able to see the HA interface on the same network segment but have a different gateway and dns server (your firewall/router, maybe?)
Yes networks interface has other address. HA is in IoT network but Samsung TV is in default VLAN.
Now when i have connected TV to default vlan , HA found integration for Samsung TV but when i try konfigure it i get error in HA that is some error with websocket something. And can not connect.
Samsung should be able to see the HA interface on the same network segment but have a different gateway and dns server (your firewall/router, maybe?)
What you mean ?
How does the Samsung TV get to the internet for updates? What’s the exit/gateway IP? What’s the dns resolver IP?
IP example for Samsung TV VLAN network:
192.168.0.0 - network
192.168.0.1 - router/firewall/gateway (maybe dhcp and dns server too?)
192.168.0.2 - Samsung TV
192.168.0.3 - HA new interface
So HA and Samsung can see each other directly in this new VLAN.
HA does NOT need/ should NOT have a gateway set in this interface, as it can use the normal/default/old interface to access the internet.
TV has LAN 192.168.4.12 gateway 192.168.4.1
But HA is in other LAN 192.168.10.x and gateway 192.168.10.1
Next inteface which create in HA should has 192.168.4.x and no gateway ?
yes, that’s it