[Help]: Struggling with HomeKit and mDNS

[Prodeguerriero]

Controller Version

6.1.0.19

Describe Your Issue or Question

I am struggling with getting Home Assistant to detect a HomeKit device in my network.
Details regarding the setup and topology are already on Reddit.

Before I dig any deeper, I wonder if there's anyone who is using the controller via Docker who has successfully gotten HomeKit to work.

Expected Behavior

I'd expect HomeKit devices to work across the network once mDNS is enabled.

Steps to Reproduce

See https://www.reddit.com/r/TPLink_Omada/comments/1r41fhs/comment/o5njbf6/?context=1

How You're Launching the Container

services:
  omada-controller:
    container_name: omada-controller-v6
    image: mbentley/omada-controller:6.1
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - UPGRADE_HTTPS_PORT=8043
      - PORT_APP_DISCOVERY=27001
      - PORT_DISCOVERY=29810
      - PORT_MANAGER_V1=29811
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V2=29814
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - PORT_DEVICE_MONITOR=29817
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Etc/UTCervices
    volumes:
      - type: bind
        source: /DATA/AppData/omada-controller-v6/data
        target: /opt/tplink/EAPController/data
      - type: bind
        source: /DATA/AppData/omada-controller-v6/logs
        target: /opt/tplink/EAPController/logs
      - type: bind
        source: /mnt/nas/backup/omada-controller-v6
        target: /opt/tplink/EAPController/data/autobackup

Container Logs

See attacched.

MongoDB Logs

No response

Additional Context

logs.txt

[GoodOmens83]

You'll need to creare custom mDNS entries as the default don't cover HomeKit. Use the discover app to see which devices are using what mDNS calls. Attached is a list of ones I've added - HAP is the most important.

[Prodeguerriero]

Apologies for the delayed reply. What's the "discover app" you mention?

[mbentley]

https://support.omadanetworks.com/us/download/software/omada-discovery-utility/

[GoodOmens83]

https://apps.apple.com/us/app/discovery-dns-sd-browser/id305441017

Run it on your phone while connected to a wifi network and it will show you all the mDNS protocols being broadcasted on the network.

[Prodeguerriero]

Hi both,

Apologies for disappearing. I kind of gave up on the whole matter for a while. But I found some time to look into it this weekend.

Some remarks:

• I don't have an iPhone, so the iOS app is not an option for me. I tried to look for an alternative on Android, with mixed results.
• I also tried the official Omada Discover Utility on three different machines and two different OSes. Same result: no device shows up
• I then tried to use avahi on Ubuntu, and I finally got some results back, which make me think mDNS is working as intended
• Sadly, the one device that I need to connect via HomeKit is not showing up (a Tado Bridge for my thermostat)

As I suspect this has something to do with a combination of my setup and the Tado Bridge, I think we can close this conversation. But I appreciate the help. Unless either of you happens to have a Tado thermostat at home, of course. :P