-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
New discovered device: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble #652
Comments
same by me |
yes i have this too ... |
Seems to be related to this error message for me:
|
same as: #655 |
SAme issue |
Fixed by #658 for me |
Fixed in release 0.3.4 |
i updated to 0.3.5 this morning, rebooted but get the same error. I have
not tried removing and install it fresh
…On Thu, Mar 3, 2022 at 6:02 PM Håkan Åkerberg ***@***.***> wrote:
Fixed in release 0.3.4
—
Reply to this email directly, view it on GitHub
<#652 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABITWQ5QEQJDW36MR7USIG3U6DWB3ANCNFSM5OXWHU3A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am new to ShellyForHASS and thus tried to install it the first time on Home Assistant 2022.3.5. ShellyForHASS v0.3.5 via HACS. Error Log:
|
Have you restarted HA after installation of ShellyForHass? |
Yes i did a restart of HA as suggested by HACS. I did a another search regarding the stack trace and found the similar issues #496 and #562. Manually adding a new instance of the integration works as suggested in #496 (comment) |
New device (my only shelly) was auto discovered, clicking Configure gives this error:
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble
HAOS 7.4
Core 2022.2.8
The text was updated successfully, but these errors were encountered: