I need to spend the next two days dealing with some miscellaneous broken house things, so I’m taking a very brief break from this fun project. I thought though, this would be a good time to give an update on usage and next steps. I’ll make a separate thread about 1.5 features.
But first I have to say ya’ll are doing a great job of helping each other. Huge thanks in no particular order:
- The thirteen of you who have donated translations into your native language
- Everyone who has sent in code fixes, improvements and bug reports. Especially those who have become pretty active co-developers @dafeman, @lgx and @Professr.
The remaining fixes for 1.0 are looking like they going pretty well, if you’d like to help out - see any of the items in the left two columns of our project tracker.
My personal work queue for the next 1-2ish weeks (just because I know some of you are waiting on bug fixes) is:
- some channel names don’t work - check for illegal symbols per forum report
- auto invalidate old BLE handles (bug in esp32-arduino)
- disable software update button after update finishes
- check BLE handle stability across sleep - stress test sleep/wake - btu_init_core calls gatt_init - which assigns handles global
- @feh123 Sony Xperia Z1 C6903 running Android 5.1.1
- first message sent is still doubled for some people
- Android frontend should refetch the android messages from backend service on Resume
- let users set arbitrary params in android
- implement first cut of router mode: preferentially handle flooding, and change sleep and GPS behaviors
- NRF52 BLE support
Usage has really been progressing at a good clip. Some stats: about 2000 people a day read this forum. The android app has a little over 1000 installs. About half of those people are probably just ‘tire-kickers’ - i.e. the app reports they don’t have a radio connected. But about 600 people regularly have radios connected to their apps talking to a mesh with at least two nodes. Usage is about 1/3 Europe, 1/3 Asia and 1/3 US+Brazil. There are still bugs (alas, of course) but the app reliability is now much better than it was just three weeks ago. I’ll include a screencap at the end of this update…
I’ve heard through the grapevine that a Chinese manufacturer will soon be pre installing meshtastic on the devices they ship (and I just reactivated BLE based software update of ESP32 boards - it will be in this weeks android release). I’ve asked them about this and as soon as I have an update I’ll post.
I’ll post a device build in a couple of days, which include some really good fixes contributed by the other devs.