Upgrade 0.6 --> 0.8 When unlocking, stuck in state 4 (unlocking)

[eigenphase]

I upgraded from 0.6 to 0.8 yesterday and all of a sudden my unlocking mechanism stopped working. However, on iPhone/watch I got the indication that it was successful.

I haven't changed any configuration; prior config was working flawlessly for years.

After some debug I found out that actually everything is working. However, when I scan my phone, the state published to MQTT goes to 4 which means "Unlocking" and is then stuck there. I believe it should be "0" for unlocked.

What could cause this?

EDIT: I double checked all my settings and I with MQTTLoupe/MQTT Explorer I can clearly see that a successful scan results in homekey/homekey/state=4 (which is my status topic). This must be a bug

[eigenphase]

Issue is described here: #258

In short, newer version added a logic that puts lock into "Unlocking" while it waits for the successful (or unsuccessful) locking of the lock. If there is no hardware/software in the loop, there is now a "Dummy Trigger" that has to be enabled. On upgrade it may be that it's not getting enabled automatically.