I have a critical problem about mesh network.
After running 2 days, some device in mesh network cannot publish message with error 15 ( forbidden ).
I tried to search in devzone, I found some people has the same problem with me.
I think iv index update produce or sequence number has problems.
But i only send 1 ping message per hour, and sometimes response keep alive message from gateways.
I cannot figure with that problems happen.
How can i recover device when publishcation forbidden occurs?
I noticed this from an earlier post:
huybk213 said:When forbidden error occurred, i am restart device but it never publishcation success again.
If reset is done many times, either manually or automatically…
The sequence number is on the message as sent from the originator. The number of relays through the network is not related to sequence number, as the sequence number stays the same when relayed.
This thread is related to what you see here.
It will be helpful if you can provide the following information:
- Mesh SDK version
- What example you are running?
- Have you made any modifications to the example?
I was used lastest SDK Mesh 4.1
BLE SDK 16
I was custom example light switch.
Instead of send ( 1 or few ) bytes in origin example, i send a byte array payload with length 12 bytes.
When forbidden error occurred, i am restart device but it never publishcation success again.
I tried to reprovisioned device (without reflashing),
After thatcthat, node send message again without any problems.
In my mesh network, we have 60 mesh devices, but only 10 device was power on, 50 other device we will setup later after 1 week.I was use setting default TTL is 60 for all node.Does seq number increase in every relay message? May be TTL is too large.
Dear Mttrinh, could you please give me your suggestion?Today, once more node die again, it's a big problem for us.I review my code, i am sure only send ping message and response ping from gateway.Regards.
I have asked the Mesh team to take a look at this. Will come back to you with an update.