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



<!-- github-sync-id:2303550258 -->
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 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As the tittle says, i'm only getting the info from new application print
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.