Ok so it’s a bit of a challenge to get this working for those who don’t have Docker. But here we go.
You need to add the community package source in DSM. In the Package Sources tab, click Add, type SynoCommunity as Name and http://packages.synocommunity.com/ as Location and then press OK to validate. Now the Debian Chroot package is available and you can install it. The community Python package is a requirement and the package manager will ask for permission to install it. After the package is installed, the package will automatically install the necessary files on your filesystem. The status of this installation can be tracked within the package application on the DSM web interface.
ssh into you Synology (ssh admin@NASip)
then enter: sudo -i
then
sed -i s:3rdparty/debian-chroot/debian-chroot.cgi/direct/router:/webman/3rdparty/debian-chroot/debian-chroot.cgi/direct/router: /var/packages/debian-chroot/target/app/debian-chroot.js && sed -i s:3rdparty/debian-chroot/debian-chroot.cgi/direct/poller:/webman/3rdparty/debian-chroot/debian-chroot.cgi/direct/poller: /var/packages/debian-chroot/target/app/debian-chroot.js
/var/packages/debian-chroot/scripts/start-stop-status start
/var/packages/debian-chroot/scripts/start-stop-status chroot
then
apt-get update && \
apt-get -y upgrade && \
apt-get -y install locales && \
dpkg-reconfigure locales
then
dpkg-reconfigure tzdata
then
apt-get update && \
apt-get install -y apt-utils nano && \
apt-get install -y \
curl \
wget \
git \
apt-transport-https \
python \
build-essential \
make \
g++ \
libavahi-compat-libdnssd-dev \
libkrb5-dev \
vim \
net-tools \
sudo \
git-core \
libnss-mdns
Then
curl -L https://git.io/n-install | bash -s -- -y
export N_PREFIX="$HOME/n"; [[ :$PATH: == *":$N_PREFIX/bin:"* ]] || PATH+=":$N_PREFIX/bin"
npm config set registry http://registry.npmjs.org/
npm install -g --unsafe-perm homebridge
npm install -g --unsafe-perm homebridge-vera
rm -r /var/run && rm -r /var/lock && ln -s /run /var/run && ln -s /run/lock /var/lock && rm /run/dbus/*
sed -i s/rlimit-nproc=3/#rlimit-nproc=3/ /etc/avahi/avahi-daemon.conf && sed -i s/AVAHI_DAEMON_DETECT_LOCAL=1/AVAHI_DAEMON_DETECT_LOCAL=0/ /etc/default/avahi-daemon
mkdir /root/.homebridge && printf '%s\n' '#!/bin/bash' '# LANCEMENT DES SERVICES DBUS, AVAHI, HOMEBRIDGE' '# RUNNING DBUS, AVAHI AND HOMEBRIDGE SERVICES' 'export N_PREFIX="$HOME/n"; [[ :$PATH: == *":$N_PREFIX/bin:"* ]] || PATH+=":$N_PREFIX/bin"' 'dbus-daemon --system' '/etc/init.d/dbus restart' 'service avahi-daemon start' 'homebridge' >/root/.homebridge/run.sh && chmod 755 /root/.homebridge/run.sh
Then modify /root/.homebridge/config.json with your correct info
vi /root/.homebridge/config.json
Then type exit to go back to Synology shell
Then printf '%s\n' '/var/packages/debian-chroot/scripts/start-stop-status start' 'chroot /usr/local/debian-chroot/var/chroottarget/ /root/.homebridge/run.sh' >/volume1/HomeKitVeraAuto.sh
chmod 755 /volume1/HomeKitVeraAuto.sh
Then open Task Scheduler in Synology GUI.
Create a schedules task called: HomeKitVera Start
Select user “root”
Choose event: Boot-up
Then in task settings, type: /volume1/HomeKitVeraAuto.sh
Then reboot and see if it shows up on your phone.
Still working out a few kinks.