server and client model in same element index

RE: server and client model in same element index

bivay — Tue, 12 May 2020 13:39:40 GMT

Is this issue solved in newer Mesh SDK 4.1.0.

RE: server and client model in same element index

bivay — Tue, 15 Oct 2019 08:56:53 GMT

Thank You

RE: server and client model in same element index

Mttrinh — Tue, 15 Oct 2019 08:35:08 GMT

Yes, that is correct :)

RE: server and client model in same element index

bivay — Tue, 15 Oct 2019 05:29:11 GMT

As you said when client and server is in different element, I can use above function to communicate.

Thank you for segmented message idea, I think I should try unsegmented method.

As in code message length for unsegmented message is 11 byte. I am right?

RE: server and client model in same element index

Mttrinh — Mon, 14 Oct 2019 14:01:21 GMT

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.

I'm a little bit confused, you said "I got worked for server and client model in single node, but they are in different element index." but now it doesn't work?

RE: server and client model in same element index

bivay — Thu, 10 Oct 2019 13:39:29 GMT

Mesh SDK: 3.2.0

I also tried to use two element one for server with health and config server.

and another for client.

and used this function:

static uint32_t set_model_publish_address(uint16_t publish_address, access_model_handle_t model_handle) {
  if (!m_device_provisioned) return;
  if(get_model_publish_address(model_handle)==publish_address) return;
  uint32_t status = NRF_SUCCESS;
  //publish_address=0xc000;
  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);
  }
}

when I use group address : 0xC000 and other this function works,

but when I use unicast address it didn't work

RE: server and client model in same element index

Mttrinh — Thu, 10 Oct 2019 13:27:38 GMT

Hi,

Which Mesh SDK are you using? I think your issue is related to this.