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
{{ message }}
Repository navigation
HomeKit _hap._tcp advertisement missing with official HAOS add-on
#2148
I'm trying to determine whether I've hit an mDNS/HomeKit issue specific to the official Scrypted Home Assistant OS add-on.
Setup
Home Assistant Yellow
Home Assistant OS
Official Scrypted HA add-on: v0.147.0-noble-full
HomeKit plugin: v1.2.65
Reolink Video Doorbell WiFi
Scrypted Server Address explicitly set to 192.168.1.44
Doorbell in Standalone Accessory Mode
HomeKit Bridge Port: 40625
Flat 192.168.1.0/24 LAN
UniFi network
Apple TV on Ethernet selected as Preferred Home Hub
The Reolink side appears healthy:
Live stream works in Scrypted
Motion events work
Doorbell press events work
Scrypted reports the device online
The HomeKit plugin reports:
[Doorbell] Device is in accessory mode and is online. HomeKit services are being published.
and:
mdns bind address [ '192.168.1.44' ]
What seems unusual
The HAP TCP listener itself is reachable from another machine on the LAN:
nc -vz 192.168.1.44 40625
returns:
Connection to 192.168.1.44 port 40625 [tcp/*] succeeded!
However, on a Mac on the same LAN:
dns-sd -B _hap._tcp local.
shows all of my existing Home Assistant HomeKit bridges/accessories, but never shows the Scrypted Doorbell.
I left dns-sd running during a complete Scrypted add-on restart. The existing HomeKit advertisements remained visible, but no new Scrypted _hap._tcp service appeared.
Apple Home pairing reflects this inconsistency:
Sometimes "Accessory Not Found"
After some Scrypted restarts the accessory is discovered immediately and I get the uncertified accessory warning
It proceeds to "Setting Up"
It then fails with "Unable to Add Accessory" / "Accessory is not reachable"
Troubleshooting already done
Explicitly set Scrypted Server Address to 192.168.1.44
Verified TCP port 40625 is reachable
Verified iPhone can reach 192.168.1.44
Disabled UniFi Multicast Enhancement
Tested Default/Ciao advertiser
Tested bonjour-hap
Reset HomeKit pairing multiple times
Restarted HomeKit plugin
Restarted full Scrypted add-on
Changed preferred Home Hub from HomePod mini to Ethernet Apple TV
Confirmed phone, Scrypted, and Home Hub are on the same subnet
Continuously monitored _hap._tcp during Scrypted restart
Possibly relevant
During Scrypted startup the HAOS container logs:
SCRYPTED_DOCKER_AVAHI != true, won't manage dbus nor avahi-daemon
SCRYPTED_DOCKER_AVAHI != true, not starting dbus-daemon
SCRYPTED_DOCKER_AVAHI != true, not starting avahi-daemon
The add-on is using host networking.
So at the moment the behaviour appears to be:
HAP service listening and reachable → Scrypted says HomeKit service is published → no Scrypted _hap._tcp advertisement observable from another LAN host.
Has anyone seen this with the HAOS add-on?
In particular:
Is the lack of internal Avahi/dbus expected with the HAOS add-on?
Is bonjour-hap or Ciao expected to advertise correctly in this configuration without Avahi?
Is there an HAOS-specific mDNS setting or add-on limitation I'm missing?
Would testing SCRYPTED_DOCKER_AVAHI=true be appropriate/supported on HAOS?
I have a sanitized startup log and dns-sd screenshot available if useful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to determine whether I've hit an mDNS/HomeKit issue specific to the official Scrypted Home Assistant OS add-on.
Setup
v0.147.0-noble-fullv1.2.65192.168.1.4440625192.168.1.0/24LANThe Reolink side appears healthy:
The HomeKit plugin reports:
[Doorbell] Device is in accessory mode and is online. HomeKit services are being published.and:
mdns bind address [ '192.168.1.44' ]What seems unusual
The HAP TCP listener itself is reachable from another machine on the LAN:
nc -vz 192.168.1.44 40625returns:
Connection to 192.168.1.44 port 40625 [tcp/*] succeeded!However, on a Mac on the same LAN:
dns-sd -B _hap._tcp local.shows all of my existing Home Assistant HomeKit bridges/accessories, but never shows the Scrypted Doorbell.
I left
dns-sdrunning during a complete Scrypted add-on restart. The existing HomeKit advertisements remained visible, but no new Scrypted_hap._tcpservice appeared.Apple Home pairing reflects this inconsistency:
Troubleshooting already done
192.168.1.4440625is reachable192.168.1.44bonjour-hap_hap._tcpduring Scrypted restartPossibly relevant
During Scrypted startup the HAOS container logs:
SCRYPTED_DOCKER_AVAHI != true, won't manage dbus nor avahi-daemonSCRYPTED_DOCKER_AVAHI != true, not starting dbus-daemonSCRYPTED_DOCKER_AVAHI != true, not starting avahi-daemonThe add-on is using host networking.
So at the moment the behaviour appears to be:
HAP service listening and reachable → Scrypted says HomeKit service is published → no Scrypted
_hap._tcpadvertisement observable from another LAN host.Has anyone seen this with the HAOS add-on?
In particular:
bonjour-hapor Ciao expected to advertise correctly in this configuration without Avahi?SCRYPTED_DOCKER_AVAHI=truebe appropriate/supported on HAOS?I have a sanitized startup log and
dns-sdscreenshot available if useful.scrypted_homekit_mdns_key_lines.log
All reactions