TCP error

    • Autor
    Code
    6906417 mgos_mqtt_conn.c:472    MQTT0 connecting to 192.168.1.12:1883
6948883 mgos_mqtt_conn.c:230    MQTT0 TCP connect error (-9)
6980928 mgos_mqtt_conn.c:257    MQTT0 Disconnect
6984555 mgos_mqtt_conn.c:551    MQTT0 connecting after 4224 ms

Anyone with an idea why me 3em doesnt like mosquitto

    check mosquitto.conf, protocol type should be mqtt, not websockets.


    listener 1883

    protocol mqtt

    >100 Shellies, darunter so gut wie alles was der Hersteller produziert hat. ;)
    :!: ich beantworte grundsätzlich keine Fragen per persönlicher Nachricht:!:

    • Autor

    Ever asked yourself what one needs a mosquitto.conf for? It works out of the box being dockerized since a much longer term.

    And AFAIK websockets isn't auto-enabled but MQTT is the default.

    But no problem, played with the 3em mainly in combination with Home Asssistant the past weeks. What to say ..... propper recording would be something different.

    I see bunches of spikes where the shelly says I wasted 800kWh on a single phase within an hour. Stunning, I haven't noticed the light bulk around my home which likely would have happened if that would have been reality.

    And, these glitches started to happen with either the latest firmware or when having enabled MQTT in the setting.

    I must admit I forgot about my principles to not do 2 such things at a time to be able to track such errors.

    Switched MQTT off for the moment so that I could see if these mismatching spikes remain (then I'd assume it's firmware issue) or if they go away (then it's likely cause by enabling MQTT.

    Means I first have to solve this issue since if I can't there would be no shelly in my house and I won't need to bother about an MQTT problem.

    thanks for the help anyway