EasySkyMesh released PowerSaving 15 on April 24, 2026, and the headline this time is on the companion side. ESP32 BLE companions drop from a typical idle of 120 mA to 15-20 mA with power saving on. That’s an order-of-magnitude reduction on the firmware that pairs with your phone. Built on top of MeshCore v1.15.0.

The other big addition is on the repeater side. Repeaters and room servers running EasySkyMesh now apply a timestamp offset during powersaving on that eliminates the time drift operators have been quietly working around for months. That one is flagged BETA in the release notes. Important caveat. We’ll get to it.
Numbers below come from the PowerSaving 15 release notes and the 15.0.1 hotfix notes added to that same release page on April 27 and May 4.
ESP32 BLE Companion Power Saving
This is the headline. Until now, ESP32 BLE companion power saving in EasySkyMesh was a beta for the Heltec V3 and V4 only (added in 14.1.1, at 32 mA and 39 mA). PowerSaving 15 makes it official for all ESP32, ESP32-S3 and ESP32-C3 BLE companions. Without it, phones connected over BLE meant a node sitting at around 120 mA idle, which is fine on USB but punishing on a battery. PowerSaving 15 changes that. With power saving on, the same boards land in the 15-20 mA range while still keeping the BLE link alive for the connected phone.
Supported variants in this release:
- Xiao S3 at around 16.3 mA
- Xiao C3 at around 15.1 mA
- Heltec V3 at around 19.6 mA
- Heltec V4.2 and V4.3 at around 24.9 mA with the FEM LNA on, and the V4.3 at around 18 mA with it off
The release also picks up a hotfix on May 4. Version 15.0.1 for ESP32 BLE companions skips the sleep cycle when a BLE read is in progress and trims the sleep period from 50 ms down to 10 ms. The practical effect is BLE responsiveness during sustained reads (think contact list sync, location sharing, an active conversation in the app) without giving up the idle savings when the phone is quiet. If you flashed 15.0 before May 4, re-flash to get the hotfix.
No Time Drift on Repeaters
The second big addition is for repeaters and room servers. Time drift on EasySkyMesh nodes has been a known annoyance. Long-running powersave nodes accumulate clock skew because the sleep cycles aren’t perfectly accounted for in the system clock. PowerSaving 15 addresses that with a timestamp offset applied during powersaving on. Net effect: no drift over the kind of multi-day runs where it used to add up.
The release notes flag this BETA. Treat it that way. If you’re running a sensor logger or anything where timestamps matter for downstream analysis, test it on an easy-to-reach node before rolling it across your repeater fleet. If you do run into drift on 15.0, please report it back upstream. The maintainer is responsive and the cycle time on hotfixes has been good (see: the May 4 BLE companion patch landing 10 days after the initial release).
Idle Current Numbers Across the Board
PowerSaving 15 ships with consolidated idle-current targets across the supported boards. Numbers from the release notes (the individual board rows are BLE companion figures):
| Board | Before | With Powersaving |
|---|---|---|
| Heltec V3 (ESP32) | ~100 mA | 19.6 mA |
| Heltec V4.2 / V4.3 (FEM ON) | ~120 mA | 24.9 mA |
| Heltec V4.3 (FEM Off) | ~120 mA | 18 mA |
| Xiao S3 | ~70 mA | 16.3 mA |
| Xiao C3 | ~70 mA | 15.1 mA |
| ESP32 BLE Companion | ~120 mA | 15-20 mA |
| ESP32 Repeaters | 50+ mA | 10-13 mA |
The Heltec V4.3 companion rows show the same lever we covered in the PowerSaving 14.1 post: 24.9 mA with the FEM LNA on, 18 mA with it off. FEM LNA control is still the lever that does the heavy lifting on high-power boards. If you haven’t been using radio.fem.rxgain off on your V4.3 repeaters, that’s where the easiest wins still live.
What’s Not Supported Yet
Worth flagging clearly. ESP32C6, including the Xiao C6, is not supported by PowerSaving 15. If you bought a C6 expecting parity with the C3, it’s not there in this release. Watch the next release for ESP32C6 coverage. In the meantime, the C3 and S3 variants are well covered.
The release also picks up a separate April 27 hotfix for Heltec V4 repeaters and room servers. That patch added the missing get radio.fem.rxgain, made the radio.fem.rxgain setting survive reboots, and applied the latest changes from upstream MeshCore PR #2140. (The release notes spell it “rxgrain”, but the command in the source is radio.fem.rxgain.) If you flashed PowerSaving 15 between April 24 and April 27, re-flashing picks up that fix.
The May 4 Hotfix in Detail
Worth its own callout because it’s fresh. PowerSaving 15.0.1 for ESP32 BLE companions:
- Skipped sleep when BLE read is busy. Prevents the node from dropping into sleep mid-read, which was causing perceptible lag in app interactions during sync events.
- Reduced sleep period from 50 ms to 10 ms. Tighter wake cadence means the BLE stack can service requests faster without waiting for the next 50 ms boundary.
The two changes work together. The skip handles the case where a read is in progress. The shorter period handles the case between reads. Net effect is a more responsive BLE link while keeping the idle current win.
How to Flash
Upgrade existing devices. Download upgrade.bin from the release.
Fresh installs. Download freshInstall-merged.bin.
Detailed flashing instructions: Flash Custom Firmware Guide.
Source code: PowerSaving-v15 branch.
Download EasySkyMesh PowerSaving 15 (the 15.0.1 hotfix files are on the same release page).
Should You Update
If you’re running an ESP32 BLE companion on battery, this is the release you’ve been waiting for. The 15 to 20 mA idle band is what makes a phone-paired node viable for multi-day runs without scheduled charging. Upgrade.
If you’re running repeaters with PowerSaving 14.1, the no-time-drift addition is worth taking. Flag it BETA in your own head and pin one node to 15.0 before rolling it broadly. If your network logs depend on accurate timestamps, this is finally a fix that doesn’t require a workaround on your side.
If you’re on an ESP32C6 / Xiao C6 board, sit this one out and watch the next release.
Upgrade your easy-to-access devices first. Same advice we gave for 14.1, same reason. Test the new behavior on nodes you can reach before pushing it to your rooftop fleet.
Support the Developer
Power optimization, board-specific tuning, BLE companion work, and rapid hotfix turnaround. This is the work that makes MeshCore deployable on real batteries in real conditions. If EasySkyMesh is running anywhere on your network:
- PayPal: paypal.me/iotthinks
- GitHub Sponsors: github.com/sponsors/IoTThinks
Newer PowerSaving builds, and every earlier one, are listed in our EasySkyMesh release tracker.
This post covers community firmware built on MeshCore. NodakMesh isn’t affiliated with EasySkyMesh or IoTThinks. We highlight ecosystem work that makes mesh networking more practical for everyone. For more on the base firmware this release builds on, see our MeshCore v1.15.0 release post.
Comments
Related Posts

EasySkyMesh Power Saving 14.1: Heltec V4.3 at 5.5 mA
EasySkyMesh 14.1 brings Heltec V4.3 support at 5.5 mA idle, FEM LNA toggle for 1W boards, powerlog CLI, and nRF52 companion savings to 5.8 mA.

EasySkyMesh PowerSaving 18: Beta on MeshCore 1.18
EasySkyMesh PowerSaving 18 is a beta on MeshCore 1.18 that turns power saving on by default for new installs. What changed, which boards, and known issues.

EasySkyMesh PowerSaving 17: RX Sleep Down to 0.9 mA
EasySkyMesh PowerSaving 17 adds RX duty-cycle sleep, pushing RAK4631 repeaters to 0.9 mA. Built on MeshCore 1.16, plus a GPS powersaving catch-up.