RE: Separating code concerns for bluetooth mesh models

parksj10 — Tue, 27 Aug 2024 16:22:35 GMT

Thanks a lot Amanda Hsieh , I'll give it a go and report back if there are any road blocks!

RE: Separating code concerns for bluetooth mesh models

Amanda Hsieh — Tue, 27 Aug 2024 15:44:28 GMT

Hi,

struct led_ctx is specific to this sample, created for convenience, and does not require the use of Mesh APIs at all. If it doesn't fit your use case, you'll have to replace it with something else you wrote to fit your use case. The sample is, as the word suggests, a sample, not meant to be a drop-in application.

The only thing you are required to do to accomplish "a Bluetooth mesh light with hue, saturation, brightness, on/off, etc.", is to have implementations for the relevant handler functions for the Hue Server, Saturation Server and Lightness Server, and then pass these handlers to BT_MESH_LIGHTNESS_SRV_INIT and BT_MESH_LIGHT_HSL_SRV_INIT. What these handlers do is completely up to the application author, and depends on the specific use-case. In this case, where they would like to handle hue logic in one file, onoff in another, etc., and don't like to have a huge model_handler.c, I'd suggest to keep the handler implementations in model_handler.c short, just containing calls to application-specific functions in other files exposed in application-specific headers.

Regards,
Amanda H.