Node-red-contrib-homekit-bridged: [BUG] LockMechanism doesn't work with Siri

[Supergiovane]

First of all, thank you for this great node!
The LockMechanism doesn't work with commands issued by my voice to Siri. Using the home app, it works instead.
Before updating to 0.8.0, it worked flawlessly.

To Reproduce
1) Create a node set to LockMechanism, with name, for example "main door"
2) Deploy in node-red
3) Add the new device to the Home App
4) try open the "main door" from Siri (Hey siri, open the main door).

Expected behaviour
The door should open, but instead, siri tells me "i'm still opening the door, ask me later if the door is open", and nothing happens.

Additional context
If i open the door by tapping the icon in the Home App, the node emits a message to the flow and the door opens.
If i open the door by saying "hey Siri, open the main door", in the Home App i see the door opening icon lights up but the node doesn't emit any message to the flow.

Nodered v1.0.2
node-red-contrib-homekit-bridged v0.8.0
Thank you.

[feens]

I tried this today and can confirm the behaviour (I just finished setting up a lock).

[Supergiovane]

I raised the question to HAP-NodeJS and i'll let you know.

[Shaquu]

Related to KhaosT/HAP-NodeJS#776

[Supergiovane]

https://github.com/KhaosT/HAP-NodeJS/issues/776#issuecomment-574363192

[Shaquu]

@Supergiovane
0.8.0 is not using hap-nodejs in 0.5.5 (it uses 0.5.0)

So you either have to wait for official release (1.0.0) or you can use dev branch but it is unstable and untested (and doesn't have backward compatibility, you will have to re-add accessories in Home.app).

[feens]

@Shaquu is there an ETA for 1.0.0? I know there's a PR open for it, and hap-nodejs 0.5.6 has been released (I know yo were waiting for that project to stabilize a bit).

[Shaquu]

@feens mostly I need people to test their current set up under dev version (with backup because everything can be lost either way). I can make a test on mine devices but everyone has a different scripts, guards etc so something can work for me and break for others - and that happened in 0.7 I believe and it was bad.

And recently @crxporter got back here so I hope he will push this subject :)

Answering. Best option is the couple of days. Worst unknown.

[crxporter]

I’ll try the lock tonight or tomorrow.

@Shaquu - I saw hap nodejs got 0.5.6 today, can we get a dev.5 to get the very latest version?

[Shaquu]

@crxporter published (PR in #199)
npm i [email protected]

[crxporter]

@Supergiovane and @feens is there any improvement with 1.0.x? I never ended up experimenting with this one but it should have updated hap-nodejs as discussed

[Supergiovane]

Hello
Manually updating hap-nodejs to latest version, has fixed the issue for me. I’ve not currently update to the official 1.0.x

[Supergiovane]

V. 1.0.4 solved the issue. Thank you.