Is there documentation for the Node Identity (get, set, status) messages?

[Berry Blue]

I see references to a get (0x8046), set (0x8047), and status (0x8048) messages for Node Identity. Where could I find documentation about these messages? There is no sample code in the Nordic App for these messages.

[tesc]

Hi,

This is all part of the Configuration Model, which is one of the foundation models in Bluetooth mesh. The message formats for the Bluetooth mesh packets are directly from the Bluetooth mesh specification, and the data structures used in our nRF5 SDK for Mesh is described in the Message formats chapter of our Configuration Model documentation. You should use our API functions and the Configuration Model module in the SDK for handling these messages.

Regards,
Terje

[Berry Blue]

Yes, I see the definitions for these messages but not what they actually do or how to pack the data for these messages. Is there more documentation like this for them? 

[tesc]

Hi,

Those messages are core parts of the Configuration Model, and are handled automatically by the Bluetooth mesh stack. From what I can tell you are not supposed to hook into it. As it is considered internal to the mesh stack implementation it is not documented on our Infocenter. For details on how this works, message formats, etc., please consult the Bluetooth mesh networking specifications, or the nRF5 SDK source code (e.g. config_server.c, config_messages.h, etc.)

May I ask what the use case is, do you have a particular situation where you need to handle this manually from the application, or are you just looking into the stack in order to understand how Bluetooth mesh works?

Regards,
Terje

[Berry Blue]

I want to connect to a provisioned node from multiple devices. So, I provision a node from one iPhone and then I want a second iPhone to be able to connect and send messages. It does work in principle but I don't know how to identify the provisioned node from the second iPhone when I have multiple nodes. The UUID changes between iPhones for a particular node so I'm wondering if there is any other identifiable information that stays consistent on the node such as in the configuration model that I can get.

[tesc]

Hi,

Ah, right, so this is on the smartphone side that you need to use the configuration model for probing node ID? Then I understand the motivation for the question.

Have you looked in the IOS-nRF-Mesh-Library?

Regards,
Terje

[Berry Blue]

Yes, but I'm not able to find an existing code sample on how to accomplish this. The Nordic App does 1-1 connections with nodes so you provision one node with one iPhone but I'm not able to find out how to interact with a single mesh network from multiple phones. I just need some way to determine the identity of a node from different phones. The UUID changes between phones for the same node.

[Berry Blue]

Also, if I send a blank get message I'm not getting a status message back. I don't know what data I'm supposed to send with the get messages to get a status response.

[tesc]

Hi,

The Config Node Identity Get message has one field 2 bytes in size, for NetKeyIndex, ref. Mesh Profile Specification 1.0.1, section 4.3.2.43 "Config Node Identity Get", where the encoding for NetKey Index is described in detail in section 4.3.1.1 "Key indexes" in the same document.

The main reasoning for having that field would be that a node can take part in multiple networks, with different node identity for each network.

Regards,
Terje