Tasmota power1 turning off after restart

[danpadure]

power2 stays on
however at restart I get:

17:50:14.465 MQT: Attempting connection...
17:50:14.466 WIF: DNS resolved '192.168.12.45' (192.168.12.45) in 0 ms
17:50:14.615 MQT: Connected
17:50:14.618 MQT: tele/sonoff-3dprinter/LWT = Online (retained)
17:50:14.622 MQT: cmnd/sonoff-3dprinter/POWER = 
17:50:14.623 MQT: Subscribe to cmnd/sonoff-3dprinter/#
17:50:14.626 MQT: Subscribe to cmnd/tasmotas/#
17:50:14.628 MQT: Subscribe to cmnd/DVES_5A3B2B_fb/#
17:50:14.635 MQT: tele/sonoff-3dprinter/INFO1 = {"Info1":{"Module":"Sonoff Basic","Version":"14.0.0(release-lite)","FallbackTopic":"cmnd/DVES_5A3B2B_fb/","GroupTopic":"cmnd/tasmotas/"}}
17:50:14.638 MQT: tele/sonoff-3dprinter/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"sonoff-3dprinter-6955","IPAddress":"192.168.12.60"}}
17:50:14.640 MQT: tele/sonoff-3dprinter/INFO3 = {"Info3":{"RestartReason":"Software/System restart","BootCount":2641}}
17:50:14.642 MQT: stat/sonoff-3dprinter/RESULT = {"POWER1":"ON"}
17:50:14.644 MQT: stat/sonoff-3dprinter/POWER1 = ON
17:50:14.646 MQT: stat/sonoff-3dprinter/RESULT = {"POWER2":"ON"}
17:50:14.648 MQT: stat/sonoff-3dprinter/POWER2 = ON
17:50:14.700 SRC: MQTT
17:50:14.702 CMD: Grp 0, Cmd 'POWER', Idx 1, Len 3, Pld 0, Data 'OFF'
17:50:15.001 MQT: stat/sonoff-3dprinter/RESULT = {"POWER1":"OFF"}
17:50:15.004 MQT: stat/sonoff-3dprinter/POWER1 = OFF

You would say that something on mqtt commands it to turn off.
However I am looking at cmnd/sonoff-3dprinter/POWER1 topic with MQTT Explorer and I see NO ACTIVITY

What am I missing?
Obviously if I disable MQTT, Tasmota power1 stays ON after restart

[danpadure]

oh, and yes - it;'s a 3d printer and it's messing my prints

[Jason2866]

Looks like a retained message in your mqtt broker. Delete the retained messages in your broker and your issue should be gone.

[sfromis]

SRC: MQTT says what the cause is. A message is arriving via MQTT. Could also be some automation you have running, but a retained command message is indeed plausible.

[danpadure]

I tried: publishing a raw message of 0 bytes to the command topic - still powering off
I tried restarting the 2 mosquitto servers that are in bridge mode - still powering off
as soon as it connects to the mqtt server it powers off

But you are right
I can see this in mqtt explorer too: as soon as I connect it, I see the POWER1=OFF in the command topic appearing, along other topics, most of them being LWT from various devices
What causes this data to be....persistent?

[danpadure]

oh well - I just found a yellow button "RETAINED" with a X button to delete it in MQTT Explorer, and..... it deleted it
problem solved.
i wonder how that topic got "retained" in the first place...

[sfromis]

Publishing an empty message to the command topic also works if you publish it as retained; to replace the older retained one - which got retained because you asked for it. Maybe some time ago while trying to get things to work. A retained message can have a very long lifetime if you do not replace/delete it.

[danpadure]

yeah, I noticed!

I can tell you it took me a VERY long time to discover how randomly my 3dprinter would turn off by itself. I looked at power supply, at data cable, software. Just today I found the reason, noticing the strange log in the console
I guess sometimes the wifi would disconnect and when it reconnected, the retained message would kick in :P

Thanks a lot

[sfromis]

In general, only use retain if you know exactly what benefit you get from it, and are aware of the many pitfalls with retained commands.