Hello,
My first thought is for instance that one of the peers have some bonding information cached/stored from previous communication, and when you now have updated some configuration, then one of the peers have at the same time erased it's bonding information, and thereby you end up in a situation where you are not able to successfully bond again (for security reasons).
My suggestion would be to do a full eraseall on both peers before you reprogram them, if that doesn't solve the problem my next suggestion would be to check for any errors in the application log which may provide further details of what is failing.
Kenneth
Hello again,
A collegue tipped me off that you also need to update these locations:
Hope that helps,
Kenneth
Hello again,
A collegue tipped me off that you also need to update these locations:
Hope that helps,
Kenneth