Adding RT-BE88U guest network messes up Spotify Connect for IOT network devices

[jimmybond009_]

I need help understanding why adding a Guest network on an RT-BE88U would mess up Spotify Connet for devices on the separate IOT network, thanks.

=============
I have an Asus RT-BE88U on up-to-date stock firmware.
It was set up with a main 2.4/5ghz network, along with a separate IOT network at 2.4 (set up as a 'Default IOT Network', shows up under Guest Network PRO)
I had my older Yamaha musiccast devices on IOT since they need 2.4 only (get confused if dual band), and things worked fine and I could use Spotify Connect to send music to them even if my Spotify app was on phone on the main network.

So things were working fine. Then I wanted to to add an actual guest network for visitors, and created one with totally unique SSID. (so now 3: main, IOT, Guest)

After adding this guest network, Spotify Connect would not work to send anything to the Musiccast devices on the IOT network. Even though I did not change any settings/networks on the devices, and Asus router settings showed there were zero devices connected to the Guest network.

Removing the newly added Guest network resolved things >> Spotify Connect worked again to cast to devices on the IOT network.

I am unclear why the new guest network caused issues as it had a totally separate SSID, and the BE88U seems to support having all sorts of networks simultaneously.

Is there some kind of setting I need to toggle so that I can have a separate guest network AND IOT network, and not end up with Spotify Connect issues for devices on the IOT network?

(Note: I already have Enable IGMP Snooping ENABLED which google suggested.)

 

[bennor]

It may help if you post your Guest Network Pro configurations (redacting any sensitive information) to provide context to your setup.

If you search the subforums here you'll see that there are numerous discussions where people experience issues with the Guest Network Pro configuration (across various 3006.102.x supported Asus routers). Common problems are being unable to communicate across different Guest Network Pro profiles. Using Home Assistant (HA) on main LAN with Guest Network Pro clients being unable to access the HA. Guest Network Pro clients being unable to access a media server/device on a different network (either main LAN or Guest Network Pro). And so on.

One may have to change from using the Guest Network Pro IoT profile to using the Custom Network profile. In some cases it means setting the Guest Network Pro profile option Use same subnet as main network to enable when creating the Guest Network Pro profile. Or it may mean enabling the Access Intranet option (if Asus fixed it) on the Guest Network Pro profile. Or it may mean using Asus-Merlin firmware, if one 's router is supported by Asus-Merlin, and setting up custom firewall scripting to pass traffic between Guest Network Pro profiles. There are numerous discussions with respect to Asus-Merlin firmware and trying to pass traffic from the Guest Network Pro profile to other IP subnets on the router.