Mqtt upload to letsmesh not working anymore

[wesselah]

After the update to the latest meshcore integration on ha the connection to letsmesh mqtt server keeps failing
MQTT2] Connection error: WebSocket handshake error, connection not upgraded
8:13:25 PM – (ERROR) MeshCore (custom integration)
meshcore-decoder not found in runtime PATH, will try Python fallback signer
8:13:25 PM – (WARNING)

Also it seems the fallback does not work anymore because in ha the meshcore decoder is not availible
I am using meshcore integration 2.6.0 and ha core 2026.4.4

[Chuck-it]

it's not a problem of meshcore-ha, the EU MQTT Server is down or broken.

https://forum.letsmesh.net/t/mqtt-connection-error-mqtt2-mqtt-eu-websocket-handshake-error-conenction-not-upgrade/684

[nakoeppen]

I think this is unrelated to the EU server issues. I am having issues with the US LetsMesh servers and my local instance. May be inconsistent in nature though, will report back if I find out more!

[awolden]

The EU broker issue is a LetsMesh service problem, not our integration. The US broker has seen intermittent outages reported on their forum too.

For local MQTT brokers, the WebSocket handshake error means the broker isn't accepting WebSocket connections on whatever port/path is configured. Check that the broker has WebSocket listener enabled (default is plain MQTT on 1883). The integration uses paho-mqtt and supports both transports.

The meshcore-decoder not found, will try Python fallback signer line is unrelated and benign. The Python fallback works fine, the decoder is only an optimization.

@nakoeppen if you're seeing this on a local broker on the current release, open a fresh issue with broker URL/port/transport and we can dig in.