server and client model in same element index

[bivay]

Can a server and a client of dimming example, have same element instead of different element ID.

I got worked for server and client model in single node, but they are in different element index.

When I combined in single element index, they worked, but I can't use unicast address to send data, I can only use Group address for it.

So, How can I use unicast address to send data from client to server and get data from server to client in response.

Thank You

Bivay

[Mttrinh]

Hi,

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

[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. 

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?

[bivay]

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? 

[Mttrinh]

Yes, that is correct :)

[bivay]

Thank You

[bivay]

Is this issue solved in newer Mesh SDK 4.1.0.