ping and test data missing #91

Closed
opened 2026-10-05 01:21:28 +02:00 by adam · 17 comments
Owner

Hi.
Loaded latest code from github, looks like for now ping and test command missing data about hops and rssi\dbm.

Hi. Loaded latest code from github, looks like for now ping and test command missing data about hops and rssi\dbm. <!-- github-sync-id:3532426428 -->
adam closed this issue 2026-10-05 01:21:28 +02:00
Author
Owner

What exactly

What exactly <!-- github-comment-id:3422082457 -->
Author
Owner

What exactly

Atleast the one that usually was provided:
PONG
SNR:6.25 RSSI:-47

Or:
Roger that!
SNR:6.25 RSSI:-47

Now it is just PONG and Roger that! without snr\rss.

> What exactly Atleast the one that usually was provided: PONG SNR:6.25 RSSI:-47 Or: Roger that! SNR:6.25 RSSI:-47 Now it is just PONG and Roger that! without snr\rss. <!-- github-comment-id:3422170538 -->
Author
Owner

What's it say now, what version firmware. This data only shows up on a confirmed direct. It works for me? What's differed for your setup.

What's it say now, what version firmware. This data only shows up on a confirmed direct. It works for me? What's differed for your setup. <!-- github-comment-id:3422267593 -->
Author
Owner

image

![image](https://github.com/user-attachments/assets/4ed07433-74fc-4509-8a47-179e799d4a28) <!-- github-comment-id:3422295728 -->
Author
Owner

What's it say now, what version firmware. This data only shows up on a confirmed direct. It works for me? What's differed for your setup.

Well, i am using 2.6.11 for my heltec v3.
All this time iam upgrading it via sh update.sh inside venv.

Sometimes copy updated config.template as config.ini and edit it for my setup.

Rolled back to the saved folder and voila it is sending rss again.

> What's it say now, what version firmware. This data only shows up on a confirmed direct. It works for me? What's differed for your setup. Well, i am using 2.6.11 for my heltec v3. All this time iam upgrading it via sh update.sh inside venv. Sometimes copy updated config.template as config.ini and edit it for my setup. Rolled back to the saved folder and voila it is sending rss again. <!-- github-comment-id:3422317422 -->
Author
Owner

image

This is chat i assume, and i have tested it in a direct message.

> ![image](https://github.com/user-attachments/assets/4ed07433-74fc-4509-8a47-179e799d4a28) This is chat i assume, and i have tested it in a direct message. <!-- github-comment-id:3422322647 -->
Author
Owner

Upgrade to 2.7.13 and see if the issue remains? Newer firmware 2.6.11 is a bit old now

Upgrade to 2.7.13 and see if the issue remains? Newer firmware 2.6.11 is a bit old now <!-- github-comment-id:3422535208 -->
Author
Owner

Upgrade to 2.7.13 and see if the issue remains? Newer firmware 2.6.11 is a bit old now

I would like to stay with the stable fw, it's kinda too hard to work with 2.7 sometimes.
Anyway, rolling back bot code fixed the issue.

> Upgrade to 2.7.13 and see if the issue remains? Newer firmware 2.6.11 is a bit old now I would like to stay with the stable fw, it's kinda too hard to work with 2.7 sometimes. Anyway, rolling back bot code fixed the issue. <!-- github-comment-id:3422689178 -->
Author
Owner

Took a clean install, only interface configured.
Same issue.

Image

Took a clean install, only interface configured. Same issue. ![Image](https://github.com/user-attachments/assets/942cb400-efa9-425d-b1be-c12bd6a5e1c7) <!-- github-comment-id:3422755872 -->
Author
Owner

I do develop on latest firmware which is coming down the pipe.

So I am now leveraging newer functions to help fine tune, more changes in the bot soon will reflect this.

Eventually 2.8 comes out and 2.7 is stable ;)

I do develop on latest firmware which is coming down the pipe. So I am now leveraging newer functions to help fine tune, more changes in the bot soon will reflect this. Eventually 2.8 comes out and 2.7 is stable ;) <!-- github-comment-id:3423151023 -->
Author
Owner

I will boot up older code and see if any interesting ideas come out but it's also easy to patch "direct" if needed

I will boot up older code and see if any interesting ideas come out but it's also easy to patch "direct" if needed <!-- github-comment-id:3423153249 -->
Author
Owner

I do develop on latest firmware which is coming down the pipe.

So I am now leveraging newer functions to help fine tune, more changes in the bot soon will reflect this.

Eventually 2.8 comes out and 2.7 is stable ;)

I was hope for not to break backward compatibility.
Just as app do, it works for 2.6 and 2.7.
Not sure why this happens for your code.

> I do develop on latest firmware which is coming down the pipe. > > So I am now leveraging newer functions to help fine tune, more changes in the bot soon will reflect this. > > Eventually 2.8 comes out and 2.7 is stable ;) I was hope for not to break backward compatibility. Just as app do, it works for 2.6 and 2.7. Not sure why this happens for your code. <!-- github-comment-id:3424523971 -->
Author
Owner

Can you enable hop debugger

[messagingSettings]

enableHopLogs = TRUE

And let me know the debug log data with problems

Can you enable hop debugger ``` [messagingSettings] enableHopLogs = TRUE ``` And let me know the debug log data with problems <!-- github-comment-id:3424632218 -->
Author
Owner

Can you enable hop debugger

[messagingSettings]

enableHopLogs = TRUE

And let me know the debug log data with problems

2025-10-21 10:12:39,301 | DEBUG | System: Watchdog started
2025-10-21 10:12:43,106 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 fi
nal_hop_value: via_mqtt:False transport_mechanism:unknown
2025-10-21 10:12:43,107 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsSttn1
2025-10-21 10:12:43,113 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsSttn1 isDM:True p
laying:False
2025-10-21 10:12:43,114 | INFO | Device:1 Sending DM: 🏓PONG To: ZedIsSttn1
2025-10-21 10:12:51,868 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 fi
nal_hop_value: via_mqtt:False transport_mechanism:unknown
2025-10-21 10:12:51,869 | INFO | Device:1 Channel: 0 Received DM: Test From: ZedIsSttn1
2025-10-21 10:12:51,870 | DEBUG | System: Bot detected Commands:[{'cmd': 'test', 'index': 0}] From: ZedIsSttn1 isDM:True p
laying:False
2025-10-21 10:12:51,870 | INFO | Device:1 Sending DM: 🎙Roger that! To: ZedIsSttn1

> Can you enable hop debugger > > ``` > [messagingSettings] > > enableHopLogs = TRUE > ``` > > And let me know the debug log data with problems 2025-10-21 10:12:39,301 | DEBUG | System: Watchdog started 2025-10-21 10:12:43,106 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 fi nal_hop_value: via_mqtt:False transport_mechanism:unknown 2025-10-21 10:12:43,107 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsSttn1 2025-10-21 10:12:43,113 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsSttn1 isDM:True p laying:False 2025-10-21 10:12:43,114 | INFO | Device:1 Sending DM: 🏓PONG To: ZedIsSttn1 2025-10-21 10:12:51,868 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 fi nal_hop_value: via_mqtt:False transport_mechanism:unknown 2025-10-21 10:12:51,869 | INFO | Device:1 Channel: 0 Received DM: Test From: ZedIsSttn1 2025-10-21 10:12:51,870 | DEBUG | System: Bot detected Commands:[{'cmd': 'test', 'index': 0}] From: ZedIsSttn1 isDM:True p laying:False 2025-10-21 10:12:51,870 | INFO | Device:1 Sending DM: 🎙Roger that! To: ZedIsSttn1 <!-- github-comment-id:3425110193 -->
Author
Owner

That's kinda interesting, if one of my node connected with udp config enabled, while ping command it says ip-network, but when disabled, no rssi data for ping/test.

That's kinda interesting, if one of my node connected with udp config enabled, while ping command it says ip-network, but when disabled, no rssi data for ping/test. <!-- github-comment-id:3425270169 -->
Author
Owner

can you try a pull and let me know if this resolves the issue?

can you try a pull and let me know if this resolves the issue? <!-- github-comment-id:3427430892 -->
Author
Owner

can you try a pull and let me know if this resolves the issue?

Looks like it works. Will take a look if hops provided correctly.

> can you try a pull and let me know if this resolves the issue? Looks like it works. Will take a look if hops provided correctly. <!-- github-comment-id:3427672435 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshing-around#91