IQ stuck in reboot loop due to SaltoApp crash caused by bad lock detach and reattach

When a lock is detached from the IQ is the detach procure is not followed and the detachment is not confined on the lock before it is confirmed in KS, the lock may be left in an attached state, but KS will think the lock is detached.

KS will then allow the lock to be reattached.

The lock will never come online if it is attached to a different IQ, however, if the lock is re-attached to its original parent IQ one of two things will happen:
1. If the lock tree ID remains the same, everything will work fine.

2. If the lock tree ID has changed, there will be mismatch between the tree id the IQ has and the tree ID that the lock has stored

This mismatch causes a crash in the Salto Application when it tries to establish communication with the lock.

Since this is a systematic error, the crash will occur as long as the lock is in range.

Fixes and workarounds:

1. Fix - this issues is resolved in Salto App v2.21. There is no IQ release with this available for update.

2. For non SoC/HSE locks it is possible to partially re-initialise the  offending lock and resolve the issue.

3. For all locks - the IQ tree needs to be modified so that the offending lock id matches - Note, this is hard to do if it is not known which lock is causing the reboot and what its original ID was

Procedure for 1:

• When a release is made available by the IQ team (no timelines yet)

  • Reset the IQ

  • Perform an update to the required IQ version

  • Restore the IQ

  • Confirm that locks come online and IQ does not reboot

Procedure for 2:

• Identify the lock causing the issue

• Alternatively, apply to all locks

• Take lock batteries out

• Immediately after inserting batteries present the maintenance card - this reinitialises the lock and will allow it to store the correct new tree ID

Procedure for 3:

• Using the KS API, move the lock entry in the IQ tree up or down the list

• Lock IDs for flat IQ trees correspond to the order of the objects in the json document

• For lock IDs in installations with repeaters please contact the IQ team and we will contact the right people to try and figure this out