millerduck
New Around Here
So, everything was fine until yesterday and then I had to turn off the breaker for some work to get done on the house. Upon power-up all kinds of issues with the Nest Guard not connecting.
3 nodes, Ethernet backhaul, AiMesh Router Mode, 5GHz SmartConnect with 1 SSID for 5-1/5-2, 1 SSID for 2.4 & 1 SSID for dedicated Nest 2.4 Guest network.
I have a dedicated 2.4GHz "Sync to AiMesh Node:Router-Only" guest network that I am using for my older Nest items (Guard, Connect, Protects).
Firmware version is 3.0.0.4.386_45898.
I have completely restarted the router, cable modem, and all Nest items on this dedicated network, no change in the behavior.
Restarting the Nest guard gets it online for a period of time. Then it goes offline, after the following system log entries (it was reporting itself online until the 18:05:28 events):
Oct 29 17:55:13 kernel: 18:B4:30:3E:06:51 not mesh client, can't delete it
Oct 29 17:58:14 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 17:58:14 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 17:58:29 wlceventd: wlceventd_proc_event(527): wl0.1: Auth 18:B4:30:3E:06:51, status: Successful (0), rssi:0
Oct 29 17:58:29 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc 18:B4:30:3E:06:51, status: Successful (0), rssi:-60
Oct 29 18:03:10 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:03:10 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:03:25 wlceventd: wlceventd_proc_event(527): wl0.1: Auth 18:B4:30:3E:06:51, status: Successful (0), rssi:0
Oct 29 18:03:25 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc 18:B4:30:3E:06:51, status: Successful (0), rssi:-62
Oct 29 18:05:16 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:05:16 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:05:28 wlceventd: wlceventd_proc_event(527): wl0.1: Auth 18:B4:30:3E:06:51, status: Successful (0), rssi:0
Oct 29 18:05:28 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc 18:B4:30:3E:06:51, status: Successful (0), rssi:-65
Any ideas? I am this close to throwing it through a window. Especially frustrating as it had been working rock solid on this firmware and config for a couple of weeks.
Thanks in advance,
MD
3 nodes, Ethernet backhaul, AiMesh Router Mode, 5GHz SmartConnect with 1 SSID for 5-1/5-2, 1 SSID for 2.4 & 1 SSID for dedicated Nest 2.4 Guest network.
I have a dedicated 2.4GHz "Sync to AiMesh Node:Router-Only" guest network that I am using for my older Nest items (Guard, Connect, Protects).
Firmware version is 3.0.0.4.386_45898.
I have completely restarted the router, cable modem, and all Nest items on this dedicated network, no change in the behavior.
Restarting the Nest guard gets it online for a period of time. Then it goes offline, after the following system log entries (it was reporting itself online until the 18:05:28 events):
Oct 29 17:55:13 kernel: 18:B4:30:3E:06:51 not mesh client, can't delete it
Oct 29 17:58:14 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 17:58:14 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 17:58:29 wlceventd: wlceventd_proc_event(527): wl0.1: Auth 18:B4:30:3E:06:51, status: Successful (0), rssi:0
Oct 29 17:58:29 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc 18:B4:30:3E:06:51, status: Successful (0), rssi:-60
Oct 29 18:03:10 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:03:10 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:03:25 wlceventd: wlceventd_proc_event(527): wl0.1: Auth 18:B4:30:3E:06:51, status: Successful (0), rssi:0
Oct 29 18:03:25 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc 18:B4:30:3E:06:51, status: Successful (0), rssi:-62
Oct 29 18:05:16 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:05:16 wlceventd: wlceventd_proc_event(508): wl0.1: Disassoc 18:B4:30:3E:06:51, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 29 18:05:28 wlceventd: wlceventd_proc_event(527): wl0.1: Auth 18:B4:30:3E:06:51, status: Successful (0), rssi:0
Oct 29 18:05:28 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc 18:B4:30:3E:06:51, status: Successful (0), rssi:-65
Any ideas? I am this close to throwing it through a window. Especially frustrating as it had been working rock solid on this firmware and config for a couple of weeks.
Thanks in advance,
MD
