Dyson Fans won’t connect to Asus WiFi?

[degrub]

Would the BE-96U have anything like that enabled by default?

I did end up getting it to connect to my “main” network after plugging in my old AX-88U and setting that as an AiMesh node. Both Dyson fans connect and are automatically routed to the AiMesh node, even though one has line of site to the main BE-96U.

I guess that works for now. Probably means I can’t buy a second BE-96U if I want these to work . They are controlled via Homebridge so I need them on the same LAN/subnet as the controlling Raspberry Pi to be able to communicate/send commands. The pi is behind a downstream network switch so I can’t use the VLAN configuration really in the Asus router without moving the Pi.

I was able to get communication between the main subnet and the /52 (guest) subnet by disabling the router’s firewall, but I really don’t think I want to do that. It doesn’t seem there is any way to manually punch that hole without Merlin/YazFi.

Unless you have another router with an active firewall between it and the internet, don't do that !!!

 

[bennor]

... by disabling the router’s firewall ...

Yeah don't do that unless you have another router (with active firewall) between the RT-BE96U and the internet.

Unless I missed it, are you running stock Asus firmware or Asus-Merlin firmware? YazFi likely won't work in its current form on Asus-Merlin 3006.102.x firmware.
You may want to post your IoT/Guest Network Pro settings, redacting any sensitive information. Its possible how it's configured is the cause.
Try using Customized Network, if you haven't done so already, rather than IoT. Customized Network may provide more configuration options than IoT.
Some WiFi devices may have trouble if you use WPA2/WPA3 authentication. You may have to set it to only WPA2. And some may have issues if you used the 2.4Ghz/5Ghz wifi option. May have to separate it out to two individual bans.
Have you configured the Guest Network Pro to use a custom DNS like Pi-Hole or some other DNS server?
Is the Guest Network Pro option Use same subnet as main network enabled or disabled?
Unfortunately 3006.102.x firmware's Guest Network Pro has a number of quirks and issues.

 

[soccerjoshj07]

Yeah don't do that unless you have another router (with active firewall) between the RT-BE96U and the internet.

Unless I missed it, are you running stock Asus firmware or Asus-Merlin firmware? YazFi likely won't work in its current form on Asus-Merlin 3006.102.x firmware.
You may want to post your IoT/Guest Network Pro settings, redacting any sensitive information. Its possible how it's configured is the cause.
Try using Customized Network, if you haven't done so already, rather than IoT. Customized Network may provide more configuration options than IoT.
Some WiFi devices may have trouble if you use WPA2/WPA3 authentication. You may have to set it to only WPA2. And some may have issues if you used the 2.4Ghz/5Ghz wifi option. May have to separate it out to two individual bans.
Have you configured the Guest Network Pro to use a custom DNS like Pi-Hole or some other DNS server?
Is the Guest Network Pro option Use same subnet as main network enabled or disabled?
Unfortunately 3006.102.x firmware's Guest Network Pro has a number of quirks and issues.

My setup:

• Stock ASUS firmware 3.0.0.6.102_37038 on BE96U
• I did try both an “IOT” network and a “guest” network.
  • I was only able to get it to connect to an “IOT” network with the “use the same subnet as main network” switched off - it created a network with the VLAN address 52.
  • AP isolation off
  • WPA2-personal only (but good call on double checking to verify that)
  • Broadcasting 2.4GHz only
  • It did not connect to an IOT or Guest network that ran on the main subnet.
  • I tried creating a different IOT network other than default since it sounded like the default IOT network can be buggy, and same result.
  • No special DNS configuration
  • I don’t think any other settings to note - WiFi 7 mode turned off of course.
• Ironically I have 1 Dyson HP01 that connected to any network no problem. It’s my 2 theoretically newer HP04’s that are the issue. Just weird that it only wants to connect with the IOT network on a diff subnet.

Appreciate the help troubleshooting!

Unless you have another router with an active firewall between it and the internet, don't do that !!!

Definitely not! I did notice that, before I factory reset last time, disabling firewall let me connect between subnets, and then when re-enabled firewall it still let me communicate. Seems like a bug so I just factory reset and started over since I was experimenting with a few other settings too.