⚠️ Check that radio.rxgain(on) and flood.advert.base (0.308) are set correctly after flashing! ⚠️

This build is based on official MeshCore 1.15.0 dev branch (as of 25-May-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR2553: Limit flood advert packet forwarding --> set flood.advert.base 0...1 (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)
• PR1810: Allow direct message paths when denyf * is set
• 🆕 PR1727: Use hardware channel activity detection for checking interference --> Use set int.thresh 1 to activate hw based channel activity detection.
• 🆕 PR2377: Disable NRF52 undervoltage bootlock feature

Additional changes:

• Flood adverts are disabled (flood.advert.interval set to 0) by default
• 🆕 modified PR1810 to not block flood adverts but only PAYLOAD_TYPE_GRP_TXT and PAYLOAD_TYPE_GRP_DATA so that some limited flood advert distribution can be managed via PR2553 to support e.g. observer maps.

Changelog:

• Based on dev v1.15.0 as of 25-May-2026

Full Changelog: v1.15.0-evo_0.1.20...v1.15.0-evo_0.1.21

⚠️ Check that radio.rxgain(on) and flood.advert.base (0.308) are set correctly after flashing! ⚠️

This build is based on official MeshCore 1.15.0 dev branch (as of 14-May-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR2553: Limit flood advert packet forwarding --> set flood.advert.base 0...1 (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)
• PR1810: Allow direct message paths when denyf * is set
• 🆕 PR1727: Use hardware channel activity detection for checking interference --> Use set int.thresh 1 to activate hw based channel activity detection.

Additional changes:

• RAK 4631, Xiao NRf, T114 variant: Lowered lockout voltage from 3.3V to 0V, preventing boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)
• Flood adverts are disabled (flood.advert.interval set to 0) by default
• 🆕 LORA_CR set to 8 as default in platformio.ini
• 🆕 modified PR1810 to not block flood adverts but only PAYLOAD_TYPE_GRP_TXT and PAYLOAD_TYPE_GRP_DATA so that some limited flood advert distribution can be managed via PR2553 to support e.g. observer maps.

Changelog:

• Based on dev v1.15.0 as of 14-May-2026

Full Changelog: v1.15.0-evo_0.1.19...v1.15.0-evo_0.1.20

This build is based on official MeshCore 1.15.0 dev branch (as of 24-Apr-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1338: Limit flood advert packet forwarding --> set flood.advert.base 0...1 (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)

• PR1810: Allow direct message paths when denyf * is set

• 🆕 PR1727: Use hardware channel activity detection for checking interference --> Use set int.thresh 1 to activate hw based channel activity detection.

Additional changes:

• RAK 4631, Xiao NRf, T114 variant: Lowered lockout voltage from 3.3V to 0V, preventing boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)
• Flood adverts are disabled (flood.advert.interval set to 0) by default
• 🆕 LORA_CR set to 8 as default in platformio.ini
• 🆕 modified PR1810 to not block flood adverts but only PAYLOAD_TYPE_GRP_TXT and PAYLOAD_TYPE_GRP_DATA so that some limited flood advert distribution can be managed via PR1338 to support e.g. observer maps.

Changelog:

• Based on dev v1.15.0 as of 24-Apr-2026

Full Changelog: v1.14.1-evo_0.1.18...v1.15.0-evo_0.1.19

This build is based on official MeshCore 1.14.1 dev branch (as of 05-Apr-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1338: Limit flood advert packet forwarding --> set flood.advert.base 0...1 (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)
• PR1810: Allow direct message paths when denyf * is set
• 🆕 PR1727: Use hardware channel activity detection for checking interference --> Use set int.thresh 1 to activate hw based channel activity detection.

Additional changes:

• RAK 4631, Xiao NRf, T114 variant: Lowered lockout voltage from 3.3V to 0V, preventing boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)
• Flood adverts are disabled (flood.advert.interval set to 0) by default
• 🆕 LORA_CR set to 8 as default in platformio.ini

Changelog:

• Based on dev v1.14.1 as of 05-Apr-2026

Full Changelog: v1.14.1-evo_0.1.17...v1.14.1-evo_0.1.18

This build is based on official MeshCore 1.14.1 dev branch (as of 29-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1338: Limit flood advert packet forwarding
• PR1810: Allow direct message paths when denyf * is set
• RAK 4631, Xiao NRf, T114 variant: Lowered lockout voltage from 3.3V to 0V, preventing boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)
• Flood adverts are disabled (flood.advert.interval set to 0) by default

PR1297, Implement token bucket duty cycle enforcement, has been merged upstream and is now part of the official dev branch. So this PR is also part of this firmware.

As a result this firmware will be suited for large and/or high density meshes:

• will reduce flood advert forwarding based on this proposal
• will handle packet forwarding better in case of denyf *

Recommended use:

• Set flood.advert.interval to zero or to 168 (weekly flood adverts), default is disabled for new installations
• Set advert.interval to 240 (every 4h)

Changelog:

• Based on dev v1.14.1 as of 29-Mar-2026

Full Changelog: v1.14.0-evo_0.1.16...v1.14.1-evo_0.1.17

This build is based on official MeshCore 1.14.0 dev branch (as of 17-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1338: Limit flood advert packet forwarding
• PR1810: Allow direct message paths when denyf * is set
• RAK 4631, Xiao NRf, T114 variant: Lowered lockout voltage from 3.3V to 0V, preventing boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)
• Flood adverts are disabled (flood.advert.interval set to 0) by default

PR1297, Implement token bucket duty cycle enforcement, has been merged upstream and is now part of the official dev branch. So this PR is also part of this firmware.

As a result this firmware will be suited for large and/or high density meshes:

• will reduce flood advert forwarding based on this proposal
• will handle packet forwarding better in case of denyf *

Recommended use:

• Set flood.advert.interval to zero or to 168 (weekly flood adverts), default is disabled for new installations
• Set advert.interval to 240 (every 4h)

Changelog:

• Based on dev v1.14.0 as of 17-Mar-2026

Full Changelog: v1.14.0-evo_0.1.15...v1.14.0-evo_0.1.16

This build is based on official MeshCore 1.14.0 dev branch (as of 08-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1297: Implement token bucket duty cycle enforcement

• PR1338: Limit flood advert packet forwarding

• PR1810: Allow direct message paths when denyf * is set

• RAK 4631, Xiao NRf, T114 variant: Lowered lockout voltage from 3.3V to 0V, preventing boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)

• Flood adverts are disabled (flood.advert.interval set to 0) by default

As a result this firmware will be suited for large and/or high density meshes:

• will reduce flood advert forwarding based on this proposal
• Implement rolling window duty cycle management, allowing for more robust tx operations of central/busy repeaters

Recommended use:

• Set flood.advert.interval to zero or to 168 (weekly flood adverts), default is disabled for new installations
• Set advert.interval to 240 (every 4h)

Changelog:

• Based on dev v1.14.0 as of 08-Mar-2026

Full Changelog: v1.14.0-evo_0.1.14...v1.14.0-evo_0.1.15

This build is based on the same commits as evo v0.1.13 is, just hours before the merge to main. But in order to prevent confusion I decided to re-release the evo firmware based on the official MeshCore v1.14.0 release.

So here it goes:

This build is based on official MeshCore 1.14.0 main branch (as of 06-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1297: Implement token bucket duty cycle enforcement

• PR1338: Limit flood advert packet forwarding

• PR1810: Allow direct message paths when denyf * is set

• RAK 4631 variant: Lowered lockout voltage from 3.3V to 0V, preventing RAK 4631 boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)

• Flood adverts are disabled (flood.advert.interval set to 0) by default

As a result this firmware will be suited for large and/or high density meshes:

• will reduce flood advert forwarding based on this proposal
• Implement rolling window duty cycle management, allowing for more robust tx operations of central/busy repeaters

Recommended use:

• Set flood.advert.interval to zero or to 168 (weekly flood adverts), default is disabled for new installations
• Set advert.interval to 240 (every 4h)

Changelog:

• Based on main v1.14.0 as of 06-Mar-2026

Change log of MeshCore v1.14.0:

• multibyte path hash support
• new ‘auto add max hops’ preference
• new radio AGC reset implementation
• HeltecV4 power fixes
• RAK3401 power optimisations
• Heltec Tracker V2 power fixes

Full Changelog: v1.13.0-evo_0.1.13...v1.14.0-evo_0.1.14

⚠️ I had to pull previous evo release v0.1.11 due to a build issue leading to a boot loop with ESP32 based repeaters (e.g. heltec v3/v4) when upgrading (#8). This has been fixed with this release. ⚠️

OK, it has only been a few days since the last evo build but many bugfixes (thanks @weebl2000!) have been merged upstream since. (AGC reset fix PR1743 being one of them, yay.)

So here it goes.

This build is based on official MeshCore 1.30 dev branch as of 05-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1297: Implement token bucket duty cycle enforcement

• PR1338: Limit flood advert packet forwarding

• PR1810: Allow direct message paths when denyf * is set

• RAK 4631 variant: Lowered lockout voltage from 3.3V to 0V, preventing RAK 4631 boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)

• Flood adverts are disabled (flood.advert.interval set to 0) by default

As a result this firmware will be suited for large and/or high density meshes:

• will reduce flood advert forwarding based on this proposal
• Implement rolling window duty cycle management, allowing for more robust tx operations of central/busy repeaters

Recommended use:

• Set flood.advert.interval to zero or to 168 (weekly flood adverts), default is disabled for new installations
• Set advert.interval to 240 (every 4h)

Changelog:

• Based on dev v1.13.0 as of 05-Mar-2026

Full Changelog: v1.13.0-evo_0.1.12...v1.13.0-evo_0.1.13

⚠️ I had to pull previous evo release v0.1.11 due to a build issue leading to a boot loop with ESP32 based repeaters (e.g. heltec v3/v4) when upgrading (#8). This has been fixed with this release. ⚠️

OK, it has only been a few days since the last evo build but many bugfixes (thanks @weebl2000!) have been merged upstream since. (AGC reset fix PR1743 being one of them, yay.)

So here it goes.

This build is based on official MeshCore 1.30 dev branch as of 04-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:

• PR1297: Implement token bucket duty cycle enforcement

• PR1338: Limit flood advert packet forwarding

• PR1810: Allow direct message paths when denyf * is set

• RAK 4631 variant: Lowered lockout voltage from 3.3V to 0V, preventing RAK 4631 boards operated with different battery chemistries like LTO or LiFePo4 from booting. This is an issue e.g. if uart.cz boards are being used. (See discussion here.)

• Flood adverts are disabled (flood.advert.interval set to 0) by default

As a result this firmware will be suited for large and/or high density meshes:

• will reduce flood advert forwarding based on this proposal
• Implement rolling window duty cycle management, allowing for more robust tx operations of central/busy repeaters

Recommended use:

• Set flood.advert.interval to zero or to 168 (weekly flood adverts), default is disabled for new installations
• Set advert.interval to 240 (every 4h)

Changelog:

• Based on dev v1.13.0 as of 04-Mar-2026

Full Changelog: v1.13.0-evo_0.1.10...v1.13.0-evo_0.1.12