nRF Mesh iOS app uses wrong unicast address for GenericOnOff state switch

[JonasJ]

Hi,

I have a device with two models, the Generic OnOff Server is located on the second element. When using the "Node Control" to change the "GenericOnOff state" the app sends the correct message but to the wrong unicast address. The model isn't subscribed to any other addresses.

The element has address 0x0002 but the app is sending to the primary element, i.e. 0x0001.

I'm using V 1.0.2 build 9.

Thanks.

[Joakim Jakobsen]

Hi.

Are you seeing this on the iOS or Android version of the nRF Mesh app?

Hard to say if this got something to with the application itself, or if it is a bug in the nRF Mesh app.
I will try to set this up myself, and see if I'm able to reproduce the issue.

Best regards.

[JonasJ]

Hi,

As per the title, I'm using iOS.

Here is a short log from repeating the procedure just now.

<t:    3964676>, main.c,   72, Successfully provisioned
<t:    3964686>, main.c,   82, Node Address: 0x000D
...
<t:   14981528>, access.c,  246, RX: [aop: 0x803D]
<t:   14981532>, config_server.c, 2415, Access  Info:
                element_index=3         model_id = 1000-FFFF            model_handle=6
...
<t:    2420330>, proxy.c,  611, RX
<t:    2420336>, proxy.c,  553, RX GATT PDU type 0x0, len 22
<t:    2420344>, net_packet.c,  230, Unencrypted data: : 000D65AA3762332C40F74C
<t:    2420351>, transport.c,  934, Message decrypted
<t:    2420354>, access.c,  246, RX: [aop: 0x8202]

The node is first assigned the address 0x000D.

It's then assign an Application Key to element_index 3, the one with the OnOff server.

When the OnOff message (0x8202) is sent it uses the wrong destination address as can be seen by the net_packet.c  printout, the first 2 bytes. I.e. 000D. The app shows that the element has the address 0010.

Thanks.

[Joakim Jakobsen]

Hi.

I'm sorry about the very long delay here.

As this might be a bug with the app, I've reported this internally to our developers.

Best regards.