Meshtastic 2.0 is live!

Development
1

It’s been a long journey, but we’re finally here. Thanks to all of those who contributed to success of this project and its community!

What have we upgraded since 1.2?

Monumental stuff!

  • Completely new LoRA band plan with faster messaging
  • Smarter and more reliable mesh routing
  • Unlimited nodes* (80 Connected at a time, oldest node will be removed when a new node joins the mesh)
  • New messaging additions: Waypoints, Reactions (tap-backs), and Telemetry
  • Improvements for Canned Messages module and CardKB messaging for stand alone communicator devices
  • Sensor, Screen, and Input device auto-detection
  • New devices supported (6 new targets!)
  • Added over the air Bluetooth updates for NRF devices (RAK-4631)
  • Ethernet support via RAK-13800
  • Compass improvements for larger screens and customizations

Nerd stuff!

  • New filesystem for ESP32 (LittleFS)
  • Upgraded Arduino framework for both NRF52 and ESP32
  • New Bluetooth stack for ESP32 (NimBLE)
  • Unified GPS stack now using NMEA
  • Support for more I2C sensors
  • Support for ATECCA608B Cryptographic Coprocessor
  • More Serial module I/O modes
  • JSON messages over MQTT
  • Device codebase refactored and optimized in many areas
  • Completely restructured protobufs and configuration
24 Likes
4

Very well done. Very well done indeed.

4 Likes
5

So many goodies in 2.0 and I love it. Updating as we speak!

6

Wow the client.meshtastic.org thing is so cool.

I had a lot of problems with python (my side).
Finally I updated firmware from the webpage. I needed a lot of reboot and retry but it worked.

2 Likes
7

Can you please tell me if version 2.0 is compatible with 1.3?

8

It is not. (1.3.48 might work) you need 2.0 for any other 1.3 version

9

Congratulations everyone! I think compression should be mentioned in the new features as well, it reduced airtime utilisation and improved reliability of message delivery.

All thanks to @mc-hamster and Arun for implementing it. :slight_smile:

5 Likes
11

Why drop compatibility?? What about already deployed infrastructure??

12

and how about 3.0 compatibility?