-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lock.lock and lock.unlock no longer working #14
Comments
I just tried my locks with 0.2.0 (re-installed via new configuration flow UI) and it worked well for my doorman v2. |
Ah... I had it installed via HACS. I tried to uninstall it and re-install via the the new configuration flow UI, but I am not able to install it... I'm at 0.117.5 will try to pull the latest release. |
You still install via HACS, but then you add the config through the UI. |
Yup, re-read the read-me and I've now got it configured via the ui :-) However, no cigar on the lock. Temperature sensors show up fine. Works fine in the app... |
The app version is v2.0.22... Don't know if that matters :-) |
I have had this myself that it works and then suddenly it does not work. |
same problem here, everything else works fine, but not the Lock / unlock Yale doorman V2... |
Do we know if this worked without failures before this integration was installed in HA? |
And you mean before using this integration unlocking/locking the door was ok without issues? |
Yes, before it was OK without any issues. Yes, Autolock is enabled. |
Can you check if this is still the case using the newest beta v0.2.2-beta1 |
Tested a while ago and it's the same problem, nothing happens. |
Still the same. I tried to have a look at it a while back and did some digging in the code. It appears as if it stems from the underlying library and the json sent to the server. There is no action on the server side even though the json appears correct. Might be that they change the format now and then? Could be the reason for the versioning? I also saw that there were different servers to choose from... In the end I gave up. I think I would have to look at the json sent by the app to get further. And I might be wrong in some of my "observations" above 😊 |
Just released new beta (beta2) addressing this. Seems to work fine for me right now with some minor tests. |
Woks like a charm, nice work! |
Yes, works. Just works :-) Out of curiosity, what was the issue? |
There were a few actually so let's just say I didn't review it properly before 😄 |
Closed with v0.3.0 |
This worked a couple of weeks ago (doorman v2), but now it no longer works.
- type: glance
#(...)
entities:
- entity: lock.ytterdor
name: Ytterdør
tap_action:
action: call-service
service: lock.lock
service_data:
entity_id: lock.ytterdor
code: !secret sector_code
The text was updated successfully, but these errors were encountered: