I am using Wifi temperature sensors for quite some time without any issues with an AP6 Pro.
Recently I assigned a different VLAN to that same SSID and since then all of those sensors are unable to connect to that SSID.
Every other device has no trouble connecting to that specific VLAN assigned SSID.
Once I switch back to default VLAN1, the temperature sensors are connecting again.
Without expecting any healing I tried resetting the sensors as well but obviously that didn’t fix the issue.
How is that even possible?
I was always thinking that SSID assigned VLANs are not even visible to the client device? Am I wrong or what could be happening?
I just realize I should try again with network type “Standard” instead of “IOT” in case this could make a difference to some devices in with non default VLAN.
Will try that once possible.
But just for my understanding, clients do not know about any SSID assigned VLANs at all, is that correct?
You need to ensure that your VLANs are configured in your network as well, not only on your SSID.
Clients, by default, don’t know about the VLAN they are in. They can know, if you have a smart enough client, but in 99% cases you will not have a client who tags any VLAN on its own.
To pass VLAN traffic across a switch, tag the ports with the VLAN where it’s allowed to send that data. If no ports are tagged with that VLAN, it doesn’t have any ports to travel through.
All of my other devices work fine with that VLAN assigned SSID, getting coresponding IP/subnet of that specific VLAN, but the Tuya’s - nope.
My conclusion is, this does not seem to be an issue with VLAN at all, since the thermometers just not accept a different IP, not even in the default VLAN when forcing .42 instead of the DHCP assigned .40
They are just stuck on whatever IP they first got.
This thread has been automatically closed due to inactivity. If you believe you have the same issue, please create a new post describing your issue. Feel free to link to this post for context if desired.
