Feilmelding når Add Integration - Config flow could not be loaded #12
Comments
lunsj
changed the title
|
Hi! The last warning is a generic (and recommended) warning to issue when custom stuff is loaded through HACS or other non-official locations, so no worries there. About the 500 internal server error, it may sound like it was just a temporary server error at the API side just when you tried to add the integration? I am not sure, but I just tested adding on my test setup right now and it works fine. Perhaps you could try again a couple of times at different time of day to confirm? If it is still a problem, it could be something else. Which hardware platform are you running HA on? (RPi, NUC etc). |
|
Hi, great that you responded so quickly! :)
The warning from the log was only included to show that the installation
step was completed, and the log entry was as expected.
I’m using Home Assistant Yellow with an RPi CM4 -
https://www.home-assistant.io/yellow/.
I’ve tried installing both manually and via HACS, but I keep getting the
same error. I’ve tried several times yesterday (and today), but the issue
persists. It would be really nice to get the tide tables/graphs working on
the dashboard.
Br
Magnus
|
|
Thanks for your feedback. It may be related to #8 where RPi seems to fail on installation of a library Matplotlib that is used. It is something I should try to look into. Perhaps you could see in detailed logs if you see anything similar or related to Matplotlib? |
Prøver "add integration" - > Norwegian Tide men får feilmelding:
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble
Error
Brukte HACS for å legge til Integrasjon og har restartet Hassio.
Kjører Core 2024.10.2
I loggen står det som forventet:
2024-10-15 11:39:45.354 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration norwegiantide which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
The text was updated successfully, but these errors were encountered: