[TOPIC] Domotique
Publié : mer. 27 janv. 2016 11:23
pareil en interface de jeedom en attendant mieux leur dashboard sont facile à faire et utiliser
+ un peu de tunning et waf ok
+ un peu de tunning et waf ok
En revanche pour utiliser le serveur Open Z-Wave, il faut un autre plugin (en plus du plugin Z-Wave) qui s’appelle Open Z-Wave et est payant.
C'est a vendre pour moins cher qu'un jeedom/rpi/clé zave ?.. et ça va quoi, c'est pas la ruine.
Si tu veux on a des Fibaro Home Center 2 en stock, sous blister à vendre !![]()
Installation de socket.io et express (peut etre très long > 30min)npm ERR! network getaddrinfo ENOTFOUND
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! System Linux 4.2.0-25-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "socket.io"
npm ERR! cwd /usr/share/nginx/www/jeedom/core/nodeJS
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! syscall getaddrinfo
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/share/nginx/www/jeedom/core/nodeJS/npm-debug.log
npm ERR! not ok code 0
npm ERR! network getaddrinfo ENOTFOUND
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! System Linux 4.2.0-25-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "express"
npm ERR! cwd /usr/share/nginx/www/jeedom/core/nodeJS
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! syscall getaddrinfo
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/share/nginx/www/jeedom/core/nodeJS/npm-debug.log
npm ERR! not ok code 0
OK
[END UPDATE SUCCESS]
160127 16:10:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2016-01-27 16:10:50,896 CRIT Supervisor running as root (no user in config file)
2016-01-27 16:10:50,896 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2016-01-27 16:10:50,908 INFO RPC interface 'supervisor' initialized
2016-01-27 16:10:50,908 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2016-01-27 16:10:50,908 INFO RPC interface 'supervisor' initialized
2016-01-27 16:10:50,908 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-01-27 16:10:50,909 INFO supervisord started with pid 1
2016-01-27 16:10:51,911 INFO spawned: 'sshd' with pid 932
2016-01-27 16:10:51,912 INFO spawned: 'nodejs' with pid 933
2016-01-27 16:10:51,914 INFO spawned: 'crond' with pid 934
2016-01-27 16:10:51,915 INFO spawned: 'nginx' with pid 935
2016-01-27 16:10:51,916 INFO spawned: 'mysqld' with pid 936
2016-01-27 16:10:51,917 INFO spawned: 'php5-fpm' with pid 937
2016-01-27 16:10:51,924 INFO exited: crond (exit status 1; not expected)
2016-01-27 16:10:52,993 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-27 16:10:52,993 INFO success: nodejs entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-27 16:10:52,994 INFO spawned: 'crond' with pid 963
2016-01-27 16:10:52,995 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-27 16:10:52,995 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-27 16:10:52,995 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-27 16:10:53,000 INFO exited: crond (exit status 1; not expected)
2016-01-27 16:10:55,004 INFO spawned: 'crond' with pid 965
2016-01-27 16:10:55,010 INFO exited: crond (exit status 1; not expected)
2016-01-27 16:10:58,014 INFO spawned: 'crond' with pid 966
2016-01-27 16:10:58,020 INFO exited: crond (exit status 1; not expected)
2016-01-27 16:10:59,021 INFO gave up: crond entered FATAL state, too many start retries too quickly
2016-01-27 16:11:01,497 CRIT reaped unknown pid 986)
2016-01-27 16:11:01,506 CRIT reaped unknown pid 998)
2016-01-27 16:11:01,512 CRIT reaped unknown pid 1011)
2016-01-27 16:12:01,619 CRIT reaped unknown pid 1033)
2016-01-27 16:12:01,632 CRIT reaped unknown pid 1045)
2016-01-27 16:12:01,638 CRIT reaped unknown pid 1058)
Oui et nonJeedom sans protocole de communication (zwave, EnOcean,rfxcom, knx...) ne sert pas à grand chose !
... à moins de disposer d'ampoule Hue et de systèmes Netatmo.