You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ve experienced an issue when configuring it for the first time, that is related to the way the ovh api is requested.
I finally figured out this is not a bug in the code but a side effect.
My dynhost entry had been set up using OVH manager, and i've added the ovh related data in HA configuration.yaml.
When restarting, HA was keeping complaining about a connection error raised by line 66 of __init.py__.
I finally figured out that the problem was coming from a '#' character in my dynhost username entry password, and that the presence of this character was breaking the url built with the pattern found in line 83 of the same script url = f"https://{user}:{password}@{HOST}?system=dyndns&hostname={domain}"
Maybe it should be useful to add a note in the documentation to warn about special characters usage in passwords.
My 2 cents.
The text was updated successfully, but these errors were encountered:
Hi,
First of all, thx for this helpful integration.
I ve experienced an issue when configuring it for the first time, that is related to the way the ovh api is requested.
I finally figured out this is not a bug in the code but a side effect.
My dynhost entry had been set up using OVH manager, and i've added the
ovh
related data in HA configuration.yaml.When restarting, HA was keeping complaining about a connection error raised by line 66 of
__init.py__
.I finally figured out that the problem was coming from a '#' character in my dynhost username entry password, and that the presence of this character was breaking the url built with the pattern found in line 83 of the same script
url = f"https://{user}:{password}@{HOST}?system=dyndns&hostname={domain}"
Maybe it should be useful to add a note in the documentation to warn about special characters usage in passwords.
My 2 cents.
The text was updated successfully, but these errors were encountered: