Lock won't change status to open

[electric-m]

After tinkering around a good bit, I think I finally got this up and running, at least regarding the hardware.
The Homekey of the iPhone is recognized just fine in the Serial Console, but the lock inside the Home App does not change the status from closed to open. It just stays closed.
MQTT Status also stays at 0.

Any ideas?

I (20889) Blinker: Pausing LED
I (54773) LockMechanism: loop > *** PASSIVE TARGET DETECTED ***
I (54800) LockMechanism: loop > *** SELECT HOMEKEY APPLET SUCCESSFUL ***
I (54935) HKAuthCtx: HKAuthenticationContext > Initialization Time: 135 ms
I (55139) HKAuthCtx: authenticate > Flow complete, transaction took 203 ms
I (55161) LockMechanism: loop > Total Time (from detection to mqtt publish): 387 ms
I (64361) LockMechanism: loop > *** PASSIVE TARGET DETECTED ***
I (64387) LockMechanism: loop > *** SELECT HOMEKEY APPLET SUCCESSFUL ***
I (64522) HKAuthCtx: HKAuthenticationContext > Initialization Time: 135 ms
W (64749) LockMechanism: loop > We got status FlowFailed, mqtt untouched!
I (264122) LockMechanism: loop > *** PASSIVE TARGET DETECTED ***
I (264149) LockMechanism: loop > *** SELECT HOMEKEY APPLET SUCCESSFUL ***
I (264285) HKAuthCtx: HKAuthenticationContext > Initialization Time: 135 ms
I (264486) HKAuthCtx: authenticate > Flow complete, transaction took 201 ms
I (264508) LockMechanism: loop > Total Time (from detection to mqtt publish): 385 ms
I (290182) LockMechanism: loop > *** PASSIVE TARGET DETECTED ***
I (290209) LockMechanism: loop > *** SELECT HOMEKEY APPLET SUCCESSFUL ***
I (290345) HKAuthCtx: HKAuthenticationContext > Initialization Time: 135 ms
I (290539) HKAuthCtx: authenticate > Flow complete, transaction took 194 ms
I (290560) LockMechanism: loop > Total Time (from detection to mqtt publish): 377 ms

[stresli]

lock changes status via mqtt, not via home key authorization. search information in previous discussion.

[thorsten-gehrig]

@electric-m : may you take a look here: #18 (reply in thread)

[electric-m]

Thanks Thorsten, that’s absolutely what I needed. I don’t need the lock to have the correct visualization, I ended up setting a flow in nodered, that actuates my actual motorized lock when the correct MQTT message arrives.