I've read through a decent amount of the BLE Mesh spec sheet(s), but I still have a few things that I'm not completely sure on. If someone could answer even just a few of these questions, that would be great:
-
It sounds like a smartphone (with Bluetooth 4.0/4.1) can implement the provisioner service to add devices with Bluetooth 5.0 Mesh to a mesh, but the smartphone itself can't be a part of the Mesh (i.e. it can't send or receive messages) . Is this correct?
-
If a phone without Bluetooth 5.0 can't be a part of a mesh, how can it control the mesh?
-
If a device leaves a mesh, the mesh blacklists the device and changes the security key in order to prevent "trash can attacks". Is there any way to prevent this? For example, a wearable device is connected to a mesh at the users home, but they leave their house with the device. How can it reconnect automatically when the user comes back home if the security key has been updated?
-
A device can belong to multiple different Mesh networks simultaneously, correct? Not just sub-nets, but whole mesh ecosystem.
-
Can a SiLabs BLE Module work with a Nordic BLE Module in the same mesh as long as they are both using the new official Bluetooth Mesh Standard?
Thanks!