Releases: meshtastic/firmware
0.6.1 alpha
I had hoped to let this release bake at my house for a few days but... I botched the heltec builds per https://meshtastic.discourse.group/t/no-display-on-firmware-ttgo-lora32-v2-us-0-6-0-or-firmware-heltec-us-0-6-0/167/5
So this has all the recent changes. Seems to be working quite nicely on my nodes though. Notably: it does not have my fix for sometimes dropping messages, that will be released by monday.
Changes since previous release:
0.6.0...0.6.1
0.6.0 alpha
A lot of changes since the 0.4.3 release. Not urgent to upgrade unless you want to use the new python API.
0.4.3 alpha
oops, recent builds were all using US frequencies. If you are outside the US, you should upgrade ASAP (and really really - soonish I'll turn on software update from the android app)
Thanks to @spattinson and @eugene for the report. I'm sorry about my mistake.
Changes since last release:
0.4.2
0.4.1 alpha
hmm - one of my four test devices stops sending packets with this load. I think ya'll should wait for the next release. I'm deleting the binary from this release.
This release has lots of good changes/progress. Real mesh networking is back in. However, two warnings:
- you'll need to update all your nodes for this change (it is not backwards compatible)
- it might have more bugs than usual
Highlights:
- Reimplement full mesh networking (just flooding for now though - which is all we currently need). Now truly a mesh once again
- Experiment with using disaster.radio's mesh implementation - which for a variety of technical reasons turned out to be not a good fit at this time. We might share a lib in the future.
- remove most of the unused radiohead code
- comment out tbeam0.7 builds until someone with that old tbeam can test and debug
- substantial cleanup of the networking code
- add lora32 v2 fixes contributed by @eriktheV-king and @BeardyWalrus
- increase screen timeout - thanks to @android606
- add collision avoidance for transmit - substantially decreases the odds of dropped packets
0.2.3 alpha
Some good improvements! Upgrading is recommended.
Highlights:
- @android606 contributed OS-X build instructions
- A bug in our LORA receive code could cause corrupted packets
- Some NEO 6M gps give bogus time info until their internal battery is charged
- radio config information wasn't being properly passed to the phone
- We weren't turning on bluetooth while the device was in the DARK power management state
- Fix bug #73 reported by @lburrowes
This release zip is getting kinda big. At some point we'll use fuse bits for the various regions/frequency bands. And we'll stop needing a different build for each region. Sometime in the next couple of weeks I'll probably turn firmware update over bluetooth back on in the android app.
Full list of changes:
0.2.0...0.2.3
0.2.0 alpha
Some good improvements! Upgrading is recommended.
Also included are untested builds (because I don't have the hardware) for: the original 0.7 version of the TBEAM and both the 1.0 and 2.0 versions of the TTGO Lora board. I'll post on the forum with more details and ask for someone to try it.
Highlights:
- @girtsf added show GPS lock status and battery voltage on the debug screen
- @spattinson fixed interrupt handling for the AXP192 power management chip on the TBEAM boards
- Changed to use the platformio build system for our various different board types (rather than the old hacky way we used to do it). Thanks to @sensorslot for the pointer to https://github.com/arendst/Tasmota and thanks to Tasmota for the settings I copied from you ;-)
- Plausible settings for TBEAM07, TTGO LORA V1 and LORA V2 boards based on spreadsheet from @SensorsIot and reading various git repos
This release zip is getting kinda big. At some point we'll use fuse bits for the various regions/frequency bands. And we'll stop needing a different build for each region. Sometime in the next couple of weeks I'll probably turn firmware update over bluetooth back on in the android app.
Full list of changes:
0.1.10...0.2.0
0.1.10 alpha
Minor improvements - update if you want.
Highlights:
- When you press a button to wake the screen, the device will now (behind the scenes) ask any remote node you are looking at to exchange updated position data. This should make navigation to other users work much better once you are close.
- Devices that don't have a GPS will now automatically learn their network time from other nodes on the mesh that do have GPS (either built in or because the attached phone is helping it)
- More debugging support to track down a couple of issues that show remotely but not here.
Full list of changes:
0.1.9...0.1.10
0.1.9 alpha
Everyone will want this change, it fixes some serious bugs.
Highlights:
- The failure to connect from the phone to the device should be fixed now
- An 'installer script' now programs devices completely from scratch, so HELTEC clone devices should now work. Would one of ya'll mind testing the new instructions I added in the README? If someone wants to make a Windows batchfile version of device_install.sh, that owuld be great!
- We now keep full elf files in the release zip, which makes it easier to debug remote crash reports (though this does make the zip file quite a bit larger)
- Device bugs are now reported up to the phone (and then back to the devs via analytics starting in the next Android release). This should help a lot in tracking down remaining problems that happen in the field.
- @girtsf flipped the TBEAM screen so it has the correct orientation.
Full list of changes:
0.1.8...0.1.9
0.1.8 alpha
Everyone will want this change, a lot of important fixes
Great fixes from @girtsf (related to bluetooth android problems and general cleanup):
- Work towards separating out how Screen interacts with other stuff.
Screen
should now be thread-safe. All commands to it are put in a
queue and handled indoTask
from theloop()
task.- Break dependency from
BluetoothUtil
toScreen
by changing the
pairing request into a callback. - All accesses to screen now happen through the class.
- Fix
drawRows
so that the text scrolls along with frame animations.
Changes from geeksville:
- Oops, my recent GPS 'improvements' broke the compass display update, fixed.
- We now report dynamic 'has working gps' data to the phone (so if your device doesn't have a GPS the phone automatically helps out and provides position data for this node)
- devices that only have a single data wire for their GPS should now work.
- Whenever you are watching a node on the OLED display, behind the scenes the devices will be exchanging your position more quickly than normal (just for those two nodes), to ensure a nice user experience if you are trying to get to someone.
Full list of changes:
0.1.7...0.1.8