adam/meshtastic-node-red
1
0 Fork 0
mirror of https://github.com/scruplelesswizard/meshtastic-node-red.git synced 2026-10-31 11:12:12 +01:00
Code Issues Packages Projects Releases Wiki Activity

"Ingest from MQTT" subflow need modification after meshtastic 2.3.0 #8

New Issue
Closed
opened 2026-10-05 06:11:27 +02:00 by adam · 2 comments
adam commented 2026-10-05 06:11:27 +02:00
Owner
Copy link
Copy source

After meshtastic 2.3.0 mqtt protobuf messages come in at msh/+/c but MQTT node in the "Ingest from MQTT" subflow subscribes to msh/+/e

-- from meshtastic documentation
Protobufs topic
A gateway node will uplink and/or downlink raw protobuf MeshPackets to the topic:
msh/2/e/CHANNELNAME/USERID, where CHANNELNAME is the name of the channel (firmware versions prior to 2.3.0 will publish to a topic with /c/ in the place of /e/).

For example: msh/2/e/LongFast/!abcd1234

After meshtastic 2.3.0 mqtt protobuf messages come in at msh/+/**c** but MQTT node in the "Ingest from MQTT" subflow subscribes to msh/+/**e** -- from [meshtastic documentation ](https://meshtastic.org/docs/software/integrations/mqtt) Protobufs topic A gateway node will uplink and/or downlink raw protobuf MeshPackets to the topic: msh/2/e/CHANNELNAME/USERID, where CHANNELNAME is the name of the channel **(firmware versions prior to 2.3.0 will publish to a topic with /c/ in the place of /e/).** For example: msh/2/e/LongFast/!abcd1234 <!-- github-sync-id:2322629217 -->
adam commented 2026-10-05 06:11:28 +02:00
Author
Owner
Copy link
Copy source

dev havent asnwered my issue so dono if they are active eat all

dev havent asnwered my issue so dono if they are active eat all <!-- github-comment-id:2192370305 -->
adam closed this issue 2026-10-27 16:56:49 +01:00
adam commented 2026-10-27 16:56:50 +01:00
Author
Owner
Copy link
Copy source

Thanks for the clear write-up. You are right: firmware 2.3.0 moved protobuf uplinks from /c/ to /e/ topics, and the flow still subscribes to msh/+/c/#. This project is now archived, so I won't be shipping a fix. To use the flow with current firmware, edit the MQTT in node inside the "Ingest from MQTT" subflow to subscribe to the /e/ topic that your gateway publishes to (check your broker for the exact topic layout, which also depends on your root topic setting). The README documents this status. Closing as not planned.

Thanks for the clear write-up. You are right: firmware 2.3.0 moved protobuf uplinks from `/c/` to `/e/` topics, and the flow still subscribes to `msh/+/c/#`. This project is now archived, so I won't be shipping a fix. To use the flow with current firmware, edit the MQTT in node inside the "Ingest from MQTT" subflow to subscribe to the `/e/` topic that your gateway publishes to (check your broker for the exact topic layout, which also depends on your root topic setting). The README documents this status. Closing as not planned. <!-- github-comment-id:6202261372 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshtastic-node-red#8