GUVWAF

The firmware doesn't do this for direct messages, as we discussed in #3752. ~For direct messages in >2.5 it's also not really defined, as there's no "channel" settings for this...

Exciting! Unfortunately I get the following output with this currently: ``` ��@INFO | ??:??:?? 0 //\ E S H T /\ S T / C Program Error, 0x1 Program Error,...

Sounds really nice. Any idea on how long a write and read takes (since it seems this isn't asynchronous)?

Please see #6121: currently this causes the radio to be not detected, so the reorganization of the SPI definitions when using an SD card has to be revisited.

Please see my comment here: https://github.com/meshtastic/firmware/issues/6953#issuecomment-2952215969.

This issue is related to #6955. The issue is probably not hop count limitations, but because of how a `CLIENT` works. It will only forward the packet if it does...

> Routing from point A to point B should prioritize the most reliable nodes, and node configuration shouldn’t be something users need to worry about. Unfortunately this is much easier...

You can probably still reflash it with the CLI: https://meshtastic.org/docs/getting-started/flashing-firmware/esp32/cli-script/ You'll likely need to try to connect to it multiple times, because it only has a small amount of time...

Probably a good idea indeed, although it shouldn’t get a higher priority than ACKs, because those will stop retransmissions and rebroadcasting and thus prevent unnecessary transmissions. I think we’ll need...

Please double-check that you flashed the firmware for the correct device.