I’ve tried running Homebridge 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).
What does “failed to install” mean?
Maybe it’s my knowledge, but can’t even add the repo/source:
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
I guess you should start by installing gpg:
sudo apt install gpg
That helped a bit:
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:
sudo: unable to resolve host homey-pro-sandbox: Name or service not known
That’s a warning, not an error. You can ignore it.
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 bullseye InRelease [116 kB]
Err:1 Index of /debian bullseye InRelease
Couldn’t create temporary file /tmp/apt.conf.jPAaoX for passing config to apt-key
Get:2 Index of /debian-security bullseye-security InRelease [48.4 kB]
Err:2 Index of /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 stable InRelease [3242 B]
Err:3 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 bullseye-updates InRelease [44.1 kB]
Err:4 Index of /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 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 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 stable InRelease: Couldn’t create temporary file /tmp/apt.conf.lwdAw4 for passing config to apt-key
E: The repository ‘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 bullseye-updates InRelease: Couldn’t create temporary file /tmp/apt.conf.CKsYoc for passing config to apt-key
This shouldn’t happen. What does ls -al /tmp/ return?
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 …
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:
sudo chmod 1777 /tmp
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!
