-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Notion integration needs reauthentication daily #113601
Comments
Hey there @bachya, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) notion documentation |
I've been running 2024.3.1 since it was released and haven't seen this problem reoccur; I'll keep an eye out. In the meantime, if you could provide actual diagnostics and debug level logs, that may reveal something. |
Perhaps its only a problem for me somehow. I've re-authenticated and enabled debug logging (waiting). Attached diagnostics. |
I am having the same issues still on 2024.3.1. Mine seems to be failing reauthentication once every 6 or so hours. It may be a connection issue as others are having reauthentication issues with other integrations? #113481 ? |
No more issues over the past 3 days, I'm guessing whatever was causing the re-auths solved itself. |
I'm having a different problem whereby the integration will not work at all (can't reauthenticate). The error is (email redacted):
|
@Valdorama That code no longer exists in the codebase. What version are you using? |
I'm using 2024.3.1 Edit: just pulled the latest HA image and restarted and still getting that error. |
I see: this was fixed in #112832, which is slated for 2024.3.2. |
Just upgraded to 2024.3.3 now that it's available, and still getting the same error. Anyone else getting it? Does the config need to be redone altogether? i.e. delete existing hub and add it again... |
Getting a similar error on 2024.3.3 Traceback (most recent call last): |
I'm having the same re-auth issues since the update to 2024.3.3. |
Is there a way to get this working temporarily until a fix is available? |
Please update to the 2024.4.0 beta and see if it resolves the issue. |
Thanks, I'm happy to wait till next week for the release since it's fixed, and especially since it's a pretty huge release. |
Updated to 2024.04 and still seem to be getting an error, albeit slightly different:
|
I know this is marked closed but after upgrading to 2024.4.1 it is still not working for me. The error is different though. I have tried deleting the hub altogether and adding it again. There is nothing in the HA logs anymore. I turned on debug logging for the integration and now in the logs I see some messages from aionotion that seem to indicate that it is reading the right data for my account. But at the end of the log it says:
When I hover over the 'Failed setup, will retry' text on the integration page, I see this message popup: |
That error is not something controllable by Home Assistant—a quick search suggests a Redis issue, which may be something in the Notion API itself. |
In case it's useful for anyone else, at some point over the weekend the status changed from 'Failed setup, will retry' to 'Authentication expired'. After re-entering my Notion password, it started working again and seems to be fine now. |
The problem
Notion integration needs reauthentication daily. Previously, with core-2024.3.0, the integration was broken and would not authenticate but after installing 2024.3.1 authentication worked, but periodically needs re-authentication (so far less than 1 day).
What version of Home Assistant Core has the issue?
core-2024.3.1
What was the last working version of Home Assistant Core?
core-2024.2.5
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Notion
Link to integration documentation on our website
https://www.home-assistant.io/integrations/notion
Diagnostics information
Found an error from the authentication dialogue:
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: