Sensor server get message send to root element address (should be send to 2. element)

[Jakub K.]

Hello,

I'm working with ESP_BLE_MESH and nRF Mesh app for Android.

I hope you can read structure of my elements causing the problem from image.

What i got is timeout when i hit GET on Sensor Information (in app) when Sensor server is not in root model.

Verbose log tells me that app is sending message to root element.

Am i doing something wrong or it's a bug?

[Hung Bui]

Hi Jakub, 

I don't see a problem with your composition data as in the screenshot. 
I did a quick test here with the light switch server (I changed the light server to second element ) and it worked fine for me. 
Do you have an issue when setting the appkey and the publication address ? 
Could you try to test with the light switch server ? 

[Jakub K.]

I added on/off Server to the same element (0x003C) as sensor server and it seems to work fine (sensor server still timeout)

those messages should have the same destination

1. is for sensor server (not working)

2. is for on/off server (working)

To be specific 0x003a is root element address (i picked different when provisioning)

I had no problem setting appkey, also setting up publication addres was not an issue but the messages are not send with error i dont understand fully

[Hung Bui]

Hi Jakub, 

Could you clarify, when you added  an on/off server to the element 0x3C (not the root element)  and you send 2 message, one to the on/off server and you can see the address is 0x3C, but when you send the message to the sensor server (also on 0x3C) the destination turned to be 0x3A ? 

[Jakub K.]

Yes, that is exacly what happend

Here is elements list with added on/off server and updated addresses

[Hung Bui]

Hi Jakub, 

I reported the issue to our developers and we found a bug. It's possible to fix the bug in the app source code: 

 It’s a bug in the app, so there are two methods in the app one sending a message to the local element and the other sending it to a given address. So the sensor server screen is calling the wrong method. However it’s a bug in the app not in the library itself.

The app should be calling sendMessage(final int address, @NonNull final MeshMessage meshMessage) in the SensorServerActivity instead of sendMessage(@NonNull final MeshMessage meshMessage)

  

We will fix the issue in our next release. In the mean time you can fix the bug in the app's source and re-build it.