Closed NanaDada closed 3 years ago
So do you use the same provisioner from the second instance? if so the messages sent from the second instance would be ignore because of the sequence numbers keep incrementing. So you would have to create a new provisioner on the second device with a different address and this should help I believe.
On another note, I will get to your other issues as soon as I get some time because I am a bit busy with some other tasks at the moment.
Thanks for the hint! I've ended up adding a bunch of provisioners and a setting to chose one.
Describe the bug Unable to use a mesh network on multiple Android devices at the same time.
To Reproduce Steps to reproduce the behavior:
MeshManagerApi.exportMeshNetwork()
MeshManagerApi.importMeshNetwork()
Expected behavior Both devices should be able to use the mesh.
Platform details:
Imagine you want to operate a Mesh network with multiple Android devices. How do you copy the mesh across devices, so that all devices can use the mesh at the same time (i.e. in parallel)?
To share the mesh across devices, my app calls
MeshManagerApi.exportMeshNetwork()
andMeshManagerApi.importMeshNetwork()
. This is basically working: Reboot the mesh, start the app on any of the devices and you can connect and use the mesh. So far, so good.The problem arises as soon as a second instance of the app connects to the mesh: Then all commands sent from the second instance are simply ignored. Now the question is why, and how to fix it?
Do you have any ideas what could be wrong here? Is it sufficient to just call
MeshManagerApi.exportMeshNetwork()
andMeshManagerApi.importMeshNetwork()
, or is there anything else that needs to be done to allow multiple instances access the mesh at the same time?