Using diyhue on Synology NAS

[Mr-Groch]

Hi!

I've managed to get it working on Synology NAS as docker container 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/config
    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

[zwenty]

Hi!

I'm desperately trying to get this work. No luck so far. I'd like to see my Home Assistant lights in diyHue.

I got Home Assistant running on Docker on my DS and access it via my DS ip port 8123.

I changed your docker-compose with my network settings and the DS mac address.

btw: why do you mount
- ./:/opt/hue-emulator/export
instead of:
- ./:/opt/hue-emulator/config

When I run the compose I do get the following error:

ERROR: for diyhue Cannot start service diyhue: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: time="2022-04-12T23:10:27+02:00" level=fatal msg="failed to add interface dockercadfed9 to sandbox: failed to set link up: device or resource busy": unknown

So I did leave the vlan in portainer and started the container: success

Next I deleted the vlan and set up a new one in portainer with same network settings but different name.
I joined the new macvlan with the diyhue container and voila: container is running

So now I'm able to access diyHue UI via the macvlan ip address: nice

Next I did configure the Home Assistant settings in the diyHue UI
IP: DS IP address | port: 8123 | token | include by default

Unfortunately this did not do the trick, no lights showed up.

I checked the logs and found that diyHue is not connecting to Home Assistant.

2022-04-12 23:05:19,929 - services.homeAssistantWS - WARNING - Home Assistant Web Socket Client disconnected trying to (re)connect 2022-04-12 23:05:22,937 - services.homeAssistantWS - ERROR - Error connecting to Home Assistant WebSocket Traceback (most recent call last): File "/opt/hue-emulator/services/homeAssistantWS.py", line 234, in create_websocket_client homeassistant_ws_client.connect() File "/usr/local/lib/python3.9/dist-packages/ws4py/client/__init__.py", line 217, in connect self.sock.connect(self.bind_addr) OSError: [Errno 113] No route to host Starting remote discovery

Now I'm kinda lost...

Any clue why diyHue doesn't connect to HA?

[Mr-Groch]

It can be many things...

eth0 here you should change to network interface name of your Synology LAN port

    driver_opts:
      parent: eth0

subnet should be your LAN subnet where Synology is connected to
gateway should be your LAN gateway (router IP) where Synology is connected to
ip_range IP here should not be used in your network by any host

      config:
        - subnet: 192.168.1.0/24
          gateway: 192.168.1.1
          ip_range: 192.168.1.64/32

And for biridge network - subnet and gateway should not be used by any other docker network...

      config:
        - subnet: 172.18.0.0/30
          gateway: 172.18.0.1

For macvlan MAC address you can choose any not used MAC on your network

[zwenty]

Well, thats what I did. But let me delete everything and try again. I report back.

Is it normal that it appends docker_ to the network names I specified in the compose?

[zwenty]

Ok, one step further I guess. Deleted networks and container, restarted my DS.
Run docker-compose, ... done, no error this time.

Two networks were created docker_10_vlan and docker_20_internal. Container is connected to both.
MAC address of vlan is the one I specified in the docker compose.
MAC address of internal is different.

Unfortunately it is still not connecting to Home Assisstant

2022-04-13 16:26:03,922 - services.homeAssistantWS - WARNING - Home Assistant Web Socket Client disconnected trying to (re)connect
A
B
2022-04-13 16:26:06,928 - services.homeAssistantWS - ERROR - Error connecting to Home Assistant WebSocket
Traceback (most recent call last):
File "/opt/hue-emulator/services/homeAssistantWS.py", line 234, in create_websocket_client
homeassistant_ws_client.connect()
File "/usr/local/lib/python3.9/dist-packages/ws4py/client/__init__.py", line 217, in connect
self.sock.connect(self.bind_addr)
OSError: [Errno 113] No route to host
Starting remote discovery

Home Assistant settings in the diyHue UI unchnged to before...
IP: DS IP address | port: 8123 | token | include by default

Anything I'm missing?

EDIT: DS firewall I turned off, just in case...

[Mr-Groch]

What IP address you've entered as Home Assistant IP in diyHue config? You should use docker_20_internal gateway IP there

[zwenty]

OMG this really did it 👍
Thanks a lot this saved my day 🥇

2022-04-13 19:02:21,006 - services.homeAssistantWS - WARNING - Home Assistant Web Socket Client disconnected trying to (re)connect
2022-04-13 19:02:21,010 - services.homeAssistantWS - INFO - Home Assistant WebSocket Connection Opened
2022-04-13 19:02:21,011 - services.homeAssistantWS - INFO - Home Assistant Web Socket Client connected
2022-04-13 19:02:21,012 - services.homeAssistantWS - INFO - Home Assistant Web Socket Authorisation required
2022-04-13 19:02:21,044 - services.homeAssistantWS - INFO - Home Assistant Web Socket Authorisation complete
2022-04-13 19:02:21,096 - services.homeAssistantWS - INFO - Found light.couch

I still don't under stand how diyHue can connect without knowing the HA ip but just the port though...

And why is there docker_ set before the network names I specified in the docker compose?