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).
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:
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 -->
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.
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:
Just pushed a fix. thanks!