Bluetooth Mesh E: Invalid address

[Leon Weigel]

I have been trying to configure a Mesh Node with several Level Servers and Clients to send/receive messages to/from different virtual addresses. 

Unfortunately, one of the level servers, which is set to subscribe to a virtual address, returns the error "E: Invalid address 0xb2f2". Also, one of the level clients returns the error "E: Invalid address 0x9503". I tried to configure the virtual addresses as group addresses instead, but with no success.

• CONFIG_BT_MESH_LABEL_COUNT is configured to allow for 10 different labels.
• The Nordic mesh app is acting as provisioner.
• nRF Connect SDK v2.6.0, Toolchain v2.6.0 are in use.

Any help would be appreciated

[Leon Weigel]

The error is created in the block of function element_model_recv in access.c line 1495:

if (!model_has_dst(model, ctx->recv_dst, ctx->uuid)) {

        LOG_ERR("Invalid address 0x%02x", ctx->recv_dst);

        return ACCESS_STATUS_INVALID_ADDRESS;

    }

[AHaug]

Hi,

It looks like you're trying to use a group address that is outside of the available address range for non-fixed group addresses defined by the spec. In the Mesh protocol specification v1.1 (https://www.bluetooth.com/specifications/specs/?types=specs-docs&keyword=mesh&filter=), section 3.4.2.4 Group address you can see that addresses in the range of 0xC000 through 0xFEFF are available for other usage, whereas your address 0xb2f2 are outside of this range. Could you try to change the address to something inside of the valid range and report back if this resolves the error?

Kind regards,
Andreas

[Leon Weigel]

They are virtual addresses that were automatically generated by the nordic mesh app according to Bluetooth Mesh protocol specifications. The same problems happens with both group and virtual addresses.

[AHaug]

Hi, 

Can you confirm if your models are subscribed to the correct UUID labels as well? 

While using virtual addresses, a care must be taken to ensure that address collisions are handled correctly. A single virtual address can map to many label UUIDs. While configuring things, you also need to consider label UUIDs. According to the developers if a message is sent from a node to an unknown virtual address, the app won't be able to decode it, as the full UUID is needed for decryption. The error triggers when the given model is not subscribed to that specific virtual address.

Let me know if this gets you any closer to a resolution of the issues

Kind regards,
Andreas

[Leon Weigel]

The server models were subscribed to said virtual addresses. I used the nordic mesh app to do so.

[AHaug]

AHaug said:

Can you confirm if your models are subscribed to the correct UUID labels as well? 

Please show me screenshots and/or describe the steps you used in the subscription procedure so that I can relay it to the developers for input.

Kind regards,
Andreas