# Running Homebridge on the Homey Pro 2023 **URL:** \ **Category:** Questions & Help\ **Tags:** homey-pro\ **Created:** [September 21, 2023, 9:07am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866 "2023-09-21T09:07:10Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![nielsoet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nielsoet/32/34829_2.png) [@nielsoet](https://community.homey.app/u/nielsoet)\ **Post date:** [September 21, 2023, 9:07am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/1 "2023-09-21T09:07:10Z")
I’ve tried running [Homebridge](https://homebridge.io/) on the Homey Pro 2023 experiment, but failed to install it. I’ve got my complete smart home on my Homey Pro 2023, except the camera functionality Homebridge offers me to Homekit on my Apple devices. I’m running UniFi Protect cameras around the house connected to the UniFi CloudKey Gen2 Plus. I use Homebridge to show the UniFi cameras in my APple Homekit environment. Anyone else got any tips to handle this? Or should I stick to my Linux mini PC (which is only being used for this now). ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 21, 2023, 9:26am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/2 "2023-09-21T09:26:42Z")
What does “failed to install” mean? ---
**Author:** ![nielsoet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nielsoet/32/34829_2.png) [@nielsoet](https://community.homey.app/u/nielsoet)\ **Post date:** [September 21, 2023, 9:34am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/3 "2023-09-21T09:34:20Z")
Maybe it’s my knowledge, but can’t even add the repo/source: ```auto homey@homey-pro-sandbox:~$ curl -sSfL https://repo.homebridge.io/KEY.gpg | sudo gpg --dearmor | sudo tee /usr/share/keyrings/homebridge.gpg > /dev/null sudosudo: unable to resolve host homey-pro-sandbox: Name or service not known : unable to resolve host homey-pro-sandbox: Name or service not known sudo: gpg: command not found (23) Failed writing body homey@homey-pro-sandbox:~$ curl -sSfL https://repo.homebridge.io/KEY.gpg | gpg --dearmor | tee /usr/share/keyrings/homebridge.gpg > /dev/null -bash: gpg: command not found tee: /usr/share/keyrings/homebridge.gpg: Permission denied (23) Failed writing body homey@homey-pro-sandbox:~$ ``` From: [Install Homebridge on Debian or Ubuntu Linux · homebridge/homebridge Wiki · GitHub](https://github.com/homebridge/homebridge/wiki/Install-Homebridge-on-Debian-or-Ubuntu-Linux) ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 21, 2023, 9:37am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/4 "2023-09-21T09:37:29Z")
I guess you should start by installing gpg: ```auto sudo apt install gpg ``` ---
**Author:** ![nielsoet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nielsoet/32/34829_2.png) [@nielsoet](https://community.homey.app/u/nielsoet)\ **Post date:** [September 21, 2023, 9:41am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/5 "2023-09-21T09:41:40Z")
That helped a bit: ```auto homey@homey-pro-sandbox:~$ curl -sSfL https://repo.homebridge.io/KEY.gpg | sudo gpg --dearmor | sudo tee /usr/share/keyrings/homebridge.gpg > /dev/null sudosudo: : unable to resolve host homey-pro-sandboxunable to resolve host homey-pro-sandbox: Name or service not known : Name or service not known ``` I now see I get this error for almost everything: ```auto sudo: unable to resolve host homey-pro-sandbox: Name or service not known ``` ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 21, 2023, 10:43am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/6 "2023-09-21T10:43:41Z")
That’s a warning, not an error. You can ignore it. ---
**Author:** ![TheAdrianMc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/theadrianmc/32/87273_2.png) [@TheAdrianMc](https://community.homey.app/u/TheAdrianMc)\ **Post date:** [October 8, 2023, 7:57am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/7 "2023-10-08T07:57:02Z")
So this is what im getting on mine. I got gpg installed but cant get the repo/source to take. > sudo apt-get update > sudo: unable to resolve host homey-pro-sandbox: Name or service not known > Get:1 [Index of /debian](http://deb.debian.org/debian) bullseye InRelease [116 kB] > Err:1 [Index of /debian](http://deb.debian.org/debian) bullseye InRelease > Couldn’t create temporary file /tmp/apt.conf.jPAaoX for passing config to apt-key > Get:2 [Index of /debian-security](http://deb.debian.org/debian-security) bullseye-security InRelease [48.4 kB] > Err:2 [Index of /debian-security](http://deb.debian.org/debian-security) bullseye-security InRelease > Couldn’t create temporary file /tmp/apt.conf.QEZv93 for passing config to apt-key > Get:3 [https://repo.homebridge.io](https://repo.homebridge.io) stable InRelease [3242 B] > Err:3 [https://repo.homebridge.io](https://repo.homebridge.io) stable InRelease > Couldn’t create temporary file /tmp/apt.conf.lwdAw4 for passing config to apt-key > Get:4 [Index of /debian](http://deb.debian.org/debian) bullseye-updates InRelease [44.1 kB] > Err:4 [Index of /debian](http://deb.debian.org/debian) bullseye-updates InRelease > Couldn’t create temporary file /tmp/apt.conf.CKsYoc for passing config to apt-key > Reading package lists… Done > W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: [Index of /debian](http://deb.debian.org/debian) bullseye InRelease: Couldn’t create temporary file /tmp/apt.conf.jPAaoX for passing config to apt-key > W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: [Index of /debian-security](http://deb.debian.org/debian-security) bullseye-security InRelease: Couldn’t create temporary file /tmp/apt.conf.QEZv93 for passing config to apt-key > W: GPG error: [https://repo.homebridge.io](https://repo.homebridge.io) stable InRelease: Couldn’t create temporary file /tmp/apt.conf.lwdAw4 for passing config to apt-key > E: The repository ‘[https://repo.homebridge.io](https://repo.homebridge.io) stable InRelease’ is not signed. > N: Updating from such a repository can’t be done securely, and is therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration details. > W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: [Index of /debian](http://deb.debian.org/debian) bullseye-updates InRelease: Couldn’t create temporary file /tmp/apt.conf.CKsYoc for passing config to apt-key ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [October 8, 2023, 8:00am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/8 "2023-10-08T08:00:38Z")
> [@TheAdrianMc](#): > > Couldn’t create temporary file /tmp/apt.conf.jPAaoX for passing config to apt-key This shouldn’t happen. What does `ls -al /tmp/` return? ---
**Author:** ![TheAdrianMc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/theadrianmc/32/87273_2.png) [@TheAdrianMc](https://community.homey.app/u/TheAdrianMc)\ **Post date:** [October 16, 2023, 4:50am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/9 "2023-10-16T04:50:46Z")
homey@homey-pro-sandbox:~$ ls -al /tmp/ total 8 drwxr-xr-t 2 root root 4096 Oct 8 07:33 . drwxr-xr-x 1 root root 4096 Oct 8 07:00 … ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [October 16, 2023, 4:56am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/10 "2023-10-16T04:56:45Z")
Yeah, that’s wrong, apparently Athom never listened to my comments about the permissions on `/tmp` not being correct 🙄 You can fix it with this: ```auto sudo chmod 1777 /tmp ``` ---
**Author:** ![TheAdrianMc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/theadrianmc/32/87273_2.png) [@TheAdrianMc](https://community.homey.app/u/TheAdrianMc)\ **Post date:** [October 16, 2023, 5:10am UTC](https://community.homey.app/t/running-homebridge-on-the-homey-pro-2023/89866/12 "2023-10-16T05:10:30Z")
Was able to get Homebridge to start installing and I got a "failed to write (no space left on device) error. Looks like it was right! ![IMG_4998](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/d/1d0b0d39a34e9d3915a965b745f20749d0d3185b.jpeg)