I have a ‘remote’ Raspberry Pi 4- connected via LAN with my home network (192.168.178.x) and the wifi module connected to my guest network wifi (192.168.179.x) - I can connect to HA when connected to Home wifi on 192.168.178.x:8123 and when I switch to Guest Network - I’m able to connect to 192.168.179.x:8123
Now I try to add some devices which I want to connect to the Guest Network due to privacy/security and get these into my HA remote installation - In the past I was succesful, but with some refresh / update - I don’t know how I did this.
As example - I have added a shelly device to my Guest network, it’s not discoverable by HA remote - when I reconfigure the shelly device to my own network, it’s inmediatly seen by the HA remote
How can I bridge these networks on HassOS on Raspberry Pi so I’m able to discover items on the Guest network and add them to HA
Note 1: Using Fritzbox router - no special configuration made for the Guest Network
Note 2: Need to enable IP 6 as well due to Matter
The IPv6 requirement will mean you need to study that protocol.
IPv6 is NOT just IPv4 with more addresses and there are specifics that makes it hard to do what you want here.
Segmented networks are both difficult to maintain and set-up. You also have to know how they work in order to know what is happening.
The guest network by design is not going to talk to the main network.
Also Ha is designed to work on a flat network with 1 set of IP addresses.
Basically what you want to do can be done, but only if you know what you are doing to both set it up and maintain it.
I highly suggest you add a router that can do wifi at the beginning of your network connection to the world, then connect all your stuff to that that you want talking to HA.
Can you elaborate what hopes you have in improved privacy and security connecting your devices to your guest network? And also which devices are you using were you have privacy and security concerns in the first place?
If you are concerned was the manufacture is doing on the device you might want to “free” this devices and take full local control and ownership with espHome. After that no vender/manufacture code/firmware is left on the device and you are the sole owner controlling everything
For example you could even run wireguard on a esp based Shelly device working everywhere in the world with your remote ha (also running wireguard)
I do too, I have a sub-net that the only thing on it is the HA server. But if you can’t set it up you can’t maintain it or conceptualize what is happening, you really shouldn’t do it is the point.
When you ask why things don’t talk to each other when you set them on exclusive sub-nets, it’s best to start simple and work more difficult, not watch YouTube, have someone tell you what to do here, and in a month when a router reboots blame HA because it doesn’t talk to your WIFI plug.
I offered the HA suggested method (at least to start) which is a single Router that you can control and a flat sub-net. I would add a static IP address for the HA instance as well. Get to know that, then add sub-nets and firewall rules.
It very much depends of what of the thousands of available integrations one is using and what technologies are involved - like multicast/unicast mdns etc.
Many pitfalls - specially for not network savy folks
Also many people have simple thoughts like “if I put my random cloud camera on my guest wifi network I improve my privacy” - totally forgetting that the streams/records still is processed/saved on other people computers (cloud )
) 