Not send message with example Light_switch of Mesh 2.2

RE: Not send message with example Light_switch of Mesh 2.2

Giang — Thu, 03 Jan 2019 05:14:20 GMT

Yes, i will. server can receiver msg if client send data to group address. If client send data to unicast address of server , server don't receiver any thing

RE: Not send message with example Light_switch of Mesh 2.2

Hung Bui — Mon, 17 Dec 2018 09:29:33 GMT

Hi Giang,

Did you provision the server and client the first time with the phone or with the provisioner ?

I assume you were pressing button 0 on the server ? Could you please enable logging in access layer (enable LOG_LEVEL_DBG1 level) and check if it's the server didn't send the message (log "RX:") or it's the client couldn't receive the message (no "TX:" in the log)

RE: Not send message with example Light_switch of Mesh 2.2

Giang — Thu, 13 Dec 2018 01:42:03 GMT

Yes, I have done enough steps. Problem is the first time, server can't send to client and if I reflash or reset by mobile and reconfiguration , it run normal. I only encountered this problem with generic onoff model , if I create 1 vendor model, I do not have this problem. I tried sample of SDK on 2 DEV KIT nrf52832 and the same problem occurs

RE: Not send message with example Light_switch of Mesh 2.2

Hung Bui — Wed, 12 Dec 2018 15:56:17 GMT

You would need to make sure the server actually has the publication address point to the client, or the client subscribe to the group address that the server publishing to. This is not configured by default by the provisioner.

RE: Not send message with example Light_switch of Mesh 2.2

Giang — Mon, 10 Dec 2018 15:21:54 GMT

I deleted all before flash firmware. Client can send message to server, but server can't send. When I push button on Server kit, client not receiver anything. And when client send ack message, server not reply ack

RE: Not send message with example Light_switch of Mesh 2.2

Hung Bui — Mon, 10 Dec 2018 12:34:17 GMT

Hi,

Could you explain what you meant by "Server can't send message to client " ? Were it about server sending status reply to client ?

When you test the first time, did you try to do an erase all ? There could be some data on the flash of the previous firmware, it's better to have the chip fully erased before testing.