is there a reason you can’t put your HA in that VLAN too? if it’s a segregated, non-networked environment then why not create a second network adapter for your HA and give it an address in that VLAN too?
This is the right way!
VLANs typically can only cross communicate via the gateway, most broadcast discovery protocols don't get routed via the gateway (because its not considered local), and while you can get the gateway to repeat some traffic, its very brittle... lots of network stack developers made assumptions about broadcast packets being on the local network segment.
Well, I haven't thought about it, I can't see any drawback. Thanks!
I've added an extra NIC that is in the IoT VLAN, but there are no new devices. The NIC is ok, because I see that it gets the IP from the router. What can I check/run?
can you ping one of the IoT devices from the HA device on that new NIC?
can you manually add a device and HA see it/add it normally?
is there a firewall routing between HA and the IoT devices that might be blocking discovery somehow?
I can ping the devices. No firewall, the NIC is directly in the VLAN and the Proxmox firewall is off. How can I add a device manually? ...I'm just starting with HA.
I have my HA setup with a trunk and a sub-interface in each VLAN for auto discovery. The IOT sub-interface then doesn’t require a gateway and the two networks can then be kept Isolated.
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io