Meshtastic T-Beam Supreme bug breaks compass and heading data

A T-Beam Supreme owner running Meshtastic firmware 2.7.25 hit a failure that goes straight to the heart of the board’s appeal: the compass errored out, the device would not run correctly, and heading data disappeared entirely. The bug report landed in Meshtastic’s hardware compatibility tracker, not in a general complaints thread, which makes it look less like a cosmetic glitch and more like a board-level break in the sensor stack.

That matters because the T-Beam Supreme is not a bare LoRa node. Meshtastic’s hardware docs place it in the LILYGO T-Beam family and describe it as an ESP32-S3 device with an SX1262 radio, Wi-Fi, Bluetooth 5, GPS, a 1.3-inch OLED, a BME280 air-pressure sensor, a QMI8658 IMU, a QMC6310 magnetometer and a PCF8563 RTC. In other words, heading and orientation are part of what people buy this board for, especially when they use Meshtastic for hiking, field tracking or any navigation-adjacent setup.

The timing makes the case even sharper. Meshtastic’s downloads page lists 2.7.15.567b8ea as stable, while 2.7.25.104df5f sits on the alpha track. The affected board was on the testing branch, which raises the stakes for anyone treating “supported” as a guarantee that core sensors will keep behaving the same after every flash.

The report, opened June 10 by EA7JRS, is categorized under Hardware Compatibility, Hardware and T-Beam S3. That framing points maintainers toward the questions that matter most: whether this is a firmware regression in 2.7.25, a board-variant mismatch, a calibration problem, or something lower in the stack such as sensor initialization or pin mapping. Meshtastic’s own flashing guidance for ESP32-S3 boards adds another wrinkle, since these devices typically rely on Espressif firmware download mode, either through the web flasher’s 1200bps reset flow or a manual BOOT-button procedure.

Meshtastic has already done dedicated work for this board class. A prior pull request for the T-Beam Supreme added IMU integration for the QMI8658 and QMC6310, using GPS-aided sensor fusion with a Madgwick filter. That history suggests heading support on the Supreme is not a generic on-off feature, but a specific software path that depends on the right board behavior and the right sensor plumbing.

For Supreme owners, the takeaway is practical. The board can still pass packets without heading, but once the compass breaks, the value of a tracker board drops fast. The failure now sits where Meshtastic can test it against board revisions and firmware branches, and that is exactly where a compatibility drift like this needs to be caught before it becomes the new normal.