Domoticz

no cigar. Segmentation fault.

Alas I was using an standard RPI, if that install was for an RPI3, hmm will consider running on rpi3 but didn't want to break the default domoticz install as its live

All of the above should work on any raspPi running Wheezy onwards, other than the final line (bluetooth bits - sudo apt-get install pi-bluetooth bluetooth bluez blueman) which are rPi3 specific. All tested on Pi1vB, Pi2, Pi3 on both wheezy and jessie.

If they don’t, you have issues elsewhere with your Pi / OS.

where does it download Homebridge and Forever in the script ? did a fresh jessie again and still get segmentation fault on a standard rpi. at sudo npm install -g homebridge and forever. ?...will try rpi3 later after I've made a backup

pi@raspberrypi:~ $ sudo npm install -g homebridge
pi@raspberrypi:~ $ sudo bash
root@raspberrypi:/home/pi# npm install -g forever
Segmentation fault
root@raspberrypi:/home/pi#

Where as in to what location on your disk? /usr/local/lib/node_modules (stock global node module location)

You can start homebridge manually without forever, just head to /usr/local/lib/node_modules/homebridge/bin and ./homebridge

That said, could be armv6 issue... try:
(The additional line comes after hash -r)

NB sudo bash -

sudo curl -sL https://deb.nodesource.com/setup_0.12 | sudo bash -

Nah...still same on Jessie even with that source change

Made a backup of the rpi3...will give it go there.

okay we have a winner!!!

RPI3 - Success all the way through to controlling with eve and siri (Although it gets confused)

I followed your installer script and used edomoticz

Things your installer script.txt needs in addition

bash - = sudo bash -
sudo apt-get install git = (because it isn't) on the lite version of jessie

by default for some reason it couldn't put homebridge in the path /usr/local/lib/node_modules/homebridge/bin/homebridge
if goes in /usr/bin/homebridge.

and finally

.homebridge does exist until you run it for the first time. so you can't put a config.json until its either you create it or it exists after you run homebridge first.

Have updated that into the file - ta!

All neatly installed on a new PI, I got home bridge not installed on the old spinning Pi.
However, it can not start Homebridge like the wike page with start, but i use homebridge in the / bin directory. to start.
How can I correct this? And all the devices may be on the iPhone, however, Siri does not work, do I have to use the English Siri or can I use the Dutch?

Wiki is outdated... See http://www.domoticz.com/forum/viewtopic ... 440#p77846

Fire up a HomeKit app and configure your Siri names? Should work with Dutch or English. Takes a few minutes for iCloud etc to pick up your HomeKit config, and you need Bluetooth on if you use and want to change scenes.

Hi All - great work on the new Homebridge install that is part of the latest Rpi SD.

Was up and working quite quickly although did come across a number of issues most of which were solved by scouring the pages of this forum. The installation seems to be a little different to references around the web when searching for information but for anyone else new to RPi/Domoticz/Homebridge this is what I found:

1) To avoid authentication issues which gives the error "There was a problem connecting to Domoticz" add 127.0.0.* to the Local Networks (no username/password) section on the settings page. Separate networks with a semi colon ";"

2) I had great problem trying to get Homebridge to restart on boot up. Tried Forever as per the Wiki and also tried adding a start up file to etc/init.d and then linking it with update-rc but without success. Also tried PM2 which I eventually got to work. Most of the information has the following instruction to set up PM2:

pm2 start app.js --name HomeBridge

however there is no app.js in the .homebridge directory so it produces an error. Through reading various posts eventually I replaced app.js with the following:

/usr/lib/node_modules/homebridge/bin/homebridge

That resolved the issue and PM2 scheduled the job and by following all of the other PM2 steps Homebridge starts after a reboot.

3) I have been using Eve as a client and when adjusting the duration for the override on a Heating Device (using Evohome) it caused Homebridge to crash.

I have found two errors in /usr/lib/node_modules/homebridge-edomoticz/index.js

Lines 885 and 886

Original lines
url = (mode == "TemporaryOverride")? "&until=" + isonow + "&used=true" : "&used=true";

that.log("Setting thermostat SetPoint to " + setpoint +", mode to " + mode);

Amended lines:
Added variable url to the conditional sections of the line
url = (mode == "TemporaryOverride")? url + "&until=" + isonow + "&used=true" : url + "&used=true";
Changed setpoint to temp as setpoint is not defined
that.log("Setting thermostat SetPoint to " + temp + ", mode to " + mode);

Thanks everyone for their posts which helped me get this far. Hope this helps someoneelse.

Now to move it across to my production system

Homebridge-eDomoticz has it’s own separate support thread & install guide, and shouldn’t be confused with the plugin / instructions on the out-of-date Wiki pages...

Whether Temp / setPoint is used depends on the device type etc as per:
So if it gets it wrong, i need to know about it / account for your specific combination (hard to cater for all devices when I don’t own them all). Instructions for sharing your sensor info so i can include it’s combination are in the first post of the support thread. Good spot on the missing url reference - ta!

Hi Experts,

While reading a lot of wiki, this forum and some other tutorials I managed to setup homebridge and run it by starting it manual. I now want to have it start automatically after booting the PI (Jessie). I'm following the PM route to do this as mentioned in this thread earlier. Can you please explain the proces around the app.js process?
I guess this occurs because there is no app.js in that directory. How can I solve this issue?

Follow the homebridge-edomoticz thread, which covers the current way of doing it with the current version of homebridge and plugin with full step-by-step instructions, rather than this which covers the discontinued method for the old version of homebridge and plugin.

Aha, was not aware of that. Thanks for the head-up.

hello you can use Homebridge off the net? I read that if you have an Apple TV connected but you can not get it to work

Artic1980 wrote:hello you can use Homebridge off the net? I read that if you have an Apple TV connected but you can not get it to work

Yes you can and you are correct, you need an Apple TV 3 or 4. I am currently using ATV4 but have tested it on a 3. Even works when the ATV goes into standby/sleep mode.

All you need to do is log into your ATV using your same Apple ID, also make sure "allow remote access" is enabled under homekit settings on your iPhone.

I can not understand where the mistake atv3 is connected to the same network Raspberry iCloud on both ATV on the iPhone on domoticz I have to configure something?


Inviato dal mio iPhone utilizzando Tapatalk

Hello I have a problem I connected a esp01 and a relay to the entrance gate but to do so I have to pronounce turn open the gate and you do not open the gate as I can make it recognize as a door or gate ?

Issues with external access to HomeBridge are a homebridge issue, and need bringing up over on the homebridge github issues page at https://github.com/nfarina/homebridge/issues

As for the gate... no plugins for homebridge/Domoticz thus far have Service.Door support as of yet, so if you’re relying on a homebridge plugin to link you to Domoticz, commands requesting to “open” or “close” a door/gate won’t work. Homebridge will simply see your door/gate as an on/off switch, so will only recognise “turn on/off [Domoticz name of door device]”.

For Door / Gate support via the eDomoticz plugin, post the device JSON output for your doors / gates to the eDomoticz github issues page and I’ll add it in.

OK, maybe a stupid question, but does somebody has this already working on a Synology? If yes: how?
I cannot find it in the many replies and topics.