As in my understanding until now, you need a provisioner to provision the nodes in the network and to configure the Server and the Client model. The Provisioner CAN be the implemented in the client model as well, if you want to though. If you are only using a Server and a Client you can use the Mesh App, which should then serve as the provisioner in the network.
As in my understanding until now, you need a provisioner to provision the nodes in the network and to configure the Server and the Client model. The Provisioner CAN be the implemented in the client model as well, if you want to though. If you are only using a Server and a Client you can use the Mesh App, which should then serve as the provisioner in the network.
That is correct. In order for devices to participate in a network, you do need to "put all devices into the same network", and in Bluetooth mesh that is the job of the provisioner.
The provisioner is usually also used to configure all other nodes. That makes sense because each device gets a unique key as part of the provision process (the "device key"), and this key is used for configuring the node afterwards. That way only the provisioner knows the secret for handling network connectivity and configuration for the nodes.
Any node participating in the network can be a provisioner, so you do not need to have a dedicated provisioner. It is even possible to have multiple provisioners if they exchange the provisioning data between each others, although this data exchange is not currently specified and so the recommendation would be to have only one provisioner. Combining the provisioner with e.g. server og client model is no problem.
