Ben Meadors

Would this be a good place to mention other parters like Vercel for instance who have given us premium services?

Closes #1679

Yes `meshtastic --set serial.rxd 15 --set serial.txd 16` should do it. You can set this to any available GPIO ports that are capable of serial though.

Closing this. Serial module has been confirmed working for text message and should for the other portnums. Hopefully we'll get some of these avenues documented for folks.

That's a good thing. If they're sent over the serial portnum, they wouldn't show up in the messages for the apps. Which is a use case for some.

Was the device flashed via device-install.bat or device-install.sh script? This release has a new partitioning scheme for the esp32 boards.

@caveman99, would you mind taking a look at our platformio setup in light of the partition change? I'm having issues with esp32 devices after it (https://github.com/meshtastic/Meshtastic-device/commit/d6d936b5d2e5f8960092a0055fd64c1fc79dc63b) as well with just...

Closing this. On the latest releases cant repro after fresh flash on multiple permutation of T-Beams. Please comment if you have issues with the current release.

Hmmm, holding down the PWR button for 10 seconds is working on my node with the region unset screen.

Output: ``` 0x400e01e0: recordCriticalError(_CriticalErrorCode, unsigned int, char const*) at /home/runner/work/Meshtastic-device/Meshtastic-device/src/mesh/NodeDB.cpp:669 0x400f8383: pb_write at /home/runner/work/Meshtastic-device/Meshtastic-device/.pio/libdeps/tbeam/Nanopb/pb_encode.c:87 0x400df0d7: MeshModule::allocAckNak(_Routing_Error, unsigned int, unsigned int, unsigned char) at /home/runner/work/Meshtastic-device/Meshtastic-device/src/mesh/MeshModule.cpp:40 0x400e02fd: NodeDB::updatePosition(unsigned int, _Position const&, RxSource)...