Skip to content

Releases: meshtastic/firmware

Meshtastic Firmware 2.5.2.771cb52 Alpha

24 Sep 17:12
Compare
Choose a tag to compare
Pre-release

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.5.1.c13b44b...v2.5.2.771cb52

Meshtastic Firmware 2.5.1.c13b44b Alpha

22 Sep 01:48
Compare
Choose a tag to compare
Pre-release

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.5.0.9ac0e26...v2.5.1.c13b44b

Meshtastic Firmware 2.5.0.9ac0e26 Alpha

11 Sep 15:26
9ac0e26
Compare
Choose a tag to compare
Pre-release

Important

This release adds Public Key encryption to direct messages and enhanced session key based security to remote admin messages. It's recommended to back up your private keys.

Remote administration of 2.5 nodes will require client updates to all of the platforms.

Warning

There is a known-issue with LR111X based radios (Seeed Tracker / T1000-E) in communicating with older SX1276 based devices. The issue pre-dates this release.

Enhancements

Bug fixes and Maintenace

Read more

Meshtastic Firmware 2.4.3.91d6612 Alpha (Hotfix)

19 Aug 14:11
Compare
Choose a tag to compare

Tip

This version contains a hotfix for the original 2.4.3 release regression in setting node time from the network.

Enhancements

  • Update architecture.h add Minewsemi ME25LS01 LR1110 breakout ME25LE01_V1.0 and fix buzzer by @markbirss in #4472
  • Radio Master Joystick by @todd-herbert in #4476
  • Move NeighborInfo interval default to 6 hours (double NodeInfo) by @thebentern in #4483

Bug fixes

New Contributors

Full Changelog: v2.4.3.efc27f2...v2.4.3.91d6612

Meshtastic Firmware 2.4.3.efc27f2 Alpha (Revoked)

15 Aug 21:36
efc27f2
Compare
Choose a tag to compare

Important

This version was revoked due to a regression in setting node time from the network. Please install the follow-up hotfix release

Enhancements

Bug fixes and maintenance

New Contributors

Full Changelog: v2.4.2.5b45303...v2.4.3.efc27f2

Meshtastic Firmware 2.4.2.5b45303 Beta

09 Aug 11:31
Compare
Choose a tag to compare

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.4.1.394e0e1...v2.4.2.5b45303

Meshtastic Firmware 2.4.1.394e0e1 Beta

28 Jul 15:19
Compare
Choose a tag to compare

Important

This version removes the status (/stat) MQTT topic support from the firmware. Stay tuned for some exciting features ahead for MQTT.

Enhancements

Bug fixes

New Contributors

Full Changelog: v2.4.0.46d7b82...v2.4.1.394e0e1

Meshtastic Firmware 2.4.0.46d7b82 Beta

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

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