LoRa Mesh blog

Meshcore firmware version 1.16.0 has been released

Title says it all.  It will be recalled that Meshcore firmware version 1.15.0 had been released on April 19, 2026.  Now on June 6, 2026, version 1.16.0 has been released, as you can read about in this Meshcore blog page

Effect on the user of a companion device.  My best guess is that many a day-to-day user of Meshcore, meaning a user that interacts directly only with some single companion device, will not feel a need to urgently update the firmware on his or her personal Meshcore companion device.  Having said this, the 1.16.0 change log lists many “bug fixes” with respect to this or that make and model of companion device.  As just one example the change log says:

  • RAK Wismesh Tag fixes #2664

and so for example the day-to-day user of a RAK Wismesh Tag might want to look at pull 2664 to see what got fixed, and then might want to consider doing a firmware update on one’s tag so that whatever needed fixing about the tag gets fixed on that person’s tag.

Effects on the administrator of a repeater.  I’d guess that if one is the administrator of a repeater (or, as in my case, the administrator of half a dozen repeaters, a number that will soon double), one will want to make at least general plans to migrate away from the previous firmware.  In the change log I see over a dozen listed pull requests that are clearly designed specifically to help repeaters work better and faster and smarter.  In my case I’ll allow a bit of time to pass to see whether a version 1.16.1 comes along soon, and then if 1.16.0 remains unchanged for a while, I imagine I will do a firmware update on one or two of my repeaters.  Then if things look stable I would update the rest of my repeaters.

What are other factors that a person might want to consider about doing updates away from previous firmware?  Please post a comment below.


Discover more from LoRa Mesh blog

Subscribe to get the latest posts sent to your email.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *