Homebridge on RaspberryPi

Posted on
Wed Jul 06, 2016 2:30 am
yassi offline
Posts: 468
Joined: Sep 06, 2015
Location: Germany

Re: Homebridge on RaspberryPi

Devildog0331 wrote:
If you stop your Indigo Server and restart it, you'll get the screen where you can set some options. Look for the "Override web server (HTTP) port number" part. The number in there is what I used in my Homebridge config.json file. The default port of 8176 gave me the same issue you have... No devices but no errors either. Once I changed that... Everything populated as it should have.


Ok.
But what port are you using?
I mean the default port is 8176 and I have this already in my config.json.
Do I have to use another port?
Attachments
Indigo Server settings.jpg
Server settings
Indigo Server settings.jpg (63.56 KiB) Viewed 4123 times

Posted on
Mon Jul 11, 2016 11:39 pm
webdeck offline
Posts: 436
Joined: May 07, 2005

Re: Homebridge on RaspberryPi

yassi wrote:
webdeck wrote:
Does it work if you just run it from the command line? You should rule that out before getting systemd all setup.

This is a guess, but I think you need quotes around the value of HOMEBRIDGE _OPTS, since it has a space, e.g.:
Code: Select all
HOMEBRIDGE_OPTS="-U /opt/homebridge"


Actually it worked , it didn't showed up errors.
And the homebridge was and is visible in the HomeKit Apps. I was able to add it with the PIN code.
But, no device appears.

Maybe I will try my Synology NAS instead, there is a plugin too.

That could be an option, but in all articles I've found they are not using quotes.
Here is another one:

https://gist.github.com/impressiver/175 ... 89a056cd19


Did you try adding the quotes? Did it work?

As for trying it on the command line, what I'm asking is, can you run
Code: Select all
homebridge -D -U /opt/homebridge
and put the output here? The output you posted before is the output you get if homebridge doesn't find the config.json file. There are no platforms configured in that case, so homebridge runs, but there are no platforms, and therefore no devices, configured, so you don't see anything when you are in a Homekit app. I would like to debug only your homebridge install and config instead of your systemd config to reduce the number of variables involved.

Posted on
Mon Jul 11, 2016 11:41 pm
webdeck offline
Posts: 436
Joined: May 07, 2005

Re: Homebridge on RaspberryPi

Devildog0331 wrote:
If you stop your Indigo Server and restart it, you'll get the screen where you can set some options. Look for the "Override web server (HTTP) port number" part. The number in there is what I used in my Homebridge config.json file. The default port of 8176 gave me the same issue you have... No devices but no errors either. Once I changed that... Everything populated as it should have.


I don't know why you had to change the default port for Indigo to get your setup to work, but you shouldn't need to do that.

Posted on
Tue Jul 12, 2016 1:24 am
yassi offline
Posts: 468
Joined: Sep 06, 2015
Location: Germany

Re: Homebridge on RaspberryPi

webdeck wrote:
yassi wrote:
webdeck wrote:
Does it work if you just run it from the command line? You should rule that out before getting systemd all setup.

This is a guess, but I think you need quotes around the value of HOMEBRIDGE _OPTS, since it has a space, e.g.:
Code: Select all
HOMEBRIDGE_OPTS="-U /opt/homebridge"


Actually it worked , it didn't showed up errors.
And the homebridge was and is visible in the HomeKit Apps. I was able to add it with the PIN code.
But, no device appears.

Maybe I will try my Synology NAS instead, there is a plugin too.

That could be an option, but in all articles I've found they are not using quotes.
Here is another one:

https://gist.github.com/impressiver/175 ... 89a056cd19


Did you try adding the quotes? Did it work?

As for trying it on the command line, what I'm asking is, can you run
Code: Select all
homebridge -D -U /opt/homebridge
and put the output here? The output you posted before is the output you get if homebridge doesn't find the config.json file. There are no platforms configured in that case, so homebridge runs, but there are no platforms, and therefore no devices, configured, so you don't see anything when you are in a Homekit app. I would like to debug only your homebridge install and config instead of your systemd config to reduce the number of variables involved.


Hi webdeck,

got it!
Damn, it was my fault: didn't realized that there is a difference in the username (not Indigo but indigo).

Now it find's the devices, but see the output, there still are some errors, some unknow device as well by the end of the capture, after the block with the PIN code.
But can't see yes the devices in my HomeKit apps - maybe due to last errors in the debug file?

Code: Select all
pi@homebridge:/opt/homebridge $ homebridge -D -U /opt/homebridge
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
[7/12/2016, 9:09:34 AM] Loaded plugin: homebridge-indigo
[7/12/2016, 9:09:35 AM] Registering platform 'homebridge-indigo.Indigo'
[7/12/2016, 9:09:35 AM] ---
[7/12/2016, 9:09:35 AM] Loaded config.json with 0 accessories and 1 platforms.
[7/12/2016, 9:09:35 AM] ---
[7/12/2016, 9:09:35 AM] Loading 1 platforms...
[7/12/2016, 9:09:35 AM] [Indigo Server] Initializing Indigo platform...
[7/12/2016, 9:09:35 AM] [Indigo Server] Indigo base URL is http://192.168.100.9:8176
[7/12/2016, 9:09:35 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices.json/
[7/12/2016, 9:09:35 AM] Loading 0 accessories...
[7/12/2016, 9:09:36 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/002%20-%20Bewegungsmelder%20Flur%20EG.json
[7/12/2016, 9:09:36 AM] [Indigo Server] Discovered Motion Sensor (FGMS001) (ID 434970789): 002 - Bewegungsmelder Flur EG
[7/12/2016, 9:09:36 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/002%20-%20Helligkeitssensor%20Flur%20EG.json
[7/12/2016, 9:09:36 AM] [Indigo Server] Discovered Motion Sensor (FGMS001) (ID 1164660725): 002 - Helligkeitssensor Flur EG
[7/12/2016, 9:09:36 AM] [Indigo Server] Ignoring unknown accessory type Motion Sensor (FGMS001)
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/002%20-%20Temperatursensor%20Flur%20EG.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered Motion Sensor (FGMS001) (ID 1570645400): 002 - Temperatursensor Flur EG
[7/12/2016, 9:09:37 AM] [Indigo Server] Ignoring unknown accessory type Motion Sensor (FGMS001)
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/002%20-%20Vibrationssensor%20Flur%20EG.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered Motion Sensor (FGMS001) (ID 219398179): 002 - Vibrationssensor Flur EG
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/003%20-%20T%C3%BCrsensor%20Eingangst%C3%BCr.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered Unknown (ID 299950306): 003 - Türsensor Eingangstür
[7/12/2016, 9:09:37 AM] [Indigo Server] Ignoring unknown accessory type Unknown
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/004%20-%20Blue.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered RGBW Controller (FGRGBWM) (ID 146494714): 004 - Blue
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/004%20-%20Composite.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered RGBW Controller (FGRGBWM) (ID 881611461): 004 - Composite
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/004%20-%20Green.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered RGBW Controller (FGRGBWM) (ID 1824948089): 004 - Green
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/004%20-%20LED%20Stripes%20B%C3%BCro.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered Combined Fibaro RGBW device (ID 1256290123): 004 - LED Stripes Büro
[7/12/2016, 9:09:37 AM] [Indigo Server] Ignoring unknown accessory type Combined Fibaro RGBW device
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/004%20-%20Red.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered RGBW Controller (FGRGBWM) (ID 1280347622): 004 - Red
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/004%20-%20White.json
[7/12/2016, 9:09:37 AM] [Indigo Server] Discovered RGBW Controller (FGRGBWM) (ID 1671201529): 004 - White
[7/12/2016, 9:09:37 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/005%20-%20Temperatursensor%20Keller.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Leak Sensor (FGFS111) (ID 1144209086): 005 - Temperatursensor Keller
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Leak Sensor (FGFS111)
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/005%20-%20Vibrationssensor%20Keller.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Leak Sensor (FGFS111) (ID 1489449001): 005 - Vibrationssensor Keller
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/005%20-%20Wassermelder%20Keller.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Leak Sensor (FGFS111) (ID 1086408816): 005 - Wassermelder Keller
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/006%20-%20Sirene/Warnlicht.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Error parsing Indigo response for /devices/006%20-%20Sirene/Warnlicht.json
Exception: SyntaxError: Unexpected token c
Response: could not find device "Warnlicht"
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring accessory /devices/006%20-%20Sirene/Warnlicht.json due to error
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/007%20-%20Remote%20Yasmin.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Key Fob (ZW088) (ID 461083636): 007 - Remote Yasmin
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Key Fob (ZW088)
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/10%20Minuten%20Timer.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Timer (ID 38681069): 10 Minuten Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/15%20Minuten%20Timer.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Timer (ID 825696030): 15 Minuten Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/20%20Minuten%20Timer.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Timer (ID 565907339): 20 Minuten Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/30%20Sekunden%20Timer.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Timer (ID 126625691): 30 Sekunden Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/5%20Minuten%20Timer.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Timer (ID 128409798): 5 Minuten Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Timer
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/APC%20Back-UPS%20BX700U.json
[7/12/2016, 9:09:38 AM] [Indigo Server] Discovered Battery and UPS Monitor (ID 1107441085): APC Back-UPS BX700U
[7/12/2016, 9:09:38 AM] [Indigo Server] Ignoring unknown accessory type Battery and UPS Monitor
[7/12/2016, 9:09:38 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/ATV1.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered XBMC Device (ID 477474772): ATV1
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/EyeTV.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered EyeTV Application (ID 538717186): EyeTV
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type EyeTV Application
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/iPad%20Yasmin%20%28Locate%20Beacon%29.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered beacon (ID 163499112): iPad Yasmin (Locate Beacon)
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type beacon
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/iPhone%20SE%20Yasmin%20%28Locate%20Beacon%29.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered beacon (ID 1281019336): iPhone SE Yasmin (Locate Beacon)
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type beacon
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/Pi-0.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered rPI (ID 808844548): Pi-0
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type rPI
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/Plex%20Server.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered Plex Media Server (ID 33900102): Plex Server
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type Plex Media Server
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/Prowl.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered Prowl Account (ID 1508557629): Prowl
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type Prowl Account
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/RadBeacon%20Dot%20Leoni.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered beacon (ID 320470535): RadBeacon Dot Leoni
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type beacon
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/RadBeacon%20Dot%20Uschi.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered beacon (ID 134871094): RadBeacon Dot Uschi
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type beacon
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/RadBeacon%20Dot%20Yasmin.json
[7/12/2016, 9:09:39 AM] [Indigo Server] Discovered beacon (ID 499428799): RadBeacon Dot Yasmin
[7/12/2016, 9:09:39 AM] [Indigo Server] Ignoring unknown accessory type beacon
[7/12/2016, 9:09:39 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/UPS%20%28MacMini%29.json
[7/12/2016, 9:09:40 AM] [Indigo Server] Discovered apcupsd UPS (ID 639447391): UPS (MacMini)
[7/12/2016, 9:09:40 AM] [Indigo Server] Ignoring unknown accessory type apcupsd UPS
[7/12/2016, 9:09:40 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/Verkehrsmeldungen%20Bayern.json
[7/12/2016, 9:09:40 AM] [Indigo Server] Discovered GhostXML Device (ID 693326963): Verkehrsmeldungen Bayern
[7/12/2016, 9:09:40 AM] [Indigo Server] Ignoring unknown accessory type GhostXML Device
[7/12/2016, 9:09:40 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/devices/Wetter/%20Au%C3%9Fentemperatur.json
[7/12/2016, 9:09:40 AM] [Indigo Server] Error parsing Indigo response for /devices/Wetter/%20Au%C3%9Fentemperatur.json
Exception: SyntaxError: Unexpected token c
Response: could not find device " Außentemperatur"
[7/12/2016, 9:09:40 AM] [Indigo Server] Ignoring accessory /devices/Wetter/%20Au%C3%9Fentemperatur.json due to error
[7/12/2016, 9:09:40 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/actions.json/
[7/12/2016, 9:09:40 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/actions/Mail%20senden%20alle%2010%20Minuten%20wenn%20Bewegung%20im%20Flur%20EG.json
[7/12/2016, 9:09:40 AM] [Indigo Server] Discovered Action (ID 780301784): Mail senden alle 10 Minuten wenn Bewegung im Flur EG
[7/12/2016, 9:09:40 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/actions/Mail%20senden%20alle%2010%20Minuten%20wenn%20Vibration%20im%20Flur%20EG.json
[7/12/2016, 9:09:40 AM] [Indigo Server] Discovered Action (ID 477230288): Mail senden alle 10 Minuten wenn Vibration im Flur EG
[7/12/2016, 9:09:40 AM] [Indigo Server] Indigo request: http://192.168.100.9:8176/actions/Mail%20senden%20alle%2010%20Minuten%20wenn%20Wasser%20im%20Waschraum.json
[7/12/2016, 9:09:40 AM] [Indigo Server] Discovered Action (ID 1943459219): Mail senden alle 10 Minuten wenn Wasser im Waschraum
[7/12/2016, 9:09:40 AM] [Indigo Server] Created 13 accessories
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '002 - Bewegungsmelder Flur EG'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '002 - Vibrationssensor Flur EG'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '004 - Blue'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '004 - Composite'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '004 - Green'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '004 - Red'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '004 - White'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '005 - Vibrationssensor Keller'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory '005 - Wassermelder Keller'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory 'ATV1'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory 'Mail senden alle 10 Minuten wenn Bewegung im Flur EG'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory 'Mail senden alle 10 Minuten wenn Vibration im Flur EG'...
[7/12/2016, 9:09:40 AM] [Indigo Server] Initializing platform accessory 'Mail senden alle 10 Minuten wenn Wasser im Waschraum'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

   ┌────────────┐
   │ 031-45-154 │
   └────────────┘

[b]fs.js:549
 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                ^

Error: EACCES: permission denied, open '/opt/homebridge/persist/AccessoryInfo.CC223DE3CE30.json'
   at Error (native)
   at Object.fs.openSync (fs.js:549:18)
   at Object.fs.writeFileSync (fs.js:1156:15)
   at Object.LocalStorage.persistKeySync (/usr/local/lib/node_modules/homebridge/node_modules/node-persist/local-storage.js:457:12)
   at Object.LocalStorage.setItemSync (/usr/local/lib/node_modules/homebridge/node_modules/node-persist/local-storage.js:275:14)
   at Object.nodePersist.setItemSync (/usr/local/lib/node_modules/homebridge/node_modules/node-persist/node-persist.js:99:29)
   at AccessoryInfo.save (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/model/AccessoryInfo.js:163:11)
   at Bridge.Accessory.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:430:23)
   at Server._publish (/usr/local/lib/node_modules/homebridge/lib/server.js:92:16)
   at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:351:14)[/b]
pi@homebridge:/opt/homebridge $



Update July 12, 7:29pm

Ok, I can see my devices.
But maybe one can have a look about the last error(s) in the debug log.
Attachments
File 12.07.16, 19 28 33.png
File 12.07.16, 19 28 33.png (322.56 KiB) Viewed 4009 times

Posted on
Tue Jul 12, 2016 9:42 pm
webdeck offline
Posts: 436
Joined: May 07, 2005

Re: Homebridge on RaspberryPi

The error at the end is because homebridge can't write to the file /opt/homebridge/persist/AccessoryInfo.CC223DE3CE30.json. You need to make sure whatever user account you're running homebridge under has read and write permission to /opt/homebridge and all of the files and directories under there.

The other two parsing errors appear to be bugs in Indigo's RESTful API. Those two devices have a forward slash / in their names. If you remove the slash from the device names, those parsing errors should go away.

Posted on
Wed Jul 13, 2016 8:17 am
yassi offline
Posts: 468
Joined: Sep 06, 2015
Location: Germany

Re: Homebridge on RaspberryPi

webdeck wrote:
The error at the end is because homebridge can't write to the file /opt/homebridge/persist/AccessoryInfo.CC223DE3CE30.json. You need to make sure whatever user account you're running homebridge under has read and write permission to /opt/homebridge and all of the files and directories under there.

The other two parsing errors appear to be bugs in Indigo's RESTful API. Those two devices have a forward slash / in their names. If you remove the slash from the device names, those parsing errors should go away.


Hmmm, strange. It runs under the homebdrige account and the account is the owner.

About the other thing: I've removed the / from the device names. Thx!
Attachments
Bildschirmfoto 2016-07-13 um 16.14.16.png
Bildschirmfoto 2016-07-13 um 16.14.16.png (84.08 KiB) Viewed 3958 times

Posted on
Tue Apr 04, 2017 12:18 am
haavarda offline
User avatar
Posts: 702
Joined: Aug 18, 2012
Location: Norway

Re: Homebridge on RaspberryPi

I am trying to get Homebride to run on a Raspberry PI I had lying around. But I am struggling with one of the steps in the tutorial.

Running Homebridge on Bootup (systemd)

On newer Raspberry Pi and Debian systems (Jessie +), managing of services with init.d is (transparently) replaced with systemd. If you wish to use systemd for running Homebridge on boot, you can find instructions in a Gist under johannrichard/homebridge. As you can see, the service definition is much shorter than a comparable init.d script.

Download the two files and place homebridge under /etc/default and homebridge.service under /etc/systemd/system on your Raspberry Pi.
.

https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi

How can I access the root and etc folder? I was able to connect with transmit, but I was unable to writhe to the spesified folder (/etc/default).
I am a beginner on this SSH and raspberry so hope someone can help :)

Håvard

Posted on
Tue Apr 04, 2017 12:48 am
yassi offline
Posts: 468
Joined: Sep 06, 2015
Location: Germany

Re: Homebridge on RaspberryPi

You must use a sudo command, otherwise you are not able to modify files there.

Yassi

Posted on
Tue Apr 04, 2017 12:56 am
haavarda offline
User avatar
Posts: 702
Joined: Aug 18, 2012
Location: Norway

Re: Homebridge on RaspberryPi

Yes. I understand. But what is the command for copy a file to that location? Or do you use a different client to do file sharing?

Håvard

Posted on
Tue Apr 04, 2017 4:18 am
haavarda offline
User avatar
Posts: 702
Joined: Aug 18, 2012
Location: Norway

Re: Homebridge on RaspberryPi

I might have been a bit unclear in my description. So to be a bit more precise.

How can I add a file to the following directory on my PI:
Code: Select all
 /etc/default and under /etc/systemd/system
?

Håvard

Posted on
Mon Apr 10, 2017 1:42 am
yassi offline
Posts: 468
Joined: Sep 06, 2015
Location: Germany

Re: Homebridge on RaspberryPi

For an empty file use:

Code: Select all
touch /path/to/file


Otherwise you can use
Code: Select all
nano /path/to/file


Yassi

Who is online

Users browsing this forum: No registered users and 4 guests

cron