[solved] permanent mqtt messages

---

Hi, I built on a SmartHomeDisplay like this one: HomeStatusDisplay
A NodeMCU controls the WS2812 and the commands are transmitted via mqtt. After some teething troubles, the display works perfectly.
Unfortunately, with one exception. A device constantly sends its status, in contrast to other identical devices.

 {
      "id": "anbau-tuer",
      "name": "AnbauTür",
      "class": "HomeduinoContactSensor",
      "pin": 16,
      "interval": 15000,
      "inverted": false,
      "xClosedLabel": "Zu",
      "xOpenedLabel": "auf",
      }

The Device sends its status in the interval as defined in the device setting. As I said, only this device reacts like this, others with similar settings I don’t have this behavior.

For example, this device has very similar settings:

  
    {
      "id": "homeduino-gartenhaus-tuer",
      "name": "Gartenhaus",
      "class": "HomeduinoContactSensor",
      "pin": 15,
      "interval": 2000,
      "inverted": false,
      "xClosedLabel": "verschlossen",
      "xOpenedLabel": "nicht verschlossen",
    }

But it does not have the mqtt behavior like the first device.

My problem is the permanent (in this case all 15 sec) opening of the message when I have opened the GUI of pimatic.
I can’t find the reason for this behavior.

For a better understanding I show my rule here.
My rule for the output on the display looks like this:

when anbau-tuer is closed then publish mqtt message "070700" on topic "cmnd/node1/led21" on broker 192.168.178.22 retain: true

Set retain to false otherwise your Display don’t so it’s Job proper

I already tried that. It has no effect.
And, other devices also have “retain: true”; and it works without constant messages.
The problem must be somewhere else.

Set retain to false and delete all old Message from mosquitto. IT was also my fault.

@temp said in permanent mqtt messages:

delete all old Message from mosquitto.

Maybe that’s the reason.
How can I delete all old messages from mosquitto?

On the other hand, the messages come in the same interval as the device is queried.

edit: I tried “retain: false” again. Unfortunately without success.

In order to “delete” a retained message send an empty message to the topic with “retain: true”

Do you understand what retain:true does?

The broker provides the last retained message to a subscriber as long as no new message is added.

You need this e.g. when a message is published and the subscriber isn’t online at this moment.

@saxnpaule
Yeah, that’s what I thought. And that’s actually a good thing. At least in the beginning, when I had problems with the stable work of the NodeMCU. After a restart of the NodeMCU the display got the last status and the LEDs were lit again.

But currently a new message about pimatic is constantly coming to the broker. Every 15 seconds, every time the device is updated.
If I set a different time, the message appears in the new interval.

I’m afraid the problem has another cause.

Could it be the sensor sends its status every x seconds? Could you add a trigger in the rule?

@rikki78
The interval in the device is already 15000ms (15sek). A longer interval also extends the message.
But then the query time becomes too long. Thank you for the idea, but unfortunately this is not the solution.

Maybe you misunderstood what I meant. can you check if the sensor is sending its signal frequently?
So for example change your rule so it shows a message instead of sending a mqtt message. If the message appears it is a sensor issue and not related to mqtt

Now I tried something else. And the problem is gone.
I deleted the HomeduinoContactSensor device and created a new HomeduinoPir device. Changed the rule and see there, no more permanent messages.

I don’t think the HomeduinoContactSensor device was a wrong device. Another device works with this setting via mqtt.
Possibly something had overlapped in pimatic at the furnishing. Or whatever… I don’t know enough about it.
Unfortunately, I haven’t been able to care much about this problem lately. But it has existed since I put the HomeStatusDisplay into operation.
Thanks for the help everyone.