MQTT Boot Loop

[fefi-byte]

version: 0.67
MQTT via IOBroker

If I connect the clock via MQTT, it is in a boot loop.
with home assistant there are no problems.

[Blueforcer]

#163

You need to disable "publish own states on subscribe" and "publish own states on connect" in your iobroker adapter

[DcFamas]

@Blueforcer I'm now in the bootloop as well.
Installed a new mqtt instance, because I need those two states in the adapter (openDTU needs them).

'cause of Shelly and openDTU the two standard mqtt ports are occupied. So I set the port to 8884.

The pixel clock says:
CHECK
No UP :(

What does this mean? Best regards :)

[fefi-byte]

@DcFamas
So please adjust.

@BlueforcerIch bin jetzt auch im Bootloop. Habe eine neue mqtt-Instanz installiert, da ich diese beiden Zustände im Adapter benötige (openDTU benötigt sie).

Aufgrund von Shelly und openDTU sind die beiden Standard-MQTT-Ports belegt. Also habe ich den Port auf 8884 eingestellt.

Die Pixeluhr sagt: CHECK No UP :(

Was bedeutet das? Mit freundlichen Grüßen :)

[DcFamas]

wtf, I'm stupid. I changed those both settings for my first instance mqtt.0, which I'm using for openDTU and made the screenshot for the second instance mqtt.1 which I'm using for the pixelwatch.

Thanks for your patience. :)