Zanzito - A lightweight bridge between your Android device and your MQTT/home automation system

I have not your problem, will give you my config when back home (but its basic)

@MrMep - Is Zanzito still actively supported? I tried the support forum on your site, but it’s sorta quiet over there. I’m still having the issue with Zanzito increasing the pitch over my settings in Android when using “say MQTT Texts”.

I just set this up as I was getting constant zone enter/leave notifications. Here’s how I did it.

For zone enter:

    - service: mqtt.publish
      data_template:
        topic: "zanzito/homeassistant/set_prefs"
        payload: >-
          {
            "location_high_precision": false
          }

For zone leave:

    - service: mqtt.publish
      data_template:
        topic: "zanzito/homeassistant/set_prefs"
        payload: >-
          {
            "location_high_precision": true
          }

Not sure how well it’s working yet, but worth a shot. Otherwise Zanzito works great (bought the full license) for me entering/leaving zones; it’s just when I idle at home (although I suspect it’s an indoors/outdoors scenario) I get a lot of transition notifications but when I’m driving to work or back home, works like a champ.

2 Likes

Just a follow-up here. This seems to have quieted down the false positive zone transitions for me a fair bit (I still got two since I implemented this) so I’m going to take this a step further and adapt @oakbrad script here:

To see if I can filter out the data some more. I know I can use OwnTracks emulation but I’d prefer not to as I see it as a step backwards (in that, I know I can get this working…)

I may have to break out my device_tracker bits into separate items (ie; ping, gps, etc) as I want to leverage Node-Red here too but first to get things stable (seems to have become a problem for me with 0.67+ in that zone transitioning is very sensitive/touchy…)

@chrisw how is that script working? I’m having similar issues and need to come up with something.

I was able to adapt it - check my script here; working great for me (plenty of views but not sure if anyone has tried it since I posted it…)

1 Like

Thanks. Will check it out this weekend

Will you share your automation please?

Owntracks hasn’t worked that well to me. Location sending was pretty random, it tended to “disappear” from notifications in phones with not a lot of resources, and it was clear that the main app was for iPhone, and Android was more like a last thought.

Zanzito works flawlessly, it’s very low on resources, and it also has a lot of very useful features. It would be wonderful if it was open source, though, I would still pay for it.

Look at the Scripts section for Zanzito GPS Filter - I have the automation there.

Has anyone been able to get current_foreground_app working, looking at the mqtt data it only ever sends Zanzito if im in the app, in any other app an empty string is sent

Zanzito keep closing for me on my Oneplus 5 running Android 8.1.0 on Oxygen OS 5.1.3

I have it set as automatic connection and autostart. I also have it set as “do not optimise” in battery area so that the OS doesn’t force close it.

Any suggestions about why it’s closing - apparently at random?

I seem to hav miraculously resolved the above issue (no idea what I did!) and am now trying to set up an MQTT sensor to read the device_info topic that is published by Zanzito.

Can anyone tell me why the following is notworking?

- platform: mqtt
  name: james_oneplus_5_info
  state_topic: 'zanzito/jamesop5/device_info'
  qos: 1
  json_attributes: 
    - time
    - device_info
    - charge_type
    - battery_charging
    - battery_level
    - current_foreground_app
    - screen_locked
    - screen_on
    - screen_orientation
    - current_wifi
    - current_operator

Thanks,

James

This is because the MQTT sensor will not read a message with more than 255 characters. I’ve raised a bug.

Hi,
is Zanzito ready for Android Oreo and his changed behaviour regarding background services? And is battery friendly?
Thanks for info :slight_smile:

I’ve been running on Oreo since it was released with no issues regarding services.

Thanks, I’m still struggling between mqtt and Google Firebase Messaging. What will be better for battery and still have reasonable latency.

MQTT seems fine to me.

Somebody made it working with Ngnix?
Just try to set it up - but cant find good informations

Is what working with nginx?
mqtt?