[done] WS2812 and mqtt, uncontrolled LED glow

---

Hi, I have a problem with mqtt and one ws2812 LED.
I built a LED strip into a picture frame as a status indicator. The LEDs are controlled by a nodeMCU and tasmota 6.41.
Now I have now and then a wildly shining LED. Apparently without a reason an LED lights up in any color. Maybe it’s a tasmota problem. But it only appeared after the pimatic update yesterday. I have changed from 0.9.42 to 0.9.47, with node 4.6.2 and npm 2.15.11.
Everything else obviously runs without problems. Thanks @mwittig.
Now I looked at the problem in the terminal with mosquitto_sub.

pi@rpistrech:~ $ mosquitto_sub -v -t cmnd/node1/led12
cmnd/node1/led12 000000
cmnd/node1/led12 true
cmnd/node1/led12 false
cmnd/node1/led12 true
cmnd/node1/led12 false

First he shows me the right attitude. After some time I get the output “true”. A little later he shows me “false”. With “false” this LED goes on. I have set this LED to 000000 via a terminal and sent retain with it. Even without success.
Can someone help me and tell me why that is. And how I can change it.

Edit:
Also in the console of tasmota he shows me this change. But I don’t know where it comes from. I don’t have a rule that sets this LED to this color.

17:50:00 MQT: stat/node1/RESULT = {"Led12":"FA0000"}
17:50:25 MQT: stat/node1/RESULT = {"Led12":"000000"}

19:28:09 MQT: stat/node1/RESULT = {"Led12":"000000"}
19:28:25 MQT: stat/node1/RESULT = {"Led12":"FA0000"}
19:30:11 MQT: stat/node1/RESULT = {"Led12":"000000"}
19:30:40 MQT: stat/node1/RESULT = {"Led12":"FA0000"}

Meanwhile, I think that the problem has nothing to do with pimatic. It’s probably just a coincidence that it just showed up after the upgrade.
I have 3 rules that address this LED12. Now I have changed these rules to LED13. That didn’t solve the problem. The problem seems to be mqtt or tasmota. Although I didn’t change anything at mqtt or tasmota.
Can anyone help me here?

After I tried to get a solution in github/tasmota, without success. I had the idea to stop pimatic. It looks like I was able to narrow down the cause of the problem. If I quit pimatic and mosquitto continues running, LED 12 will no longer switch randomly. I have been driving pimatic down for 3h. Not a wrong display from this LED. Obviously the problem is in pimatic. Maybe it’s the mqtt-plugin? I have no idea. Is there a way to find the sender of an mqtt message?

In pimatic I only have two rules concerning this LED. I searched my config again in the editor.

As already said, only this one LED has this wild display.

I have run the pimatic log parallel to the log of tasmota console. There is no time overlap when this error occurs.

Is your topicand stateTopic correct?
Can you post your config?

@Michael-Rudek
I think topic and stateTopic is fine. I haven’t changed it. Before the problem occurred I had the same.
What part of the config do you want to see? The complete config would be a bit too long. Meanwhile over 3600 lines…
The plugin settings? The rules?

Why not both
Not the whole config…

@michael-rudek

{
      "brokers": [
        {
          "brokerId": "192.168.178.22"
        }
      ],
      "plugin": "mqtt",
      "active": true
    },

Sorry, Excuse me, I spoke about 2 rules above

 {
      "id": "frost",
      "name": "Frost",
      "rule": "when $4ch-sensor.BME280.Temperature < 1 and its after 04:00 then pushover message:\"Frostgefahr $4ch-sensor.BME280.Temperature °C\" and publish mqtt message \"000007\" on topic \"cmnd/node1/led12\" on broker 192.168.178.22 retain: true",
      "active": true,
      "logging": true
    },
    {
      "id": "frost-warnung",
      "name": "Frost Warnung",
      "rule": "when $4ch-sensor.BME280.Temperature < 3 then publish mqtt message \"070700\" on topic \"cmnd/node1/led12\" on broker 192.168.178.22 retain: true",
      "active": true,
      "logging": true
    },
    {
      "id": "kein-frost",
      "name": "kein Frost",
      "rule": "when $4ch-sensor.BME280.Temperature > 3 then publish mqtt message \"000000\" on topic \"cmnd/node1/led12\" on broker 192.168.178.22 retain: true",
      "active": true,
      "logging": true
    },

Looks OK for me…

1. Console Tasmota. Are there no cmd lines? Only state?
2. The BME Sensor. Try something like when $4ch-sensor.BME280.Temperature < 1 for 5 minutes....
   ans see what happens.

@michael-rudek

I get in tasmota console this („Led12":"FA0000“ is the same as cmnd/node1/led12 false in terminal)

15:40:22 SRC: MQTT
15:40:22 RSL: Received Topic cmnd/node1/led12, Data Size 6, Data 000000
15:40:22 RSL: Group 0, Index 12, Command LED, Data 000000
15:40:22 MQT: stat/node1/RESULT = {"Led12":"000000"}
15:40:31 WIF: Checking connection...
15:40:31 WIF: Connected
15:40:43 SRC: MQTT
15:40:43 RSL: Received Topic cmnd/node1/led12, Data Size 4, Data true
15:40:43 RSL: Group 0, Index 12, Command LED, Data true
15:40:43 MQT: stat/node1/RESULT = {"Led12":"000000"}
15:40:51 WIF: Checking connection...
15:40:51 WIF: Connected
15:40:59 SRC: MQTT
15:40:59 RSL: Received Topic cmnd/node1/led12, Data Size 5, Data false
15:40:59 RSL: Group 0, Index 12, Command LED, Data false
15:40:59 MQT: stat/node1/RESULT = {"Led12":"FA0000"}
15:41:11 WIF: Checking connection...
15:41:11 WIF: Connected
15:41:31 WIF: Checking connection...
15:41:31 WIF: Connected

The terminal shows me about at the same time the

pi@rpi_strech:~ $ mosquitto_sub -v -t cmnd/node1/led12
cmnd/node1/led12 000000
cmnd/node1/led12 true
cmnd/node1/led12 false
cmnd/node1/led12 true
cmnd/node1/led12 false
^C
pi@rpi_strech:~ $ mosquitto_pub -t cmnd/node1/led12 -r -m '000000'
pi@rpi_strech:~ $ mosquitto_sub -v -t cmnd/node1/led12
cmnd/node1/led12 000000
cmnd/node1/led12 true
cmnd/node1/led12 false
cmnd/node1/led12 true
cmnd/node1/led12 false
cmnd/node1/led12 true
cmnd/node1/led12 false
cmnd/node1/led12 true
cmnd/node1/led12 false
^C
pi@rpi_strech:~ $ mosquitto_pub -t cmnd/node1/led12 -r -m '000000'
pi@rpi_strech:~ $

I changed the rules once for built-in. Without success.
Then I deactivated all rules with „LED 12“. Also without reaction. The behavior remained as usual. LED 12 continues to bitch.

The temperature for the display is supplied by a Sonoff. So by wifi. Could it be that this error occurs if the sonoff briefly loses the wifi and does not send any data?
Mosquitto obviously sends from time to time false. If mosquitto true the state is apparently preserved. But why does the broker send false and true?

Isn’t there anyone here who can help me? @wutu Maybe you can help me? As far as I know you wrote the plugin.

I may have finally found the cause of my crazy playing LED. It seems to have been my mqtt broker. For several reasons I installed a new mosquitto on a Proxmox drive. Unfortunately this meant that I had to change all IPs in the config (about 2700 lines). A bad job.
But since I did this mqtt move, the LED problem is gone. I guess there was a “retain” problem in the old broker. But I guess only.