Only New application packets #7

Closed
opened 2026-10-05 06:11:25 +02:00 by adam · 1 comment
Owner

As the tittle says, i'm only getting the info from new application print

image
image
image

As the tittle says, i'm only getting the info from new application print ![image](https://github.com/scruplelesswizard/meshtastic-node-red/assets/52419539/e1700831-d5e0-4bcc-b5ca-768d9d5048c0) ![image](https://github.com/scruplelesswizard/meshtastic-node-red/assets/52419539/8c5f5781-b762-42fb-85e4-1e5955d6c8d1) ![image](https://github.com/scruplelesswizard/meshtastic-node-red/assets/52419539/d85c79c8-c612-400b-a890-102d85c01ae2) <!-- github-sync-id:2303550258 -->
adam closed this issue 2026-10-27 16:56:48 +01:00
Author
Owner

Thanks for the report, and sorry for the silence. This project is now archived and no longer maintained, so I can't investigate this. If you are only seeing NodeInfo (new application) packets, the most likely cause is the MQTT topic change in firmware 2.3.0 described in #11: the flow subscribes to msh/+/c/# but newer firmware publishes protobufs under an /e/ topic. Updating the subscription in the "Ingest from MQTT" subflow to match your gateway's topic is the first thing to try.

Thanks for the report, and sorry for the silence. This project is now archived and no longer maintained, so I can't investigate this. If you are only seeing NodeInfo (new application) packets, the most likely cause is the MQTT topic change in firmware 2.3.0 described in #11: the flow subscribes to `msh/+/c/#` but newer firmware publishes protobufs under an `/e/` topic. Updating the subscription in the "Ingest from MQTT" subflow to match your gateway's topic is the first thing to try. <!-- github-comment-id:6202260563 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshtastic-node-red#7