As we prepare for our upcoming goTenna Mesh 5.0 app (+ firmware & protocol) release, the time has come for us to prepare for external beta testing.
We’re lucky to have lots of Mesh aficionados here on Mesh Community — many of you have beta tested for us in the past and found critical bugs and provided really constructive feedback for us. We’re looking to recruit 10-12 beta testers who can help us refine 5.0 prior to public release!
Beta testing for 5.0 will include:
Testing in various environments.
Testing more mesh hops! (Excitingggg.)
Providing in-depth and robust feedback on your test experiences.
Providing feedback on our new app UI.
Providing photos of your test setup/endeavors when possible.
It would be great if you had:
At least 4-6 devices & ideally at least 3-4 fellow Meshers (i.e. people) to test with.
An ability to test across both iOS and Android devices (though just one OS is fine).
Outdoor/travel plans for late April/May OR easy everyday access to various environments (outdoors, urban, suburban, etc.).
If you’re interested in beta testing Mesh 5.0 please fill out the survey here. We’ll begin review and selecting testers immediately so submit your beta testing application ASAP!
This is a BIG one, guys! Getting early access to the major revamp and increased hops is kinda killer. Plus: you can help us make something great even better.
Sent in my application for the beta test. Hope I get picked!
Any chance this update will include the ability for the gotenna mesh device to auto restart after the battery is temporarily depleted then recharged the following day via solar?
I have a couple questions. For beta testing, do all Mesh devices (relays) need a firmware update to perform testing or just the endpoint (paired) devices? Once the beta test is complete, will all devices be able to go back to mainstream code?
I’m pretty sure all devices will need the update, because the expansion of hops available would require all nodes to be capable of handling the higher hop count .
It may be that legacy firmware can coexist and the new is backwards compatible with the old, but without the update units lacking it would not be able to utilize the mesh network improvements in the firmware. The stationary node improvements must incorporate the new in order to fully implement the stationary node monitoring and control scheme capabilities it is suggested the new firmware makes possible.
All devices would need the beta update. I’ll find out more about returning to firmware 0.13.48 and let you know. My instinct is that the devices would remain on new firmware.