UniFi: configured UDM Pro Max still offered as a new discovery after #180343 (announced_ips is empty) #185529

The problem

After #180343 (released in 2026.10.0), the UniFi discovery prompt for a console that is already configured still comes back, because announced_ips is empty for my UDM Pro Max and the fix has nothing to match against.

Setup: UDM Pro Max with several VLAN interfaces, one UniFi Network entry created by hand (source: user, host 192.168.0.1). Home Assistant sits on another VLAN, so the scan hears the console at 192.168.80.1. This is the case from #177083, where I commented that I would verify after release.

What happened: on 2026.9.x the discovery flow stood for weeks. Home Assistant is now on 2026.10.0 (Core restarted on 2026-10-09), so the flow was recreated by the new code and is still listed (config_entries/flow/progress: unifi, integration_discovery, host 192.168.80.1). The MAC-first abort did not fire either, so the entry is not keyed by the console's MAC (an entry created through the user flow is not).

What I measured: with homeassistant.components.unifi_discovery.discovery at debug, four consecutive hourly scans logged the same record for the console. ip_info, primary_addr and addr_entry are all None, and echoed is True. The record's remaining data (platform, services, direct-connect domain) looks like it came from the console's HTTP probe. So _announced_ips() returns [], known_hosts is only {source_ip, direct_connect_domain}, and the entry's host 192.168.0.1 matches neither.

Caveat: I only know what Home Assistant receives. I have not captured the wire, so I cannot say whether this console sent no address list or whether it did not reach the VLAN Home Assistant is on.

What I expected: no discovery flow for a console that already has a configured entry.

Suggestion, not a request for a specific design: the device registry already knows this console's MAC for the configured entry. The gateway device the UniFi entry registered carries a mac connection equal to the discovered hw_addr. Comparing hw_addr with the MAC connections of devices that belong to existing unifi entries would work without ip_info. It relates to uilibs/unifi-discovery#158, which proposes exposing the announced addresses; that cannot help when none arrive.

Workaround in use: ignoring the discovery (config_entries/ignore_flow).

What version of Home Assistant Core has the issue?

core-2026.10.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

UniFi Network

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

[homeassistant.components.unifi_discovery.discovery] Found devices: [UnifiDevice(source_ip='192.168.80.1', hw_addr='<console MAC>', ip_info=None, addr_entry=None, fw_version=None, mac_address=None, ..., platform='UDMPROMAX', model=None, ..., signature_version=None, services=mappingproxy({<UnifiService.Protect: 1>: True, <UnifiService.Network: 2>: True, <UnifiService.Access: 3>: False}), direct_connect_domain='<redacted>', device_id='<redacted>', guid='<redacted>', primary_addr=None, is_managed=None, ..., product_name=None, version=None, echoed=True)]

Fields shown as ... and identifiers shown in angle brackets were removed by me; the other values are as logged.

Additional information

UniFi Network application 10.6.106 as of 2026-09-27, UDM Pro Max. Related: #177083, #180343, uilibs/unifi-discovery#158.