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

Features configuration with nRF MEsh

Hello,

I'm developping an evaluation purposed mesh network  based on the simple light example and I plan to provision it with the nRF Mesh App (Android and iOS).

I will need to configure features on my nodes as relay or friend/lowpower. Is it possible to do it with the app? or what would be an easy workaround?

thanks

Mickael

Parents
  • Hi Mickael,

    We do not support the friend/low power feature on our mesh sdk yet. We will support it in the future sometime.

    As for a workaround, it should be possible to do something similar with the nrf mesh app. You could make your own proxy node that can communicate via the phone using the PB-GATT bearer layer & via a regular BLE connection. Then, you could enable a regular ble connection to a ble peripheral device, which can act as your low power node. The proxy node would be your friend node.

    The proxy node would need to have a peripheral & central role defined. The peripheral role would be for provisioning via the phone & the central role would be for connecting to the "low power" device.

    You would also need to implement some sort of caching mechanism to store the messages that should be sent to the low power node via the proxy/friend node.

    It might also be useful to take a look at the enocean switch translator client example. I am not sure if this solution would be an "easy workaround", but it might be a doable workaround. You would most likely need to implement quite a lot to get this to work.

Reply
  • Hi Mickael,

    We do not support the friend/low power feature on our mesh sdk yet. We will support it in the future sometime.

    As for a workaround, it should be possible to do something similar with the nrf mesh app. You could make your own proxy node that can communicate via the phone using the PB-GATT bearer layer & via a regular BLE connection. Then, you could enable a regular ble connection to a ble peripheral device, which can act as your low power node. The proxy node would be your friend node.

    The proxy node would need to have a peripheral & central role defined. The peripheral role would be for provisioning via the phone & the central role would be for connecting to the "low power" device.

    You would also need to implement some sort of caching mechanism to store the messages that should be sent to the low power node via the proxy/friend node.

    It might also be useful to take a look at the enocean switch translator client example. I am not sure if this solution would be an "easy workaround", but it might be a doable workaround. You would most likely need to implement quite a lot to get this to work.

Children
No Data
Related