Hi Sierra,
Thank you for your comments.
In answer to your questions:
GoTennaHub cannot send or receive messages from the goTenna App.
The SDK does not allow messages to be exchanged with applications using a different SDK Key or the standard app.
This is both for security and also to protect the available bandwidth - there is a good explanation for this in the goTennaSDKintro.pdf included with the SDK.
In its current form, goTennaHub only supports shouts, although there is no technical reason why it cannot be extend to support one to one messaging.
I have just pushed a new version of goTennaHub to GitHub, which cleans up a couple of issues with the code and also includes battery and temperature info as part of the “timestamp” functionality.
This would allow you to use goTennaHub in a different scenario, where you have a number of GoTenna’s in fixed locations acting as repeaters.
Adding ar300m’s running goTennaHub and a cron based timestamp would allow for the devices to keep track of battery levels etc and also communication drop outs as all of the devices would be talking to each other.
If you were to do this, I would suggest that you change line:
if len(messagesArray) > 100:
To a different value as this limits the number of messages recorded to 100.
Crucially, though the devices would still be acting as beacons as my understanding is that even though you are using a specific SDK token, the goTennas will still route other messages over the mesh.
To monitor your mesh you would simply have to connect a device with a browser to one of the routers.
Hope this helps.