Skip to content

Releases: meshtastic/firmware

Meshtastic Firmware 2.4.0.46d7b82 Alpha

18 Jul 11:05
46d7b82
Compare
Choose a tag to compare
Pre-release

Important

Version 2.4 along with the last 2.3.X update brings some default traffic management practices to increase the resilience of larger meshes and allow more airtime for messaging. Some of the important changes which help accomplish this:

  • Deprecation of ROUTER_CLIENT role (2.3.15)
  • Move up all telemetry default intervals to every 30 minutes (instead of 15 minutes)
  • Don't send node info interrogation for unknown nodes when Ch. utilization is >25%
  • Scale configured / default intervals back based on online mesh size > 40 nodes
  • Requesting history from a Store & Forward Server over LoRa is not available on the channel with default key. As a new feature, when connecting to it with a client app, the history will be retrieved automatically.

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.15.deb7c27...v2.4.0.46d7b82

Meshtastic Firmware 2.3.15.deb7c27 Beta

08 Jul 15:59
deb7c27
Compare
Choose a tag to compare

Important

Regarding deprecation of ROUTER_CLIENT role:
This role was deprecated because it's frequent misuse in non-strategically placed roles, leading to increased rebroadcast packet collisions as well as premature hop consumption decreasing the effective range of a mesh. In some larger public meshes, it has been reported that almost half of the nodes were configured as ROUTER_CLIENT and ROUTER. Going forward, the mixed ROUTER_CLIENT role will be retired and simply behave as the CLIENT role.

Alternatively, users can decide to use the ROUTER role if their node does indeed fall into the strategically placed criteria, such as on top of a mountain, skyscraper, or any other location with a significant line of sight viewshed advantage. Examples of non-strategically placed nodes would be any mobile node, a car node, a home node on a mast, or really any node without significant elevation difference providing advantage to the mesh's reach. Nodes under those placement conditions should not be configured as ROUTER or REPEATER role.

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.14.64531fa...v2.3.15.deb7c27

Meshtastic Firmware 2.3.14.64531fa Alpha

25 Jun 01:25
64531fa
Compare
Choose a tag to compare

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.13.83f5ba0...v2.3.14.64531fa

Meshtastic Firmware 2.3.13.83f5ba0 Beta

18 Jun 11:09
83f5ba0
Compare
Choose a tag to compare

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.12.24458a7...v2.3.13.83f5ba0

Meshtastic Firmware 2.3.12.24458a7 Beta

09 Jun 23:46
24458a7
Compare
Choose a tag to compare

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.11.2740a56...v2.3.12.24458a7

Meshtastic Firmware 2.3.11.2740a56 Beta

01 Jun 20:15
2740a56
Compare
Choose a tag to compare

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.10.d19607b...v2.3.11.2740a56

Meshtastic Firmware 2.3.10.d19607b Beta

21 May 17:48
d19607b
Compare
Choose a tag to compare

Important

If you are seeing sporadic artifacts in environmental telemetry data, we suggest upgrading to 2.3.11 or above.

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.9.f06c56a...v2.3.10.d19607b

Meshtastic Firmware 2.3.9.f06c56a Alpha

10 May 13:15
Compare
Choose a tag to compare
Pre-release

Enhancements

Important

If you have a T-Beam Supreme (S3 Core) device, this release has known issues with using the CLI over USB connection, which is fixed in the next release.

Bug fixes

New Contributors

Full Changelog: v2.3.8.d490a33...v2.3.9.f06c56a

Meshtastic Firmware 2.3.8.d490a33 Alpha (Revoked)

04 May 13:19
d490a33
Compare
Choose a tag to compare

Revoked

Important

If you have a T-Beam Supreme (S3 Core) device, this release has an issue with bluetooth pairing failures.

Enhancements

  • Rebrand "send network ping" to more honest "try send position" with better output by @thebentern in #3737
  • Add Notification on device screen following feature toggle by @HarukiToreda in #3627
  • Allow setting hopLimit for MQTT json sendtext and sendposition by @mskvortsov in #3735
  • ADC battery readings quicker to reach steady state after boot by @todd-herbert in #3761
  • Remove phone nodenum warning and empty else clause by @thebentern in #3756
  • Optimization: stop relaying when reply is received by @GUVWAF in #3753
  • Publish fixed position updates and consider changes in only altitude as an updated point by @ndoo in #3758
  • Update TinyGPSPlus by @titan098 in #3727
  • Update Heltec HT-C62 variant based on HT-DEV-ESP board by @ndoo in #3731

Bug fixes

New Contributors

Full Changelog: v2.3.7.30fbcab...v2.3.8.d490a33

Meshtastic Firmware 2.3.7.30fbcab (Revoked)

26 Apr 00:04
30fbcab
Compare
Choose a tag to compare

Revoked due to BLE regression

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.3.6.7a3570a...v2.3.7.30fbcab