What's new

Smart Life Device Keeps Disconnecting Daily

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

techdiver

Occasional Visitor
Hi,

I have an RT-AC86U as my main mode and 3 other nodes connected in mesh. I recently bought some bulbs that connect using the Smart Life app. Setting up was fine and everything worked correctly. What I have noticed that every morning they have been disconnected in both the app and Alexa cannot see them any more either.

I had previously had similar issues with smart plugs but it was more infrequent and a power cycle of the device would solve the issue. The difference here is this smart bulb will never reconnected even after the power being turned off to it.

The only way to fix it is to bounce the router (or as I found a more elegant way of just disabling/enabling the 2.4Ghz band). So it seems to me the issue is on the router side.

I have checked the logs and the issues start happening when I see this in the logs:

Code:
Mar 31 04:34:06 RT-AC86U-8FC8-A87D544-C kernel: 50:8B:B9:65:7A:BB not mesh client, can't delete it
Mar 31 04:38:03 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(511): eth5: Disassoc 50:8B:B9:65:7A:BB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 31 04:38:03 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 04:38:04 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind 50:8B:B9:65:7A:BB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 31 04:38:04 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 04:38:04 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 04:38:05 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 04:38:06 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 04:38:16 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0

We then get this repeated in the logs every minute until I either bounce the router or the wifi band:


Code:
Mar 31 11:50:46 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 11:50:46 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind 50:8B:B9:65:7A:BB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 31 11:50:46 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 11:50:47 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 11:50:48 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 11:50:49 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0

Once I bounce the wifi or router those log entries stop and the device is connected fine.

I have tried many troubleshooting steps that I have found online. I set a mac reservation for the device, disabled (Enable WMM APSD), but once again today the same issue that required the wifi to be bounced.

I did notice in the logs before the entry above where it failed to reconnect that there were a few successful cycles of it connecting:

Code:
Mar 31 00:07:25 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 00:07:25 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(559): eth5: Assoc 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 00:07:26 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPDISCOVER(br0) 50:8b:b9:65:7a:bb
Mar 31 00:07:26 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPOFFER(br0) 192.168.1.11 50:8b:b9:65:7a:bb
Mar 31 00:07:26 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPREQUEST(br0) 192.168.1.11 50:8b:b9:65:7a:bb
Mar 31 00:07:26 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPACK(br0) 192.168.1.11 50:8b:b9:65:7a:bb
Mar 31 00:07:26 RT-AC86U-8FC8-A87D544-C kernel: 50:8B:B9:65:7A:BB not mesh client, can't update it's ip
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(511): eth5: Disassoc 50:8B:B9:65:7A:BB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(530): eth5: Auth 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C wlceventd: wlceventd_proc_event(559): eth5: Assoc 50:8B:B9:65:7A:BB, status: Successful (0), rssi:0
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPDISCOVER(br0) 50:8b:b9:65:7a:bb
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPOFFER(br0) 192.168.1.11 50:8b:b9:65:7a:bb
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPREQUEST(br0) 192.168.1.11 50:8b:b9:65:7a:bb
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C dnsmasq-dhcp[21616]: DHCPACK(br0) 192.168.1.11 50:8b:b9:65:7a:bb
Mar 31 00:07:51 RT-AC86U-8FC8-A87D544-C kernel: 50:8B:B9:65:7A:BB not mesh client, can't update it's ip

Is there anything else to try as I've an out of ideas at this point.
 
Last edited:
An update on this. I had read elsewhere that adding these devices to the guest wifi network can help stop issues. I reluctantly did so and it actually seems to have worked. I added the device to the 2.4Ghz guest network and now everything is stable 2 days later.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top