Skip to content

Fetching external URL unexpectedly raises NoURLAvailableError when cloud is not yet setup #100728

Open
@Nardol

Description

@Nardol

The problem

I use Home Assistant cloud for external access to my Home Assistant instance.
When checking the MDNS service _home-assistant._tcp we should find the internal URL, base URL and external URL.
But when using I.E. avahi-browse to check, I have both internal and base URL set to my HA IP which is expected, but I have no value for external_url.

What version of Home Assistant Core has the issue?

2023.9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Zeroconf

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zeroconf

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

$ avahi-browse -rtl _home-assistant._tcp
+ enp3s0 IPv4 Maison                                        _home-assistant._tcp local
= enp3s0 IPv4 Maison                                        _home-assistant._tcp local
   hostname = [xxx.local]
   address = [IP4_addr]
   port = [8123]
   txt = ["requires_api_password=True" "base_url=http://<ipv4>:8123" "internal_url=http://<ipv4>:8123" "external_url=" "version=2023.9.2" "uuid=xxx" "location_name=Maison"]

Additional information

It has already worked before but I prefer not to say when because I am not sure, a long time ago.
Maybe Zeroconf advertise before Home Assistant Cloud finished to initialize so unable to get the remote URL?

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions