TTLock now "failed to set up," since HA 2023.9

jbergler / hass-ttlock

Home Assistant integration for TTLock locks

69 stars 13 forks source link

TTLock now "failed to set up," since HA 2023.9 #69

Closed FaberO42 closed 1 year ago

FaberO42 commented 1 year ago

Firstly, major kudos for your most valued work on this plugin!!!

However sadly for me, TTLock now shows as "failed to set up," since HA 2023.9.

Repeated attempts to reload integration and/or restart Home Assistant, now consistently results in same error.

NOT a new installation - everything was clearly configured correctly, since working 100% okay for months, prior to this.

TTLock home-assistant_ttlock_2023-09-09T02-09-17.371Z.log

acenuke commented 1 year ago

Exact same issue with HA 2023.9.0 and 2023.9.1

FaberO42 commented 1 year ago

Concur. 😔

jbergler commented 1 year ago

Thanks for the report, I don't think this is related to the latest release, at least I can't reproduce this locally. My suspicious is that theres an issue renewing the auth token. Could you try removing / re-adding the integration to force a new session? If that fixes it I can take another look at the error handling here.

nedzalife commented 1 year ago

Adding context that might be related?

Brand new HA OS + HACS install
Newly approved, never used TTLocks OAuth creds
Plugin asks for Client ID / Secret
Plugin asks for TTLock account username & password
Login failed error (have confirmed the login creds work to access OAuth info).

Perhaps TTLocks changed something in their CDN / Netscaler / DNS that's causing the settings within this plugin to no longer work?

Edit: ignore all of the above. My issues were completely PEBKAC. Thanks for the great add-on!

acenuke commented 1 year ago

I deleted the integration then added it back and it worked again. Not sure why that happened

FaberO42 commented 1 year ago

Thanks for the report, I don't think this is related to the latest release, at least I can't reproduce this locally. My suspicious is that theres an issue renewing the auth token. Could you try removing / re-adding the integration to force a new session? If that fixes it I can take another look at the error handling here.

Hi sir, I can confirm that Deleting and (Re-)Adding the Integration does successfully resolve for me.

jbergler commented 1 year ago

I had tried in a previous release to add some automated credential expiration handling (since the sessions are only valid for a few months). If this happens again please let me know and I can take another look. In the meantime I'll mark this as closed.

Thanks for the reports!