Tutorial: add Homebridge to Hass.io using Portainer

I would try removing homebridge from the Apple Home app (under Hubs & Bridges) and re-adding it. Also, make sure the hub identifier, looks like a MAC address, and the port in your homebridge config.json are unique, and not the same as homeassistant homekit bridge if you are using that feature. If this fails to help, I would look for help from homebridge folks on github and give them information about the specific accessory/plugin you are trying to add to Apple Homekit and any logs or error codes you encounter.

Are you able to access via hassio shares (config) to access the hombridge (config file, persistent and accessory dir)?

I’m not able to map /homebridge to ./config/ or ./config/homebridge on host (hassio).

answer:
Bind:
config in hassio is:
/mnt/data/supervisor/homeassistant(/homebridge) /homebridge

for me it says:

2020/01/30 07:58:18 [WARN] [docker,snapshot] [message: unable to snapshot engine information] [endpoint: primary] [err: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39]
2020/01/30 07:58:18 [WARN] [docker,snapshot] [message: unable to snapshot containers] [endpoint: primary] [err: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39]
2020/01/30 07:58:18 [WARN] [docker,snapshot] [message: unable to snapshot images] [endpoint: primary] [err: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39]
2020/01/30 07:58:18 [WARN] [docker,snapshot] [message: unable to snapshot volumes] [endpoint: primary] [err: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39]
2020/01/30 07:58:18 [WARN] [docker,snapshot] [message: unable to snapshot networks] [endpoint: primary] [err: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39]
2020/01/30 07:58:18 [WARN] [docker,snapshot] [message: unable to snapshot engine version] [endpoint: primary] [err: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39]

hello @thecem can you share how you did that? i’m new to all this…thanks.

Go to “Supervisor” in HA -> Install “Portainer”.
In Portainer-AddOn-Config “Disable Protection Mode”.
In Portainer WEB UI go to Stacks -> Add Stacks -> name stack: HomebridgeXYZ.
Cpy following into the docker-cpompose field:

version: '2'
services:
  homebridge:
    image: oznu/homebridge:latest
    restart: always
    network_mode: host
    environment:
      - PGID=0
      - PUID=0
      - HOMEBRIDGE_CONFIG_UI=1
      - HOMEBRIDGE_CONFIG_UI_PORT=8581
    volumes:
      - /mnt/data/supervisor/homeassistant/homebridge:/homebridge

-> Deploy the Stack

If you would update to the latest version of oznu/homebridge:

  • Portainer -> container -> homebridge -> recreate
  • Check Pull latest Image
  • go to images and delete the unused Image of homebrdge
  • enjoy!
17 Likes

Hi, I’ve followed your guide to the T and keep getting the above error that @weaverprojects had except it says homebridge:raspberry-pi. Only difference I notice between my Portainer UI us it say dock.io before you input the image name:

image

Please help as all of this is completely new to me! Thanks.

Maybe you can try @thecem 's method posted above using the docker compose file.

Also the docker.io appears in my screen too, likely an updated portainer since my first post.

Thank you. Worked perfectly

Thanks for this tutorial. I’ve now sucessfully migrated my Raspberry Installation of homebridge to a homeassistant portainer setup. Would anyone know how to enable https access for the homebridge docker container? I have my home assistant running under https (using the addons letsencrypt and nginx ssl proxy) and would like to also access homebridge as a path under my homeassistant url. e.g. https://homeassistant/homebridge. Similar to how the homeassistant addons work.

@simon.lock: Did you try it with https://github.com/oznu/homebridge-config-ui-x#enabling-ssl ?

If yes what’s was the result?

Thanks for the guide!
Would take ages for me to figure it out myself!

Thanks for the tutorial. I gather I am supposed to see the homebridge server on port 8181, by typing <home_assistant_ip_address>:8181. When I go to the address I am getting a refused to connect error (ERR_CONNECTION_REFUSED).

Anything I should be looking at?

Should be port :8080.

1 Like

Thanks, for some reason I thought it was 8181.

Sorry if this isnt within the scope of this post, but when creating the volume, what is actually happening here? I’m running HA on a raspberry pi, and if I go into the shell of the home bridge container i see the /homebridge directory. Is the volume supposed to be creating this directory on my host system (the raspberry pi)? If so I cant find it, the mount path for the volume it created is /mnt/data/docker/volumes/{id}/_data but when I ssh to my pi that directory doesn’t exist.

Thanks

As @thecem points out in an earlier post, use the following volume information to be able to access your homebridge instance on the host.

Gibt es auch die Möglichkeit „Hoobs“ auf eine ähnliche Art und Weise einzubinden?

Ich habe es versucht und in Home Assistent wird mir die Hoobs HomeKit Bridge angezeigt aber ich finde keine IP Adresse um über die Web Oberfläche darauf zuzugreifen.

Hi, I installed Homebridge on my ri4 as discribed! I now have to update my npm and node.js. I read that you have to update the docker image. Is it possible to keep the plug ins and keep the config file as it is?

You should be able to perform updates through the home bridge web interface, there is not typically a need to directly use docker commands.