Skip to content

Qnap error after upgrade #38940

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

Closed
biroby opened this issue May 8, 2025 · 2 comments
Closed

Qnap error after upgrade #38940

biroby opened this issue May 8, 2025 · 2 comments

Comments

@biroby
Copy link

biroby commented May 8, 2025

Feedback

Hi all,
after upgrade to HA 2025.5 I have this error:

Failed setup, will retry: 'NoneType' object does not support the context manager protocol

User that I use to connect with HA logon to NAS.
Can you help me?

URL

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

Version

2025.5.0

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented May 8, 2025

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

Code owner commands

Code owners of qnap can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign qnap Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@frenck
Copy link
Member

frenck commented May 8, 2025

Oh hi there @biroby 👋

Thank you for reaching out. We use GitHub for documentation feedback, not for providing support.

If you are in need of support, you should try our Community Forum or join our Discord chat server.

You are more likely to get the answer you are looking for in those places.

Thanks! 👍

../Frenck

@frenck frenck closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants