home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.48k stars 29.41k forks source link

OZW: lock.unlock failed #36668

Closed lielle1 closed 3 years ago

lielle1 commented 4 years ago

The problem

I have danalock zwave lock, with OpenZwave beta integration, if the lock is in unlock state, service lock.unlock (in order to unlatch) not working neither lock.open. If the lock is in lock state, lock.unlock working and open the door.

Environment

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

probot-home-assistant[bot] commented 4 years ago

ozw documentation ozw source (message by IssueLinks)

probot-home-assistant[bot] commented 4 years ago

Hey there @cgarwood, @marcelveldt, @MartinHjelmare, mind taking a look at this issue as its been labeled with a integration (ozw) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)

MartinHjelmare commented 4 years ago

Sorry, I'm not following. Do you want to unlock an already unlocked lock? Or do you want to use the unlatch feature that only some locks have?

We haven't implemented support yet for the lock.open service to unlatch a lock. We just have lock and unlock.

You can support the development by recording an mqtt dump of your lock device with the mqtt dump service and post the file here.

https://www.home-assistant.io/docs/mqtt/service/#service-mqttdump

lielle1 commented 4 years ago

Sorry, I'm not following. Do you want to unlock an already unlocked lock? Or do you want to use the unlatch feature that only some locks have?

We haven't implemented support yet for the lock.open service to unlatch a lock. We just have lock and unlock.

Well, on regular zwave integration lock.unlock use to "re" unlock the door and hold back the latch, this was the way we use to open the door in our house...

MartinHjelmare commented 4 years ago

We don't do any checks of state before sending the value to the mqtt broker. If the device isn't reacting as it did in the old integration, I think the change is due to the OpenZWave library. You can try searching that issue tracker or opening a new issue there.

https://github.com/OpenZWave/open-zwave/issues

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.