Hi TheRamon,TheRamon wrote:Awst6000 wrote:I also tried the parameter usescenes, but still no luck.
Hi, have just checked. there is no usescenes or loadscenes parameter. We would have to build this. I'll check this out
I'm not sure what the Domoticz plugin is, but this plugin is called eDomoticz. I did not know there was a 'Domoticz' plugin..Awst6000 wrote:Hi TheRamon,TheRamon wrote:Awst6000 wrote:I also tried the parameter usescenes, but still no luck.
Hi, have just checked. there is no usescenes or loadscenes parameter. We would have to build this. I'll check this out
Is this other software? How can I check this?
https://github.com/nfarina/homebridge/pull/129/files
Txs
So yeah, I think it's other software.Hi MaKin,MaKin wrote:Hello everyone,
I am coming from Home-Assistant so please excuse my lack of knowledge regarding Domoticz.
Can you tell me how to have Temperature and Humidity sensors shown in the iOS Homeapp? I added my mysensors devices to domoticz and they are listed as following:
TempHum Livingroom (Temp is shown, Humidity can be found under details)
TempHum Bedroom (Temp is shown, Humidity can be found under details)
Hum Livingroom ("not yet supported" is shown)
Hum Bedroom ("not yet supported" is shown)
This is weird, as the sensors actually are made up like this NodeX with two children (V_HUM, V_TEMP).
Is there a simple way to have temperature and humidity listed?
Thanks in advance.
Also another strange behavior is, that under devices there is a MySensors "Security Device" from type "Lighting 2" and Subtype "AC" listed. Any idea what this is supposed to mean?
i search for the file but there is no homebridge.err fileTheRamon wrote:Sounds like that could do the job. More interesting is why homebridge crashes / hangs though. You should try and get the contents of /var/log/homebridge.err before you restart. There might be something in there.
That's from the original Domoticz homebridge plugin shipped with earlier Domoticz releases... hasn't been in active development for 2 years, and only supported on/off switches and dimmers. Completely different plugin.Awst6000 wrote:Hi TheRamon,TheRamon wrote:Awst6000 wrote:I also tried the parameter usescenes, but still no luck.
Hi, have just checked. there is no usescenes or loadscenes parameter. We would have to build this. I'll check this out
Is this other software? How can I check this?
https://github.com/nfarina/homebridge/pull/129/files
Txs
Run...bing69 wrote:i search for the file but there is no homebridge.err fileTheRamon wrote:Sounds like that could do the job. More interesting is why homebridge crashes / hangs though. You should try and get the contents of /var/log/homebridge.err before you restart. There might be something in there.
Code: Select all
sudo touch /var/log/homebridge.err
sudo chmod 777 /var/log/homebridge.err
I have a cron job set up which restarts Domoticz & Homebridge every 24hrs, alongside a switch in Domoticz for manual restarts of homebridge when required.bing69 wrote:thanks for your response. For now I solved it by creating a dummy switch and hang a script with the content: sudo service home bridge starts.
These switches every 6 hours and solves the time being.
This does not deserve any prizes and I'm looking also for a good solution.
Curious to know what your Cron Job look like. Is it advisable to restart everyday?Marci wrote:I have a cron job set up which restarts Domoticz & Homebridge every 24hrs, alongside a switch in Domoticz for manual restarts of homebridge when required.
Code: Select all
systemctl restart domoticz && systemctl restart homebridge
Code: Select all
30 02 * * * /root/monitor.shMaybe this can help?TheRamon wrote: Hehehe, alright. I have just reverted the setcolbrightnessvalue commit since it's not yet working 100%.. Does not have support for RGB values and such. I'll wait for Domoticz to implement that, too..
I'm completely stuck and I hope someone is able to give me some general directions..Marci wrote:[...]Code: Select all
sudo service homebridge stop sudo npm set prefix '/usr' -g sudo npm update -g homebridge --unsafe-perm sudo npm update -g homebridge-edomoticz --unsafe-perm cd /usr/lib/node_modules sudo npm rebuild homebridge sudo npm rebuild homebridge-edomoticzLaunch homebridge!Code: Select all
sudo pico ~/.homebridge/config.jsonCode: Select all
homebridge
Yes, thank you so much but the MQTT call itself does not support a RGB value yet. I'm happy to convert to Hue, saturation and brightness but 'saturation' does not work. So we're left with Hue and brightness. We really need to wait for Domoticz to get full color support instead of only the brightest of the bunch. (100% saturation).G3rard wrote:Maybe this can help?TheRamon wrote: Hehehe, alright. I have just reverted the setcolbrightnessvalue commit since it's not yet working 100%.. Does not have support for RGB values and such. I'll wait for Domoticz to implement that, too..
http://www.domoticz.com/forum/viewtopic ... 38&t=14941
https://github.com/t0mg/reacticz/blob/m ... tchRGBW.js
It is also using MQTT and I can change the colors of my Hue lights.
But I have no RGB lights, so not sure if this is the solution you're searching for
Hi,matv wrote: I'm completely stuck and I hope someone is able to give me some general directions..
After following the outdated Wiki and finding out that that is not the way to go anymore I started with these instructions.
Being completely new to Unix it naturally involves a lot of trial and error for me..
The first error I get when executing the code above;
-bash: cd: /usr/lib/node_modules: No such file or directory
I found that there's a way to search with find / -name "node_modules" and that showed the location of the folder:
/usr/local/lib/node_modules
I then changed the code on top, replcaing cd /usr/lib/node_modules with the path I just found.
The error is gone but when is type ls in /usr/local/lib/node_modules, I only see a folder called npm with the following contents:
Could someone provide me with some tips on how to proceed? All the folders, Node-installs and file locations are getting a bit too much to oversee at this point.. Thanks in advance!
Code: Select all
* Installing homebridge and the plugin *
sudo service homebridge stop
sudo npm set prefix '/usr/local' -g
sudo npm install -g homebridge --unsafe-perm
sudo npm install -g homebridge-edomoticz --unsafe-perm
cd /usr/local/lib/node_modules
sudo npm rebuild homebridge
sudo npm rebuild homebridge-edomoticz
* To edit your config: *
sudo nano -w ~/.homebridge/config.json
* Starting homebridge *
homebridge
* Auto-starting homebridge *
sudo service homebridge startCode: Select all
pi@raspberrypi:~ $ cd /usr/local/lib/node_modules
pi@raspberrypi:/usr/local/lib/node_modules $ sudo npm rebuild homebridge
> [email protected] install /usr/local/lib/node_modules/homebridge/node_modules/curve25519-n
> node-gyp rebuild
gyp ERR! clean error
gyp ERR! stack Error: EACCES: permission denied, unlink 'build/Makefile'
gyp ERR! stack at Error (native)
gyp ERR! System Linux 4.4.38-v7+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/homebridge/node_modules/curve25519-n
gyp ERR! node -v v6.3.1
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm ERR! Linux 4.4.38-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "rebuild" "homebridge"
npm ERR! node v6.3.1
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the curve25519-n package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs curve25519-n
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls curve25519-n
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /usr/local/lib/node_modules/npm-debug.log