v0.1.3

Homelable for Home Assistant — v0.1.3

A debug release on the road to nailing down a streaming-scan bug. Two real fixes plus diagnostic logs.

🐛 Fixes

• Stop creating a second Zeroconf instance. HA was logging a frame warning on every scan: "Detected that custom integration 'homelable' attempted to create another Zeroconf instance". The mDNS sweep now uses HA's shared async_get_async_instance(hass) and only falls back to a private AsyncZeroconf when running outside HA (tests / standalone smoke). Side benefit: no more contention on UDP 5353 with HA's own discovery flow.

🔬 Diagnostic logging

If your scans complete with placeholders but no service badges (a bug some users hit on HA OS), this build adds five [trace] log lines that pinpoint where the data drops:

Checkpoint	What it reports
tcp_connect_scan	per-IP open ports found by the pure-Python TCP path
nmap_scan_single	per-IP open ports found by the nmap path
emit_phase2	open ports + services count just before broadcasting device_enriched
handle_scan_event	services count + status the coordinator actually stored
scan_done	final totals: devices returned, pending in store, services total, discovering dropped

Trigger one scan after upgrading and grep [trace] in your home-assistant.log. We'll strip the lines once the root cause is fixed.

Install / upgrade

HACS → Homelable → Redownload → pick 0.1.3 → restart Home Assistant.

If you're seeing the no-services issue: run a scan, open an issue with the [trace] lines, we'll have the answer in one round-trip.