My setup was rock solid prior to the switch. Only real issues where if I was playing around and did something wrong.
I recently changed my home network setup from ISP-provided eero to Ubiquiti (UDM Pro, switch, AP AC Pro). I did set up VLANs for IoT and separated everything out manually as I used the same SSID/password combo to not have to reconnect everything. My phone and unraid server where I host HA are both currently on the IoT network, so that shouldn’t be an issue. (Phone will be on a Trusted network most often)
I can see that the bulbs are connected to WiFi, most with good connection, but I can’t control them via HA or HomeKit. I did reconnect one bulb after they went unavailable for the third time; it’s unavailable as well. I’m not really sure where to go from here for troubleshooting. It doesn’t look like reconnecting is going to help, but maybe I need to do a separate SSID and give it enhanced IoT connectivity, then reconnect everything?
Things I’ve tried:
Just power cycled a single bulb (the one I reconnected) and still unavailable.
Cycled HA & matter server the other day a that didn’t do anything either.
Force restarting the AP has worked to get most everything back online. But they’re going unavailable more often than every 24 hours and I obviously won’t be rebooting my AP nightly. (This makes me think it’s the AP’s fault and I’m thinking about buying a U6 pro instead of the used AC Pro I grabbed off eBay for $40)
Would appreciate any advice. I can give details on what my setup is, just not sure what would be helpful up front
Your network setup is unclear. This is relevant info.
Matter may need IPv6 so it should be enabled.
Likely mdns needed so your vlans may cause trouble with that.
And JA and matter server should be able to access matter devices vlan
You should not use VLANs because you have clearly not the knowledge to do so.
VLANs require you to understand all the protocols of the devices that needs to be routed between them.
That among other things means all the unroutable discovery protocols and how they interact with both IPv4 and IPv6.
IPv6 is also something you need to understand really good and your IPv4 knowledge is not really useful.
IPv6 likely hasn’t been enabled, so I’ll start there. (And reading more about matter makes me think this is definitely the issue)
mDNS was on by default.
HA/matter server are both being ran on an Unraid server (does have IPv6 enabled too) that is connected to my switch that natively sends IoT network.
As far as what the whole setup looks like, it’s IPv4 (I don’t believe my ISP offers IPv6 WAN). I have 7 VLANs - default, trusted for my personal stuff, cameras (no internet access), work for work laptop, shared for my Apple TVs and a printer when I get one (allow guest VLAN to connect over to airplay/print), IoT, guest. Trusted can talk to everything, IoT can respond to Trusted & talk to cameras (running Scrypted on my unraid server too). I’m still trying to nail everything down, but I think Ubiquiti tries to streamline it a bit too.
why? I use vlans and I question the justification I use for doing this. 7 vlans is crazy.
trusted. nothing is trusted. ever. I understand it as a naming concept but from a logical standpoint. nothing should be trusted. I wouldnt use the name as it comforts you into doing just that, “trusting”
camera and IOT. both dont need internet or even lan access. camera does not need access to LAN. a device on LAN needs to access it. same with most IOT devices. If an IOT devices needs internet access, expect it to cause you problems and be the source of your issues.
Printer. needs mdns. if you can get that working it doesnt need internet or lan. well, if your scanning to ftp maybe lan but that can be single allow
Guests. this is always hard. its worse than IOT.
apple tv / streaming media players are guests. whatever you figure out for guest is probabIy what you do for these
main: basically network gear and servers
iot: no wan/lan access. limited access to server(cant think of need for this) on case by case. esphome device, camera, iot devices
guest: guest devices, streaming players. geoblocked, log, has WAN but no LAN. limited access to servers (jellyfin for example)
you can do all the above using IP address blocks and firewall rules without the added headache of broken mdns and other issues.
Matter is designed to work in a flat network and runs off of ipV6.
Segmented networks are not officially supported within HA.
HA is designed and expects a flat subnet to work as intended.
Just learn about firewall rules and subnet masks and use them instead of VLANS otherwise you will get nothing but pain.
This is because every segmented network is different for IP’s and number of segments and firewalls and sharing rules and about 650495849085 other things.
This does not mean you can’t use them or that they can’t be made to work, it means that to get them working you are the support structure on your own subnet(s). Consider it Advanced mode…
Your assumption is wrong.
You talk they can talk to everything, but there are a lot of protocols that are not routable with standard IP routing and those protocols needs to handled too.
