[Bug]: RX packets ignored with error=-7 in LONG_MODERATE preset (Wio Tracker L1 Pro)

[spawnrider]

Category

Other

Hardware

Other

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.22.96dd647

Description

Bug: RX packets ignored with error=-7 in LONG_MODERATE preset (Wio Tracker L1 Pro)

Description

When using the LONG_MODERATE modem preset on a Wio Tracker L1 Pro, received packets are consistently ignored with error=-7 and classified as noise.

The issue does not occur when switching to LONG_FAST with the same configuration and environment.

This suggests a potential issue with the LONG_MODERATE preset handling (modem parameters, decoding, or compatibility).

---

Hardware

• Device: Seeed Wio Tracker L1 Pro
• Chipset: SX126x (assumed)
• Antenna: stock antenna

---

Firmware

• Meshtastic firmware version: 2.7.22.96dd647
• Other nodes firmware version: (same issue with 2.7.15.567b8ea Beta)

---

Region / Radio Settings

• Region: EU_868
• Frequency: 869.4625 MHz
• Modem preset:
  • ✅ LONG_FAST → works correctly
  • ❌ LONG_MODERATE → issue occurs
• TX Power: tested from 10 to 22 dBm
• RX Boosted Gain: ON
• Channel / PSK: identical on all nodes

---

Steps to Reproduce

1. Configure two nodes (including Wio Tracker L1 Pro) with:
   • same region (EU_868)
   • same frequency (869.4625 MHz)
   • same channel / PSK
2. Set modem preset to LONG_MODERATE on both nodes
3. Send messages between nodes

---

Expected Behavior

• Packets should be received and decoded normally
• ACK / rebroadcast should occur as expected

---

Actual Behavior

• Packets are received but ignored
• Logs show repeated errors:

ERROR [RadioIf] Ignore received packet due to error=-7
DEBUG [RadioIf] Packet RX (noise?)

• rxGood=0 while rxBad increases
• Reliable send fails and results in NAK

---

Additional Observations

• Same setup works immediately when switching to LONG_FAST
• Issue appears specific to LONG_MODERATE preset
• Devices tested at short range (2–5 meters)
• TX power variations do not change behavior
• Behavior suggests packets are received but not decodable

---

Logs

See below / attached log

---

Possible Cause (hypothesis)

• Incorrect modem parameters in LONG_MODERATE (SF/BW/CR mismatch)
• Demodulation or decoding issue specific to this preset
• Potential incompatibility between devices or firmware handling of LONG_MODERATE

---

Impact

• LONG_MODERATE preset unusable on this device in current conditions
• Prevents use of a balanced range/throughput configuration

---

Additional Info

Happy to provide additional logs, configs, or run targeted tests if needed.

Relevant log output

DEBUG | 23:54:28 54 [RadioIf] Started Tx (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x3b pri
DEBUG | 23:54:28 54 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:54:29 55 [RadioIf] Packet TX: 1036ms
DEBUG | 23:54:29 55 [RadioIf] Completed sending (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0
ERROR | 23:54:33 59 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x7ff0414d fr=0xe6ecdb54 to=0x8cffffff flags=0x4d rxSNR=-22 rxRSSI=-96 nextHop=0xc0 relay=0x5e)
DEBUG | 23:54:33 59 [RadioIf] Packet RX (noise?) : 3870ms
DEBUG | 23:54:34 60 SX126x AGC reset: warm sleep + Calibrate(0x7F)
DEBUG | 23:54:37 62 [Router] Sending retransmission fr=0x0,to=0xffffffff,id=0x90921373, tries left=2
INFO  | 23:54:37 62 [Router] Packet History - insert: Reusing slot aged 9.092s TRACE MATCHED PACKET
DEBUG | 23:54:37 62 [Router] Expand short PSK #1
DEBUG | 23:54:37 62 [Router] Use AES128 key!
DEBUG | 23:54:37 63 [Router] enqueue for send (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x
DEBUG | 23:54:37 63 [Router] txGood=1,txRelay=0,rxGood=0,rxBad=1
DEBUG | 23:54:37 63 [Router] Setting next retransmission in 9096 msecs: 
DEBUG | 23:54:37 63 [Router]  (id=0x90921373 fr=0x00000000 to=0xffffffff, transport = 0, WantAck=1, HopLim=3 Ch=0x3 Portnum=1 rxtime=1776203668 hopStart=3)
DEBUG | 23:54:38 63 [RadioIf] Started Tx (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x3b pri
DEBUG | 23:54:38 63 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:54:39 64 [RadioIf] Packet TX: 1036ms
DEBUG | 23:54:39 64 [RadioIf] Completed sending (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0
INFO  | 23:54:40 66 [DeviceTelemetry] Send: air_util_tx=0.057556, channel_utilization=9.903334, battery_level=98, voltage=4.163000, uptime=66
DEBUG | 23:54:40 66 [DeviceTelemetry] Partially randomized packet id 3239527930
DEBUG | 23:54:40 66 [DeviceTelemetry] updateTelemetry LOCAL
DEBUG | 23:54:40 66 [DeviceTelemetry] Node status update: 1 online, 2 total
INFO  | 23:54:40 66 [DeviceTelemetry] Send packet to phone
INFO  | 23:54:40 66 [DeviceTelemetry] Sending local stats: uptime=66, channel_utilization=9.903334, air_util_tx=0.057556, num_online_nodes=1, num_total_nodes=2
INFO  | 23:54:40 66 [DeviceTelemetry] num_packets_tx=2, num_packets_rx=1, num_packets_rx_bad=1
DEBUG | 23:54:40 66 [DeviceTelemetry] Partially randomized packet id 325431803
INFO  | 23:54:40 66 Tell client we have new packets 7
INFO  | 23:54:40 66 BLE notify fromNum
DEBUG | 23:54:40 66 FromRadio=STATE_SEND_PACKETS
DEBUG | 23:54:40 66 phone downloaded packet (id=0xc11745fa fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x0 Portnum=67 rxtime=1776203680 priority=10)
DEBUG | 23:54:40 66 FromRadio=STATE_SEND_PACKETS
DEBUG | 23:54:40 66 phone downloaded packet (id=0x1365b1fb fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x0 Portnum=67 rxtime=1776203680 priority=10)
DEBUG | 23:54:40 66 [Power] Battery: usbPower=0, isCharging=0, batMv=4163, batPct=98
DEBUG | 23:54:46 72 [Router] Sending retransmission fr=0x0,to=0xffffffff,id=0x90921373, tries left=1
INFO  | 23:54:46 72 [Router] Packet History - insert: Reusing slot aged 9.203s TRACE MATCHED PACKET
DEBUG | 23:54:46 72 [Router] Expand short PSK #1
DEBUG | 23:54:46 72 [Router] Use AES128 key!
DEBUG | 23:54:47 72 [Router] enqueue for send (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x
DEBUG | 23:54:47 72 [Router] txGood=2,txRelay=0,rxGood=0,rxBad=1
DEBUG | 23:54:47 72 [Router] Setting next retransmission in 9096 msecs: 
DEBUG | 23:54:47 72 [Router]  (id=0x90921373 fr=0x00000000 to=0xffffffff, transport = 0, WantAck=1, HopLim=3 Ch=0x3 Portnum=1 rxtime=1776203668 hopStart=3)
DEBUG | 23:54:47 72 [RadioIf] Started Tx (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x3b pri
DEBUG | 23:54:47 72 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:54:48 73 [RadioIf] Packet TX: 1036ms
DEBUG | 23:54:48 73 [RadioIf] Completed sending (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0
DEBUG | 23:54:56 81 [Router] Reliable send failed, returning a nak for fr=0x0,to=0xffffffff,id=0x90921373
DEBUG | 23:54:56 81 [Router] Partially randomized packet id 3942054396
WARN  | 23:54:56 81 [Router] Alloc an err=5,to=0x10b9183b,idFrom=0x90921373,id=0xeaf6f9fc
DEBUG | 23:54:56 81 [Router] Enqueued local (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 priority=1
DEBUG | 23:54:56 81 [Router] cancelSending id=0x90921373, removed=0
DEBUG | 23:54:56 81 [Router] Rx someone rebroadcasting for us (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=177
DEBUG | 23:54:56 81 [Router] Didn't find pending packet
INFO  | 23:54:56 81 [Router] Packet History - insert: Using new slot @uptime 81.330s TRACE NEW
DEBUG | 23:54:56 81 [Router] handleReceived(REMOTE) (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 pr
DEBUG | 23:54:56 81 [Router] Module 'routing' wantsPacket=1
INFO  | 23:54:56 81 [Router] Received routing from=0x10b9183b, id=0xeaf6f9fc, portnum=5, payloadlen=2
DEBUG | 23:54:56 81 [Router] Routing sniffing (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 priority
DEBUG | 23:54:56 81 [Router] Received a NAK for 0x0, stopping retransmissions
DEBUG | 23:54:56 81 [Router] Delivering rx packet (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 prio
DEBUG | 23:54:56 81 [Router] Ignore update from self
DEBUG | 23:54:56 81 [Router] Forwarding to phone (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 prior
DEBUG | 23:54:56 81 [Router] Module 'routing' considered
INFO  | 23:54:56 81 Tell client we have new packets 8
INFO  | 23:54:56 81 BLE notify fromNum
DEBUG | 23:54:56 81 FromRadio=STATE_SEND_PACKETS
DEBUG | 23:54:56 81 phone downloaded packet (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 p
ERROR | 23:55:02 87 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x7ff09d70 fr=0x97ecdb54 to=0x88ffffff flags=0x4d rxSNR=-24.75 rxRSSI=-93 nextHop=0x79 relay=0xb1)
DEBUG | 23:55:02 87 [RadioIf] Packet RX (noise?) : 1904ms

[Nevermore-42]

I had the impression that "error =-7" is an generic error message when something goes wrong on the RX side.
Since (if I am not mistaken) LONG_MODERATE takes twice (or maybe even more) as much time on air to TX the same message vs LONG_FAST, couldn't this be just noise that there is in the band that gets amplified to unusable levels?

[GUVWAF]

Yes, this error means a packet was detected, but the CRC did not match, hence there was an error while decoding the packet. Your airtime is very long: Packet RX (noise?) : 3870ms, and yes, then this may happen more frequently especially if there is interference.

You mention "Configure two nodes (including Wio Tracker L1 Pro)"; are both nodes the Wio Tracker L1 Pro?

[spawnrider]

Yes, this error means a packet was detected, but the CRC did not match, hence there was an error while decoding the packet. Your airtime is very long: Packet RX (noise?) : 3870ms, and yes, then this may happen more frequently especially if there is interference.

You mention "Configure two nodes (including Wio Tracker L1 Pro)"; are both nodes the Wio Tracker L1 Pro?

No, the second one is a Lilygo T beam. The two nodes were spaced a maximum of 1m apart?

[GUVWAF]

Okay, that's good info to have. Which T-Beam version is it? Most of those do not have a TCXO, which can cause them to drift, especially with longer packets: https://youtu.be/PND1GlMSrEM

[spawnrider]

I think this is one the first version (T22_V1.0) :

[GUVWAF]

Yes, that one doesn't have a TCXO, which is likely the cause of what you're observing.

[spawnrider]

Ok, I will buy a new TBeam to compare the results and check with the Wio.

But how do you explain that the communication is working between my old TBeam and a new one (V1.2) ?

[GUVWAF]

A reason I can think of is that each chip will have a different offset from the actual carrier frequency (usually only a couple kHz). Normally the chip can compensate for this (for LoRa it should be within 25% of the used bandwidth I believe), but if the offset changes during the transmission when the chip heats up, this might fail.
I can imagine that if the initial offset of the receiving hardware is close to that of the transmitter, it might work. So it might even be that it does work with another Wio Tracker L1.

[nightjoker7]

The error=-7 (RADIOLIB_ERR_CRC_MISMATCH) flood has a root cause that's separate from TCXO crystal offset variance: every 60 seconds, the AGC calibration path (resetAGC → CALIBRATE_ALL) wipes register 0x8B5, which was applied in init() by #9571 and #9777 for improved SX1262 RX sensitivity. That register controls low-noise frontend behavior; losing it drops sensitivity by ~6–10 dB until next boot.

Borderline-SNR packets that decoded fine on first boot start failing CRC after the first AGC reset. LONG_MODERATE runs at thinner SNR margins than LONG_FAST, so this surfaces there first — which matches why you see a flood of error=-7 in this preset specifically.

Fixed and merged in #10219 two days ago (SX126x: re-apply 0x8B5 register in resetAGC()). Worth pulling develop and seeing if your error=-7 rate drops from "sustained" to "occasional noise-floor events."

Not a full explanation of your TBeam-vs-Wio delta — TCXO variance still matters for edge cases as @GUVWAF noted — but I'd expect the bulk of the error=-7 floor to drop to near-zero once 2.7.24 or a develop build with #10219 propagates to your hardware.

[GUVWAF]

The case described here is not one of borderline sensitivity, the devices were only a meter apart.
I don't think you'll see anything different with that patch, but happy to be proved wrong.

[spawnrider]

I’ve just bought a new T-Beam (v1.2). All my nodes are configured in LONG_MODERATE — this applies to both of my T-Beams and my Seeed Wio.

The two T-Beams are clearly communicating well with each other in both directions, so that part seems to be working fine.

However, my Seeed Wio is not working. I’m consistently getting the same error.

Here are the logs:

ERROR | 20:10:42 728 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x7fe11f0a fr=0x8c422e23 to=0xf8ffffff flags=0x4d rxSNR=-24.5 rxRSSI=-93 nextHop=0x83 relay=0x60)
DEBUG | 20:10:42 728 [RadioIf] Packet RX (noise?) : 2035ms
ERROR | 20:11:08 754 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x4f65d235 fr=0x3d3a7ae8 to=0xffffffff flags=0x4d rxSNR=-30.25 rxRSSI=-82 nextHop=0xc5 relay=0x85)
DEBUG | 20:11:08 754 [RadioIf] Packet RX (noise?) : 1249ms
ERROR | 20:11:20 766 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x4f65a2c1 fr=0xcc9c0815 to=0x1fffffff flags=0x4d rxSNR=13 rxRSSI=-50 nextHop=0xae relay=0x6)
DEBUG | 20:11:20 766 [RadioIf] Packet RX (noise?) : 4395ms
ERROR | 20:11:28 774 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x4f65022c fr=0x623a7ae8 to=0xffffffff flags=0x4d rxSNR=31.75 rxRSSI=-80 nextHop=0xf5 relay=0x7a)
DEBUG | 20:11:28 774 [RadioIf] Packet RX (noise?) : 1249ms
ERROR | 20:11:32 778 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x4f651a28 fr=0x9d18e289 to=0x3b2b148c flags=0x43 rxSNR=-22.25 rxRSSI=-100 nextHop=0x3 relay=0xde)
DEBUG | 20:11:32 778 [RadioIf] Packet RX (noise?) : 3346ms
DEBUG | 20:11:33 780 SX126x AGC reset: warm sleep + Calibrate(0x7F)
INFO  | 20:11:39 786 [DeviceTelemetry] Send: air_util_tx=0.417333, channel_utilization=17.065001, battery_level=98, voltage=4.163000, uptime=786
DEBUG | 20:11:39 786 [DeviceTelemetry] Partially randomized packet id 727318861
DEBUG | 20:11:39 786 [DeviceTelemetry] updateTelemetry LOCAL
DEBUG | 20:11:39 786 [DeviceTelemetry] Node status update: 1 online, 2 total

This makes me think that the assumption suggesting the issue was related to the T-Beam v1.0 might not be correct, since I’m seeing the same problem with the v1.2.

At this point, it seems more likely that the issue is on the Wio side.

What do you think?

[spawnrider]

I just compiled and installed the develop firmware version. I confirm that there is no more error=-7 but still having the Tx/Rx issue...

DEBUG | 23:06:33 69 [RadioIf] Started Tx (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0x3b pri
DEBUG | 23:06:33 69 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:06:35 70 [RadioIf] Packet TX: 1249ms
DEBUG | 23:06:35 70 [RadioIf] Completed sending (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0
DEBUG | 23:06:43 78 [Router] Sending retransmission fr=0x0,to=0xffffffff,id=0x7e36dd30, tries left=2
INFO  | 23:06:43 78 [Router] Packet History - insert: Reusing slot aged 9.683s TRACE MATCHED PACKET
DEBUG | 23:06:43 78 [Router] Expand short PSK #1
DEBUG | 23:06:43 78 [Router] Use AES128 key!
DEBUG | 23:06:43 79 [Router] enqueue for send (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0x
DEBUG | 23:06:43 79 [Router] txGood=4,txRelay=0,rxGood=0,rxBad=0
DEBUG | 23:06:43 79 [Router] Setting next retransmission in 9686 msecs: 
DEBUG | 23:06:43 79 [Router]  (id=0x7e36dd30 fr=0x00000000 to=0xffffffff, transport = 0, WantAck=1, HopLim=3 Ch=0x0 Portnum=1 rxtime=1777590393 hopStart=3)
DEBUG | 23:06:43 79 [RadioIf] Started Tx (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0x3b pri
DEBUG | 23:06:43 79 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:06:44 80 [RadioIf] Packet TX: 1249ms
DEBUG | 23:06:44 80 [RadioIf] Completed sending (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0
DEBUG | 23:06:52 88 [Router] Sending retransmission fr=0x0,to=0xffffffff,id=0x7e36dd30, tries left=1
INFO  | 23:06:52 88 [Router] Packet History - insert: Reusing slot aged 9.793s TRACE MATCHED PACKET
DEBUG | 23:06:52 88 [Router] Expand short PSK #1
DEBUG | 23:06:52 88 [Router] Use AES128 key!
DEBUG | 23:06:52 88 [Router] enqueue for send (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0x
DEBUG | 23:06:52 88 [Router] txGood=5,txRelay=0,rxGood=0,rxBad=0
DEBUG | 23:06:52 88 [Router] Setting next retransmission in 9686 msecs: 
DEBUG | 23:06:52 88 [Router]  (id=0x7e36dd30 fr=0x00000000 to=0xffffffff, transport = 0, WantAck=1, HopLim=3 Ch=0x0 Portnum=1 rxtime=1777590393 hopStart=3)
DEBUG | 23:06:53 89 [RadioIf] Started Tx (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0x3b pri
DEBUG | 23:06:53 89 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:06:54 90 [RadioIf] Packet TX: 1249ms
DEBUG | 23:06:54 90 [RadioIf] Completed sending (id=0x7e36dd30 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x59 encrypted len=26 rxtime=1777590393 hopStart=3 relay=0
DEBUG | 23:07:02 98 [Router] Reliable send failed, returning a nak for fr=0x0,to=0xffffffff,id=0x7e36dd30
DEBUG | 23:07:02 98 [Router] Partially randomized packet id 3839688182
WARN  | 23:07:02 98 [Router] Alloc an err=5,to=0x10b9183b,idFrom=0x7e36dd30,id=0xe4dcfdf6
DEBUG | 23:07:02 98 [Router] Enqueued local (id=0xe4dcfdf6 fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x0 Portnum=5 requestId=7e36dd30 rxtime=1777590422 priority=1
DEBUG | 23:07:02 98 [Router] cancelSending id=0x7e36dd30, removed=0
DEBUG | 23:07:02 98 [Router] Rx someone rebroadcasting for us (id=0xe4dcfdf6 fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x0 Portnum=5 requestId=7e36dd30 rxtime=177
DEBUG | 23:07:02 98 [Router] Didn't find pending packet
INFO  | 23:07:02 98 [Router] Packet History - insert: Using new slot @uptime 98.536s TRACE NEW
DEBUG | 23:07:02 98 [Router] handleReceived(REMOTE) (id=0xe4dcfdf6 fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x0 Portnum=5 requestId=7e36dd30 rxtime=1777590422 pr
DEBUG | 23:07:02 98 [Router] Module 'routing' wantsPacket=1
INFO  | 23:07:02 98 [Router] Received routing from=0x10b9183b, id=0xe4dcfdf6, portnum=5, payloadlen=2
DEBUG | 23:07:02 98 [Router] Routing sniffing (id=0xe4dcfdf6 fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x0 Portnum=5 requestId=7e36dd30 rxtime=1777590422 priority
DEBUG | 23:07:02 98 [Router] Received a NAK for 0x0, stopping retransmissions
DEBUG | 23:07:02 98 [Router] Delivering rx packet (id=0xe4dcfdf6 fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x0 Portnum=5 requestId=7e36dd30 rxtime=1777590422 prio
DEBUG | 23:07:02 98 [Router] Ignore update from self
```

[spawnrider]

I also check the signal using an RTL/SDR, there is no bandwith drift or shift at all :(

[GUVWAF]

So it looks like now it is not receiving anything at all (it doesn't even detect a valid LoRa header). Do the other devices receive its transmission?

And to be clear: the signal in the waterfall is from the Wio Tracker, right?

I'm wondering if maybe you are too close to the other devices (saturating the input of the Wio Tracker). Can you try it at a further distance, or maybe try decreasing the transmit power of the T-Beams?