Mesh - Vendor Sensor Type?

[Hayden Ball]

Hopefully a simple question: is it possible to define a vendor-specific sensor type for the standard Mesh Sensor Model?

The nRF Connect SDK documentation seems to be confused.

The Mesh Sensor documentation says:

> The Bluetooth Mesh specification only allows sensor types that have a Device Property ID in the Bluetooth Mesh Device Properties Specification

The Bluetooth Mesh sensor types documentation disagrees:

> any additional, proprietary sensor types should be added to sensor_types.c

So... is it possible correct to define a proprietary sensor type, or is it not?

If it is correct, what is the allowable range for sensor IDs? Will custom sensor IDs behave correctly with the nRF Connect SDK, and the nRF Mesh iOS / Android libraries?

[Hung Bui]

Hi Hayden, 
I'm sorry for the late response. I'm checking this internally with the Mesh team. I will keep you updated when I get the information from them. 

[Hayden Ball]

Hello Hung Bui - I don't suppose you've been able to find out any more information?

[Hung Bui]

Hi Hayden, 
I still haven't got any feedback yet. 

[Hung Bui]

Hi Hayden, 
I got the feedback from the developer: 

This Note in the documentation is the truth: 

The Bluetooth Mesh specification only allows sensor types that have a Device Property ID in the Bluetooth Mesh Device Properties Specification. It’s not possible to represent vendor specific sensor values.

It is not possible to add proprietary Property IDs, and therefore, it is not possible to add proprietary sensors.  

The other reference that the customer provided means:

It is possible to add a proprietary implementation of valid sensor IDs. 

We will remove the note in the Bluetooth Mesh sensor types section as it may create confusion. 

[Hayden Ball]

Thank you Hung Bui