MQTT Me Cookbook

After playing around with my MQTT Me and testing various use cases I realized that I needed to extend MQTT Me with additional capabilities.  If you have installed version 1.x you need to uninstall it before installing version 2.0.  Sorry about this.  The release notes are included in the download package.

I have created a cookbok that describes how MQTT Me can be configured and used.

  1. Publishing text to a camera Text overlay
  2. Mobile Voice Notification on Camera Motion Detection
  3. Monitoring Axis Device Alive (or not)
  4. Monitoring Device CPU load and Bandwidth
  5. Publishing JPEG images and storing them with PHP
  6. Setting Device Parameter Settings with MQTT message



Download MQTT ME


MQTT integration with Axis devices

MQTT Me gives your Axis Device the ability to integrate with MQTT systems.  MQTT (Message Queuing Telemetry Transport) is an ISO standard machine-machine messaging protocol targeting IoT devices.

There are several applications/clients supporting MQTT such as Home Assistant (home automation) and mobile apps such as Zanzito and MQTT Dashboard.  There are also more professional systems that use MQTT extensively.

MQTT Me supports both publishing (upon Axis device events) and subscribe to topics to execute actions on the Axis device.

One of my usage is to get a speach notification in my phone when someone triggers motion detection in any of my cameras.  I have Zanzito on my phone that subscribes to a topic published by my cameras.  The MQTT payload from my cameras includes a string that Zanzito will do TTS (Text-To-Speach) to play on my phones speaker.  I will hear the message even if the phone is idle in my pocket.

Onther usage is having MQTT Dashboard on my phone.  The app is configured with a button that toggles a digital IO port on the Axis device.

Compared to integrating with VAPIX/ONFIV, MQTT enables a for more flexible and simplified integration for event/action solutions.  The Axis device does not need to have network access to the MQTT application as long as the device and client have access to the same MQTT broker.  You can close all the incoming ports on your firewall.  MQTT clients conntect to broker from the inside.

Since MQTT Me does not support TLS (encryption) you should not connect to a broker on the Internet.  A  local broker is safe OK.   Remote clients can always connect to the broker over TLS if you configured your broker with plain text (port 1883) and  TLS (port 8883) for the clients accessing from Internet e.g. mobil devices.

Read more in the MQTT Me manual [PDF]

Download the ZIP file containing ACAP (MIPS, ARM7 and ARM7hf)

Current version is 2.0.   Note: Version 2.0 is not compatible with version 1.X.  You need to uninstall 1.x before installing version 2.0.

Please, share any interesting MQTT integration solutions by using the comments.

Upload Now

In logistics, it is common to have devices that make scans of products or their identifications. For example barcode scanners. This information is then stored in a database. It is convenient to store with that information an image of the product, so that a human can, for example, at a later time do things like check whether a package was already damaged during the scan. (more…)