Possible Zanzito Presence Detection Issue

Archive Zanzito for Android
1

Hi, I’m a bit at a loss here. Since one of the recent hassio updates my log has been spammed with the below (four of many many examples) basically changing my wife and my devices from home to not_home and back repeatedly. I’ve been using Zanzito for a few months and it’s been awesome but recently I noticed presence detection is all over the place. I’m not sure it is a Zanzito problem but when I disable it on either or both of our phones the other device_tracker (Asuswrt) works fine. Tracks location when I’m home and away with no dropouts. As soon as I enable Zanzito it’s back to the constant state changes. Anyone any suggestions, I’m out of options!

2018-03-22 20:32:31 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1915433520: Sending {‘id’: 2, ‘type’: ‘event’, ‘event’: {‘event_type’: ‘state_changed’, ‘data’: {‘entity_id’: ‘device_tracker.galaxys8’, ‘old_state’: <state device_tracker.galaxys8=home; source_type=router, latitude=-redacted, longitude=redacted, gps_accuracy=0, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:01.257014+11:00>, ‘new_state’: <state device_tracker.galaxys8=not_home; source_type=gps, latitude=-redacted, longitude=redacted, gps_accuracy=20, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:31.217277+11:00>}, ‘origin’: ‘LOCAL’, ‘time_fired’: datetime.datetime(2018, 3, 22, 9, 32, 31, 217466, tzinfo=)}}
2018-03-22 20:32:32 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=device_tracker.galaxys8, old_state=<state device_tracker.galaxys8=not_home; source_type=gps, latitude=-redacted, longitude=redacted, gps_accuracy=20, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:31.217277+11:00>, new_state=<state device_tracker.galaxys8=home; source_type=router, latitude=-redacted, longitude=redacted, gps_accuracy=0, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:32.277429+11:00>>
2018-03-22 20:32:32 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1857851728: Sending {‘id’: 2, ‘type’: ‘event’, ‘event’: {‘event_type’: ‘state_changed’, ‘data’: {‘entity_id’: ‘device_tracker.galaxys8’, ‘old_state’: <state device_tracker.galaxys8=not_home; source_type=gps, latitude=-redacted, longitude=redacted, gps_accuracy=20, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:31.217277+11:00>, ‘new_state’: <state device_tracker.galaxys8=home; source_type=router, latitude=-redacted, longitude=redacted, gps_accuracy=0, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:32.277429+11:00>}, ‘origin’: ‘LOCAL’, ‘time_fired’: datetime.datetime(2018, 3, 22, 9, 32, 32, 277601, tzinfo=)}}
2018-03-22 20:32:32 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1915433520: Sending {‘id’: 2, ‘type’: ‘event’, ‘event’: {‘event_type’: ‘state_changed’, ‘data’: {‘entity_id’: ‘device_tracker.galaxys8’, ‘old_state’: <state device_tracker.galaxys8=not_home; source_type=gps, latitude=-redacted, longitude=redacted, gps_accuracy=20, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:31.217277+11:00>, ‘new_state’: <state device_tracker.galaxys8=home; source_type=router, latitude=-redacted, longitude=redacted, gps_accuracy=0, battery=32, friendly_name=Holsa_S8, entity_picture=/local/holsa.jpg @ 2018-03-22T20:32:32.277429+11:00>}, ‘origin’: ‘LOCAL’, ‘time_fired’: datetime.datetime(2018, 3, 22, 9, 32, 32, 277601, tzinfo=)}}

2

A bit more digging and I’m narrowing down the issue a little but it still seems to point to Zanzito although that could just be triggering another issue. I changed my heartbeat settings in Zanzito to 600 seconds and it’s slowed the issue down in the logs to less frequently. I still have instant updates on so I presume that when anything changes i.e. battery reduces or increases it sends an update and that update is somehow changing the device status from router for a second which is then changing the status to not_home?

I’m partly guessing on this but it does appear that that’s what it’s doing. @MrMep, does this sound like it’s Zanzito causing this or something else that the Zanzito update is just triggering?

3

Managed to fix this by deleting the devices from known_devices and a restart then add them back.

Weird one

4

@greybags how are you finding Zanzito? I have totally given up on Owntracks atleast for now.
Owntracks worked perfectly for us (2 iphones) but it all of a sudden became unreliable and since then I have moved to Android and owntracks is garbage on droid. Had Zanzito running bt couldn’t really test it because of demo mode.
cheers

5

Forgive me for jumping in since you asked @greybags, but I too found Owntracks to be unreliable on Android and started using Zanzito about 4 months ago. It works great. The presence detection is really good, plus I like the fact it can monitor my other MQTT channels (like door entry sensors) and speak “Front Door Open”. I paid for the full app as I think its well worth the few dollars.

6

Well I have to say I’ve been using Zanzito for a while after finding Owntracks spotty and have had few complaints. The only issue I ever have is that once a month or so it will revert to demo mode, as if I never purchased. But a phone restart usually clears that up.

7

The demo mode thing has happened to me a few times, but it normally “sorts itself out”

8

@ericleejoe Are you using MQTT with the owntacks profile on Zanzito?

9

I don’t use the Owntracks emulation. My setup just uses Zanzito/GPS and I have Tasker auto connect back to my local network via OpenVPN and Zanzito talks to my MQTT server directly. I am very happy with it. It has me home/not_home correctly 99% of the time.

10

Sorry for the delay in replying. I use it on three different devices and it works great. The zones work perfectly for automations and for notification (“I’m on my way home” when I’m on the bridge sort of thing). My only concern is that the author of the app MrMep seems to have dropped out of sight. No response to a couple of questions I’ve had, which I eventually fixed myself, but for $8 the support is non-existant. If you know what you’re doing and can get support here then go for it, it works great.

1 Like