Hi,
We're really stumped on this one. We recently deployed 150 devices running nRF SDK for Mesh. All except three of these devices are running a modified SimpleOnOff Server model, the other three are gateways running the serial example with PERSISTENT_STORAGE turned on. We provisioned the devices using nRF Mesh app for Android which has unicast address of 0x0001 with a range 0x0000 to 0x1999. We used
Bluetooth Mesh Addr Local Unicast Set
Opcode: 0x9f
to set the three gateways to unicast addresses 0x2004, 0x2006 and 0x2008 respectively. 0x2004 was deployed first, we were able to subscribe and publish messages with it successfully. The other two were installed a couple of days later but weren't tested for a week. Then in the middle of the process of commisioning, we accidentally did a Net State Clear on all three gateways.
We could still see subscription messages sent to group addresses but our
Bluetooth Mesh Packet Send
Opcode: 0xab
messages were being ignored by the server devices. The server devices could still receive messages from the Android device but not from the gateways. I don't know what I did but about after half a day, gateway 0x2004 started working again, and its published messages were being received and replied to by the server devices.
The other two are still stuck in limbo. How can we recover from this?
Here's how we publish messages:
1) Read synchronised json file
2) Use
Bluetooth Mesh Addr Publication Add
Opcode: 0xa4
to get a local publication handle. Remove unused handles if none available.
3) Use Packet Send to publish, received SUCCESS response code.
Thanks,
Arif
