-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Yale Doorman L3 works, even if listed as "known not to work" #21362
Comments
Hey there @bdraco, mind taking a look at this feedback as it has been labeled with an integration ( |
Its reported here #19882 and here home-assistant/core#54722 (comment) as not working I don't have one myself so I can't validate either way. |
Ok. Let me know if you need any assistance from me to validate/test things either way. I am a software developer and I have that lock, it works for me in Home Assistant right now, and I am willing to support you with my time if you need me to test/check things out.. |
To validate we are doing everything correctly in The app uses certificate pinning so you'll have to use something like https://httptoolkit.tech/blog/frida-certificate-pinning/ to see the https requests. If you don't have any luck getting the dumps, in the past I setup a dev account setup to allow people to share owner access to their lock for a brief time for me to take the dumps so we could add support for their lock: augustdev@koston.org |
I'll get back to you. I'm not feeling 100% after having had covid last week. Also, I need to set up Android dev-env again as I have new computers. :) Just letting you know. |
No worries. Take your time. Feel better |
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. |
Feedback
Just tested it? I have the wifi bridge.
Device info
IRCN190916
by August Home Inc.
Firmware: 3.2.1-3.3.0-2.0.8
URL
https://www.home-assistant.io/integrations/august/
Version
2021.12.10
Additional information
No response
The text was updated successfully, but these errors were encountered: