meshcoretomqtt integration casts SNR and RSSI as wrong type (strings instead of float and int) #79

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

In the community MQTT (meshcoretomqtt) integration/fanout module, casting SNR and RSSI as strings causes their values to not be properly picked up by mesh analyzer software (e.g. CoreScope- https://github.com/Kpa-clawbot/CoreScope).

https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blob/7151cf384650ca59abb2d0354156340f3c337b30/app/fanout/community_mqtt.py#L178-L182

I've confirmed that changing these lines to the following fixes the issue and SNR and RSSI are now recognized and stats using them (in CoreScope) are populated:

    snr: float | None = data.get("snr")
    rssi: int | None = data.get("rssi")
In the community MQTT (meshcoretomqtt) integration/fanout module, casting SNR and RSSI as strings causes their values to not be properly picked up by mesh analyzer software (e.g. CoreScope- https://github.com/Kpa-clawbot/CoreScope). https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blob/7151cf384650ca59abb2d0354156340f3c337b30/app/fanout/community_mqtt.py#L178-L182 I've confirmed that changing these lines to the following fixes the issue and SNR and RSSI are now recognized and stats using them (in CoreScope) are populated: ```python snr: float | None = data.get("snr") rssi: int | None = data.get("rssi") ``` <!-- github-sync-id:4164645482 -->
adam closed this issue 2026-10-05 01:56:25 +02:00
Author
Owner

Just pushed a fix. thanks!

Just pushed a fix. thanks! <!-- github-comment-id:4151526141 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#79