ble mesh API standardization
Posted: Mon Mar 18, 2024 5:49 pm
Hi team,
I dont want to sound like I linger or something, because so far i think that ble mesh stack is great and easy to work with, but can we have some standardization in API please.
For example we have names like this:
- esp_ble_mesh_lighting_server_cb_t
- esp_ble_mesh_light_client_cb_t
whats the difference between lighting and light?
Similar functions, but params order
Its not big deal, but sometimes it makes me confused.
There is probably more examples, but i am not trying to find all, just those 2 hit me at this moment.
Thanks
I dont want to sound like I linger or something, because so far i think that ble mesh stack is great and easy to work with, but can we have some standardization in API please.
For example we have names like this:
- esp_ble_mesh_lighting_server_cb_t
- esp_ble_mesh_light_client_cb_t
whats the difference between lighting and light?
Similar functions, but params order
Code: Select all
esp_err_t esp_ble_mesh_provisioner_bind_app_key_to_local_model(uint16_t element_addr, uint16_t app_idx,
uint16_t model_id, uint16_t company_id)
esp_err_t esp_ble_mesh_node_bind_app_key_to_local_model(uint16_t element_addr, uint16_t company_id,
uint16_t model_id, uint16_t app_idx)
There is probably more examples, but i am not trying to find all, just those 2 hit me at this moment.
Thanks