-
-
Notifications
You must be signed in to change notification settings - Fork 28.7k
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
HVV departures integration fails to load config-flow #98362
Comments
Hey there @vigonotion, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) hvv_departures documentation |
I am facing the same error. |
Hi, Home Assistant 2023.10.0 Thanks |
+1, same setup. |
The problem
Hi,
I've encountered a possible issue with the configuration of the "HVV Departures"-integration.
Adding an entry for the integration succeeds without any issues, and the integration itself also works fine.
However, trying to open the "Configure"-dialog for an added entry results in an error message ("Config flow could not be loaded: 400: Bad request"):
I have an entry that was added a really long time ago, and for this entry the configuration flow still loads successfully, so this issue just seems to occur with entries that were recently added.
Neither the browser console, nor the Home Assistant log in debug mode show any issues, apart from the failed request. The issue was reproducible for me in a fresh installation of Home Assistant.
What version of Home Assistant Core has the issue?
core-2023.8.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
HVV Departures
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hvv_departures
Diagnostics information
No response
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: