This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Is it possible to implement Configuration Client on non-provisioner?

I'm trying to extend the light_switch client example (from mesh SDK 3.1.0) to a gateway. The gateway will consists of nRF52832 and a WiFi module connected via serial interface. Purpose of this is to display the status of the lights on a IoT dashboard and allow users controlling the lights from the dashboard as well.

The light_switch client and servers will be provisioned using nRF mesh application on a mobile phone. 

With existing examples, it is possible to display and control the on/off status of the lights.

However, I wonder whether it's possible to allow the dashboard to display and control the publication and subscription addresses of every light server. To achieve this, it seems the best way is to have Configuration Client on the light_switch client node. After some researching, this seems to be impossible. In order for Configuration Client to be bound to Configuration Server, the device key of the light server need to be known. The device key is only known to the light server node and the provisioner, i.e. the phone. There doesn't seem to be a way for the light client node to know it.

There is a similar question at https://devzone.nordicsemi.com/f/nordic-q-a/27343/how-to-set-mesh-model-publish-address-to-a-client-model-which-is-on-other-mesh-node?ReplySortBy=CreatedDate&ReplySortOrder=Ascending. But I dont find the answer there.

Any answer and suggestion is appreciated.

Parents Reply Children
No Data
Related