gomba777 Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 @ggpublic ok 100 fois mieux j'ai peut être un peu exageré :-) J'ai un thermostat horstman mais je n'ai pas vérifié si il se mettait àjour. Par contre j'ai 6 vannes danfoss et làça fonctionne. Dis siri règle le chauffage du rez de chaussée sur 21 degré et il passe l'ordre àtoutes les vannes du rez.
JossAlf Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 Je ne cherche pas a "survendre" EVE (j'ai railleurs téléchargé MyHome il y a 15 jours sans l'utiliser car je n'ai pas remis en route Homebridge) Je donne les caractéristiques pour que chacun puisse choisir en fonction de ses besoins. Pour ta question sur le type d'accessoire lumière : Le réglage se fait dans les pref (engrenage) dans Accessoires en troisième ligne "utilisé pour" tu as 3 types "Ampoule", "Ventilateur", "Autre". Un plus pour certain : Eve est entièrement en Français.
ggpublic Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 question débile, myHome c'est laquelle (y'en a plusieurs). "myHome App", gratuite qui ressemble comme deux gouttes d'eau àl'appli "figaro home center toolkit" ? ou bien c'est l'appli "myHome - Home Automation" payante à8,99 de Joeri Wissemann ou bien c'est l'appli "myHome - All-in-one Smart Home Automation" à9,99 de Vicinno Soft LLC
gomba777 Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 Il faut taper 'MyHome App' dans la recherche de l'app store. Je ne vois plus le prix, il met open à la place mais à mon avis c'était gratuit..
gomba777 Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 @Jossalf ok mais quand je vais sur accessoire dans Eve, je ne retrouve que la pièce qui a été importée comme accessoire et donc par exemple 'Dressing' je peux lui dire que c'est une lumière mais par contre Dressing contient d'autres trucs que des lumières. Par contre dans Myhome j'ai pu aller sur chaque device contenu dans les pièces pour dire si c'était une prise ou une lampe. mais peut être que je suis passé àcôté?!
ggpublic Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 les deux apps qui ont l'air bien sont payantes. MyHome app a l'air vraiment basique
ggpublic Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 @ggpublic Par contre j'ai 6 vannes danfoss et là ça fonctionne. Dis siri règle le chauffage du rez de chaussée sur 21 degré et il passe l'ordre à toutes les vannes du rez. quand bien meme j'arriverais à importer mon srt 321, je ne vois pas d'accessoire que l'on puise déclarer comme thermostat tes danfoss apparaissent comme accessoire dans ton app (myHome) ?
Thibal34 Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 Sorry @Thibal34, the second command should also "npm" and not "ppm". The config.json should be in: ~/.homebridge[/size] Thanks what i have to do when i have change the config file. Thanks
ilcato Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 Thanks what i have to do when i have change the config file. Thanks run homebridge at the terminal in order to test it. If it works you can then setup an autostart mechanism.
ilcato Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 quand bien meme j'arriverais à importer mon srt 321, je ne vois pas d'accessoire que l'on puise déclarer comme thermostat tes danfoss apparaissent comme accessoire dans ton app (myHome) ? Until now I only implemented Danfoss thermostats. In order to support other kind of devices I need some documentation from you. Are you available for supporting this activity?
ilcato Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 question débile, myHome c'est laquelle (y'en a plusieurs). "myHome App", gratuite qui ressemble comme deux gouttes d'eau à l'appli "figaro home center toolkit" ? ou bien c'est l'appli "myHome - Home Automation" payante à 8,99 de Joeri Wissemann ou bien c'est l'appli "myHome - All-in-one Smart Home Automation" à 9,99 de Vicinno Soft LLC My app "Fibaro home center toolkit" is based on a sample app from Apple called HMCatalog. It is a stripped down version on which I added specific Fibaro Home Center functionalities. MyHome app is essentially HMCatalog.
ggpublic Posté(e) le 25 janvier 2016 Signaler Posté(e) le 25 janvier 2016 @ilcato sure I am. The thermostat I am talking about (srt321) is rather popular among zwave thermostats. Just pm what you need to get in order to move forward. Sent from my iPad using Tapatalk
ggpublic Posté(e) le 26 janvier 2016 Signaler Posté(e) le 26 janvier 2016 J'ai aussi ce problème récurrent de Eve qui ne se met plus à jour. Le seul moyen pour moi est de changer le username du bridge (codé comme une adresse MAC) , de nettoyer le répertoire "persist", Reboot et recommencer la config. ça marche aussi chez moi, le problème c'est que ça n'efface pas les anciens devices dans la database homekit et on se retrouve avec des devices "morts" qui polluent la base car chaque device doit comporter un nom siri unique. Il faudrait vraiment un systeme de reset homebridge dans la base homekit
gomba777 Posté(e) le 26 janvier 2016 Signaler Posté(e) le 26 janvier 2016 @ggpublic, quand ça m'arrivait, j'effaçais aussi la db homekit. J'avais tout le temps ce problème aussi après quelques heures ou 1 jour max eve ne se mettait plus àjour. Ce qui semble avoir réglé le problème chez moi (+de 10 jours up pour l'instant) c'est la mise àjour de homebridge et homebridge-fibaro-hc2 avec npm -g update homebridge et npm -g update homebridge-fibaro-hc2 ...
ilcato Posté(e) le 27 janvier 2016 Signaler Posté(e) le 27 janvier 2016 Just released version 0.5.3 of the plugin. Version 0.5.3 Added support for Horstmann thermostat (eg.: Horstmann HRT4-ZW, Secure SRT321, ...) 1
971jmd Posté(e) le 28 janvier 2016 Signaler Posté(e) le 28 janvier 2016 je suis désespérer j'ai 7x l'installe sur plusieur tuto et toujours pareille..... HELP gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/4.0.0" gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/.node-gyp" gyp WARN install got an error, rolling back install gyp WARN install got an error, rolling back install gyp ERR! configure error gyp ERR! stack Error: ENOSPC: no space left on device, mkdir '/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/.node-gyp' gyp ERR! stack at Error (native) gyp ERR! System Linux 3.18.11-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/hap-nodejs/node_modules/curve25519 gyp ERR! node -v v4.0.0 gyp ERR! node-gyp -v v3.0.1 gyp ERR! not ok npm ERR! Linux 3.18.11-v7+ npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge" npm ERR! node v4.0.0 npm ERR! npm v2.14.2 npm ERR! code ELIFECYCLE npm ERR! bignum@0.11.0 install: `node-gyp configure build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bignum@0.11.0 install script 'node-gyp configure build'. npm ERR! This is most likely a problem with the bignum package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp configure build npm ERR! You can get their info via: npm ERR! npm owner ls bignum npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR!
ggpublic Posté(e) le 28 janvier 2016 Signaler Posté(e) le 28 janvier 2016 well done Ilcato and thanks much for the amazing reactivity. je ne sais pas si qqn a rencontré le problème : j'affecte mes accessoires à mes pieces via une app homekit (Eve ou myHome), cela fonctionne mais uniquement une journée. Le lendemain, tout se retrouve de nouveau dans la pièce principale "Domicile". une idée du problème ? (je précise que j'ai plusieurs appareils iOS, je ne sais pas comment se fait la synchro des données homekit). D'ailleurs, savez vous où est hébergée la db homekit ? cloud apple ?
ilcato Posté(e) le 28 janvier 2016 Signaler Posté(e) le 28 janvier 2016 je suis désespérer j'ai 7x l'installe sur plusieur tuto et toujours pareille..... HELP gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/4.0.0" gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/.node-gyp" gyp WARN install got an error, rolling back install gyp WARN install got an error, rolling back install gyp ERR! configure error gyp ERR! stack Error: ENOSPC: no space left on device, mkdir '/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/.node-gyp' gyp ERR! stack at Error (native) gyp ERR! System Linux 3.18.11-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/hap-nodejs/node_modules/curve25519 gyp ERR! node -v v4.0.0 gyp ERR! node-gyp -v v3.0.1 gyp ERR! not ok npm ERR! Linux 3.18.11-v7+ npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge" npm ERR! node v4.0.0 npm ERR! npm v2.14.2 npm ERR! code ELIFECYCLE npm ERR! bignum@0.11.0 install: `node-gyp configure build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bignum@0.11.0 install script 'node-gyp configure build'. npm ERR! This is most likely a problem with the bignum package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp configure build npm ERR! You can get their info via: npm ERR! npm owner ls bignum npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! What platform are you installing on? It seems that you have no more space on your device. Are you installing with sudo?
971jmd Posté(e) le 28 janvier 2016 Signaler Posté(e) le 28 janvier 2016 bonjour j'ai suivi le tuto à la lettre https://detintelligentehjem.dk/blog/FibaroHC2HB/ mai juste à la fin j'ai un soucie Quand le lance homebridg : pi@raspberrypi:~ $ sudo su root@raspberrypi:/home/pi# 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> Loaded plugin: homebridge-fibaro-hc2 Registering platform 'homebridge-fibaro-hc2.FibaroHC2' --- Loaded config.json with 2 accessories and 1 platforms. --- Loading 1 platforms... [FibaroHC2] Initializing FibaroHC2 platform... [FibaroHC2] Fetching Fibaro Home Center rooms... Loading 2 accessories... /usr/local/lib/node_modules/homebridge/lib/api.js:47 throw new Error("The requested accessory '" + name + "' was not registered by any plugin."); ^ Error: The requested accessory 'Http' was not registered by any plugin. at API.accessory (/usr/local/lib/node_modules/homebridge/lib/api.js:47:13) at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:164:42) at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:36:38) at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:23:16) at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22) at Module._compile (module.js:434:26) at Object.Module._extensions..js (module.js:452:10) at Module.load (module.js:355:32) at Function.Module._load (module.js:310:12) at Function.Module.runMain (module.js:475:10) root@raspberrypi:/home/pi# Quand le lance sudo forever list: sudo: forever: command not found
ilcato Posté(e) le 28 janvier 2016 Signaler Posté(e) le 28 janvier 2016 bonjour j'ai suivi le tuto à la lettre https://detintelligentehjem.dk/blog/FibaroHC2HB/ mai juste à la fin j'ai un soucie Quand le lance homebridg : pi@raspberrypi:~ $ sudo su root@raspberrypi:/home/pi# 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> Loaded plugin: homebridge-fibaro-hc2 Registering platform 'homebridge-fibaro-hc2.FibaroHC2' --- Loaded config.json with 2 accessories and 1 platforms. --- Loading 1 platforms... [FibaroHC2] Initializing FibaroHC2 platform... [FibaroHC2] Fetching Fibaro Home Center rooms... Loading 2 accessories... /usr/local/lib/node_modules/homebridge/lib/api.js:47 throw new Error("The requested accessory '" + name + "' was not registered by any plugin."); ^ Error: The requested accessory 'Http' was not registered by any plugin. at API.accessory (/usr/local/lib/node_modules/homebridge/lib/api.js:47:13) at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:164:42) at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:36:38) at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:23:16) at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22) at Module._compile (module.js:434:26) at Object.Module._extensions..js (module.js:452:10) at Module.load (module.js:355:32) at Function.Module._load (module.js:310:12) at Function.Module.runMain (module.js:475:10) root@raspberrypi:/home/pi# Quand le lance sudo forever list: sudo: forever: command not found It seems that you have configured in config.js an http accessory but you didn't install the corresponding plugin. Can you send me the config.json file?
971jmd Posté(e) le 28 janvier 2016 Signaler Posté(e) le 28 janvier 2016 Une autre question a quoi correspond l'adresse MAC ? Mon fichier est il ok ? merci d'avance { "bridge": { "name": "HomebridgeMAC", "username": "xx:xx:xx:xx:xx:xx", "port": 51826, "pin": "031-45-154" }, "description": "This is an example configuration file. You can use this as a template for creating your own configuration file.", "platforms": [{ "platform": "FibaroHC2", "name": "FibaroHC2", "host": "192.168.xx.x", "username": "xxxx", "password": "xxxx" } ], "accessories": [{ "accessory": "Http", "name": "Lampe salon", "on_url": "http://admin:xxxx@192.168.x.x/api/callAction?deviceID=274&name=turnOn", "off_url": "http://admin:xxxx@192.168.x.x/api/callAction?deviceID=274&name=turnOff", "http_method": "GET" }, { "accessory": "Http", "name": "Lampe salon2", "on_url": "http://admin:xxxxx@192.168.x.x/api/callAction?deviceID=367&name=turnOn", "off_url": "http://admin:xxxxx@192.168.x.x/api/callAction?deviceID=367&name=turnOff", "http_method": "GET" }] }
971jmd Posté(e) le 29 janvier 2016 Signaler Posté(e) le 29 janvier 2016 Je n'ai pas de problème d'arrêt automatique. Cela fait une bonne semaine que ça tourne. Par contre je n'utilises pas forever mais un script init rc.d pour le démarrage automatique. Mais est-ce que ton rpi reboote régulièrement car le process ne doit pas s'arrêter. je suis sous raspberry PI 2 SD de 32 voila plus d'une semaine que je suis la chose et je n'y arrive toujours pas y-t-il une âme charitable pour m'aider svp
ilcato Posté(e) le 29 janvier 2016 Signaler Posté(e) le 29 janvier 2016 Une autre question a quoi correspond l'adresse MAC ? Mon fichier est il ok ? merci d'avance { "bridge": { "name": "HomebridgeMAC", "username": "xx:xx:xx:xx:xx:xx", "port": 51826, "pin": "031-45-154" }, "description": "This is an example configuration file. You can use this as a template for creating your own configuration file.", "platforms": [{ "platform": "FibaroHC2", "name": "FibaroHC2", "host": "192.168.xx.x", "username": "xxxx", "password": "xxxx" } ], "accessories": [{ "accessory": "Http", "name": "Lampe salon", "on_url": "http://admin:xxxx@192.168.x.x/api/callAction?deviceID=274&name=turnOn", "off_url": "http://admin:xxxx@192.168.x.x/api/callAction?deviceID=274&name=turnOff", "http_method": "GET" }, { "accessory": "Http", "name": "Lampe salon2", "on_url": "http://admin:xxxxx@192.168.x.x/api/callAction?deviceID=367&name=turnOn", "off_url": "http://admin:xxxxx@192.168.x.x/api/callAction?deviceID=367&name=turnOff", "http_method": "GET" }] } As I mentioned before you are specifying two accessories in the config.json file (Lampe salon and Lampe salon2) that are based on a different plugin (the Http one) that you didn't install. Try to remove this accessories and run only the Fibaro plugin. After it works you can add the other ones. Leave in the "username" the original value. It is not related to the MAC address of the PI.
971jmd Posté(e) le 29 janvier 2016 Signaler Posté(e) le 29 janvier 2016 l { "bridge": { "name": "Homebridgejmd", "username": "CC:22:3D:E3:CE:30", "port": 51826, "pin": "031-45-154" }, "description": "This is an example configuration file. You can use this as a template for creating your own $ "platforms": [ ], "accessories": [{ "accessory": "Http", "name": "Lampe salon", "on_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=274&name=turnOn", "off_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=274&name=turnOff", "http_method": "GET" }, { "accessory": "Http", "name": "Lampe salon2", "on_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=367&name=turnOn", "off_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=367&name=turnOff", "http_method": "GET" }] } sudo homebridge résultat : sudo 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=libd ns_sd&e=node> *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not su pported (or only supported partially) in the Apple Bonjour compatibility layer o f Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libd ns_sd&e=node&f=DNSServiceRegister> Loaded plugin: homebridge-fibaro-hc2 Registering platform 'homebridge-fibaro-hc2.FibaroHC2' --- Loaded config.json with 0 accessories and 1 platforms. --- Loading 1 platforms... [FibaroHC2] Initializing FibaroHC2 platform... [FibaroHC2] Fetching Fibaro Home Center rooms... Loading 0 accessories... [FibaroHC2] Fetching Fibaro Home Center devices... [FibaroHC2] Found: com.fibaro.temperatureSensor [FibaroHC2] Found: com.fibaro.seismometer [FibaroHC2] Found: com.fibaro.lightSensor [FibaroHC2] Found: com.fibaro.temperatureSensor [FibaroHC2] Found: com.fibaro.FGMS001 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.FGRM222 [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.ipCamera [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.FGRM222 [FibaroHC2] Found: com.fibaro.FGRGBW441M [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.ipCamera [FibaroHC2] Found: com.fibaro.doorSensor [FibaroHC2] Found: HC_user [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwavePrimaryController [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: weather [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: HC_user [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.remoteController [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: iOS_device [FibaroHC2] Found: iOS_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.lightSensor [FibaroHC2] Found: com.fibaro.humiditySensor [FibaroHC2] Found: com.fibaro.multilevelSensor [FibaroHC2] Initializing platform accessory 'VARIABLE'... [FibaroHC2] Initializing platform accessory 'IOS Info v1.00'... [FibaroHC2] Initializing platform accessory 'Passer Cable ou Apple'... [FibaroHC2] Initializing platform accessory 'Aube'... [FibaroHC2] Initializing platform accessory 'Presence Ipade'... [FibaroHC2] Initializing platform accessory 'Presence_ HS'... [FibaroHC2] Initializing platform accessory 'Mode ECO'... [FibaroHC2] Initializing platform accessory 'Mode Nuit OFF'... [FibaroHC2] Initializing platform accessory 'Mode Nuit ON'... [FibaroHC2] Initializing platform accessory 'Désactive scéne '... [FibaroHC2] Initializing platform accessory 'PCGEA'... [FibaroHC2] Initializing platform accessory 'clime'... [FibaroHC2] Initializing platform accessory 'TV sony'... [FibaroHC2] Initializing platform accessory 'Appel TV'... [FibaroHC2] Initializing platform accessory 'Logitech'... [FibaroHC2] Initializing platform accessory 'On Off General'... [FibaroHC2] Initializing platform accessory 'Numericable'... [FibaroHC2] Initializing platform accessory 'Radio'... [FibaroHC2] Initializing platform accessory 'Réglage LP cuisine'... [FibaroHC2] Initializing platform accessory 'Alarm Clim OFF'... [FibaroHC2] Initializing platform accessory 'Dodo'... [FibaroHC2] Initializing platform accessory 'Alarm Clim On'... [FibaroHC2] Initializing platform accessory 'Climatiseur'... [FibaroHC2] Initializing platform accessory 'var 10 on off'... [FibaroHC2] Initializing platform accessory 'GEA Alarm on 323'... [FibaroHC2] Initializing platform accessory 'GEA Off 324'... [FibaroHC2] Initializing platform accessory 'sarah'... [FibaroHC2] Initializing platform accessory 'Alarm Clim On'... /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js: 175 throw new Error("Cannot add a bridged Accessory with the same UUID as anot her bridged Accessory: " + existing.UUID); ^ Error: Cannot add a bridged Accessory with the same UUID as another bridged Acce ssory: dd392522-c377-4d94-89d7-548531d21e90 at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebri dge/node_modules/hap-nodejs/lib/Accessory.js:175:13) at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js: 224:24) at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/o nce.js:15:19 at Request._callback (/usr/local/lib/node_modules/homebridge-fibaro-hc2/inde x.js:208:9) at Request.self.callback (/usr/local/lib/node_modules/homebridge-fibaro-hc2/ node_modules/request/request.js:199:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7) at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-fibaro-hc2/no de_modules/request/request.js:1036:10) at emitOne (events.js:82:20) at Request.emit (events.js:169:7)
ilcato Posté(e) le 29 janvier 2016 Signaler Posté(e) le 29 janvier 2016 l { "bridge": { "name": "Homebridgejmd", "username": "CC:22:3D:E3:CE:30", "port": 51826, "pin": "031-45-154" }, "description": "This is an example configuration file. You can use this as a template for creating your own $ "platforms": [ ], "accessories": [{ "accessory": "Http", "name": "Lampe salon", "on_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=274&name=turnOn", "off_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=274&name=turnOff", "http_method": "GET" }, { "accessory": "Http", "name": "Lampe salon2", "on_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=367&name=turnOn", "off_url": "http://admin:xxxxx@192.168.0.5/api/callAction?deviceID=367&name=turnOff", "http_method": "GET" }] } sudo homebridge résultat : sudo 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=libd ns_sd&e=node> *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not su pported (or only supported partially) in the Apple Bonjour compatibility layer o f Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libd ns_sd&e=node&f=DNSServiceRegister> Loaded plugin: homebridge-fibaro-hc2 Registering platform 'homebridge-fibaro-hc2.FibaroHC2' --- Loaded config.json with 0 accessories and 1 platforms. --- Loading 1 platforms... [FibaroHC2] Initializing FibaroHC2 platform... [FibaroHC2] Fetching Fibaro Home Center rooms... Loading 0 accessories... [FibaroHC2] Fetching Fibaro Home Center devices... [FibaroHC2] Found: com.fibaro.temperatureSensor [FibaroHC2] Found: com.fibaro.seismometer [FibaroHC2] Found: com.fibaro.lightSensor [FibaroHC2] Found: com.fibaro.temperatureSensor [FibaroHC2] Found: com.fibaro.FGMS001 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.FGRM222 [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.ipCamera [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.FGRM222 [FibaroHC2] Found: com.fibaro.FGRGBW441M [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.ipCamera [FibaroHC2] Found: com.fibaro.doorSensor [FibaroHC2] Found: HC_user [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwavePrimaryController [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.binarySwitch [FibaroHC2] Found: weather [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: HC_user [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.remoteController [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: iOS_device [FibaroHC2] Found: iOS_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: com.fibaro.multilevelSwitch [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: virtual_device [FibaroHC2] Found: com.fibaro.FGWP101 [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.motionSensor [FibaroHC2] Found: com.fibaro.zwaveDevice [FibaroHC2] Found: com.fibaro.lightSensor [FibaroHC2] Found: com.fibaro.humiditySensor [FibaroHC2] Found: com.fibaro.multilevelSensor [FibaroHC2] Initializing platform accessory 'VARIABLE'... [FibaroHC2] Initializing platform accessory 'IOS Info v1.00'... [FibaroHC2] Initializing platform accessory 'Passer Cable ou Apple'... [FibaroHC2] Initializing platform accessory 'Aube'... [FibaroHC2] Initializing platform accessory 'Presence Ipade'... [FibaroHC2] Initializing platform accessory 'Presence_ HS'... [FibaroHC2] Initializing platform accessory 'Mode ECO'... [FibaroHC2] Initializing platform accessory 'Mode Nuit OFF'... [FibaroHC2] Initializing platform accessory 'Mode Nuit ON'... [FibaroHC2] Initializing platform accessory 'Désactive scéne '... [FibaroHC2] Initializing platform accessory 'PCGEA'... [FibaroHC2] Initializing platform accessory 'clime'... [FibaroHC2] Initializing platform accessory 'TV sony'... [FibaroHC2] Initializing platform accessory 'Appel TV'... [FibaroHC2] Initializing platform accessory 'Logitech'... [FibaroHC2] Initializing platform accessory 'On Off General'... [FibaroHC2] Initializing platform accessory 'Numericable'... [FibaroHC2] Initializing platform accessory 'Radio'... [FibaroHC2] Initializing platform accessory 'Réglage LP cuisine'... [FibaroHC2] Initializing platform accessory 'Alarm Clim OFF'... [FibaroHC2] Initializing platform accessory 'Dodo'... [FibaroHC2] Initializing platform accessory 'Alarm Clim On'... [FibaroHC2] Initializing platform accessory 'Climatiseur'... [FibaroHC2] Initializing platform accessory 'var 10 on off'... [FibaroHC2] Initializing platform accessory 'GEA Alarm on 323'... [FibaroHC2] Initializing platform accessory 'GEA Off 324'... [FibaroHC2] Initializing platform accessory 'sarah'... [FibaroHC2] Initializing platform accessory 'Alarm Clim On'... /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js: 175 throw new Error("Cannot add a bridged Accessory with the same UUID as anot her bridged Accessory: " + existing.UUID); ^ Error: Cannot add a bridged Accessory with the same UUID as another bridged Acce ssory: dd392522-c377-4d94-89d7-548531d21e90 at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebri dge/node_modules/hap-nodejs/lib/Accessory.js:175:13) at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js: 224:24) at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/o nce.js:15:19 at Request._callback (/usr/local/lib/node_modules/homebridge-fibaro-hc2/inde x.js:208:9) at Request.self.callback (/usr/local/lib/node_modules/homebridge-fibaro-hc2/ node_modules/request/request.js:199:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7) at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-fibaro-hc2/no de_modules/request/request.js:1036:10) at emitOne (events.js:82:20) at Request.emit (events.js:169:7) You have different device (probably virtual devices) with the same name: Alarm Clim On This is not possible in Homebridge
Messages recommandés