Announcing MQTT/Android bridging app: Zanzito. Beta testers wanted!

myname.duckdns.org

it looks like a DNS problem, but I can’t say much more: your android devices isn’t resolving the host name. Try putting the ip address directly, just to confirm that it is a DNS problem.

I put my WAN address, but still the same result

failed to connect to /mywanipaddress (port 1883) isConnected failed ETIMEDOUT

We continued in PM :wink:

Thanks. I managed to copy the activities to another phone. But the problem is I set every topics to start with device name. This has few advantages such as I will know which device the traffic comes from. That way, HA can send notification to the correct device with a single automation. For example this automation to get state of any sensors…

- alias: 'MQTT Get States - Sensors'
  trigger:
    platform: mqtt
    topic: +/getstates/sensor
  action:
    service: mqtt.publish
    data_template:
      topic: >-
        zanzito/{{ trigger.topic.split('/')[-3] }}/notification
      payload: >-
        {{ states('sensor.' ~ trigger.payload ~ '') }}

The problem is when I copied over the activities from let say “device01” to “device02”, I still need to change each topics for each activities in “device02”. For example from devices01/getstates/sensor to devices02/getstates/sensor

I am wondering is it possible for zanzito to accept variables in the activity’s topic? For example: %devicename%/getstates/sensor. Zanzito will replace %devicename% with the actual device name before publish to the broker.

The idea of a variable in topics is very good, added to the list :wink:

But I’m sure I understand you usage: you get data from a sensor device that has the same device name of a Zanzito instance?

Thanks.

For example, I created this activity in Zanzito…

  • Topic: device01/getstates/sensor
  • Payload: room_temperature (same with the entity ID in HA)

When Zanzito sends it, it will trigger the above automation and publish to zanzito/device01/notification with the state of sensor.room_temperature as the payload. Zanzito of device01 will receive it as notification.

Ok,
What about this:
if the sensor is already MQTT, you can subscribe directly to the sensor topic from Zanzito.
or
if the sensor is not MQTT, you can have a HA automation that re-publishes the sensor value to an MQTT topic everytime it changes, then you subscribe to that topic from Zanzito.

Wouldn’t the result be same, that is having a notification every time the value changes?

Hi guys,
I’ve just released an update, available through the Play store. The news:

  • Switched to new permissions model in Android; (@Landrash)
  • Added Photo preview in notification; (@IoTmessenger)
  • Added Zanzito’s version status message;
  • Bug fixing.

Please let me know if you encounter any trouble with the new permission model or anything else.
Thanks
gl

Do I need to change anything in Zanzito settings, HASS or in the app notifications on my phone for the picture to show up?
Like the former version, my screen turns on and I see the notification with the message ‘Picture received’ (no picture shown). I did reboot my phone to be sure and checked if all app notification settings were still in place.

Btw, the added checkbox (in former version) for auto focus when sending images works ok for me (when ticked). I now have sharp images in the correct high resolution.
:slight_smile:

The notification needs to be expanded: drag it down

Good for the resolution, it took a bit of work :wink:

Of course that does not work for my phone.
:smiley:

The MIUI (version 8.2.3) only allows me to swipe it away to the side, not down for opening.
This is not a custom software (ROM), but the official version which come on the Chinese Xiaomi phones.

I guess these ROMS do not following the Android 6.x standards completely.
http://en.miui.com/zt/miui8/index.html

damn… :smiley:
try swiping it down with two fingers!
It should be Android’s standard behaviour…

Nope, tried that (I saw you mention this before in this thread).
Definitely nothing standard on Chinese Android phones.
:wink:

Very strange! This feature is present from Android 4.1, and there’s no other way to expand a Big view notification other than dragging it down, unless it’s the first notification and there is enough screen room, in that case it would auto-expand.
Isn’t there a custom system preference, by any chance?
Can you expand Zanzito’s main notification so to see the buttons?

I will check tomorrow, first need some sleep.
It must be related to the complete overhaul of the interface and launcher in MIUI.

1 Like

Can you make a snapshot??

No. It doesn’t send the notification everytime the sensor value changes. I only receive the notification when I request it from zanzito. I use the voice command. For example I can say “what is the room temperature?”. Then I will receive a notification with the sensor value. My phone will speak out the notification using another app (voice notify). That’s why I think zanzito is a good alternative to Alexa if only it can always listen to a wake word.

Oh, I understand. Sorry if I insisted, but knowing the exact use case helps me to understand what to do.
Ok, so the best solution looks like a placeholder for the device name, like you suggested, I will work on it.

What about a wake whistle?

You mean I whistle a certain tune to wake up zanzito? That’s sounds cool but not everyone in the house can whistle. I think most of them can’t whistle.

I still prefer using a name.