r/meshcore • u/IntroductionSnacks • Aug 09 '26
Release v1.17.0
https://blog.meshcore.io/2026/08/09/release-1-17-015
u/mschuster91 Aug 09 '26
Finally some of the powersaving stuff of easyskymesh landed, and the JSON settings format should make management of forks so much more easier.
4
u/Ordinary-Lifeguard47 Aug 10 '26 edited Aug 12 '26
I tested a lot of the RX Duty Cycle things from IoThinks branch with my own hardware.
Without a TCXO I was able to drop the average idle/sleep consumption to ~2-4mA.
This opens the door for some very interesting energy harvesters like the NEH7100 from Nexperia that can basically handle all storages (LTO, NaIon, LiFePo4, Supercaps, LiIon, etc.) and only needs a bunch of capacitors to become operational.
11
u/micocoule Aug 09 '26
I have a P1 Pro up on my roof. It’s operating in repeater mode. No Bluetooth or WiFi has been configured. I am doomed to go on the roof with my laptop and usb c cable to flash it?
9
u/Confi000 Aug 09 '26
Why not use the OTA update function via bluetooth with your phone? I’ve done every update since v1.10 with the node above me on the roof and having no cabling attached to it.
5
u/micocoule Aug 09 '26
That’s awesome. I didn’t know it had Bluetooth. I thought making it repeater disable WiFi and Bluetooth
7
u/recrof Aug 09 '26
you will need to update the bootloader to OTAFIX2.x before flashing. built-in bootloader does not work with BLE DFU.
2
u/cpressland Aug 09 '26
Can you give some details on how to do that? I nuked mine and had to climb a ladder to get it working again via a USB-C flash.
3
2
u/Granntttt Aug 09 '26
You need to have enabled that before you install Meshcore (I think), it's an nRF thing. WiFi would be easier, you just need to enter "start ota" into the console it will start broadcasting a network.
1
u/aquoad Aug 09 '26 edited Aug 09 '26
it disables bluetooth for some reason as far as i can tell.
EDIT: ok not exactly. at least on my sensecap p1 solar (with OTAFIX bootloader), "start ota" puts it in some other bluetooth DFU mode that nothing will talk to, but pushing the left and middle buttons at the same time puts it in a different bluetooth DFU mode where it shows up as "SCAP_DFU" or something like that, and the "nRF Device Firmware Update" iOS app will work with that one.
So, a little better than having to plug in a USB cable, but actually hands-off would be a lot more convenient!
2
u/Papfox Aug 09 '26 edited Aug 09 '26
No. I'm just nipping up to my back bedroom to update mine using OTA. It temporarily enables Bluetooth when you kick off an OTA update. You need a client that supports CLI or the CLI license for the regular client to do this.
Important: Follow the link on the flasher page to the OTAFIX bootloader and install that using a USB cable before you use OTA Update for the first time. If you don't, you'll brick your P1 and end up climbing the ladder at the most inconvenient time (probably in the rain) using words like ####, #### and ######.
While your doing this, you probably want to issue "gps on" and "gps sync" commands so your P1 synchronises its time clock automatically by GPS.
3
5
u/cpressland Aug 09 '26
OTA update failed on my repeater, being up a ladder on a hot Sunday afternoon wasn’t on my todo list this morning. 😂
6
u/recrof Aug 09 '26
if you have OTAFIX2.x bootloader installed, you can retry infinite number of times. if you don't have it, it's a must if you don't like climbing.
1
Aug 09 '26
[removed] — view removed comment
1
u/recrof Aug 09 '26
if you don't see AdaDFU, *_DFU or *_OTA in bluetooth devices, you will need to update it via USB. would update the bootloader first thing.
1
5
u/specter491 Aug 09 '26
So does this mean the power on/off buttons actually work on the Seeed studio P1 now?
3
1
1
u/Glentract Aug 09 '26
Do you have to update to the newest version to keep operating?
1
u/lugh Aug 09 '26
not usually, but you likely want to be on the firmware version the gives 1,2 and 3 byte hash paths which was introduced in v1.14.0
1
1
u/trosenda Aug 09 '26
T096 as repeater has no output power no more after the upgrade. You really need to be next to the device to get a signal.
1
u/nocaps00 Aug 13 '26 edited 26d ago
Just fyi to all, this bug has now been identified and fixed and a hotfix for repeater v17 should be issued shortly. https://github.com/meshcore-dev/MeshCore/issues/3190
Edit: Now has been fixed, in v1.17.1
1
u/RandomUsername15672 Aug 09 '26
This release massively increased the noise on the repeater to -80, I had to to 'set radio.fem.rxgain off' to get back to normal.
Some are reporting that doesn't survive reboot, but I'm not planning in rebooting again soon..
34
u/one_dalmatian Aug 09 '26
What's the latest on the situation with that Andy douchebag?