Hallo,
nachdem ich jetzt mein System halbwegs am laufen habe, wollte ich mich mal um homebridge kümmern... Ich habe anhand der Anleitung homebridge installiert, stelle aber fest, dass es scheinbar 2x auf dem raspi vorhanden ist.
Ich bin genau nach der Anleitung https://wiki.fhem.de/wiki/Homebridge_einrichten vorgegangen und habe bei: "Homebridge konfigurieren
Wichtig: Für die weiteren Schritte sollte man nicht root verwenden, sondern beispielsweise einen dedizierten Nutzer für homebridge oder der Einfachheit halber den Nutzer, unter dem auch FHEM läuft (meist "fhem")." - auf den user fhem gewechselt... da ich bei der config.json einen eigenen code vergeben habe, kann ich sehen, dass unter dem user pi eine homebridge installation läuft, die ich so nicht angelegt habe....
Homebridge unter pi:
pi@raspberrypi:~ $ homebridge
*** WARNING *** The program 'nodejs' 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=nodejs>
*** WARNING *** The program 'nodejs' 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=nodejs&f=DNSServiceRegister>
[2017-3-21 08:19:44] Loaded plugin: homebridge-fhem
homebridge API version: 2.1
this homebridge-fhem 0.3.7
[2017-3-21 08:19:44] Registering platform 'homebridge-fhem.FHEM'
[2017-3-21 08:19:44] ---
[2017-3-21 08:19:44] config.json (/home/pi/.homebridge/config.json) not found.
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
Server listening on: http://<ip>:8282
[2017-3-21 08:19:44] Homebridge is running on port 35322.
Homebridge unter fhem
pi@raspberrypi:~ $ sudo su fhem
fhem@raspberrypi:/home/pi$ homebridge
*** WARNING *** The program 'nodejs' 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=nodejs>
*** WARNING *** The program 'nodejs' 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=nodejs&f=DNSServiceRegister>
[2017-3-21 08:35:05] Loaded plugin: homebridge-fhem
homebridge API version: 2.1
this homebridge-fhem 0.3.7
[2017-3-21 08:35:05] Registering platform 'homebridge-fhem.FHEM'
[2017-3-21 08:35:05] ---
[2017-3-21 08:35:05] Loaded config.json with 0 accessories and 1 platforms.
[2017-3-21 08:35:05] ---
[2017-3-21 08:35:05] Loading 1 platforms...
[2017-3-21 08:35:05] [FHEM] Initializing FHEM platform...
starting longpoll: https://192.168.0.54:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1490081705839
[2017-3-21 08:35:05] [FHEM] Fetching FHEM devices...
[2017-3-21 08:35:05] Loading 0 accessories...
Server listening on: http://<ip>:8282
[2017-3-21 08:35:06] [FHEM] Checking devices and attributes...
[2017-3-21 08:35:06] [FHEM] executing: https://192.168.0.54:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&fwcsrf=csrf_16517432503121&XHR=1
[2017-3-21 08:35:06] [FHEM] executing: https://192.168.0.54:8083/fhem?cmd=jsonlist2%20TYPE=siri&fwcsrf=csrf_16517432503121&XHR=1
[2017-3-21 08:35:06] [FHEM] Fetching FHEM devices...
[2017-3-21 08:35:06] [FHEM] fetching: https://192.168.0.54:8083/fhem?cmd=jsonlist2%20room=Homekit&fwcsrf=csrf_16517432503121&XHR=1
[2017-3-21 08:35:06] [FHEM] no siri device found. please define it.
[2017-3-21 08:35:06] [FHEM] executing: https://192.168.0.54:8083/fhem?cmd=%7B%20addToAttrList(%20%22homebridgeMapping:textField-long%22%20)%20%7D&fwcsrf=csrf_16517432503121&XHR=1
[2017-3-21 08:35:06] [FHEM] homebridgeMapping attribute created.
[2017-3-21 08:35:06] [FHEM] executing: https://192.168.0.54:8083/fhem?cmd=%7BaddToAttrList(%20%22genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock%22%20)%20%7D&fwcsrf=csrf_16517432503121&XHR=1
[2017-3-21 08:35:06] [FHEM] got: 5 results
[2017-3-21 08:35:06] [FHEM] HM_4ADEB3: no service type detected
[2017-3-21 08:35:06] [FHEM] no accessory created for HM_4ADEB3 (CUL_HM)
[2017-3-21 08:35:06] [FHEM] HM_514F4E is thermostat
[2017-3-21 08:35:06] [FHEM] HM_514F4E is NOT a thermostat. set command for target temperature missing:
[2017-3-21 08:35:06] [FHEM] HM_514F4E has
[2017-3-21 08:35:06] [FHEM] StatusLowBattery [battery]
[2017-3-21 08:35:06] [FHEM] FirmwareRevision [D-firmware]
[2017-3-21 08:35:06] [FHEM] CurrentTemperature [measured-temp]
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState [undefined]
2017-03-21 08:35:06 caching: HM_514F4E-battery: ok
[2017-3-21 08:35:06] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2017-03-21 08:35:06 caching: HM_514F4E-D-firmware: 1.3
[2017-3-21 08:35:06] [FHEM] caching: FirmwareRevision: 1.3 (as string; from '1.3')
2017-03-21 08:35:06 caching: HM_514F4E-measured-temp: 20.1
[2017-3-21 08:35:06] [FHEM] caching: CurrentTemperature: 20.1 (as number; from '20.1')
[2017-3-21 08:35:06] [FHEM] caching: CurrentHeatingCoolingState: 1 (as number; means HEAT; from 'mapping.default')
[2017-3-21 08:35:06] [FHEM] HM_515B40 is thermostat
[2017-3-21 08:35:06] [FHEM] HM_515B40 is NOT a thermostat. set command for target temperature missing:
[2017-3-21 08:35:06] [FHEM] HM_515B40 has
[2017-3-21 08:35:06] [FHEM] StatusLowBattery [battery]
[2017-3-21 08:35:06] [FHEM] FirmwareRevision [D-firmware]
[2017-3-21 08:35:06] [FHEM] CurrentTemperature [measured-temp]
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState [undefined]
2017-03-21 08:35:06 caching: HM_515B40-battery: ok
[2017-3-21 08:35:06] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2017-03-21 08:35:06 caching: HM_515B40-D-firmware: 1.3
[2017-3-21 08:35:06] [FHEM] caching: FirmwareRevision: 1.3 (as string; from '1.3')
2017-03-21 08:35:06 caching: HM_515B40-measured-temp: 18.3
[2017-3-21 08:35:06] [FHEM] caching: CurrentTemperature: 18.3 (as number; from '18.3')
[2017-3-21 08:35:06] [FHEM] caching: CurrentHeatingCoolingState: 1 (as number; means HEAT; from 'mapping.default')
[2017-3-21 08:35:06] [FHEM] HM_515B4B is thermostat
[2017-3-21 08:35:06] [FHEM] HM_515B4B is NOT a thermostat. set command for target temperature missing:
[2017-3-21 08:35:06] [FHEM] HM_515B4B has
[2017-3-21 08:35:06] [FHEM] StatusLowBattery [battery]
[2017-3-21 08:35:06] [FHEM] FirmwareRevision [D-firmware]
[2017-3-21 08:35:06] [FHEM] CurrentTemperature [measured-temp]
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState [undefined]
2017-03-21 08:35:06 caching: HM_515B4B-battery: ok
[2017-3-21 08:35:06] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2017-03-21 08:35:06 caching: HM_515B4B-D-firmware: 1.3
[2017-3-21 08:35:06] [FHEM] caching: FirmwareRevision: 1.3 (as string; from '1.3')
2017-03-21 08:35:06 caching: HM_515B4B-measured-temp: 19.2
[2017-3-21 08:35:06] [FHEM] caching: CurrentTemperature: 19.2 (as number; from '19.2')
[2017-3-21 08:35:06] [FHEM] caching: CurrentHeatingCoolingState: 1 (as number; means HEAT; from 'mapping.default')
[2017-3-21 08:35:06] [FHEM] HM_515B5E is thermostat
[2017-3-21 08:35:06] [FHEM] HM_515B5E is NOT a thermostat. set command for target temperature missing:
[2017-3-21 08:35:06] [FHEM] HM_515B5E has
[2017-3-21 08:35:06] [FHEM] StatusLowBattery [battery]
[2017-3-21 08:35:06] [FHEM] FirmwareRevision [D-firmware]
[2017-3-21 08:35:06] [FHEM] CurrentTemperature [measured-temp]
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState [undefined]
2017-03-21 08:35:06 caching: HM_515B5E-battery: ok
[2017-3-21 08:35:06] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2017-03-21 08:35:06 caching: HM_515B5E-D-firmware: 1.3
[2017-3-21 08:35:06] [FHEM] caching: FirmwareRevision: 1.3 (as string; from '1.3')
2017-03-21 08:35:06 caching: HM_515B5E-measured-temp: 19.7
[2017-3-21 08:35:06] [FHEM] caching: CurrentTemperature: 19.7 (as number; from '19.7')
[2017-3-21 08:35:06] [FHEM] caching: CurrentHeatingCoolingState: 1 (as number; means HEAT; from 'mapping.default')
[2017-3-21 08:35:06] [FHEM] Initializing platform accessory 'HM_514F4E'...
[2017-3-21 08:35:06] [FHEM] creating services for HM_514F4E
[2017-3-21 08:35:06] [FHEM] information service for HM_514F4E
[2017-3-21 08:35:06] [FHEM] manufacturer, model and serial number characteristics for HM_514F4E
[2017-3-21 08:35:06] [FHEM] firmware revision characteristic for HM_514F4E
[2017-3-21 08:35:06] [FHEM] Thermostat service for HM_514F4E
[2017-3-21 08:35:06] [FHEM] StatusLowBattery characteristic for HM_514F4E:battery
[2017-3-21 08:35:06] [FHEM] CurrentTemperature characteristic for HM_514F4E:measured-temp
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState characteristic for HM_514F4E:undefined
[2017-3-21 08:35:06] [FHEM] Initializing platform accessory 'HM_515B40'...
[2017-3-21 08:35:06] [FHEM] creating services for HM_515B40
[2017-3-21 08:35:06] [FHEM] information service for HM_515B40
[2017-3-21 08:35:06] [FHEM] manufacturer, model and serial number characteristics for HM_515B40
[2017-3-21 08:35:06] [FHEM] firmware revision characteristic for HM_515B40
[2017-3-21 08:35:06] [FHEM] Thermostat service for HM_515B40
[2017-3-21 08:35:06] [FHEM] StatusLowBattery characteristic for HM_515B40:battery
[2017-3-21 08:35:06] [FHEM] CurrentTemperature characteristic for HM_515B40:measured-temp
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState characteristic for HM_515B40:undefined
[2017-3-21 08:35:06] [FHEM] Initializing platform accessory 'HM_515B4B'...
[2017-3-21 08:35:06] [FHEM] creating services for HM_515B4B
[2017-3-21 08:35:06] [FHEM] information service for HM_515B4B
[2017-3-21 08:35:06] [FHEM] manufacturer, model and serial number characteristics for HM_515B4B
[2017-3-21 08:35:06] [FHEM] firmware revision characteristic for HM_515B4B
[2017-3-21 08:35:06] [FHEM] Thermostat service for HM_515B4B
[2017-3-21 08:35:06] [FHEM] StatusLowBattery characteristic for HM_515B4B:battery
[2017-3-21 08:35:06] [FHEM] CurrentTemperature characteristic for HM_515B4B:measured-temp
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState characteristic for HM_515B4B:undefined
[2017-3-21 08:35:06] [FHEM] Initializing platform accessory 'HM_515B5E'...
[2017-3-21 08:35:06] [FHEM] creating services for HM_515B5E
[2017-3-21 08:35:06] [FHEM] information service for HM_515B5E
[2017-3-21 08:35:06] [FHEM] manufacturer, model and serial number characteristics for HM_515B5E
[2017-3-21 08:35:06] [FHEM] firmware revision characteristic for HM_515B5E
[2017-3-21 08:35:06] [FHEM] Thermostat service for HM_515B5E
[2017-3-21 08:35:06] [FHEM] StatusLowBattery characteristic for HM_515B5E:battery
[2017-3-21 08:35:06] [FHEM] CurrentTemperature characteristic for HM_515B5E:measured-temp
[2017-3-21 08:35:06] [FHEM] CurrentHeatingCoolingState characteristic for HM_515B5E:undefined
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 123-45-678 │
└────────────┘
[2017-3-21 08:35:07] Homebridge is running on port 51826.
[2017-3-21 08:35:07] [FHEM] genericDeviceType attribute was not known. please restart.
fhem@raspberrypi:/home/pi$
Allerdings findet eve keine von beiden homebridge..... Was ist schief gelaufen?
Hi,
ist das wirklich ein FHEM-Problem? Wenn diese Homebridge irgend etwas nicht findet, was kann dann FHEM dafür?
(Möglicherweise entspringt meine Frage meiner Ignoranz. In dem Fall ware eine Erklärung trotzdem nett...)
Gruß,
Thorsten
Leider habe ich zu wenig Erfahrung um das beantworten zu können...
Ich kann nur sagen, das ich mich exact an die Anleitung im FHEM Wiki für die Einrichtung von Homebridge gehalten habe und jetzt eben scheinbar 2 unterschiedliche Versionen unter 2 Usern habe. Ich vermute das deshalb gar nichts mehr läuft im Bezug auf Homebridge... Ich hatte gehofft, das das ggf. einfach behoben werden kann, nur weis ich nicht wie.
Moin,
na ja, von alleine startet Homebrige auch nicht... ;)
Du kannst aber ja mal simpler weise alle homebridge-Instanzen auf dem Pi beenden und dann nur diejenige starten, die du auch entsprechend konfiguriert hast.
Ansonsten würde sich für weitere Diskussionen, das entsprechende Unter-Forum anbieten...
https://forum.fhem.de/index.php/topic,48558.0.html (https://forum.fhem.de/index.php/topic,48558.0.html)
Gruß,
Stephan