Does Hub Mesh work across VLAN’s?

🛎️ Get Help
1

So I was thinking of moving one of my hubs out of my IoT VLAN, as I’ve discovered you can’t pair Hubitat to a matter device connected to a HomePod mini that is on a different VLAN.

So the question is, Does Hub Mesh work across VLAN’s?

If not, it looks like I’ll be reorganising my network again. :man_facepalming:

2

I have devices paired with a HomePod Mini on a different VLAN than my Hubitat, It works fine.

1 Like
3

Oh, I tried several times and it just never connected. I assumed it was due to the VLAN. That said, my Hubitat hubs have full access to the VLAN my HomePod’s are on, but not the other way around - maybe that is the issue. :thinking:

2 Likes
4

If you have a shared mDNS domain, I would expect it to work fine. You can accomplish this either by forwarding multicast between the VLANS or by using Avahi.

1 Like
5

I don’t think my router allows for multicast forwarding between VLAN’s, so I think I’ll just make sure my HomePods can reach my hubs.

6

What are you using to connect your VLANs?

7

A Synology RT6600ax router and firewall rules.

8

Hmm, I expressly allowed my HomePods to talk to my IoT VLAN, but I get the same result, homekit says pairing worked:

IMG_1179
IMG_11791179×448 58.9 KB

But Hubitat fails to finish the process:

IMG_1178
IMG_11781179×487 98.2 KB

I’m thinking it’s time to simplify my network - I had created the IoT VLAN originally so I could have my stupid LIFX bulbs on a 2.4Ghz only SSID, and then found out I had to move my hubs to that VLAN for them to see the stupid LIFX bulbs. :weary:

1 Like
9

1000016387
1000016387796×686 75.7 KB

1 Like
10

Hehe, yep!

I also tried removing it from HomeKit, pairing it to the Tapo app, updating the firmware, removing it from the tapo app, pairing it to HomeKit, and then tied pairing it to Hubitat. And I got the same result - I just cant get past the "SendNOC" stage. :frowning:

1 Like
11

I was about to share the bulb from HomeKit with my echo’s via matter, but Hubitat is still being stubborn. :weary:

Edit: reading up on one of the other threads, I don’t think I have IPv6 enabled, so I’ll try that and see what happens.

12

Ok, I turned on IPv6 and assigned the same subnet to each vlan and it still failed to pair. Looks like I’ll be rebuilding my network again. :weary:

13

Have you tried adding the subnet to the hub, I.e.:
http://<yourHubIP>/hub/allowSubnets?123.123.123.0,124.124.124.0

2 Likes
14

Honestly, I didn’t know that was possible, I’m going to try it now. :+1:t2:

15

Hmmm, I’m not sure if I’m doing it right - my hub is in 0.0 and my main subnet is 1.0

http://192.168.0.100/hub/allowSubnets?192.168.1.0,192.168.0.0

16

That should give the hub visibility, make sure to do it on all hubs in the mesh.

1 Like
17

Cheers, I’ll try moving one of my hubs tomorrow.

1 Like
18

You, sir, are an absolute legend! :ok_hand:

It freaking works!!! :scream:

SCR-20240708-isal
SCR-20240708-isal1085×455 36.4 KB

@bobbyD Why is this sort of thing not documented? When I searched for VLAN in the Doco yesterday, I got zero results.

SCR-20240708-itec
SCR-20240708-itec2002×613 74.1 KB

3 Likes
19

Argh, even after moving my primary Hub back into my main VLAN, I still cant get past the "SendNOC" part of the process. Anyone got any ideas?

20

NVM, one more hard reset and I was able to get it to pair to HomeKit, and then Hubitat! Huzzah! :tada:

1 Like