Closed dwyeraidan closed 11 months ago
Looking at the website, this like it is only Asia Pacfic
Can confirm it is broken after the update.
Yes it just broke for me also. Any way to fix this? once the user account is migrated it can't be logged into in August :(
I would first open an issue on the august api repo that I use: august-api
@donavanbecker Thank you but I doubt it will fix this issue. The reason it breaks is because the users accounts as of now no longer exists on the august database. Yale has decided to migrate them to a new infrastructure which means this plugin unless changed will not work for Yale door locks any longer. Only way to fix it I guess is to use their new portal which has been posted above I am not sure if this API can be used with Yale in that case
Looking at it it seems to be an API avaiable for Yale door locks here:
https://docs.seam.co/latest/device-guides/get-started-with-yale-locks
Maybe this is something you could integrate in this plugin @donavanbecker I would love if you could :)
@donavanbecker Thank you but I doubt it will fix this issue. The reason it breaks is because the users accounts as of now no longer exists on the august database. Yale has decided to migrate them to a new infrastructure which means this plugin unless changed will not work for Yale door locks any longer. Only way to fix it I guess is to use their new portal which has been posted above I am not sure if this API can be used with Yale in that case
Hmm I guess I shouldn't have upgraded yet....
Yale only giving folks until start of July to migrate before losing access natively even, so we don’t have much choice!
On Thu, 18 May 2023 at 17:31, Ruben Stolk @.***> wrote:
Hmm I guess I shouldn't have upgraded yet....
— Reply to this email directly, view it on GitHub https://github.com/donavanbecker/homebridge-august/issues/60#issuecomment-1552642847, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASPRLRRFF45LD6H56EVITEDXGXF4PANCNFSM6AAAAAAYEOWONA . You are receiving this because you authored the thread.Message ID: @.***>
Any updates on this? real bummer this does not work anymore to be honest one of the best plugins for Homebridge
No one has open an issue on august-api so not much that I can do with the plugin
Not so technical but the api I posted above can't that accomplish the same thing? It seems to be updated and uses the same login method as the August one. This should not be on the August api since the users has been migrated away from that platform.
Sorry, I can look into it, but don't have time right now.
Sorry, I can look into it, but don't have time right now.
That is understandable! I will send some contribution your way if you have time to fix this :) API I linked looked pretty straight forward and you can just make a switch in the plugin that switches if it is a August lock or Yale lock device.
This seems to have been fixed on the Homeassistant plugin for August now. Can we just implement the same changes they did on this plugin?
@AquaRelliux Pull requests are welcomed.
@AquaRelliux Pull requests are welcomed.
Unfortunately I don't know how to code this at all believe me I would give it an honest attempt if I knew where to even begin I think it is just to much for a beginner on this to understand :)
So I migrated this to Homeassistant August plugin it works great with homekit if anyone else also has this problem with August. The plugin on Homeassistant has now builtin support got Yale access and Yale home as well as the original August auth. I hope this gets fixed on Homebridge soon since I love the simplicity over Homeassistant but seems like developers on Homeassistant have more resources to help out which is a shame.
@donavanbecker any update on a fix for this?
Sorry it’s summertime, so not much time to work on this right now
v1.2.0 has been released, but won't fix this when I get time I will look at adding this support, might be in a different plugin though.
A new plugin? Interesting 😉
I've also had to disable this plugin as I've migrated to the new Yale account. I'm in the UK so I suppose that all European customers will have this issue also.
Anything new on this problem? :)
The plugin for homekit updated a couple of months ago to accommodate this - is there potentially something there that could help with this issue?
Unfortunately not going to happen anytime soon. Don't see any promising apis that make it easy to setup.
Unfortunately not going to happen anytime soon. Don't see any promising apis that make it easy to setup.
How is it that it works in Homeassistant then? They also have a August plugin and it was fixed within days after it broke? They must use an API?
@AquaRelliux this integrates with a module that manages all of the API components. So I don't really deal with much with the API.
If that module was updated to support Yale Home then I could add it to the plugin. Or any module that supports it.
Also it is hard to test this without an account.
Nearly! I got the August code and it finds my 3 door locks however it then throws a fault.
Hope the screenshot helps, I can grab proper logs if that helps.
The plugin used to work prior to the account change and since then it’s been disabled.
[image0.png]
Sent from my iPhone
On 29 Oct 2023, at 03:25, Donavan Becker @.***> wrote:
Okay, I may have found something which I have added into the latest beta. Without an account though, I can't test it.
Please test the latest v1.3.0 beta and report back if it works for you.
— Reply to this email directly, view it on GitHubhttps://github.com/donavanbecker/homebridge-august/issues/60#issuecomment-1783987623, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD2AEAG2WC3K4TVDA7GQB2TYBXEEFAVCNFSM6AAAAAAYEOWONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHE4DONRSGM. You are receiving this because you commented.Message ID: @.***>
With the august-api now support the YaleHome URL, I have Release v1.3.0. I am going to close this issue. If you are having issues with v1.3.0 please open a new issue.
Follow #75
I tried this today I get this error:
So no still does not work
Follow #75
We have to wait for an API fix. So follow #75
I dont understand. How can this be an API problem when it has been working in Homeassistant for +1 year now since this problem was first discovered? Homeassistant fixed this issue within a week. Do they use a different API?
If someone wants to create a new module that connects to the API, I would definitely do that. I don't know the technicalities behind the module (API) so have to rely on that module.
I found that module when I was first wanting to connect a lock that I had that wasn't able to connect to HomeKit. So I made this plugin, but I have to rely on that module to be updated to be able too update this plugin.
Still no update on this? Almost 2 years after it broke
Problem
More an awareness thing. As of today, Yale are transitioning away from Yale Access app, to Yale home app. Not sure if this will break homebridge support with this plugin or not.
Solution
Maybe as simple as adding updated links in code to new Yale domains?
Alternatives
To login via web, my app pushes me to https://account.aaecosystem.com/?brand=yale , whereas previously I'd used account.august.com to register the lock and get the verification pin.
Additional context
I have migrated my account to new Yale home, but not yet home to confirm if its broken the plugin. Thanks Donavan.