Mqtt check if subscribed topic has stopped publishing messages

user_9052957 0
Viewed 1299

I am trying to implement a way to know when a specific device has stopped publishing messages to an mqtt broker and in that case send an email to myself. I want to do this to be able to know if there is a problem with the device that is publishing the messages so I can check it and turn it back on. To try to accomplish this I created a mqtt client that subscribes to the topic that the device publishes e.g. test/device_1 and then set as last will and testament for that device status/device_1 where I put as payload="Offline". Ideally, I want to be able to do this for more than 1 device, but let's assume I just want it for the simple case of one device.

I created another script that implements another client that is subscribed to the topic status/device_1 and then on the on_message function it checks if it gets the payload="Offline" and if it does get it then I send an email to myself.

This approach however doesn't work as when I turn off my device, the mqtt client that is subscribed to the topic test/device_1 keeps listening but gets no messages. In other words, it doesn't send its last will even when the topic is empty. However, it seems to work when I stop the script that is subscribed to the topic test/device_1.

Am I missing something or is it not possible to accomplish what I am trying to do? Any advice is appreciated!

mosquitto paho mqtt python
2 Answers

You can use last timestamp when device published the messages as heartbeat and in your another script, if (current_time - last_timestamp) > 30 then you can email yourself that your device is offline. this way you can have threshold of time when you want to get email of device offline.

script 1:

mqttCient.on_message(msg):
    last_timestamp = time.time()

script 2:

cur_time = time.time()
if ((cur_time - last_timestamp) > 30):
    # email yourself

use Json file or database as buffer for storing and accessing last_timestamp

user_96424070

First LWT messages are only published by the broker if the client goes offline unexpectedly, which means if it shuts down cleanly then it will not get published, you have to manually publish a message as part of shut down process.

You can set the retained flag on the LWT so that any client that subscribes after the device has gone offline it will still see the state message.

You should also clear that message on when the device starts up, either by publishing something like Online or a null payload to clear the retained message.

user_5045540
Related