homebridge-edomoticz Plugin

Marci · Post by **Marci** » Monday 01 February 2016 17:49

steppi wrote: My AVR can be connected via telnet and precise commands ..
Do you have any idea?

thank you! Hello!!

Shell script which sends relevant commands, Domoticz virtual switch which calls the script... but that's a Domoticz general thang rather than eDomoticz plugin thang. eDomoticz will handle whatever switches you setup in Domoticz.

DOM5525 · Post by **DOM5525** » Monday 01 February 2016 18:32

I have a Homekit deadbolt installed, Schlage Sense. Would I be able to use this plugin to get the status of the deadbolt locked / unlocked into domoticz? The way this all reads is that devices in domoticz can be made available in Homekit. I need it to go the other way and get the status of my deadbolt in domoticz.

thanks!

Marci · Post by **Marci** » Monday 01 February 2016 19:42

Nope... ‘fraid not, sorry! You need to ask the Domoticz devs to write support into Domoticz for it, or work out how to access it without using home kit (e.g.: http query over wifi, bluetooth query).

Heisenberg · Post by **Heisenberg** » Monday 01 February 2016 20:34

Thank you for the updated eDomoticz Homebridge plugin. However when I follow the installation guide and copy the configuration file I get the following:

Code: Select all

pi@domoticzpi ~/homebridge $ sudo npm ls -g homebridge
/usr/local/lib
└── (empty)

npm ERR! code 1

deejc · Post by **deejc** » Monday 01 February 2016 20:50

updated to the plugin version, removed the legacy plugin but it seems to no longer respect the "Room" entry in the config.json again.

i also have a youless meter in Domoticz but it does not seem to show that in the Home App..

Jem101 · Post by **Jem101** » Monday 01 February 2016 21:18

I can second that, it's now loading all devices rather than just those defined in the room ID.

Also another odd thing, I have a couple of thermometer/humidity sensors in various rooms. In the older legacy version, these appeared as 'dimmer-type' devices where the actual temperature figure (in deg. C) was given but as a percentage - a bit annoying but not too bad.

With this version though I'm seeing the sensors shown as a simple On/Off button with no actual values being returned. The same with my electricity consumption meter which didn't show up before but now does, but as a simple On/Off button.

Is there something I need to edit in any Config to get these working properly?

Nautilus · Post by **Nautilus** » Tuesday 02 February 2016 12:18

Jem101 wrote:I have a couple of thermometer/humidity sensors in various rooms. In the older legacy version, these appeared as 'dimmer-type' devices where the actual temperature figure (in deg. C) was given but as a percentage - a bit annoying but not too bad.

With this version though I'm seeing the sensors shown as a simple On/Off button with no actual values being returned.

Just updated the Homebridge (I was still running the old version without plugins) and changed from legacy Domoticz to eDomoticz. Everything looked fine at first but I also noticed that only pure Temp sensors show an actual temperature value, Temp/Hum sensrors (which I have a majority off) show as type other (plug) on/off. It would be very nice to see these as temp (and why not also hum) devices with a value available

I can also confirm that roomid does not seem to result in any restriction of loaded devices. I was wondering why Eve iOS app did not want to pair with the bridge and learned that there is a limit of 100 devices per bridge (though some source said that a bridge can connect to another bridge). So I tried to limit the number of Domoticz devices with roomid but that did not work. Then after removing other platforms I was finally able to run it

All in all, a very good improvement for the legacy plugin, it is nice to see the actual value in Eve + other device types as well. Thanks a lot!

Marci · Post by **Marci** » Tuesday 02 February 2016 18:19

If you can hit your temp/hum sensors via json.htm, then Open a new issue over on the GitHub repo including the output from the json api, I’ll get round to it at somepoint! In meantime, supported Domoticz sensor types are listed in the OP.

https://www.domoticz.com/wiki/Domoticz_ ... fic_device

Marci · Post by **Marci** » Tuesday 02 February 2016 18:22

Heisenberg wrote:Thank you for the updated eDomoticz Homebridge plugin. However when I follow the installation guide and copy the configuration file I get the following:
Code: Select all
pi@domoticzpi ~/homebridge $ sudo npm ls -g homebridge
/usr/local/lib
└── (empty)

npm ERR! code 1

Only works with latest Homebridge, not the version on the Domoticz RPi SD card image - you need to install Homebridge via npm...

Install latest homebridge from npm if you don’t already have it...
Code: Select all
sudo npm install -g homebridge

Marci · Post by **Marci** » Tuesday 02 February 2016 18:25

deejc wrote:updated to the plugin version, removed the legacy plugin but it seems to no longer respect the "Room" entry in the config.json again.

i also have a youless meter in Domoticz but it does not seem to show that in the Home App..

Haven't written support for Youless as don't have one. Get me the json for it - see https://www.domoticz.com/wiki/Domoticz_ ... fic_device - then Open a new issue over on the GitHub repo including the output from the json api, I’ll get round to it at somepoint! In meantime, supported Domoticz sensor types are listed in the OP.

Room thang - will fix again... Soz! Fixed.

Marci · Post by **Marci** » Tuesday 02 February 2016 18:28

Jem101 wrote:
With this version though I'm seeing the sensors shown as a simple On/The same with my electricity consumption meter which didn't show up before but now does, but as a simple On/Off button.

Is there something I need to edit in any Config to get these working properly?

Your elec sensor doesn't fall under Type: General, SubType: kWh in Domoticz, therefore won't display. I'd need json.htm output for it to add support, then Open a new issue over on the GitHub repo including the output from the json api, I’ll get round to it at somepoint! In meantime, supported Domoticz sensor types are listed in the OP.

See https://www.domoticz.com/wiki/Domoticz_ ... fic_device

Marci · Post by **Marci** » Tuesday 02 February 2016 19:18

Room thang - fixed! Grab index.js from the git repo (link in sig) and overwrite the one in /usr/local/lib/node_modules/homebridge-eDomoticz/ then clear persist and restart homebridge. Sorry about that!

Heisenberg · Post by **Heisenberg** » Tuesday 02 February 2016 21:06

Install latest homebridge from npm if you don’t already have it...
Code: Select all
sudo npm install -g homebridge

If I install the latest homebridge I run into this error. What should I do?

Code: Select all

pi@domoticzpi ~ $ sudo npm install -g homebridge
npm ERR! addLocal Could not install /tmp/npm-4885-f389f5b0/git-cache-8f8e52588e4                               9/2a8f1303712c6b6f10eaf49c80f6db7ef21e4336
npm ERR! Linux 4.1.13-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge"
npm ERR! node v0.12.6
npm ERR! npm  v2.11.2

npm ERR! No version provided in package.json
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log

Marci · Post by **Marci** » Tuesday 02 February 2016 21:14

Good question... Try:

Code: Select all

sudo apt-get update && sudo apt-get upgrade

...first to update node, npm and the rest of your base packages, then try again.

Otherwise - copy / paste your error as a new issue over at https://GitHub.com/nfarina/homebridge ... Errors installing Homebridge itself are beyond my scope I'm afraid.

batso · Post by **batso** » Tuesday 02 February 2016 21:45

deejc · Post by **deejc** » Tuesday 02 February 2016 23:47

Marci wrote:Open a new issue over on the GitHub repo including the output from the json api

Done

Marci wrote:Room thang - will fix again... Soz! Fixed.

Thanks.. looking good again

Marci · Post by **Marci** » Tuesday 02 February 2016 23:49

*thumbs up*

Marci · Post by **Marci** » Tuesday 02 February 2016 23:57

batso wrote: I still don't have an eDomotics.js in the homebridge/platforms folder.
What did I do wrong?

You're looking in the old install in your home folder at a guess. Ignore that folder.

It's in /usr/local/lib/node_modules/homebridge-eDomoticz

Leave it there.

Code: Select all

cd ~/.homebridge

(Note the dot). This is where config.json goes and where you should find your persist folder.

Start / stop / restart with:

Code: Select all

forever start /usr/local/lib/node_modules/homebridge/bin/homebridge

(Swap out start for stop or restart)

See the link in OP to running at boot up for instructions on installing forever.

You can tail it's output by...

Code: Select all

cd ~/.forever
ls -lt

Get most recent log file name... then

Code: Select all

tail -f ~/.forever/xxxx.log

Ctrl-c to bail on tail and go back to CLI.

batso · Post by **batso** » Wednesday 03 February 2016 17:22

Marci wrote: You're looking in the old install in your home folder at a guess. Ignore that folder.

It's in /usr/local/lib/node_modules/homebridge-eDomoticz

Leave it there.
Code: Select all
cd ~/.homebridge
(Note the dot). This is where config.json goes and where you should find your persist folder.

I don't have a dot-homebridge-folder at

Code: Select all

cd ~/.homebridge

I only have a folder at

Code: Select all

cd ~/homebridge

I don't have the bin folder under:

Code: Select all

/usr/local/lib/node_modules/homebridge/

either

Marci · Post by **Marci** » Wednesday 03 February 2016 19:37

You will only see the .homebridge folder if you do ls -ltra - the . prefix means it’s a hidden folder. Completely ignore ~/homebridge and stop mentioning it - it’s irrelevant to the newer version and just confuses the issue - just forget that folder exists for now.

The .homebridge folder will only be automatically created when you first run the new install of homebridge, at which point it will error and die after prompting you to create a config.json file.

Or, you can just...

Code: Select all

mkdir ~/.homebridge

...to create it manually, then put your config.json file in there.

Make sure you don't run forever with sudo... if you do that, the .homebridge folder will be created in /root rather than ~/

Go to the new homebridge install folder, and show me what’s there... if there’s no bin folder, then homebridge didn’t install.

Code: Select all

pi@rasprf /usr/local/lib/node_modules/homebridge $ ls
bin  config-sample.json  lib  LICENSE  node_modules  package.json  persist  README.md

homebridge-edomoticz Plugin

eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

eDomoticz Homebridge-Plugin

eDomoticz Homebridge-Plugin

eDomoticz Homebridge-Plugin

eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Re: eDomoticz Homebridge-Plugin

Who is online