You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: It's at the moment it's impossible to determine the utilization of a Router remotely. Without these data we cannot determine the health of the HF chain nor if the setup/position of the entire device can be improved.
Right now following data can be gathered using the Python script:
~$ /home/had/.local/bin/meshtastic --host 192.x.x.x --request-telemetry --dest \!279xxxx
Connected to radio
Sending telemetry request to !279xxxx on channelIndex:0 (this could take a while)
Telemetry received:
Battery level: 81.00%
Voltage: 4.00 V
Total channel utilization: 42.40%
Transmit air utilization: 13.42%
Uptime: 109625 s
It would be great to have an additional absolute counter of received, valid Meshtastic packets.
Example:
Received Packets: 20000
On the other side "Battery level" and "Voltage" is IMHO redundant.
The text was updated successfully, but these errors were encountered:
We could possibly make this one available over the wire as well. We need to break it out into its own module instead of leaning on Device Telemetry module as it exists now.
After talking to @GUVWAF about this one, we've decided to make this a response to request instead of first class Telemetry module w/ interval. PR up shortly
Platform
NRF52, ESP32, RP2040, Linux Native, other
Description
Problem: It's at the moment it's impossible to determine the utilization of a Router remotely. Without these data we cannot determine the health of the HF chain nor if the setup/position of the entire device can be improved.
Right now following data can be gathered using the Python script:
It would be great to have an additional absolute counter of received, valid Meshtastic packets.
Example:
Received Packets: 20000
On the other side "Battery level" and "Voltage" is IMHO redundant.
The text was updated successfully, but these errors were encountered: