Send msgs via mqtt using firmware 2.5

Support
1

Hi everyone,

I have a ‘base’ node connected to a private MQTT server. It listens for incoming direct messages and send automated responses back to the LoRa network. E.g if it receives PING it responds PONG.

This worked fine with version 2.4 of the firmware. My Home Assistant automation would publish a response to the msh/REGION/2/json/mqtt topic, and the base node would forward the response to the network.

Here’s an example of the MQTT message format I was using:

data:
qos: 0
retain: false
topic: msh/EU_868/2/json/mqtt
payload: |
{
“from”: {{ send_from }},
“to”: {{ send_to }},
“type”: “sendtext”,
“payload”: “Pong at {{ now() }}”
}

Since upgrading to firmware version 2.5, this no longer works. I can see the incoming message in MQTT, and the response is being published to the MQTT broker, but the response never reaches the other node on the mesh.

I’m aware of changes in how encryption and direct messages are handled in 2.5 (e.g., public key cryptography for DMs), but I’m unsure if that’s affecting my setup. Could anyone help me figure out if there have been changes in the MQTT message format or other settings that I need to adjust in version 2.5?

2 Likes
2

The only thing I’ve found from browsing the Discord server is that the MQTT topics need to be published to some /PKI topic now. I couldn’t find more specific instructions.

I gave up on it for now because I think the 2.5 firmware is still too much in alpha stage. I don’t think the docs have been updated yet. Probably it’ll be easier in about a month from now.