thegios
Regular Contributor
I have a fiber modem from my carrier and a dual node XT8 mesh system. Node 1 WAN port is connected to one of the modem LAN port. Node 2 is connected to node 1 through dedicated wireless backbone. Only one SSID.
I am trying to troubleshoot what happens to my phone (MAC 6E:F1:74:5D:46:72) because recently Google Home presence sensing is going havoc.
Let me explain... I have a Nest Camera (made by Google) that is suppoosed to be automatically turned on or off depending if no one is at home or at least one is at home.
Both myself and my wife have the Google Home app where both phones are registered for presence sensing.
Presence sensing is using GPS LOCATION and WIFI CONNECTION: a phone is considered at home is either within the home's addess geofencing or connected to the home registered wifi network.
For the phone to be considered as away (not at home) both geofencing and wifi connection must fail. BOTH!
Recently the Google Home app has been detecting, a few times per day, my phone as being away. ONLY MY PHONE, not my wife's.
Now the probability that a few times per day, for my phone only, both geofencing and wifi connectioin fail at the same time is almost null.
By sending the logs to Google they answered back that the logs for the times I noted the problematic location point to an "unstable connection" being the root cause. They found my location rapidly entering and exiting the mome geofence while my Wi-Fi connection is quickly disconnecting and reconnecting.
Again, I doubt that both conditions may fail AT THE SAME TIME and A FEW TIMES PER DAY, yet I decided to have a look at the modem logs.
This morning I woke up and looked at the Google Home app action history and found out that tonight my phone was detected as away at 01:05 and at home again at 01:11.
In the logs this is all I found about my phone's MAC between 11:04 and 11:13
Dec 6 01:04:17 wlceventd: wlceventd_proc_event(662): eth5: Disassoc 6E:F1:74:5D:46:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 6 01:04:17 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind 6E:F1:74:5D:46:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Dec 6 01:04:20 kernel: Can't add zero mac!
...
Dec 6 01:05:43 wlceventd: wlceventd_proc_event(685): eth5: Auth 6E:F1:74:5D:46:72, status: Successful (0), rssi:0
Dec 6 01:05:43 wlceventd: wlceventd_proc_event(722): eth5: Assoc 6E:F1:74:5D:46:72, status: Successful (0), rssi:-70
Dec 6 01:05:43 kernel: Can't add zero mac!
...
Dec 6 01:07:12 roamast: determine candidate node [6A:BF:B8:26
7:11](rssi: -56dbm) for client [6E:F1:74:5D:46:72](rssi: -67dbm from client)(rssi: -71dbm from ap) to roam
Dec 6 01:07:12 roamast: Roam a client [6E:F1:74:5D:46:72], status [0]
Dec 6 01:07:19 kernel: Can't add zero mac!
...
Could someone explain what this means?
Does this mean my phone is kicked out of the wifi at 01:04 and back in at 11:05?
And what happens instead at 11:07?
What does "cant add zero mac" mean?
Also, I still do not believe that disconnection from home wifi is the REAL problem for the wrong location detection of my phone by the Google Home app, for two reasons
1- if phone disconnects from wifi, tehre is still the GPS geofencing (and again, it's almost impossible that gps fails at the same time many times per day)
2- if I configure presence sensing to use only GPS geofencing (so, no wifi) the problem still happens
Any help, suggestion, tip would be very much appreciated
I am trying to troubleshoot what happens to my phone (MAC 6E:F1:74:5D:46:72) because recently Google Home presence sensing is going havoc.
Let me explain... I have a Nest Camera (made by Google) that is suppoosed to be automatically turned on or off depending if no one is at home or at least one is at home.
Both myself and my wife have the Google Home app where both phones are registered for presence sensing.
Presence sensing is using GPS LOCATION and WIFI CONNECTION: a phone is considered at home is either within the home's addess geofencing or connected to the home registered wifi network.
For the phone to be considered as away (not at home) both geofencing and wifi connection must fail. BOTH!
Recently the Google Home app has been detecting, a few times per day, my phone as being away. ONLY MY PHONE, not my wife's.
Now the probability that a few times per day, for my phone only, both geofencing and wifi connectioin fail at the same time is almost null.
By sending the logs to Google they answered back that the logs for the times I noted the problematic location point to an "unstable connection" being the root cause. They found my location rapidly entering and exiting the mome geofence while my Wi-Fi connection is quickly disconnecting and reconnecting.
Again, I doubt that both conditions may fail AT THE SAME TIME and A FEW TIMES PER DAY, yet I decided to have a look at the modem logs.
This morning I woke up and looked at the Google Home app action history and found out that tonight my phone was detected as away at 01:05 and at home again at 01:11.
In the logs this is all I found about my phone's MAC between 11:04 and 11:13
Dec 6 01:04:17 wlceventd: wlceventd_proc_event(662): eth5: Disassoc 6E:F1:74:5D:46:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 6 01:04:17 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind 6E:F1:74:5D:46:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Dec 6 01:04:20 kernel: Can't add zero mac!
...
Dec 6 01:05:43 wlceventd: wlceventd_proc_event(685): eth5: Auth 6E:F1:74:5D:46:72, status: Successful (0), rssi:0
Dec 6 01:05:43 wlceventd: wlceventd_proc_event(722): eth5: Assoc 6E:F1:74:5D:46:72, status: Successful (0), rssi:-70
Dec 6 01:05:43 kernel: Can't add zero mac!
...
Dec 6 01:07:12 roamast: determine candidate node [6A:BF:B8:26
7:11](rssi: -56dbm) for client [6E:F1:74:5D:46:72](rssi: -67dbm from client)(rssi: -71dbm from ap) to roamDec 6 01:07:12 roamast: Roam a client [6E:F1:74:5D:46:72], status [0]
Dec 6 01:07:19 kernel: Can't add zero mac!
...
Could someone explain what this means?
Does this mean my phone is kicked out of the wifi at 01:04 and back in at 11:05?
And what happens instead at 11:07?
What does "cant add zero mac" mean?
Also, I still do not believe that disconnection from home wifi is the REAL problem for the wrong location detection of my phone by the Google Home app, for two reasons
1- if phone disconnects from wifi, tehre is still the GPS geofencing (and again, it's almost impossible that gps fails at the same time many times per day)
2- if I configure presence sensing to use only GPS geofencing (so, no wifi) the problem still happens
Any help, suggestion, tip would be very much appreciated
