can't Send data to server from client with unicast address of server

[bivay]

I set the publish address of client using function:

static uint32_t set_model_publish_address(uint16_t publish_address, access_model_handle_t model_handle) {
  uint32_t status = NRF_SUCCESS;
  dsm_handle_t publish_address_handle = DSM_HANDLE_INVALID;
  access_model_publish_address_get(model_handle, &publish_address_handle);
  NRF_MESH_ASSERT(dsm_address_publish_remove(publish_address_handle) == NRF_SUCCESS);
  status = dsm_address_publish_add(publish_address, &publish_address_handle);
  if (status != NRF_SUCCESS) {
    return status;
  } else {
    return access_model_publish_address_set(model_handle, publish_address_handle);
  }
}

Unicast address of sever is 0x0003.

After setting publish address by this function, I check publish address from mobile Nrf Mesh App, and it reflects the publish address to 0x0003.

but when I publish data from client it doesn't reach to server.

Dimmer  onoff example works perfectly for client and server, but when I use this method of publication, it didn't work.

But when I use 0xC000 subscribe address (subscribed from mobile for server), it works.

Thank You

Bivay

[Mttrinh]

Hi,

Do you use the static provisioner form our SDK to provision both nodes? Also, is the function for setting the publish address the only modification you made to the example(assuming you are using the dimming example)?

[Mttrinh]

Is there are a reason why you are not using the nRF Mesh to set the publish as well? Can you try to commenting out the modifications you have done and set the publish address of the client via the app? Does it work?

[Mttrinh]

Which Mesh SDK version are you using?

[bivay]

I am using latest mesh sdk: v3.2.0

and nrf5 SDK 15.3.0.

[Mttrinh]

I think your issue are related to this.

[bivay]

I Think you are right when i use different element index for client , server and config and health, this method works.

But I need all model in same element for proper addressing. How to solve this issue.

[Mttrinh]

As of now the only workaround is to have client and server model in seperate elements. But this only apply if the responses sent by the server model is segmented messages, if not client and server model can be on the same element. We are looking into the issue and try to fix this as soon as possible. 

Sorry for the inconvenience.