-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Could not connect error #53
Comments
Keep in mind Flow Launcher only saves settings once the settings window is closed. Please try entering your settings, closing the settings window and try to activate the plugin once more. |
Good to know. |
Please post your Be sure to replace any sensitive info such as your server URL or API key before posting. |
Hello, I also have this issue. The URL used in the settings works fine, the token was reissued and updated. There is a log in HA about the attempted login: This issue started happening after updating HA Core (currently using version 2023.5.2) |
I think your settings are not being saved correctly and the plugin is using old/incorrect settings. Until I can issue a fix you can manual update these settings |
Right you are @Garulf, manually setting the data in the plugin Settings.json file works. Thank you! |
Even after changing the settings in the json file it doesn't work for me. The log just gives this (some personal info removed):
|
Hi @Garulf , any idea what could be causing the issue? |
I have the same 'Could not connect' error.
earlier I had to manually edit the settings in the json file, and it worked for a couple of days. not sure how that got over written again. EDIT: manually editing the file again seems to retain the values and ha is working. the only concern is it may get overwritten again |
I'm getting this error both if trying the https with fully qualified domain name or http with IP:port.
Getting the error clears my settings.
The text was updated successfully, but these errors were encountered: