HomeKit Bridge integration unsuccessful - HA Container on Synology NAS

Configuration
, ,
1

Hi all,

I’m attempting to set up the Apple HomeKit Bridge integration on Home Assistant, but when I scan the generated QR code in the iOS Home app, it is unsuccessful. I scan the code, but it times out after a few minutes of searching.

I’m running Home Assistant via Container Manager on my Synology DS220+ NAS. It’s running DSM Operating system, version 7.2-64570.

Home Assistant is running on HTTPS, port forwarded on the router for port 8125.
The port setting is added in the container, 8123:8123.
The container is running on a “bridge” network of 172.17.0.2.

I’m able to add the HomeKit Bridge integration and a QR code is generated in the Notifications as expected, but adding the accessory times out after a few minutes after scanning.

I suspect something has to be configured in the networking of either the Docker container or the HA config yaml, but I’m not sure what.

Here is my configuration.yaml file:

# Loads default set of integrations. Do not remove.
default_config:

# http config
http:
    use_x_forwarded_for: true
    trusted_proxies: 172.17.0.1

# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

homekit:
   # advertise_ip: 172.17.0.2
            
sensor:
  # ...

Things I’ve tried:

  • Changing the value of the advertise_ip in the homekit config. I’m not sure what this value should be? I’ve tried the IP address of the Synology NAS (192.168.0.x), but no luck.
  • Removing the homekit config from the configuration.yaml and adding the integration through the frontend, but no luck
  • Creating a new container and running it on “host” network, but Home Assistant frontend never loads (I’m not sure if the http config setting causes this?)

Does anyone have any helpful tips? I’m new when it comes to this type of networking.

2

I was able to solve my issue:

  • In Synology Container Manager, created a new container with “home” network (saw the comment here)
  • In configuration.yaml, changed trusted_proxies to 127.0.0.1
  • Did not add any advertise_ip

QR code was able to be scanned successfully after that.

1 Like