Dyson Fans won’t connect to Asus WiFi?

[Poseidon]

I have 3 Dyson cooling fans (TP12) in my house and are 3 were successfully connected to the IoT guest wireless network in my Asus Rog GT-BE98 Pro.

However this weekend all 3 fans stopped connecting to WiFi. I reset the network connection in the fans and tried to reconnect but the connection is TIMING OUT each time and unable to connect. This is happening on all 3 fans.

Previously my 5 GHz SSID would appear under available networks but all I’m seeing now is the IoT guest network and the 2.5 GHz. Tried connecting to both and no luck.

I’ve rebooted my modem and router and also unplugged the fans to no avail.

Could a recent Asus firmware update possibly changed a previous setting or should I adjust sobering under the “professional” tab? Not sure how to get the fans to connect to WiFi again so I can use them via the Dyson app.

Thanks.

 

[degrub]

Is the channel select set to AUTO in the Asus for either/both of the 2.4 GHz and 5 GHz ?
If you update firmware, cleanest method is to factory reset and manually configure. Uploading a backup config can lead to issues.
Don't mess with the PRO pages unless you know what you are doing. IOTs are pretty simple devices.

 

[OzarkEdge]

I have 3 Dyson cooling fans (TP12) in my house and are 3 were successfully connected to the IoT guest wireless network in my Asus Rog GT-BE98 Pro.

However this weekend all 3 fans stopped connecting to WiFi. I reset the network connection in the fans and tried to reconnect but the connection is TIMING OUT each time and unable to connect. This is happening on all 3 fans.

Previously my 5 GHz SSID would appear under available networks but all I’m seeing now is the IoT guest network and the 2.5 GHz. Tried connecting to both and no luck.

I’ve rebooted my modem and router and also unplugged the fans to no avail.

Could a recent Asus firmware update possibly changed a previous setting or should I adjust sobering under the “professional” tab? Not sure how to get the fans to connect to WiFi again so I can use them via the Dyson app.

Thanks.

Where are you viewing 'available networks'?... on the client?

Do your devices support the current 5.0 control channel? If not, they won't see the 5.0 WLAN/SSID.

OE

 

[Poseidon]

Is the channel select set to AUTO in the Asus for either/both of the 2.4 GHz and 5 GHz ?
If you update firmware, cleanest method is to factory reset and manually configure. Uploading a backup config can lead to issues.
Don't mess with the PRO pages unless you know what you are doing. IOTs are pretty simple devices.

Yes the channel select are set to “auto” and yes I did perform a factory reset after the latest firmware update.

Should I select a channel manually instead of auto?

 

[Poseidon]

Where are you viewing 'available networks'?... on the client?

Do your devices support the current 5.0 control channel? If not, they won't see the 5.0 WLAN/SSID.

OE

Yes on the client (Dyson app). I previously connected to 5GHz before. Now it’s not even showing up under “available networks.”

 

[OzarkEdge]

Yes on the client (Dyson app). I previously connected to 5GHz before. Now it’s not even showing up under “available networks.”

Set the 5.0 channel to 36 and see what happens.

OE

 

[degrub]

Yes the channel select are set to “auto” and yes I did perform a factory reset after the latest firmware update.

Should I select a channel manually instead of auto?

Yes, at least for troubleshooting. And verify at each client that they see adequate signal on whichever bands they are using.
You can use an app called Airport Utility on a phone or ipad. Similar is available for android. Check signal strength at each location and any interference from neighbors so that you pick a reasonably no crowded band, particularly on 2.4 GHz.

 

[Poseidon]

Performed another factory reset and was able to connect to IoT network again. Still can’t see the 5GHz wireless network though. Even manually selected different channels and rebooted router but still not showing up under available networks (when it previously did a while back).

Assuming it has to do with the WPA 2/3 security setting. Maybe I’m wrong but can’t think of another reason.

 

[degrub]

If that is the case, try setting security to WPA2 only. Reboot

 

[degrub]

BTW, i tried searching for that product on Dyson.com and could not find it. Does the product manual / quick start give any indication of the requirements for wireless ?

 

[OzarkEdge]

Assuming it has to do with the WPA 2/3 security setting. Maybe I’m wrong but can’t think of another reason.

The Authentication Method affects authentication, not the 'visibility' of the WLAN. You should still be able to 'see' the WLAN.

OE

 

[Dd852]

I had exactly this problem too — my Dysons couldn't see my network after the firmware update. I fixed it by — 1/unplugging the Dysons (not just turning off) rebooting the router and plugging the Dysons back in. All three of mine are connected again.

 

[Poseidon]

BTW, i tried searching for that product on Dyson.com and could not find it. Does the product manual / quick start give any indication of the requirements for wireless ?

TP09. Not 12. Typo on my end. Sorry

 

[Kingp1n]

I had a similar issue with my Dyson device, try this:

Rog Rapture GT-AX6000: IoT devices continuosly disconnected

Hello everyone, First post here, but I've read a lot of this forum over the last 3 years. I'm having a problem with my Rog Rapture GT-AX6000 (latest Merlin firmware 3004.388.8_2, but also with previous firmware the behaviour was the same), with some of my IoT devices: Amazon Blink Cam (2 mini...

www.snbforums.com

 

[soccerjoshj07]

Sorry to bump an old thread but have been configuring a new RT-BE96U.

For some reason, I can only get it to connect to my “guest” network I created that uses a different subnet, not the default IoT network that was created automatically when configuring the router.

It won’t connect to a guest network sharing the same subnet as primary either.

I’ve tried tweaking all of the recommended 2.4ghz settings for compatibility (universal beam forming, turning off WiFi 7 and WiFi 6, airtime fairness)

I have 2 Dyson fans that I won’t connect.

 

[Ripshod]

Remove the IoT network then make it again. In my own experience these IoT networks built on the initial boot of the router are prone to failures.
Make a VLAN network for IoT, then add VPN via VPN Director (if that's what you want).

RT-BE88U everything going over VPN.

Got this today and immediately installed Merlin 3001.102.3. Initial setup has gone very well, as well as adding my normal lineup of addons. 5 devices are currently connected on the IoT network with VPN activated, yet absolutely everything is going through the vpn. Have I missed something, a...

www.snbforums.com

 

[soccerjoshj07]

Remove the IoT network then make it again. In my own experience these IoT networks built on the initial boot of the router are prone to failures.
Make a VLAN network for IoT, then add VPN via VPN Director (if that's what you want).

RT-BE88U everything going over VPN.

Got this today and immediately installed Merlin 3001.102.3. Initial setup has gone very well, as well as adding my normal lineup of addons. 5 devices are currently connected on the IoT network with VPN activated, yet absolutely everything is going through the vpn. Have I missed something, a...

www.snbforums.com

Just tried that - same result! I can’t get the Dyson fans (HP04 so should be capable of 5ghz) to connect to any network I create (IoT, Guest, etc. besides the SSID that uses a different subnet/VLAN address. I suppose that’s fine but just seems really weird.

 

[Tech9]

Don't know about Dyson products, but some IoT devices will refuse to work properly with DNS encryption and/or DNS interception and redirection. Not connecting to the network at all is perhaps different issue.

 

[soccerjoshj07]

Don't know about Dyson products, but some IoT devices will refuse to work properly with DNS encryption and/or DNS interception and redirection. Not connecting to the network at all is perhaps different issue.

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.

 

[Tech9]

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

No.