Cannot Detect HueDIY Bridge on Synology NAS Docker Image

[Araforn]

Hi All,

I have setup diyhue in Docker running on my Synology Disk Station (DS218+).

My container network setup is bridge and I can access the Hue link Button Web Page through its port.

This is where i'm confused. Since Docker does not assign a new IP address to my diyhue container then the app is never going to see it. Am I missing something because the docker container is not setup to be accessible from my local network and therefore the Hue app cant see it.

My Synology NAS (Docker Host) is on 192.168.1.60
I can access my diyhue web page in my web browser on 192.168.1.60:32778 (This is port 80 in the hue diy container).
In the Hue App when searching for the diyhue bridge entering the Docker host IP address: 192.168.1.60 does nothing.

Note I have also tried to set this up using the host network in docker but I cant even access the diyhue webpage.
Can anyone clear this up for me?.

Thanks in advance.

[mariusmotea]

the bridge must be available on ports 80 and 443 and i think this is a blocker issue for you. Since the Hue app is made to connect to a dedicated device (hue bridge) with its own dedicated ip address, the app miss the flexibility to work on custom ports.

[Araforn]

the bridge must be available on ports 80 and 443 and i think this is a blocker issue for you. Since the Hue app is made to connect to a dedicated device (hue bridge) with its own dedicated ip address, the app miss the flexibility to work on custom ports.

Thanks a lot for the reply. I have looked into it further and even with reverse proxy setup I cannot make it work given that the Synology NAS cannot be changed to not use port 80.

As you said the key is that I need a dedicated IP address for diyhue with nothing using port 80 and 443.

It's a real shame because docker on Synology NAS is great. I'll have to purchase a separate Pi for this. My only "always on" Docker host is my Synology NAS.

Really looking forward to using diyhue. I have so many strips that I want to add to my hie eco system.Thanks a lot for your work on this.

[alexyao2015]

Yeah this can't be fixed

[Thomas-86]

Hi all,

For anyone ending up in here...
Not sure if it was possible at the time, but I've managed to deploy DiyHue using Docker on my Synology.
The trick is to create a macvlan so your DiyHue gets it's own IP.
You can follow this guide, just replace PiHole with DiyHue :)

https://servicemax.com.au/tips/pi-hole-in-docker-on-synology-the-best-way/

Grtz!
Thomas

Pi-Hole in Docker on Synology- The Best Way! - ServiceMax

[MickeH81]

Thomas.

How did you do that? Everything is working with the Gui on prt 80 but I cant pair Hue app with DiyHue.
Its creates cert file but it wont connect.

[Thomas-86]

Hi, If I remember well I passed the MAC address of the synology as MAC parameter to docker. It should then use that one to generate the certificate. The virtual Mac doesn’t work indeed though I didn’t investigate further :) Regards, Thomas

[Mr-Groch]

Hi!

I've menaged to get it working on Synology NAS on macvlan network! Bellow you can see my docker-compose.yml.

My LAN network is 192.168.1.0/24, DHCP starts from 192.168.1.100, so I decidec to use 192.168.1.64 for diyhue container. On my NAS there is also MQTT and HA containers, so there is need to access it from diyhue - I created second bridge network to get access to other containers from diyhue (diyhue see's other containers exposed ports on 172.18.0.1).

Secret is that name of macvlan network should be lexical before bridge network!! Docker will set default route to first network alphabetical

Beyond that macvlan needs to have highest priority to obtain desired mac address...

version: '3.8'
services:
  diyhue:
    image: diyhue/core
    container_name: diyhue
    restart: unless-stopped
    volumes:
      - ./:/opt/hue-emulator/export
    environment:
      - MAC=02:42:c0:a8:84:64
      - IP=192.168.1.64
    mac_address: 02:42:c0:a8:84:64
    networks:
      10_vlan:
        priority: 100
      20_internal: ~

networks:
  10_vlan:
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: 192.168.1.0/24
          gateway: 192.168.1.1
          ip_range: 192.168.1.64/32
  20_internal:
    driver: bridge
    ipam:
      config:
        - subnet: 172.18.0.0/30
          gateway: 172.18.0.1

[oscarb]

@Mr-Groch this looks really promising! 😃 I too am using a Synology NAS and I'm trying to get diyhue up and running.

Could you share what changes you had to do in your docker compose file for the Home Assistant and MQTT services as well?

[Mr-Groch]

@oscarb I have not changed anything special for mosquitto and Home Assistant docker compose configurations. MQTT runs on standard bridge network_mode and Home Assistand on host.

[Flashlab2]

I can't get this to work. I have a working macvlan connection but I can't get the diyhue container to communicate with the MQTT broker. @Mr-Groch I used your docker compose but still it doesn't seem to communicate. I know my MQTT broker is working (checked with HA and MQTT Explorer) and I can access the diyhue container on the macvlan IP.

My standard bridge network is 172.17.x.x not 172.18.x.x but changing that gives an overlap error so I guess that's correct. I tried adding the diyhue container to the standard bridge network using Portainer but that also doesn't work.

Could someone point me into the right direction?

[Flashlab2]

Just to answer my own question as it may help others. It turned out that the extra bridge network was indeed working but what needed to be changed is that in the Diyhue settings you need to set the extra bridge network gateway ip as the server ip for mqtt not the actual server ip address.