cloudbr34k84 commented 3 weeks ago

The integration is currently blocked, and a new integration is being developed, please see

https://github.com/home-assistant/core/issues/124460#issuecomment-2306757991

The problem

As of today, im unable to authentic my using the August integration and choosing Yale Home. I have reset my password on the yale home app to make sure and logged in via the email and mobile phone so i know that works.

I have Yale Unity Entrance Door lock

I have now since deleted the August integration App thinking i do that then restart. That has not worked. I cant see any other issues yet on this

What version of Home Assistant Core has the issue?

2024.8.2

What was the last working version of Home Assistant Core?

2024.8.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

August

Link to integration documentation on our website

https://www.home-assistant.io/integrations/august

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 3 weeks ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (august) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `august` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign august` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

august documentation august source _{^{(message by IssueLinks)}}

cloudbr34k84 commented 3 weeks ago

I just restored a back up to 8 hours agao and the issue is still there. Config entry 'bradapplegate38@gmail.com' for august integration could not authenticate

phillclaxton commented 3 weeks ago

Looks like calls to https://api.aaecosystem.com/session are being blocked for me with the HTML coming back stating

Sorry, you have been blocked

Why have I been blocked?
This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

What can I do to resolve this?
You can email the site owner to let them know you were blocked. Please include what you were doing when this page. came up and the Cloudflare Ray ID found at the bottom of this page.

fishy242 commented 3 weeks ago

same issue here

Doc-C commented 3 weeks ago

Im also having the same issue. The inegration has been very on and of the last week. Now its straight up not working at all.

cloudbr34k84 commented 3 weeks ago

Sigh let's hope they are not blocking

rottweilerken commented 3 weeks ago

same issue here, after the non-refreshing issue, which is going on for a long time, having to restart the integration a few times per day, now it's completely useless with this issue. I sincerely hope the Yale Home integration gets reprogrammed or picked up by somebody with some time to make it smooth again.. fingers crossed

cloudbr34k84 commented 3 weeks ago

same issue here, after the non-refreshing issue, which is going on for a long time, having to restart the integration a few times per day, now it's completely useless with this issue. I sincerely hope the Yale Home integration gets reprogrammed or picked up by somebody with some time to make it smooth again.. fingers crossed

I haven't noticed issues.. I thought maybe the state of the door lock wasn't updating in HA, but I never paid to much attention as ppl are always coming going

fakethinkpad85 commented 3 weeks ago

Started having issues today after an update as well, looking at a Automation trace i get this,

rottweilerken commented 3 weeks ago

I haven't noticed issues.. I thought maybe the state of the door lock wasn't updating in HA, but I never paid to much attention as ppl are always coming going

It's about this one: https://github.com/home-assistant/core/issues/118474 Perhaps like you said if there is a lot of activity, that issue is not happening, good thing for you 👍 PS: I'm using the Yale Linus L2 with wifi, aside of the integration, it's working good through the app..

cloudbr34k84 commented 3 weeks ago

I have Yale unity door lock Yeah app is fine

sammyh2506 commented 3 weeks ago

Same issues as everyone else, no longer able to authenticate.

tumppi-git commented 3 weeks ago

Having the same issue, running core 2024.8.2.

Opontios commented 3 weeks ago

Same issue.

ivrlx commented 3 weeks ago

Same here, it must be a problem with the august API acording with the logs...we'll see...

OneScuzzie2k commented 3 weeks ago

Following, Same issue

PerSterin commented 3 weeks ago

Same issue. Yale Access Bluetooth: Still working. August: Needs attention, Reauthenticate an August account

Yale

Full debug log: 2024-08-23 09:23:08.743 WARNING (MainThread) [homeassistant.config_entries] Config entry 'xxx.xxx@xxx.xx' for august integration could not authenticate 2024-08-23 09:33:44.978 DEBUG (MainThread) [yalexs.authenticator_async] Cache file not found: /config/.xxx.xxx@xxx.xx.august.conf 2024-08-23 09:33:44.980 DEBUG (MainThread) [yalexs.api_async] About to call https://api.aaecosystem.com/session with header={'Accept-Version': '0.0.1', 'x-august-api-key': 'd9984f29-07a6-816e-e1c9-44ec9d1be431', 'Content-Type': 'application/json; charset=UTF-8', 'User-Agent': 'August/Luna-22.17.0 (Android; SDK 31; gphone64_arm64)', 'x-august-country': 'US', 'x-august-branding': 'yale'} and payload={'installId': '8e147b2f-1270-4546-a3f4-8f27c47b5288', 'identifier': 'email:xxx.xxx@xxx.xx', 'password': '****'} 2024-08-23 09:33:45.066 DEBUG (MainThread) [yalexs.api_async] Received API response from url: https://api.aaecosystem.com/session, code: 403, headers: <CIMultiDictProxy('Date': 'Fri, 23 Aug 2024 07:33:45 GMT', 'Content-Type': 'text/html; charset=UTF-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'X-Frame-Options': 'SAMEORIGIN', 'Referrer-Policy': 'same-origin', 'Cache-Control': 'max-age=15', 'Expires': 'Fri, 23 Aug 2024 07:34:00 GMT', 'Vary': 'Accept-Encoding', 'Server': 'cloudflare', 'CF-RAY': '8b796a8c9bd70a31-ARN', 'Content-Encoding': 'gzip')>, content: b'<!DOCTYPE html>\n\n\n\n \n\nAttention Required! | Cloudflare\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

\n \n

\n

Sorry, you have been blocked

\n

You are unable to access aaecosystem.com

\n

\n\n

\n

\n \n \n \n

\n

\n\n

\n

Why have I been blocked?

\n\n

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

\n

\n\n

\n

What can I do to resolve this?

\n\n

You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.

\n

\n\n

\n

\n Cloudflare Ray ID: 8b796a8c9bd70a31\n •\n \n Your IP:\n \n xxx.xxx.xxx.xxx\n •\n \n Performance & security by Cloudflare\n \n

\n \n

\n\n\n

\n

\n\n \n\n\n\n'

cwquek commented 3 weeks ago

Happen this morning, same issues as everyone else. Have not done any update.

DavidRCT commented 3 weeks ago

Same issue.

I have a HomeKit hub so using the HomeKit integration and input to do the switching. Unfortunately I can't rely on the August integration any more.

MMouse23 commented 3 weeks ago

Same here. Looks like a CloudFlare issue if i read the dumps here. Yale app works fine, HA does not authenticate anymore

MMouse23 commented 3 weeks ago

d9984f29-07a6-816e-e1c9-44ec9d1be431

You may want to remove your api key, not sure if its working or even a useable key, just saying.

cloudbr34k84 commented 3 weeks ago

How do you get the Yale Bluetooth integration to work. I got it working once without doing anything but never again?

I have Bluetooth proxies near by as well

On Fri, 23 Aug 2024, 6:03 pm Per Sterin, @.***> wrote:

Same issue. Yale Access Bluetooth: Still working. August: Needs attention, Reauthenticate an August account

Yale.jpg (view on web) https://github.com/user-attachments/assets/574f4a43-094b-466f-8322-e66581a93e28

Full debug log: 2024-08-23 09:23:08.743 WARNING (MainThread) [homeassistant.config_entries] Config entry @.' for august integration could not authenticate 2024-08-23 09:33:44.978 DEBUG (MainThread) [yalexs.authenticator_async] Cache file not found: @. 2024-08-23 09:33:44.980 DEBUG (MainThread) [yalexs.api_async] About to call https://api.aaecosystem.com/session with header={'Accept-Version': '0.0.1', 'x-august-api-key': 'd9984f29-07a6-816e-e1c9-44ec9d1be431', 'Content-Type': 'application/json; charset=UTF-8', 'User-Agent': 'August/Luna-22.17.0 (Android; SDK 31; gphone64_arm64)', 'x-august-country': 'US', 'x-august-branding': 'yale'} and payload={'installId': '8e147b2f-1270-4546-a3f4-8f27c47b5288', 'identifier': @.*', 'password': '**'} 2024-08-23 09:33:45.066 DEBUG (MainThread) [yalexs.api_async] Received API response from url: https://api.aaecosystem.com/session, code: 403, headers: <CIMultiDictProxy('Date': 'Fri, 23 Aug 2024 07:33:45 GMT', 'Content-Type': 'text/html; charset=UTF-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'X-Frame-Options': 'SAMEORIGIN', 'Referrer-Policy': 'same-origin', 'Cache-Control': 'max-age=15', 'Expires': 'Fri, 23 Aug 2024 07:34:00 GMT', 'Vary': 'Accept-Encoding', 'Server': 'cloudflare', 'CF-RAY': '8b796a8c9bd70a31-ARN', 'Content-Encoding': 'gzip')>, content: b'\n\n\n\n \n\nAttention Required! | Cloudflare\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n Please enable cookies. \n \n \n Sorry, you have been blocked\n You are unable to access aaecosystem.com\n

\n\n \n \n \n \n \n \n \n \n \n\n \n \n \n Why have I been blocked?\n\n

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data. \n \n\n \n What can I do to resolve this?\n\n

You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page. \n \n \n \n\n \n

\n Cloudflare Ray ID: 8b796a8c9bd70a31\n •\n \n Your IP:\n Click to reveal\n 178.78.251.242\n •\n \n Performance & security by Cloudflare https://www.cloudflare.com/5xx-error-landing\n \n \n \n \n\n\n \n \n\n \n\n\n\n'

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/124460#issuecomment-2306523650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOB2WBCK2FA2FC6NY6XPKYLZS3UEPAVCNFSM6AAAAABM7KUOTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBWGUZDGNRVGA . You are receiving this because you authored the thread.Message ID: @.***>

ericfhuber commented 3 weeks ago

I sent August an email earlier after seeing this GitHub issue, here’s their response (translated from German):

Hello Eric,

Thank you for contacting Yale Customer Service.

Our server team has temporarily blocked Home Assist integration with Yale Home.

Please note that Home Assistant is not currently an official partner, but we are working with them on an improved integration that is expected to be published in Q4.

We apologize for this and wish you a nice day.

Best regards

Carmen

Yale DACH Team

cloudbr34k84 commented 3 weeks ago

Well that's good news I wonder if anyone from home assistant can corroborate this?

mlauhalu commented 3 weeks ago

Contacted Yale customer service and this was the response (translated from Finnish):

Hello,

officially August is not a Yale integration partner, and there is no information that support is forthcoming. However, we are aware that informal support through Home Assistant is possible. But unfortunately we are unable to provide any support for this as it is not officially a partner.

Home Assistant's connection to Yale Home is currently down due to a backend server outage. As a result, Home Assistant may not be working properly with Yale Home right now. Home Assistant is aware of the issue, but unfortunately we are unable to provide any estimate of how long the outage will last.

The connection between Home Assistant and Yale Home should then return once the problem with the backend servers has been resolved.

Translated with DeepL.com (free version)

f13end commented 3 weeks ago

Yale app works fine, HA does not authenticate anymore

cloudbr34k84 commented 3 weeks ago

Question, if we are using Yale Home, but its via the August integration are we still screwed?

moritzmaier84 commented 3 weeks ago

same and following. frustrating, though. we should all spam the yale support for unblocking as long as the new version is not finished ;)

robferre commented 3 weeks ago

At least it's not a "not supported at all" and never will be. "Working with HA team", "outage", "server back up will work" is good news I guess

bdraco commented 3 weeks ago

Yale had to block the key we are using because the traffic was resulting in a denial of service attack on their servers: https://github.com/home-assistant/core/issues/103052#issuecomment-2285973777

You can track the status of the new integration here: https://github.com/home-assistant/home-assistant.io/pull/33890

home-assistant[bot] commented 3 weeks ago

yale_home documentation yale_home source

home-assistant[bot] commented 3 weeks ago

yale documentation yale source

cloudbr34k84 commented 3 weeks ago

Yale had to block the key we are using because the traffic was resulting in a denial of service attack on their servers.

#103052 (comment)

You can track the status of the new integration here:

home-assistant/home-assistant.io#33890

Thanks for the update and the effort required!

vvode commented 3 weeks ago

Yale works with SmartThings so I switched to use that integration until new yale integration is completed.

moritzmaier84 commented 3 weeks ago

Yale works with SmartThings so I switched to use that integration until new yale integration is completed.

Can you give us a quick step-by-step what ecactly you did to switch on that?

bdraco commented 3 weeks ago

Yale works with SmartThings so I switched to use that integration until new yale integration is completed.

Can you give us a quick step-by-step what ecactly you did to switch on that? Yale had to block the key we are using because the traffic was resulting in a denial of service attack on their servers: https://github.com/home-assistant/core/issues/103052#issuecomment-2285973777

Would you please take this discussion to a forum thread so we can keep this issue clean and anyone looking for why it's not working won't have to scroll through pages of workarounds/alternate solutions?

https://community.home-assistant.io/t/psa-yale-home-integration-blocked-new-integration-coming/762999

You can track the status of the new integration here: https://github.com/home-assistant/home-assistant.io/pull/33890

I'll provide updates in this issue as new integration progresses.

maniolox commented 3 weeks ago

Yale współpracuje ze SmartThings, więc przełączyłem się na korzystanie z tej integracji do czasu zakończenia nowej integracji Yale.

But unfortunately we don't have a preview is the keypad battery

bdraco commented 2 weeks ago

We worked very hard this weekend to get a temporary solution in 2024.8.3 that will allow the old integration to keep working for a limited time while we work on the new one.

If you have an automation to frequently reload or wake up the locks, please remove them, as the limited time will quickly become very short if Home Assistant users continue to overload the API.

If your account is blocked explicitly because of abusing the API, 2024.8.3 will not restore access.

Everyone using the Yale Home brand will need to switch to the new yale integration as soon as it is available.

Please continue discussion at https://community.home-assistant.io/t/psa-yale-home-integration-blocked-new-integration-coming/762999

bdraco commented 2 weeks ago

The new integration is available in beta: 2024.9.0b0. The new integration uses the new WebSocket APIs which provide updates continuously so there is no need to reload or wake the locks anymore.

For Yale Home users, to migrate, add the new yale integration, and remove the old august integration.

For August/Yale Access users, continue to use the august integration.

Please report any issues with the new integration using the normal beta channels for the next week. https://www.home-assistant.io/faq/release/. After it makes it to release, please report any issues to GitHub issues.

home-assistant / core

Unable to Authenticate Yale Home using August Integration #124460

The integration is currently blocked, and a new integration is being developed, please see

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

Sorry, you have been blocked

You are unable to access aaecosystem.com

Why have I been blocked?

What can I do to resolve this?