-
Notifications
You must be signed in to change notification settings - Fork 62
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
zeroconf error #383
Comments
I'm having a similar issue but i am running it locally and have a xfce4-panel running a script Edit: I found the solution for my problem. all i needed to do is define HASS_SERVER and HASS_TOKEN Individually in each script. |
At first glance I would say, that there is a possible mixup of the URLs. As MDNS is used to get the details, something like the command below could give you some insight about what is published by your Home Assistant instance: $ avahi-browse -art
= wlp2s1 IPv4 Home _home-assistant._tcp local
hostname = [38e..70.local]
address = [fe80::fabc:722d:74f:1b5e]
port = [8123]
txt = ["requires_api_password=True" "base_url=http://192.168.1.20:8123" "internal_url=http://192.168.1.20:8123" "external_url=" "version=2022.9.7" "uuid=38e...0" "location_name=Home"]
[...] |
Hi, currently not able to get this working. I had to downgrade click as well, after that I still get this error:
I have updated HA to latest version.
I'm not sure why cli is trying to use my nabucasa url. Is that the setup? the cert on my HA are self signed, but I can get further with --insecure switch
Kind Regards,
EDIT: After reading a bit further, I noticed I had zeroconf disabled in configuration.yaml, but even after re-enable + reboot no avail..
The text was updated successfully, but these errors were encountered: