{
  "id": "meshcore-evo",
  "name": "MeshCore-Evo",
  "type": "fork",
  "maintainer": "mattzzw",
  "description": "An improved repeater-focused fork of MeshCore that bundled pending upstream PRs and improvements for dense meshes — notably flood-advert traffic mitigation and enhanced `denyf *` handling. Largely superseded once official 1.16.0 added native flood traffic management.\n",
  "repository": "https://github.com/mattzzw/MeshCore-Evo",
  "website": "https://meshcore.io",
  "license": "MIT",
  "status": "maintenance",
  "lifecycle": "maintenance",
  "maturity": "beta",
  "distribution": "community",
  "lineage": {
    "kind": "fork",
    "upstreamFirmwareId": "meshcore-official",
    "upstreamRepository": "https://github.com/meshcore-dev/MeshCore"
  },
  "runtime": {
    "framework": "arduino",
    "language": "cpp"
  },
  "roles": [
    "companion",
    "repeater",
    "room-server"
  ],
  "features": [
    "Flood-advert traffic mitigation",
    "Enhanced denyf \"*\" handling",
    "Tuned for dense repeater meshes",
    "Tracks upstream MeshCore releases"
  ],
  "capabilities": {
    "protocol": {
      "meshcoreCompatible": true
    },
    "transports": {
      "ble": true,
      "usbSerial": true,
      "nativeTcp": true,
      "wifiAp": true
    },
    "operations": {
      "ota": true,
      "webFlasher": false
    },
    "networking": {
      "repeater": true,
      "roomServer": true,
      "observer": false,
      "kissModem": false
    },
    "hardware": {
      "gps": true,
      "display": true,
      "sensors": true,
      "lowPowerRx": true
    }
  },
  "devices": [
    {
      "id": "heltec-v3",
      "status": "supported"
    },
    {
      "id": "heltec-wsl3",
      "status": "supported"
    },
    {
      "id": "heltec-t114",
      "status": "supported"
    },
    {
      "id": "rak-4631",
      "status": "supported"
    },
    {
      "id": "uart-solar-node-station",
      "status": "supported"
    },
    {
      "id": "lilygo-t-beam-sx1262",
      "status": "supported"
    },
    {
      "id": "xiao-esp32s3",
      "status": "supported"
    },
    {
      "id": "station-g2",
      "status": "partial",
      "notes": "Builds available; less frequently tested than core repeater boards."
    }
  ],
  "source": {
    "path": "data/firmwares/meshcore-evo/firmware.yaml",
    "updatedAt": "2026-06-22T21:31:07+02:00"
  },
  "latest_version": "1.15.0-evo_0.1.21",
  "released": "2026-05-25",
  "releases": [
    {
      "version": "v1.15.0-evo_0.1.21",
      "name": "Meshcore-evo build 1.15.0_0.1.21 - 25-May-2026",
      "datetime": "2026-05-25T18:49:27Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.15.0-evo_0.1.21",
      "prerelease": false,
      "notes": "⚠️ Check that `radio.rxgain`(on) and `flood.advert.base` (0.308) are set correctly after flashing! ⚠️ \r\n\r\nThis 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:\r\n\r\n- PR2553: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/2553) --> `set flood.advert.base 0...1`   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n- :new: PR1727: [Use hardware channel activity detection for checking interference](https://github.com/meshcore-dev/MeshCore/pull/1727) --> Use `set int.thresh 1` to activate hw based channel activity detection.\r\n- :new: PR2377:    [Disable NRF52 undervoltage bootlock feature](https://github.com/meshcore-dev/MeshCore/pull/2377)\r\n\r\nAdditional changes:\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n- :new: 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.\r\n\r\nChangelog:\r\n- Based on `dev` v1.15.0 as of 25-May-2026\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.15.0-evo_0.1.20...v1.15.0-evo_0.1.21",
      "notesHtml": "<p>⚠️ Check that <code>radio.rxgain</code>(on) and <code>flood.advert.base</code> (0.308) are set correctly after flashing! ⚠️ </p>\n<p>This build is based on official MeshCore 1.15.0 <code>dev</code> branch (as of 25-May-2026 and <strong>additionally</strong> includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li>PR2553: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/2553\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a> --&gt; <code>set flood.advert.base 0...1</code>   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)</li>\n<li>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></li>\n<li>:new: PR1727: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1727\" target=\"_blank\" rel=\"noopener noreferrer\">Use hardware channel activity detection for checking interference</a> --&gt; Use <code>set int.thresh 1</code> to activate hw based channel activity detection.</li>\n<li>:new: PR2377:    <a href=\"https://github.com/meshcore-dev/MeshCore/pull/2377\" target=\"_blank\" rel=\"noopener noreferrer\">Disable NRF52 undervoltage bootlock feature</a></li>\n</ul>\n<p>Additional changes:</p>\n<ul>\n<li>Flood adverts are disabled (flood.advert.interval set to 0) by default</li>\n<li>:new: modified PR1810 to not block flood adverts but only <code>PAYLOAD_TYPE_GRP_TXT</code> and <code>PAYLOAD_TYPE_GRP_DATA</code> so that some limited flood advert distribution can be managed via PR2553 to support e.g. observer maps.</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.15.0 as of 25-May-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.15.0-evo_0.1.20...v1.15.0-evo_0.1.21\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.15.0-evo_0.1.20...v1.15.0-evo_0.1.21</a></p>\n"
    },
    {
      "version": "v1.15.0-evo_0.1.20",
      "name": "Meshcore-evo build 1.15.0_0.1.20 - 14-May-2026",
      "datetime": "2026-05-14T13:10:54Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.15.0-evo_0.1.20",
      "prerelease": false,
      "notes": "⚠️ Check that `radio.rxgain`(on) and `flood.advert.base` (0.308) are set correctly after flashing! ⚠️ \r\n\r\nThis 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:\r\n\r\n- PR2553: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/2553) --> `set flood.advert.base 0...1`   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n- :new: PR1727: [Use hardware channel activity detection for checking interference](https://github.com/meshcore-dev/MeshCore/pull/1727) --> Use `set int.thresh 1` to activate hw based channel activity detection.\r\n\r\nAdditional changes:\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n- :new: LORA_CR set to 8 as default in `platformio.ini`\r\n- :new: 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.\r\n\r\nChangelog:\r\n- Based on `dev` v1.15.0 as of 14-May-2026\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.15.0-evo_0.1.19...v1.15.0-evo_0.1.20",
      "notesHtml": "<p>⚠️ Check that <code>radio.rxgain</code>(on) and <code>flood.advert.base</code> (0.308) are set correctly after flashing! ⚠️ </p>\n<p>This build is based on official MeshCore 1.15.0 <code>dev</code> branch (as of 14-May-2026 and <strong>additionally</strong> includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li>PR2553: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/2553\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a> --&gt; <code>set flood.advert.base 0...1</code>   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)</li>\n<li>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></li>\n<li>:new: PR1727: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1727\" target=\"_blank\" rel=\"noopener noreferrer\">Use hardware channel activity detection for checking interference</a> --&gt; Use <code>set int.thresh 1</code> to activate hw based channel activity detection.</li>\n</ul>\n<p>Additional changes:</p>\n<ul>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n<li>Flood adverts are disabled (flood.advert.interval set to 0) by default</li>\n<li>:new: LORA_CR set to 8 as default in <code>platformio.ini</code></li>\n<li>:new: modified PR1810 to not block flood adverts but only <code>PAYLOAD_TYPE_GRP_TXT</code> and <code>PAYLOAD_TYPE_GRP_DATA</code> so that some limited flood advert distribution can be managed via PR2553 to support e.g. observer maps.</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.15.0 as of 14-May-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.15.0-evo_0.1.19...v1.15.0-evo_0.1.20\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.15.0-evo_0.1.19...v1.15.0-evo_0.1.20</a></p>\n"
    },
    {
      "version": "v1.15.0-evo_0.1.19",
      "name": "Meshcore-evo build 1.15.0_0.1.19 - 24-Apr-2026",
      "datetime": "2026-04-24T20:34:26Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.15.0-evo_0.1.19",
      "prerelease": false,
      "notes": "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:\r\n\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338) --> `set flood.advert.base 0...1`   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n\r\n- :new: PR1727: [Use hardware channel activity detection for checking interference](https://github.com/meshcore-dev/MeshCore/pull/1727) --> Use `set int.thresh 1` to activate hw based channel activity detection.\r\n- \r\nAdditional changes:\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n- :new: LORA_CR set to 8 as default in `platformio.ini`\r\n- :new: 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.\r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.15.0 as of 24-Apr-2026\r\n\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.1-evo_0.1.18...v1.15.0-evo_0.1.19",
      "notesHtml": "<p>This build is based on official MeshCore 1.15.0 <code>dev</code> branch (as of 24-Apr-2026 and <strong>additionally</strong> includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><p>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a> --&gt; <code>set flood.advert.base 0...1</code>   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)</p>\n</li>\n<li><p>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></p>\n</li>\n<li><p>:new: PR1727: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1727\" target=\"_blank\" rel=\"noopener noreferrer\">Use hardware channel activity detection for checking interference</a> --&gt; Use <code>set int.thresh 1</code> to activate hw based channel activity detection.</p>\n</li>\n<li></li>\n</ul>\n<p>Additional changes:</p>\n<ul>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n<li>Flood adverts are disabled (flood.advert.interval set to 0) by default</li>\n<li>:new: LORA_CR set to 8 as default in <code>platformio.ini</code></li>\n<li>:new: modified PR1810 to not block flood adverts but only <code>PAYLOAD_TYPE_GRP_TXT</code> and <code>PAYLOAD_TYPE_GRP_DATA</code> so that some limited flood advert distribution can be managed via PR1338 to support e.g. observer maps.</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.15.0 as of 24-Apr-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.1-evo_0.1.18...v1.15.0-evo_0.1.19\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.1-evo_0.1.18...v1.15.0-evo_0.1.19</a></p>\n"
    },
    {
      "version": "v1.14.1-evo_0.1.18",
      "name": "Meshcore-evo build 1.14.1_0.1.18 - 05-Apr-2026",
      "datetime": "2026-04-05T16:19:35Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.1-evo_0.1.18",
      "prerelease": false,
      "notes": "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:\r\n\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338) --> `set flood.advert.base 0...1`   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n- :new: PR1727: [Use hardware channel activity detection for checking interference](https://github.com/meshcore-dev/MeshCore/pull/1727) --> Use `set int.thresh 1` to activate hw based channel activity detection.\r\n- \r\nAdditional changes:\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n- :new: LORA_CR set to 8 as default in `platformio.ini`\r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.14.1 as of 05-Apr-2026\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.1-evo_0.1.17...v1.14.1-evo_0.1.18",
      "notesHtml": "<p>This build is based on official MeshCore 1.14.1 <code>dev</code> branch (as of 05-Apr-2026 and <strong>additionally</strong> includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a> --&gt; <code>set flood.advert.base 0...1</code>   (0: no flood adv. forwarding, 0.308: default, 1: all flood adv. forwarding)</li>\n<li>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></li>\n<li>:new: PR1727: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1727\" target=\"_blank\" rel=\"noopener noreferrer\">Use hardware channel activity detection for checking interference</a> --&gt; Use <code>set int.thresh 1</code> to activate hw based channel activity detection.</li>\n<li></li>\n</ul>\n<p>Additional changes:</p>\n<ul>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n<li>Flood adverts are disabled (flood.advert.interval set to 0) by default</li>\n<li>:new: LORA_CR set to 8 as default in <code>platformio.ini</code></li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.14.1 as of 05-Apr-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.1-evo_0.1.17...v1.14.1-evo_0.1.18\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.1-evo_0.1.17...v1.14.1-evo_0.1.18</a></p>\n"
    },
    {
      "version": "v1.14.1-evo_0.1.17",
      "name": "Meshcore-evo build 1.14.1_0.1.17 - 29-Mar-2026",
      "datetime": "2026-03-29T09:44:50Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.1-evo_0.1.17",
      "prerelease": false,
      "notes": "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:\r\n\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nPR1297, [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297), has been merged upstream and is now part of the official dev branch. So this PR is also part of this firmware.\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- will handle packet forwarding better in case of `denyf *`\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.14.1 as of 29-Mar-2026\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.16...v1.14.1-evo_0.1.17",
      "notesHtml": "<p>This build is based on official MeshCore 1.14.1 <code>dev</code> branch (as of 29-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></li>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n<li>Flood adverts are disabled (flood.advert.interval set to 0) by default</li>\n</ul>\n<p>PR1297, <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a>, has been merged upstream and is now part of the official dev branch. So this PR is also part of this firmware.</p>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>will handle packet forwarding better in case of <code>denyf *</code></li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.14.1 as of 29-Mar-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.16...v1.14.1-evo_0.1.17\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.16...v1.14.1-evo_0.1.17</a></p>\n"
    },
    {
      "version": "v1.14.0-evo_0.1.16",
      "name": "Meshcore-evo build 1.14.0_0.1.16 - 17-Mar-2026",
      "datetime": "2026-03-17T12:49:02Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.0-evo_0.1.16",
      "prerelease": false,
      "notes": "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:\r\n\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nPR1297, [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297), has been merged upstream and is now part of the official dev branch. So this PR is also part of this firmware.\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- will handle packet forwarding better in case of `denyf *`\r\n\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.14.0 as of 17-Mar-2026\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.15...v1.14.0-evo_0.1.16",
      "notesHtml": "<p>This build is based on official MeshCore 1.14.0 <code>dev</code> branch (as of 17-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></li>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n<li>Flood adverts are disabled (flood.advert.interval set to 0) by default</li>\n</ul>\n<p>PR1297, <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a>, has been merged upstream and is now part of the official dev branch. So this PR is also part of this firmware.</p>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>will handle packet forwarding better in case of <code>denyf *</code></li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.14.0 as of 17-Mar-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.15...v1.14.0-evo_0.1.16\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.15...v1.14.0-evo_0.1.16</a></p>\n"
    },
    {
      "version": "v1.14.0-evo_0.1.15",
      "name": "Meshcore-evo build 1.14.0_0.1.15 - 08-Mar-2026",
      "datetime": "2026-03-08T09:49:11Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.0-evo_0.1.15",
      "prerelease": false,
      "notes": "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:\r\n\r\n- PR1297: [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.14.0 as of 08-Mar-2026\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.14...v1.14.0-evo_0.1.15",
      "notesHtml": "<p>This build is based on official MeshCore 1.14.0 <code>dev</code> branch (as of 08-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><p>PR1297: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></p>\n</li>\n<li><p>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></p>\n</li>\n<li><p>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></p>\n</li>\n<li><p>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</p>\n</li>\n<li><p>Flood adverts are disabled (flood.advert.interval set to 0) by default</p>\n</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.14.0 as of 08-Mar-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.14...v1.14.0-evo_0.1.15\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.14.0-evo_0.1.14...v1.14.0-evo_0.1.15</a></p>\n"
    },
    {
      "version": "v1.14.0-evo_0.1.14",
      "name": "Meshcore-evo build v1.14.0_0.1.14 - 06-Mar-2026",
      "datetime": "2026-03-06T19:38:46Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.0-evo_0.1.14",
      "prerelease": false,
      "notes": "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](https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.0).\r\n\r\nSo here it goes:\r\n\r\nThis 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:\r\n\r\n- PR1297: [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `main` v1.14.0 as of 06-Mar-2026 \r\n\r\n\r\nChange log of [MeshCore v1.14.0](https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.0):\r\n\r\n- multibyte path hash support\r\n- new ‘auto add max hops’ preference\r\n- new radio AGC reset implementation\r\n- HeltecV4 power fixes\r\n- RAK3401 power optimisations\r\n- Heltec Tracker V2 power fixes\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.13...v1.14.0-evo_0.1.14",
      "notesHtml": "<p>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 <a href=\"https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.0\" target=\"_blank\" rel=\"noopener noreferrer\">official MeshCore v1.14.0 release</a>.</p>\n<p>So here it goes:</p>\n<p>This build is based on official MeshCore 1.14.0 <code>main</code> branch (as of 06-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><p>PR1297: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></p>\n</li>\n<li><p>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></p>\n</li>\n<li><p>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></p>\n</li>\n<li><p>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</p>\n</li>\n<li><p>Flood adverts are disabled (flood.advert.interval set to 0) by default</p>\n</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>main</code> v1.14.0 as of 06-Mar-2026</li>\n</ul>\n<p>Change log of <a href=\"https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.0\" target=\"_blank\" rel=\"noopener noreferrer\">MeshCore v1.14.0</a>:</p>\n<ul>\n<li>multibyte path hash support</li>\n<li>new ‘auto add max hops’ preference</li>\n<li>new radio AGC reset implementation</li>\n<li>HeltecV4 power fixes</li>\n<li>RAK3401 power optimisations</li>\n<li>Heltec Tracker V2 power fixes</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.13...v1.14.0-evo_0.1.14\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.13...v1.14.0-evo_0.1.14</a></p>\n"
    },
    {
      "version": "v1.13.0-evo_0.1.13",
      "name": "Meshcore-evo build 1.13.0_0.1.13- 05-Mar-2026",
      "datetime": "2026-03-05T22:50:53Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.13.0-evo_0.1.13",
      "prerelease": false,
      "notes": "⚠️ 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. ⚠️ \r\n\r\nOK, 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.)\r\n\r\nSo here it goes.\r\n\r\nThis build is based on official MeshCore 1.30 `dev` branch as of 05-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:\r\n\r\n- PR1297: [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.13.0 as of 05-Mar-2026 \r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.12...v1.13.0-evo_0.1.13",
      "notesHtml": "<p>⚠️ 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. ⚠️ </p>\n<p>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.)</p>\n<p>So here it goes.</p>\n<p>This build is based on official MeshCore 1.30 <code>dev</code> branch as of 05-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><p>PR1297: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></p>\n</li>\n<li><p>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></p>\n</li>\n<li><p>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></p>\n</li>\n<li><p>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</p>\n</li>\n<li><p>Flood adverts are disabled (flood.advert.interval set to 0) by default</p>\n</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.13.0 as of 05-Mar-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.12...v1.13.0-evo_0.1.13\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.12...v1.13.0-evo_0.1.13</a></p>\n"
    },
    {
      "version": "v1.13.0-evo_0.1.12",
      "name": "Meshcore-evo build 1.13.0_0.1.12- 04-Mar-2026",
      "datetime": "2026-03-04T22:48:24Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.13.0-evo_0.1.12",
      "prerelease": false,
      "notes": "⚠️ 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. ⚠️ \r\n\r\nOK, 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.)\r\n\r\nSo here it goes.\r\n\r\nThis build is based on official MeshCore 1.30 `dev` branch as of 04-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:\r\n\r\n- PR1297: [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.13.0 as of 04-Mar-2026 \r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.10...v1.13.0-evo_0.1.12",
      "notesHtml": "<p>⚠️ 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. ⚠️ </p>\n<p>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.)</p>\n<p>So here it goes.</p>\n<p>This build is based on official MeshCore 1.30 <code>dev</code> branch as of 04-Mar-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><p>PR1297: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></p>\n</li>\n<li><p>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></p>\n</li>\n<li><p>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></p>\n</li>\n<li><p>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</p>\n</li>\n<li><p>Flood adverts are disabled (flood.advert.interval set to 0) by default</p>\n</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.13.0 as of 04-Mar-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.10...v1.13.0-evo_0.1.12\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.10...v1.13.0-evo_0.1.12</a></p>\n"
    },
    {
      "version": "v1.13.0-evo_0.1.10",
      "name": "Meshcore-evo build 1.13.0_0.1.10- 28-Feb-2026",
      "datetime": "2026-02-28T15:46:42Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.13.0-evo_0.1.10",
      "prerelease": false,
      "notes": "This build is based on official MeshCore 1.30 `dev` branch as of 28-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:\r\n\r\n- PR1297: [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- PR1338: [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- PR1743: [fix agc reset on SX126x, SX1276 & LR11x0 chips](https://github.com/meshcore-dev/MeshCore/pull/1743)\r\n- PR1810: [Allow direct message paths when denyf * is set](https://github.com/meshcore-dev/MeshCore/pull/1810)\r\n\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- Flood adverts are disabled (flood.advert.interval set to 0) by default\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is disabled for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.13.0 as of 28-Feb-2026 \r\n\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.9...v1.13.0-evo_0.1.10",
      "notesHtml": "<p>This build is based on official MeshCore 1.30 <code>dev</code> branch as of 28-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><p>PR1297: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></p>\n</li>\n<li><p>PR1338: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></p>\n</li>\n<li><p>PR1743: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1743\" target=\"_blank\" rel=\"noopener noreferrer\">fix agc reset on SX126x, SX1276 &amp; LR11x0 chips</a></p>\n</li>\n<li><p>PR1810: <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1810\" target=\"_blank\" rel=\"noopener noreferrer\">Allow direct message paths when denyf * is set</a></p>\n</li>\n<li><p>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</p>\n</li>\n<li><p>Flood adverts are disabled (flood.advert.interval set to 0) by default</p>\n</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is disabled for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.13.0 as of 28-Feb-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.9...v1.13.0-evo_0.1.10\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.9...v1.13.0-evo_0.1.10</a></p>\n"
    },
    {
      "version": "v1.13.0-evo_0.1.9",
      "name": "Meshcore-evo build 1.13.0_0.1.9- 21-Feb-2026",
      "datetime": "2026-02-21T19:13:02Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.13.0-evo_0.1.9",
      "prerelease": false,
      "notes": "This build is based on official MeshCore 1.30 `dev` branch as of 21-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is 48h for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.13.0 as of 21-Feb-2026 \r\n\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.13.0_0.1.8...v1.13.0-evo_0.1.9",
      "notesHtml": "<p>This build is based on official MeshCore 1.30 <code>dev</code> branch as of 21-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is 48h for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.13.0 as of 21-Feb-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.13.0_0.1.8...v1.13.0-evo_0.1.9\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.13.0_0.1.8...v1.13.0-evo_0.1.9</a></p>\n"
    },
    {
      "version": "v1.13.0_0.1.8",
      "name": "Meshcore-evo build 1.13.0_0.1.8 - 15-Feb-2026",
      "datetime": "2026-02-16T12:06:55Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.13.0_0.1.8",
      "prerelease": false,
      "notes": "This build is based on official MeshCore 1.30 release, `main` branch as of 15-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is 48h for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `main` v1.13.0 as of 15-Feb-2026 \r\n\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.12.0_0.1.7...v1.13.0_0.1.8",
      "notesHtml": "<p>This build is based on official MeshCore 1.30 release, <code>main</code> branch as of 15-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li>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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is 48h for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>main</code> v1.13.0 as of 15-Feb-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.12.0_0.1.7...v1.13.0_0.1.8\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.12.0_0.1.7...v1.13.0_0.1.8</a></p>\n"
    },
    {
      "version": "v1.12.0_0.1.7",
      "name": "Meshcore-evo build 1.12.0_0.1.7 - 10-Feb-2026",
      "datetime": "2026-02-10T20:34:18Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.12.0_0.1.7",
      "prerelease": false,
      "notes": "This build is based on official MeshCore `dev` branch as of 10-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- RAK 4631 variant: Lowered lockout voltage from 3.3V to 3.1V, 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](https://github.com/meshcore-dev/MeshCore/issues/1572).)\r\n- [Improve Heltec v4 RX reception with undocumented register patch](https://github.com/meshcore-dev/MeshCore/pull/1398)\r\nThis is now part of dev, the PR has been merged upstream and is also part of this build.\r\n\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is 48h for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.12.0 as of 10-Feb-2026 \r\n\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.12.0_0.1.6...v1.12.0_0.1.7",
      "notesHtml": "<p>This build is based on official MeshCore <code>dev</code> branch as of 10-Feb-2026 and additionally includes the following unmerged upstream PRs/changes:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li>RAK 4631 variant: Lowered lockout voltage from 3.3V to 3.1V, 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 <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1398\" target=\"_blank\" rel=\"noopener noreferrer\">Improve Heltec v4 RX reception with undocumented register patch</a>\nThis is now part of dev, the PR has been merged upstream and is also part of this build.</li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is 48h for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.12.0 as of 10-Feb-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.12.0_0.1.6...v1.12.0_0.1.7\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.12.0_0.1.6...v1.12.0_0.1.7</a></p>\n"
    },
    {
      "version": "v1.12.0_0.1.6",
      "name": "Meshcore-evo build 1.12.0_0.1.6 - 01-Feb-2026",
      "datetime": "2026-02-01T22:03:46Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.12.0_0.1.6",
      "prerelease": false,
      "notes": "This build is based on official MeshCore `dev` branch as of 01-Feb-2026 and includes the following unmerged upstream PRs:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- [Improve Heltec v4 RX reception with undocumented register patch](https://github.com/meshcore-dev/MeshCore/pull/1398)\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n- Improve Heltec V4 RX performance\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is 48h for new installations\r\n- Set `advert.interval` to 240 (every 4h) \r\n\r\n\r\nChangelog:\r\n- Based on `dev` v1.12.0 as of 01-Feb-2026 \r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.12.0-evo...v1.12.0_0.1.6\r\n\r\nFor RAK4630 boards operated with LiFePo batteries I added a fw build `RAK_4631_repeater-v1.12.0-evo_0.1.6_lockoutfix-f34a1f8` with `PWRMGT_VOLTAGE_BOOTLOCK` set to 3100 (3.1V).  (See discussion [here](https://github.com/meshcore-dev/MeshCore/issues/1572).)",
      "notesHtml": "<p>This build is based on official MeshCore <code>dev</code> branch as of 01-Feb-2026 and includes the following unmerged upstream PRs:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1398\" target=\"_blank\" rel=\"noopener noreferrer\">Improve Heltec v4 RX reception with undocumented register patch</a></li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n<li>Improve Heltec V4 RX performance</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is 48h for new installations</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h)</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>dev</code> v1.12.0 as of 01-Feb-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.12.0-evo...v1.12.0_0.1.6\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.12.0-evo...v1.12.0_0.1.6</a></p>\n<p>For RAK4630 boards operated with LiFePo batteries I added a fw build <code>RAK_4631_repeater-v1.12.0-evo_0.1.6_lockoutfix-f34a1f8</code> with <code>PWRMGT_VOLTAGE_BOOTLOCK</code> set to 3100 (3.1V).  (See discussion <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1572\" target=\"_blank\" rel=\"noopener noreferrer\">here</a>.)</p>\n"
    },
    {
      "version": "v1.12.0-evo",
      "name": "Meshcore-evo build 1.12.0-evo - 29-Jan-2026",
      "datetime": "2026-01-29T11:22:03Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.12.0-evo",
      "prerelease": false,
      "notes": "This build is based on the official 1.12 release (`main` branch) as of 29-Jan-2026 and includes the following unmerged upstream PRs:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n\r\nAs a result this firmware will be suited for large and/or high density meshes:\r\n- only send a zero hop advert on boot \r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nAdditionally the LORA settings are defaulting to EU/narrow for erase/flash installs.\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or to 168 (weekly flood adverts), default is 48h\r\n- Set `advert.interval` to 240 (every 4h) \r\n- check `flood.advert.base`- should be ~0.308 \r\n\r\n\r\nChangelog:\r\n- Based on `main` v1.12.0 as of 29-Jan-2026 \r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.5...v1.12.0-evo",
      "notesHtml": "<p>This build is based on the official 1.12 release (<code>main</code> branch) as of 29-Jan-2026 and includes the following unmerged upstream PRs:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n</ul>\n<p>As a result this firmware will be suited for large and/or high density meshes:</p>\n<ul>\n<li>only send a zero hop advert on boot </li>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Additionally the LORA settings are defaulting to EU/narrow for erase/flash installs.</p>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or to 168 (weekly flood adverts), default is 48h</li>\n<li>Set <code>advert.interval</code> to 240 (every 4h) </li>\n<li>check <code>flood.advert.base</code>- should be ~0.308</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on <code>main</code> v1.12.0 as of 29-Jan-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.5...v1.12.0-evo\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.5...v1.12.0-evo</a></p>\n"
    },
    {
      "version": "v1.11.0_0.1.5",
      "name": "Meshcore-evo build 1.11.0_0.1.5 - 28-Jan-2026",
      "datetime": "2026-01-28T17:58:09Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.11.0_0.1.5",
      "prerelease": false,
      "notes": "This build is based on the `dev` branch as of 28-Jan-2026 and includes the following unmerged upstream PRs:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n\r\nIt does NOT include\r\n- [Default to zero hop advert when booting + STEALTH_MODE flag](https://github.com/meshcore-dev/MeshCore/pull/1199)\r\nanymore, BUT the same functionality has been merged to dev officially as part of PR1488\r\n\r\nAs a result this firmware will\r\n- only send a zero hop advert on boot \r\n- will be set to 48h flood advert interval (this is the minimum allowed in this fw)\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nAdditionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.\r\n\r\n- Includes updated PR [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338):\r\n-- Use `set flood.advert.base x: float in [0,1], defaults to 0.308`, 0 will disable flood advert forwarding, 1 forwards all.\r\n\r\n- You can now use way longer advert interval limits up to 168h.\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or higher than 168 (weekly flood adverts), default is 48h\r\n- Set `advert.interval` to 300 (every 5h) \r\n- check `flood.advert.base`- should be ~0.308\r\n\r\n\r\nChangelog:\r\n- Based on dev as of 28-Jan-2026 \r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.4...v1.11.0_0.1.5",
      "notesHtml": "<p>This build is based on the <code>dev</code> branch as of 28-Jan-2026 and includes the following unmerged upstream PRs:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n</ul>\n<p>It does NOT include</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1199\" target=\"_blank\" rel=\"noopener noreferrer\">Default to zero hop advert when booting + STEALTH_MODE flag</a>\nanymore, BUT the same functionality has been merged to dev officially as part of PR1488</li>\n</ul>\n<p>As a result this firmware will</p>\n<ul>\n<li>only send a zero hop advert on boot </li>\n<li>will be set to 48h flood advert interval (this is the minimum allowed in this fw)</li>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Additionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.</p>\n<ul>\n<li><p>Includes updated PR <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a>:\n-- Use <code>set flood.advert.base x: float in [0,1], defaults to 0.308</code>, 0 will disable flood advert forwarding, 1 forwards all.</p>\n</li>\n<li><p>You can now use way longer advert interval limits up to 168h.</p>\n</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or higher than 168 (weekly flood adverts), default is 48h</li>\n<li>Set <code>advert.interval</code> to 300 (every 5h) </li>\n<li>check <code>flood.advert.base</code>- should be ~0.308</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on dev as of 28-Jan-2026</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.4...v1.11.0_0.1.5\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.4...v1.11.0_0.1.5</a></p>\n"
    },
    {
      "version": "v1.11.0_0.1.4",
      "name": "Meshcore-evo build 1.11.0_0.1.4 - 26-Jan-2026",
      "datetime": "2026-01-26T12:34:12Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.11.0_0.1.4",
      "prerelease": false,
      "notes": "This build is based on the `dev` branch as of 26-Jan-2026 and includes the following unmerged upstream PRs:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n\r\nIt does NOT include\r\n- [Default to zero hop advert when booting + STEALTH_MODE flag](https://github.com/meshcore-dev/MeshCore/pull/1199)\r\nanymore, BUT the same functionality has been merged to dev officially as part of PR1488\r\n\r\nAs a result this firmware will\r\n- only send a zero hop advert on boot \r\n- will be set to 48h flood advert interval (this is the minimum allowed in this fw)\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nAdditionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.\r\n\r\n- Includes updated PR [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338):\r\n-- Use `set flood.advert.base x: float in [0,1], defaults to 0.308`, 0 will disable flood advert forwarding, 1 forwards all.\r\n\r\n- You can now use way longer advert interval limits up to 168h.\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or higher than 168 (weekly flood adverts), default is 48h\r\n- Set `advert.interval` to 300 (every 5h) \r\n- check `flood.advert.base`- should be ~0.308\r\n\r\n\r\nChangelog:\r\n- Based on dev as of 26-Jan-2026 \r\n- The former releases did not include PR [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297) due to a bug in a build script. Now it's properly included\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.3...v1.11.0_0.1.4",
      "notesHtml": "<p>This build is based on the <code>dev</code> branch as of 26-Jan-2026 and includes the following unmerged upstream PRs:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n</ul>\n<p>It does NOT include</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1199\" target=\"_blank\" rel=\"noopener noreferrer\">Default to zero hop advert when booting + STEALTH_MODE flag</a>\nanymore, BUT the same functionality has been merged to dev officially as part of PR1488</li>\n</ul>\n<p>As a result this firmware will</p>\n<ul>\n<li>only send a zero hop advert on boot </li>\n<li>will be set to 48h flood advert interval (this is the minimum allowed in this fw)</li>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Additionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.</p>\n<ul>\n<li><p>Includes updated PR <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a>:\n-- Use <code>set flood.advert.base x: float in [0,1], defaults to 0.308</code>, 0 will disable flood advert forwarding, 1 forwards all.</p>\n</li>\n<li><p>You can now use way longer advert interval limits up to 168h.</p>\n</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or higher than 168 (weekly flood adverts), default is 48h</li>\n<li>Set <code>advert.interval</code> to 300 (every 5h) </li>\n<li>check <code>flood.advert.base</code>- should be ~0.308</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on dev as of 26-Jan-2026 </li>\n<li>The former releases did not include PR <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a> due to a bug in a build script. Now it's properly included</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.3...v1.11.0_0.1.4\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v1.11.0_0.1.3...v1.11.0_0.1.4</a></p>\n"
    },
    {
      "version": "v1.11.0_0.1.3",
      "name": "Meshcore-evo build v1.11.0_0.1.3 - 17-Jan-2026",
      "datetime": "2026-01-17T14:59:19Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.11.0_0.1.3",
      "prerelease": false,
      "notes": "This build is based on the `dev` branch as of 17-Jan-2026 and includes the following unmerged upstream PRs:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- [Default to zero hop advert when booting + STEALTH_MODE flag](https://github.com/meshcore-dev/MeshCore/pull/1199)\r\n\r\nAs a result this firmware will\r\n- only send a zero hop advert on boot \r\n- will be set to 48h flood advert interval (this is the minimum allowed in this fw)\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nAdditionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.\r\n\r\n- Includes updated PR [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338):\r\n-- Use `set flood.advert.base x: float in [0,1], defaults to 0.308`, 0 will disable flood advert forwarding, 1 forwards all.\r\n\r\n- You can now use way longer advert interval limits than 48h (e.g. weekly, monthly, ...)\r\n\r\nRecommended use:\r\n- Set `flood.advert.interval` to zero or higher than 168 (weekly flood adverts), default is 48h\r\n- Set `advert.interval` to 300 (every 5h) \r\n- check `flood.advert.base`- should be ~0.308\r\n\r\n\r\nChangelog:\r\n- Based on dev as of 17-Jan-2026 \r\n- Changed default advert.interval limits \r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v0.1.2...v1.11.0_0.1.3",
      "notesHtml": "<p>This build is based on the <code>dev</code> branch as of 17-Jan-2026 and includes the following unmerged upstream PRs:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1199\" target=\"_blank\" rel=\"noopener noreferrer\">Default to zero hop advert when booting + STEALTH_MODE flag</a></li>\n</ul>\n<p>As a result this firmware will</p>\n<ul>\n<li>only send a zero hop advert on boot </li>\n<li>will be set to 48h flood advert interval (this is the minimum allowed in this fw)</li>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Additionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.</p>\n<ul>\n<li><p>Includes updated PR <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a>:\n-- Use <code>set flood.advert.base x: float in [0,1], defaults to 0.308</code>, 0 will disable flood advert forwarding, 1 forwards all.</p>\n</li>\n<li><p>You can now use way longer advert interval limits than 48h (e.g. weekly, monthly, ...)</p>\n</li>\n</ul>\n<p>Recommended use:</p>\n<ul>\n<li>Set <code>flood.advert.interval</code> to zero or higher than 168 (weekly flood adverts), default is 48h</li>\n<li>Set <code>advert.interval</code> to 300 (every 5h) </li>\n<li>check <code>flood.advert.base</code>- should be ~0.308</li>\n</ul>\n<p>Changelog:</p>\n<ul>\n<li>Based on dev as of 17-Jan-2026 </li>\n<li>Changed default advert.interval limits</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v0.1.2...v1.11.0_0.1.3\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v0.1.2...v1.11.0_0.1.3</a></p>\n"
    },
    {
      "version": "v0.1.2",
      "name": "Meshcore-evo build 1.11.0_0.1.2 - 14-Jan-2026",
      "datetime": "2026-01-14T11:18:05Z",
      "url": "https://github.com/mattzzw/MeshCore-Evo/releases/tag/v0.1.2",
      "prerelease": false,
      "notes": "This build is based on the `dev` branch as of 14-Jan-2026 and includes the following unmerged upstream PRs:\r\n\r\n- [Implement token bucket duty cycle enforcement](https://github.com/meshcore-dev/MeshCore/pull/1297)\r\n- [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338)\r\n- [Default to zero hop advert when booting + STEALTH_MODE flag](https://github.com/meshcore-dev/MeshCore/pull/1199)\r\n\r\nAs a result this firmware will\r\n- only send a zero hop advert on boot \r\n- will be set to 48h flood advert interval (this is the minimum allowed in this fw)\r\n- will reduce flood advert forwarding based on [this proposal](https://github.com/meshcore-dev/MeshCore/issues/1223)\r\n- Implement [rolling window duty cycle management](https://github.com/meshcore-dev/MeshCore/issues/817), allowing for more robust tx operations of central/busy repeaters\r\n\r\nAdditionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.\r\n\r\nChangelog:\r\n- Based on dev 14-Jan-2026 \r\n- Includes updated PR [Limit flood advert packet forwarding](https://github.com/meshcore-dev/MeshCore/pull/1338):\r\n-- Use `set flood.advert.base x: float in [0,1], defaults to 0.308`, 0 will disable flood advert forwarding, 1 forwards all.\r\n\r\n**Full Changelog**: https://github.com/mattzzw/MeshCore/compare/v0.1.1...v0.1.2",
      "notesHtml": "<p>This build is based on the <code>dev</code> branch as of 14-Jan-2026 and includes the following unmerged upstream PRs:</p>\n<ul>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1297\" target=\"_blank\" rel=\"noopener noreferrer\">Implement token bucket duty cycle enforcement</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a></li>\n<li><a href=\"https://github.com/meshcore-dev/MeshCore/pull/1199\" target=\"_blank\" rel=\"noopener noreferrer\">Default to zero hop advert when booting + STEALTH_MODE flag</a></li>\n</ul>\n<p>As a result this firmware will</p>\n<ul>\n<li>only send a zero hop advert on boot </li>\n<li>will be set to 48h flood advert interval (this is the minimum allowed in this fw)</li>\n<li>will reduce flood advert forwarding based on <a href=\"https://github.com/meshcore-dev/MeshCore/issues/1223\" target=\"_blank\" rel=\"noopener noreferrer\">this proposal</a></li>\n<li>Implement <a href=\"https://github.com/meshcore-dev/MeshCore/issues/817\" target=\"_blank\" rel=\"noopener noreferrer\">rolling window duty cycle management</a>, allowing for more robust tx operations of central/busy repeaters</li>\n</ul>\n<p>Additionally the LORA settings are defaulting to EU/narrow and the min/max/defaults for adverts have been adjusted, see platformio.ini.</p>\n<p>Changelog:</p>\n<ul>\n<li>Based on dev 14-Jan-2026 </li>\n<li>Includes updated PR <a href=\"https://github.com/meshcore-dev/MeshCore/pull/1338\" target=\"_blank\" rel=\"noopener noreferrer\">Limit flood advert packet forwarding</a>:\n-- Use <code>set flood.advert.base x: float in [0,1], defaults to 0.308</code>, 0 will disable flood advert forwarding, 1 forwards all.</li>\n</ul>\n<p><strong>Full Changelog</strong>: <a href=\"https://github.com/mattzzw/MeshCore/compare/v0.1.1...v0.1.2\" target=\"_blank\" rel=\"noopener noreferrer\">https://github.com/mattzzw/MeshCore/compare/v0.1.1...v0.1.2</a></p>\n"
    }
  ],
  "changelogSource": "github",
  "changelogUpdatedAt": "2026-06-21T09:55:33.290Z"
}