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

Device specific parameters in BLE Mesh

Hello,

I have a question about Mesh implementation.

I need to build a network of BLE mesh devices, lets suppose for the moment they're based on light switch server model example.

Each device has a set of specific parameters for its configuration, for example, led color, etc.

These parameters are specific for each device, and there's no need to exchange them over the network.

How should I manage these parameters?

Should I create a custom mesh server (for example light switch configuration server model)? 

Or should I manage them just via a GATT connection?

Thank you

Enrico

Parents
  • You could either make a different custom light switch server project for each of the devices (depending on how many devices you have) or do this via the provisioner (either the provisioner example or nRF Mesh app). If you use nRF Mesh, you need to use the proxy light switch examples.

    You would most likely need to update the code a bit to configure this yourself. Based on the device UUID value that is scanned by the provisioner, you could update the parameters.

  • Thank you for your answer.

    Maybe I didn't explain well, these parameters are device specific in the sense that the user could change them for a specific device.

    For example, I create a light switch based on the light switch server example. This light switch will have a RGB backlight, and I want the user to be able to change the backlight color from the mobile app. So the device will never send this information over the mesh network, since it will be used only by itself.

    What's the correct place to store this type of informations? In the light switch server itself? If I understand well, the on-off server is standard so I have to create a new server with all the required parameters (rgb backlight color, and so on)?

    Thank you

  • Sorry for the delayed response. I have been travelling for work & have unfortunately not had time to reply to this case. 

    Ebe said:
    What's the correct place to store this type of informations? In the light switch server itself? If I understand well, the on-off server is standard so I have to create a new server with all the required parameters (rgb backlight color, and so on)?

     Yes, I would recommend putting this in the light switch server itself. I would just make a custom light switch server example & just add the required parameters (rgb backlight color, etc) in a struct or something similar. 

    If you want to use the nRF Mesh app, you will need to update it to be able to communicate to only that device. Do you want to connect to the light switch RGB backlit device using the proxy node or a regular BLE connection? If you do it via the proxy node, you will need to create your own characteristic to update the rgb backlight color & other parameters.

    If you connect to a proxy node via the nRF Connect for Mobile app, you notice that there are two characteristics present (one for proxy data in & one for data out I believe). I believe you should be able to add a new characteristic in the custom proxy light switch server example to connect & transfer the desired rgb backlight color. Again, sorry for the delayed response. Hope that helps!

Reply
  • Sorry for the delayed response. I have been travelling for work & have unfortunately not had time to reply to this case. 

    Ebe said:
    What's the correct place to store this type of informations? In the light switch server itself? If I understand well, the on-off server is standard so I have to create a new server with all the required parameters (rgb backlight color, and so on)?

     Yes, I would recommend putting this in the light switch server itself. I would just make a custom light switch server example & just add the required parameters (rgb backlight color, etc) in a struct or something similar. 

    If you want to use the nRF Mesh app, you will need to update it to be able to communicate to only that device. Do you want to connect to the light switch RGB backlit device using the proxy node or a regular BLE connection? If you do it via the proxy node, you will need to create your own characteristic to update the rgb backlight color & other parameters.

    If you connect to a proxy node via the nRF Connect for Mobile app, you notice that there are two characteristics present (one for proxy data in & one for data out I believe). I believe you should be able to add a new characteristic in the custom proxy light switch server example to connect & transfer the desired rgb backlight color. Again, sorry for the delayed response. Hope that helps!

Children
No Data
Related