Device on other vlan

network noob here so please pardon me.

old laptop - HA on hyper V. (no sure which network the HA is, is it tag to the laptop connection)? the laptop is currently connected to the main network.

PC - wired via LAN. i can currently view HA via the ‘local address’.

IOT - in another vlan. this vlan is auto created by asus ax6000 when i created it under the guest network pro. this is where all the devices are.

Problem - HA cant seems to add / find the IOT in another vlan.
if i use the official tuya integration, i can see all the devices and add them. but some of the entities doesnt work.
Therefore, i tried using tuyalocal integration. Despite finding out the ip address of the IOT in the other vlan, i am not able to integration it into HA. i read somewhere that i have to open UDP 6667 and 6668 (which i did in the router webpage via portforwarding), but this doesnt help. am i missing something here?

Similarly, i tried to integrate the philips air purifier. These are on the IOT as well and despite keying in the IP address, it couldnt be integrated. the moment i shift the air purifier to the same network as HA, it work fine.

+ vlan = failure….

Either improve your network skills, or use a flat network (for which HA is designed).

PS: my best guess it goes wrong with multicast DNS, as it is in most cases :wink:

2 Likes

so flat network is what im leaning. thats why i swap the philips to the same network. the problem is, there is this very annoying ir/rf blaster that connects only on 2.4g - it current connect to the IOT 2.4 and REFUSE to connect to the main network 2.4g no matter what i tried. i reduce main network to wireless N, wpa, it just wont connect. i have also resetted the device and no, it just want to only connect to the IOT.

can i fix the multicast dns?

I had some asus router and like you and i started to using vlans on it as it should be vlan capable. But this seems to be only on paper and nothing else.

Can you configure mdns on it? Probably not and this is possible reason why vlans are not working.

You could try this to basiclly hack into your router so you can modify it settings.

But I couldn’t add or modify firewall rules so I had to add custom scripts for it.

At the end of the day all that hassle is not worth it as firmware is partially locked and there is a ton of work to make this work.

I went for openwrt and opnsense as gateway because imho it is much better to invest your time and money in firmware that actually work and dont hide things from you not it is fighting against you.

Usually guest networks are isolated from the rest of the network. You will not be able to talk to devices inside the guest network from outside of it. That’s basically the whole idea behind guest networks.

1 Like

This is sounding like an mDNS issue. Do you have an mDNS service running somewhere to route desired traffic between the vlans? Your opnsense device should have one you can install. On my pfsense it’s called Avahi.

I don’t have a opnsense tho.

You dont have to use opnsense. You can use openwrt. I’m just using it because I don’t want to put all heavy lifting on my main local router using openwrt. I want to distribute part of the load to opnsense router.
But mostly everything you can do in opnsense you can do also on openwrt.