06-02-2023 07:13 AM
Hi,
I have two EnGenius ENG5000 IoT APs that I'm using to expand network connectivity in my home using the WDS feature. The AP1 is connected using the bridge mode (cable connected on one of the LAN ports and having disabled the DHCP server) to a pfSense server which provided the Internet connection. The AP2 is on the second floor without cable, just using the WDS link. Same SSIDs on both APs (different name for each frequency of course).
The "roaming" feature using WDS works perfectly and devices, especially smartphones, can connect to the closest AP when walking around the house and have always a stable and full connectivity to Internet.
But let's put the following scenario:
- Smartphone X is connected (roamed) to AP1, because I went down to the kitchen for water
- Chromecast Y is connected to AP2, because my room is closer to that AP
- I want to cast PrimeVideo from my Smartphone X to Chromecast Y as soon as I get back to my room
At this moment, I'm not able to do it, because, although both devices are connected to the same SSID, I cannot see my Chromecast listed on my smartphone "Cast to device" window. I have to reconnect my smartphone's WiFi to let it choose the same, and closest, AP the Chromecast is connected too.
Also when this happens I can see on Home app, under Chromecast settings, a warning message that the Chromecast is "connected to a different network and some configurations may not be available". This warning goes away as soon as I connect to the same AP the Chromecast is.
Is there a way to fix this? APs are not isolated so this shouldn't happen. It seems that the Chromecasts (and also Nest speakers) detects the MAC of the BSSID and "thinks" they are on a different AP, though they are on the same SSID and same network because using the WDS link.
Regards,
06-06-2023 01:16 PM
Unfortunately, there's no a solution for this. I had to change my WiFi solution for a mesh solution and everything is now working. I think there's no way to "convince" the IoT devices that, though different SSID MAC address, it was the same WiFi. You may close this thread now.
06-06-2023 07:01 PM
Hi macfusbluer,
Thanks for posting here in the Google Nest Community. The Chromecast device is intended to work on a regular home Wi-Fi setup (simple WLAN and non complex). Based on your description, it may not be as simple as it is expected to be. But I’m glad that this has finally been sorted out. I’ll keep this thread open for one more day. Feel free to open up a new thread if you need assistance.
Cheers,
Kimy