mirror of
https://github.com/SpudGunMan/meshing-around.git
synced 2026-11-03 07:22:23 +01:00
ping hops missing #93
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/meshing-around#93
Reference in new issue
Block a user
Hi.
One of users issued ping in a primary channel, and it looks like replay had missing data about hops:
2025-10-22 15:39:37,197 | INFO | Device:1 Sending DM: 🏓PONG To: tb RT003
Iam pretty sure it was this before:
INFO | Device:1 Sending DM: 🏓PONG 3 hops
Please fix it too like you did for rssi data.
Can I get the hop debugging?
Oh, my bad.
Looks like I have tested not on the latest source code.
Updated and it looks like it works.
The only moment question mark was added sometimes right in front of SNR and no idea what does it means.
2025-10-22 16:57:20,303 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 fi
nal_hop_value:Direct? via_mqtt:False transport_mechanism:unknown Hostname:None
2025-10-22 16:57:20,304 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsSttn1
2025-10-22 16:57:20,306 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsSttn1 isDM:True p
laying:False
2025-10-22 16:57:20,307 | INFO | Device:1 Sending DM: 🏓PONG ? SNR:6.0 RSSI:-45 To: ZedIsSttn1
^[2025-10-22 16:58:24,718 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0
final_hop_value:IP-Network via_mqtt:False transport_mechanism:unknown Hostname:None
2025-10-22 16:58:24,719 | INFO | Device:1 Channel: 0 Received DM: Test From: ZedIsSttn1
2025-10-22 16:58:24,721 | DEBUG | System: Bot detected Commands:[{'cmd': 'test', 'index': 0}] From: ZedIsSttn1 isDM:True p
laying:False
2025-10-22 16:58:24,723 | INFO | Device:1 Sending DM: 🎙Is this thing on? IP-Network To: ZedIsSttn1
2025-10-22 16:58:29,935 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 fi
nal_hop_value:IP-Network via_mqtt:False transport_mechanism:unknown Hostname:None
2025-10-22 16:58:29,940 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsSttn1
2025-10-22 16:58:29,942 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsSttn1 isDM:True p
laying:False
2025-10-22 16:58:29,943 | INFO | Device:1 Sending DM: 🏓PONG IP-Network To: ZedIsSttn1
Thanks I will patch this soon with some ideas to make it better.
I was thinking of replacing the ? With [GW] and [RF]
Nice, not sure what is GW, but card t1000-e was via rf, just in the same room:
2025-10-22 22:15:39,900 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:5 hop_start:5 calculated_hop_count:0 final_hop_value:Gateway via_mqtt:False transport_mechanism:unknown Hostname:None
2025-10-22 22:15:39,901 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsCard
2025-10-22 22:15:39,903 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsCard isDM:True playing:False
2025-10-22 22:15:39,904 | INFO | Device:1 Sending DM: 🏓PONG [GW] SNR:6.25 RSSI:-49 To: ZedIsCard
How is the bot code getting RF
Not sure what is this, but i have gor some [F]:
2025-10-23 14:28:26,964 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsPb
2025-10-23 14:28:26,965 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsPb isDM:True playing:False
2025-10-23 14:28:26,966 | INFO | Device:1 Sending DM: 🏓PONG [F] 2 Hops🐇 To: ZedIsPb
2025-10-23 14:28:43,538 | INFO | Device:1 Channel: 0 Received DM: Ping From: ZedIsPb
2025-10-23 14:28:43,540 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: ZedIsPb isDM:True playing:False
2025-10-23 14:28:43,540 | INFO | Device:1 Sending DM: 🏓PONG [F] 3 Hops🐇 To: ZedIsPb
Also i would like to ask you about possible autoping enhancement.
It is fine to work for 15 seconds while iam on a bike or a car, but a bit too fast when just walking across the street.
Is it possible to have some config feature to set autoping in between 15-90 sec?
Or maybe some syntax like ping 20@90 - 20 pings in a 90 sec each?
It's UDP nodes echoing turn on all the logging
What do you mean by that?
I was on my road walk with node without internet.
Bot answered via rf i assume, as via udp connected with the bot node there is only one local node that were client_mute
You are hop, and echo, via flood route not via direct?
As bot said 2 hops, when i was on my stret, i assume it was:
Me - someone1 - someone2 - bot
As we are building network without mqtt connectivity or lan for now.
It's gonna be -you, -someone, -your radio, -your bot. So two hops via flood route. Seems good watch hop debugger
2025-10-23 20:15:29,588 | DEBUG | System: Packet HopDebugger: hop_away:0 hop_limit:4 hop_start:5 calculated_hop_count:1 final_hop_value:1 Hop via_mqtt:False transport_mechanism:unknown Hostname:None
2025-10-23 20:15:29,589 | INFO | Device:1 Channel:0 ReceivedChannel: Ping From: M1DEA_2
2025-10-23 20:15:29,590 | DEBUG | System: Bot detected Commands:[{'cmd': 'ping', 'index': 0}] From: M1DEA_2 isDM:False playing:False
2025-10-23 20:15:29,590 | INFO | Device:1 Sending DM: 🏓PONG [F] SNR:4.5 RSSI:-90 To: M1DEA_2
Still F - is it normal?
If the packet came in via flood route yes the data for SNR is 3rd party
Still don't get the idea of what is that sorry.
https://meshtastic.org/docs/overview/mesh-algo/