How are you sending packets? One to me looks like MQTT or injected like UDP. The fields are not mandatory and can be easily fudged as well.
How are you sending packets? One to me looks like MQTT or injected like UDP. The fields are not mandatory and can be easily fudged as well.
<!-- github-comment-id:2887966415 -->
I'm sending them over RF short fast. I can turn off UDP and MQTT and try again; but LF is the only other device on the LAN so it's just 2 radios on SF. Test was done with MQTT off on the G2
I'm sending them over RF short fast. I can turn off UDP and MQTT and try again; but LF is the only other device on the LAN so it's just 2 radios on SF. Test was done with MQTT off on the G2
<!-- github-comment-id:2887980406 -->
So to answer you won't have the RSSI and SNR values in those transmissions and they are null and need to be account for
```py
snr = -1
rssi = -1
if hop == "Direct":
msg = msg + hop + f" SNR:{snr} RSSI:{rssi}"
else:
msg = msg + hop + f" SNR:{snr} RSSI:{rssi}"
```
<!-- github-comment-id:2888012016 -->
I'll turn off UDP and mqtt and see if RF picks it up. It's been RF only tx from a t1000e as the unit sending out the test message
I'll turn off UDP and mqtt and see if RF picks it up. It's been RF only tx from a t1000e as the unit sending out the test message
<!-- github-comment-id:2888017998 -->
im gonna link and close this one, related in lots of ways. not sure how I will handle it yet. also see #security in mesh discord for ongoing issues.
im gonna link and close this one, related in lots of ways. not sure how I will handle it yet. also see #security in mesh discord for ongoing issues.
<!-- github-comment-id:3369166564 -->
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.
I changed the test command to always output this
Updated the env meshtastic to 2.6.3
The Routing app is getting the SNR and RSSI though
Going to nuke the folder and try a fresh install
Fresh install still has the issue. Open to debug ideas
How are you sending packets? One to me looks like MQTT or injected like UDP. The fields are not mandatory and can be easily fudged as well.
I'm sending them over RF short fast. I can turn off UDP and MQTT and try again; but LF is the only other device on the LAN so it's just 2 radios on SF. Test was done with MQTT off on the G2
So to answer you won't have the RSSI and SNR values in those transmissions and they are null and need to be account for
I'll turn off UDP and mqtt and see if RF picks it up. It's been RF only tx from a t1000e as the unit sending out the test message
From the log:
Full erase and flash of the firmware and I'm back with SNR and RSSI getting reported
Set some configuration options and the bug is back... so once I nail this down it'll probably be a firmware bug
meshtastic --set store_forward.enabled true
meshtastic --set store_forward.is_server true
That'll trigger the bug
Is the setup for this issue
A node running S&F and the bot?
Yes that's the setup for this bug. Infrastructure node was the idea. I'll do a pull request
im gonna link and close this one, related in lots of ways. not sure how I will handle it yet. also see #security in mesh discord for ongoing issues.
https://github.com/SpudGunMan/meshing-around/issues/196