MeshSDK: 3.2.0
StockSDK: 15.2
Hello,
I have a network where the sequence numbers have become corrupt due to removing devices from a network and then provisioning other devices on that freed up unicast address causing the seq number to be out of sync. This causes the devices on the network to reject messages from the new device that was assigned the old unicast address. I know this is normal behavior due to section 3.10.7 of the mesh profile specification.
Will doing a IV index update fix this problem by resetting everyones seq number back to 0x0000?
Is it possible to create a firmware where you press a button and it tiggers an IV update on a mesh network?