adam/meshcore-hub
1
0 Fork 0
mirror of https://github.com/ipnet-mesh/meshcore-hub.git synced 2026-10-30 19:52:03 +01:00
Code Issues 1 Packages Projects Releases Wiki Activity

SNR values on Message list broken #24

New Issue
Closed
opened 2026-10-04 23:09:16 +02:00 by adam · 1 comment
adam commented 2026-10-04 23:09:16 +02:00
Owner
Copy link
Copy source

SNR values no longer display at all on the message list. This was introduced when we moved to multiple receiver nodes. I think the template needs updating.

SNR values no longer display at all on the message list. This was introduced when we moved to multiple receiver nodes. I think the template needs updating. <!-- github-sync-id:3794386503 -->
adam closed this issue 2026-10-04 23:09:16 +02:00
adam commented 2026-10-04 23:09:17 +02:00
Author
Owner
Copy link
Copy source

Not sure this is possible due to change in firmware/protocol maybe? Hence why we initially had only one "receiver" node reporting SNR, possibly because it was running an earlier firmware than the other one?

So...

  • Push notifications (PacketType.CONTACT_MSG_RECV and CHANNEL_MSG_RECV) do NOT include SNR
  • Message sync responses (packet types 16 and 17, from CMD_SYNC_NEXT_MESSAGE) DO include SNR
    SNR is only available when messages are fetched via the sync mechanism.

But inspecting the received payload (which gets sent to MQTT), there is no longer any SNR value being sent or collected. Mainly because only messages retrieved from the companion node (via sync, e.g. turned on, not connected to PC/Pi) so messages queue up internally. When connected, the "receiver" app triggers a sync, and these messages WILL have SNR. However, any future messages (e.g. with the receiver node plugged in and running) will be delivered by PUSH which do not contain the SNR.

TLDR; looks like we can't get SNRs anymore.

Not sure this is possible due to change in firmware/protocol maybe? Hence why we initially had only one "receiver" node reporting SNR, possibly because it was running an earlier firmware than the other one? So... > - Push notifications (PacketType.CONTACT_MSG_RECV and CHANNEL_MSG_RECV) do NOT include SNR > - Message sync responses (packet types 16 and 17, from CMD_SYNC_NEXT_MESSAGE) DO include SNR > SNR is only available when messages are fetched via the sync mechanism. But inspecting the received payload (which gets sent to MQTT), there is no longer any SNR value being sent or collected. Mainly because only messages retrieved from the companion node (via sync, e.g. turned on, not connected to PC/Pi) so messages queue up internally. When connected, the "receiver" app triggers a sync, and these messages WILL have SNR. However, any future messages (e.g. with the receiver node plugged in and running) will be delivered by PUSH which do not contain the SNR. TLDR; looks like we can't get SNRs anymore. <!-- github-comment-id:3725830241 -->
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/meshcore-hub#24