-
Notifications
You must be signed in to change notification settings - Fork 57
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
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble #262
Comments
I've worked around it by editing |
Ok, can you post how your edits looked like so I can copy it? :) |
You just need to update the
|
After newest update v0.2.3, I have problem with weconnect package version.:
|
@prezervos works for me 🤷 and weconnect 0.60.3 is definitely published on pypi – there might be something about your particular setup that's preventing it being found (network problem, other add-ons with clashing dependencies). I didn't realise there was a new version - 0.2.3 just showed up in HACS for me just now (I was on 0.2.0) and the update worked fine. |
@dewet22 Thank you for info. I will edit the version in manifest to 0.60.2, this is installed currently . |
Awesome, thx for the help everyone and for a great addon! |
same here. had to downgrade to 0.60.2 |
Version 0.2.3 was made because of conflicts betweeen version 0.2.2 and home Assistant Core version 2024.6.x - Have you upgraded your home assistant core to version 2024.6.x - if not, that could be the reason |
Yes I am still on 2024.5.x. I'll try to upgrade. EDIT: yes, 2024.6.x fixed the issue. Thanks! |
I can also confirm that upgrading to 2024.6.x fixed the issue. |
Version of the custom_component
Installation method (hacs / manual)
hacs
Installation method of hass (venv, docker, hassio,...)
Configuration
HACS
The text was updated successfully, but these errors were encountered: