2.4 GHz Network Not Connecting on Main Deco Only
Recently several of my IoT devices stopped connecting. I have the Guest Network setup as 2.4 GHz only with it's own SSID and a simple password which has worked fine up until recently. What I've found after doing some testing is the devices are unable to connect to the Main Deco only. If I move the devices closer to one of the two Satellite Deco's then they connect without any issue. I even tried swapping the Deco's and making one of the Satellite Deco's the Main Deco and vice versa and the same phenomena occurs where the IoT devices are not able to connect to the Main Deco. I used a WiFi Analyzer app and stood close to the Main Deco and can see the Guest WiFi network and the signal is very strong so it is not a signal strength issue. I've had the IoT devices within a foot of the Main Deco and they will not connect. But, if I move to another room, then they'll connect to one of the two Satellite Deco's within a few seconds. I've also turned off Beamforming and Fast Roaming and tried several other suggestions that I've seen on various forums without any luck. Any thoughts?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Definitely an odd behavior, and I can't think of what could cause it. You might reach out to our support teams directly for followup. I have a feeling that diagnosing the behavior may require the devs to see the decos logs.
Are you able to tell if the behavior is the same when you connect a typical device to the guest network, like a phone? What are the devices that you are seeing the behavior with?
All network nodes have a BSSID on top of their SSID which is specific to the node you are connecting to. As these are IoT devices, maybe they are having trouble connecting to a different BSSID. Have you tried to fully reset a device and add the device back to the network closer to the satellite?
- Copy Link
- Report Inappropriate Content
Yes, even when I connect to the Guest network with my phone it will connect to one of the Satellite Decos rather than the Main Deco even if I'm just a few feet away from the Main Deco.
Also, I've reset the IoT devices several times and tried reconnecting them from less than a foot away and they either won't connect at all or will connect with one of the Satellites.
- Copy Link
- Report Inappropriate Content
Here's an excerpt of the log. The MAC of the IoT that I have been experimenting with is E0-98-06-BA-F4-66. It is a Sensibo Sky unit used for controlling a heat pump.
Tue Nov 26 19:12:14 2024 daemon.err udhcpd[14182]: my ntp server ip:69 164 213 136 f03818e4
Tue Nov 26 19:12:14 2024 daemon.err udhcpd[14182]: dhcp offer: add ntp server option
Tue Nov 26 19:12:14 2024 daemon.err udhcpd[14182]: Sending ACK to 192.168.68.53
Tue Nov 26 19:12:14 2024 daemon.err udhcpd[14182]: clear ip 3544a8c0
Tue Nov 26 19:12:18 2024 daemon.err client_mgmt: client(FC-9C-98-05-57-D2) ip has changed:UNKNOWN ===> 192.168.68.69, need to update client table
Tue Nov 26 19:12:20 2024 daemon.err client_mgmt: client(58-66-6D-B3-9A-D0) not found in arp table disconnect_counter=0
Tue Nov 26 19:12:20 2024 daemon.err client_mgmt: client(4C-75-25-18-39-66) not found in arp table disconnect_counter=1
Tue Nov 26 19:12:20 2024 daemon.err client_mgmt: client(44-17-93-2F-3F-4E) not found in arp table disconnect_counter=1
Tue Nov 26 19:12:20 2024 daemon.err client_mgmt: client(FC-9C-98-05-57-D2) not found in arp table disconnect_counter=0
Tue Nov 26 19:12:20 2024 daemon.err client_mgmt: client(44-17-93-2F-36-F2) not found in arp table disconnect_counter=0
Tue Nov 26 19:12:34 2024 daemon.notice nrd[13818]: estimatorPerformMeasurement: Do 11k measurement for 52:B3:83:AB:FB:D8 on channel 40 from serving BSS APId 255 ChanId 40 ESSId 0
Tue Nov 26 19:12:37 2024 daemon.err client_mgmt: mac 52-B3-83-AB-FB-D8 had uploaded
Tue Nov 26 19:12:37 2024 daemon.err client_mgmt: client(E0-98-06-BA-F4-66) not found in arp table disconnect_counter=0
Tue Nov 26 19:12:37 2024 daemon.err client_mgmt: client(4C-75-25-18-39-66) not found in arp table disconnect_counter=2
Tue Nov 26 19:12:37 2024 daemon.err nrd[13818]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 52:B3:83:AB:FB:D8
Tue Nov 26 19:12:38 2024 daemon.err client_mgmt: client(44-17-93-2F-3F-4E) not found in arp table disconnect_counter=2
Tue Nov 26 19:12:38 2024 daemon.err client_mgmt: client(44-17-93-2F-36-F2) not found in arp table disconnect_counter=1
Tue Nov 26 19:12:43 2024 authpriv.info dropbear[30361]: Child connection from 192.168.68.248:57438
Tue Nov 26 19:12:43 2024 authpriv.info dropbear[30362]: Child connection from 192.168.68.248:57440
Tue Nov 26 19:12:43 2024 authpriv.info dropbear[30365]: Child connection from 192.168.68.248:57442
Tue Nov 26 19:12:43 2024 authpriv.notice dropbear[30362]: Pubkey auth succeeded for 'root' with key sha1!! 52:a3:e3:b3:02:49:ea:33:74:98:ec:f7:55:f8:36:53:7f:46:83:84 from 192.168.68.248:57440
Tue Nov 26 19:12:43 2024 authpriv.notice dropbear[30361]: Pubkey auth succeeded for 'root' with key sha1!! 52:a3:e3:b3:02:49:ea:33:74:98:ec:f7:55:f8:36:53:7f:46:83:84 from 192.168.68.248:57438
Tue Nov 26 19:12:43 2024 daemon.info conn-indicator: Event: inet.request
Tue Nov 26 19:12:43 2024 authpriv.notice dropbear[30365]: Pubkey auth succeeded for 'root' with key sha1!! 52:a3:e3:b3:02:49:ea:33:74:98:ec:f7:55:f8:36:53:7f:46:83:84 from 192.168.68.248:57442
Tue Nov 26 19:12:44 2024 authpriv.info dropbear[30362]: Exit (root): Exited normally
Tue Nov 26 19:12:44 2024 daemon.info conn-indicator: Event: inet.request
Tue Nov 26 19:12:44 2024 authpriv.info dropbear[30361]: Exit (root): Error writing: Broken pipe
Tue Nov 26 19:12:44 2024 daemon.info conn-indicator: Event: inet.request
Tue Nov 26 19:12:44 2024 authpriv.info dropbear[30365]: Exit (root): Exited normally
Tue Nov 26 19:12:55 2024 daemon.err client_mgmt: mac 4C-75-25-18-39-66 had uploaded
Tue Nov 26 19:12:55 2024 daemon.err client_mgmt: mac 44-17-93-2F-3F-4E had uploaded
Tue Nov 26 19:12:55 2024 daemon.err client_mgmt: client(52-B3-83-AB-FB-D8) not found in arp table disconnect_counter=0
Tue Nov 26 19:12:55 2024 daemon.err client_mgmt: client(E0-98-06-BA-F4-66) not found in arp table disconnect_counter=1
Tue Nov 26 19:12:59 2024 daemon.notice nrd[13818]: ar_apinfo_collect[line 1107]: AP sync timer expires!
Tue Nov 26 19:13:01 2024 cron.info crond[11460]: crond: USER root pid 30580 cmd sh /usr/sbin/process_monit
Tue Nov 26 19:13:12 2024 daemon.err client_mgmt: client(52-B3-83-AB-FB-D8) not found in arp table disconnect_counter=1
Tue Nov 26 19:13:12 2024 daemon.err client_mgmt: client(E0-98-06-BA-F4-66) not found in arp table disconnect_counter=2
Tue Nov 26 19:13:13 2024 daemon.err client_mgmt: client(FC-9C-98-73-AC-00) not found in arp table disconnect_counter=0
Tue Nov 26 19:13:17 2024 daemon.info hostapd: ath01: STA e0:98:06:ba:f4:66 IEEE 802.11: disassociated
Tue Nov 26 19:13:17 2024 daemon.notice hostapd: ath01: AP-STA-DISCONNECTED e0:98:06:ba:f4:66
Tue Nov 26 19:13:17 2024 daemon.notice nrd[13818]: wlanifLinkEventsCmnGenerateDisassocEvent: Client E0:98:06:BA:F4:66 disassociated on APId 255 ChanId 3 ESSId 1
Tue Nov 26 19:13:17 2024 daemon.notice hostapd: ath01: ubus call client_mgmt access '{"mac":"E0-98-06-BA-F4-66","ifname":"ath01","action":"disassociate"}' &
Tue Nov 26 19:13:17 2024 daemon.notice hostapd: wpa_driver_nl80211_set_key: ifindex=27 (ath01) alg=0 addr=0x557d185970 key_idx=0 set_tx=1 seq_len=0 key_len=0 key_flag=0x20
Tue Nov 26 19:13:17 2024 daemon.notice hostapd: wpa_driver_nl80211_set_key: ifindex=27 (ath01) alg=0 addr=0x557d185970 key_idx=0 set_tx=1 seq_len=0 key_len=0 key_flag=0x20
Tue Nov 26 19:13:17 2024 daemon.err hostapd: hostapd_notif_disassoc num_sta 1
Tue Nov 26 19:13:17 2024 daemon.err hostapd: hostapd_notif_disassoc num_sta== 1 , do wpa_auth_sm_event
Tue Nov 26 19:13:17 2024 daemon.err hostapd: wpa_auth_sm_event do WPA_LAST_STA
Tue Nov 26 19:13:17 2024 daemon.info hostapd: ath01: STA e0:98:06:ba:f4:66 IEEE 802.11: authenticated
Tue Nov 26 19:13:17 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Tue Nov 26 19:13:17 2024 daemon.err client_mgmt: client_mac:E0-98-06-BA-F4-66, client_ifname:ath01, client_action:disassociate
Tue Nov 26 19:13:17 2024 daemon.err client_mgmt: client(E0-98-06-BA-F4-66) disassociate by if(ath01).
Tue Nov 26 19:13:18 2024 daemon.err client_mgmt: client(52-B3-83-AB-FB-D8) not found in arp table disconnect_counter=2
Tue Nov 26 19:13:19 2024 daemon.err client_mgmt: client(58-66-6D-B3-9A-D0) not found in arp table disconnect_counter=0
Tue Nov 26 19:13:19 2024 daemon.err client_mgmt: client(FC-9C-98-73-AC-00) not found in arp table disconnect_counter=1
Tue Nov 26 19:13:20 2024 daemon.info hostapd: ath01: STA e0:98:06:ba:f4:66 IEEE 802.11: disassociated
Tue Nov 26 19:13:20 2024 daemon.err hostapd: hostapd_notif_disassoc num_sta 1
Tue Nov 26 19:13:20 2024 daemon.err hostapd: hostapd_notif_disassoc num_sta== 1 , do wpa_auth_sm_event
Tue Nov 26 19:13:20 2024 daemon.info hostapd: ath01: STA e0:98:06:ba:f4:66 IEEE 802.11: authenticated
Tue Nov 26 19:13:20 2024 daemon.notice nrd[13818]: wlanifLinkEventsCmnGenerateDisassocEvent: Client E0:98:06:BA:F4:66 disassociated on APId 255 ChanId 3 ESSId 1
- Copy Link
- Report Inappropriate Content
Hmmm, those logs I do not think indicate anything significant as they are only indicating that the device is disconnected as it is no longer in the client list.
Looking at the specifications for the device, its Wi-Fi chip is only 802.11b/g/n which Is very old at this point. While it should not be a problem as everything is backwards compatible, it does mean that it wont have any support or consideration for newer features.
For your XE75, i believe that you have received the update adding the IoT network, I would recommend enabling the IoT network and adding your device to that network. The IoT network can be configured to use specific bands, a different (lower) encryption type for improved compatability, and will not isolate the device from your main network by default. Choosing just a 2.4Ghz band with a lower encryption type may allow the device to connect and narrow down the cause
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 145
Replies: 4
Voters 0
No one has voted for it yet.