How to configure deCONZ conbee in Docker

Hi everyone,

I just received the conbee and plugged it into my home server.
I am running Home Assistant (not hass.io) in Docker on a Ubuntu 18.04 host. So far I am very happy with that setup. Now I want to replace my Xiaomi Gateway for various reasons. I read the instructions (https://www.home-assistant.io/components/deconz/) page and setup a docker container with the marthoc image. I have the following docker-compose:

deconz:
    image: marthoc/deconz
    container_name: deconz
    ports:
      - 8085:80
      - 4043:443
    restart: always
    volumes:
      - /home/matthias/HASS/deconz:/root/.local/share/dresden-elektronik/deCONZ
    devices:
      - /dev/ttyUSB0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0

I usually have the discovery-option disabled, but I tried this with the option enabled, too. When I go to the Setup Integrations page I receive an error saying that no deconz-bridge can be found.
The logs for that moment show the following:

2018-11-16 09:55:24 INFO (SyncWorker_10) [homeassistant.components.tado] Querying mytado.com for zone 2 Schlafzimmer,
2018-11-16 09:55:41 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow_handlers to 192.168.16.9 (auth: True),
2018-11-16 09:55:39 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow to 192.168.16.9 (auth: True),
2018-11-16 09:55:41 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/entry to 192.168.16.9 (auth: True),
2018-11-16 09:55:41 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow to 192.168.16.9 (auth: True),
2018-11-16 09:55:40 INFO (MainThread) [pydeconz.utils] No discoverable bridge available.

Note: 192.168.16.9 is the docker-internal IP of my letsencrypt/nginx server - Now I assume is related to the port 443 being changed. Can I force home assistant to look on a different port for the deconz API?
I can access the Phoscon App by visiting http://192.168.1.8:8085/pwa/ and the gateway is working there.

I have no clue how to proceed from here. Thanks for any help!

1 Like

I figured it out. You can add

deconz:
  host: 192.168.1.8
  port: 4043

to the configuration.yaml file. Maybe this should be mentioned on the instructions page.

Thanks!

4 Likes

great! thank you for sharing. Im planning on getting this gateway.
somewhat related question; you got the usb; did you investigate the Raspbee on a Pi?
I like the fact it can be a completely separate device. I appreciate having a Pi just for that might be a waste, but if it has better reach and performance might be worth.
on the xiaomi gateway what was it’s disadvantage.
Thank you again

I have a Mac mini (running Ubuntu) as a server, therefore I went with the USB. If I see issues coming up I might plug that USB into an Raspberry, I anyway have one running as BLE presence detector.
The downside of the Xiaomi Gateway is mainly trust issues, and some performance problems i had lately. In the past few days the gateway uploaded 800MB of data to somewhere - I don’t know what it uploaded, but I probably don’t want that it does that. So I am replacing it with something where I have more control over.

Thank you for the feedback.
I read some people block the xiaomi gateway via their router.

Once you got it (congee) running, maybe you can share views on range.

Okay, so I spent the weekend working this out. It’s been a terrible ride and I am not sure if I am at the end of it :smiley:
I ran deconz it on my HA server using Docker, I connected some sensors, then I had troubles. Thought it is the range, so I installed the Docker on on a spare RPi to be closer to the sensors. I connected all of them, but they would not stay reachable - maybe this is a bug in the current version. Coudl not figure it out. in the end I copied the zll.db, the database which contains all sensors over to the Docker on my HA server and connected the Conbee there again, now everything is reachable and works fine. It covers all of my home from the one stick without issues.

I’ll report if there are new issues.

Thank you for your feedback. Much appreciated.
So effectively you ended where you started the only difference that you captured the sensors in the PI, but only got it working in the HA server.
Weird, but glad is working.

Hello,

I am running Home assistant on my raspberry PI with Hassbian, so not the Hassio or Docker setup.
How would I go about running Conbee now? Do I use the docker container as well? If so? I’m having trouble actually finding a complete guide as I have never used Docker before I’m not sure what I would need to configure before even downloading the docker image.