Apple Homekit: die Hoffnung stirbt zuletzt

volschin · 23 Oktober 2015, 19:21:42

Meine Antwort hing wohl in der Queue. War auf die Frage von mad24.

Posti123 · 23 Oktober 2015, 19:22:57

Zitat von: Mitch am 23 Oktober 2015, 17:22:29
Welchen Port?
Die 8084? Die stimmt

den Port von Homebridge

mad24 · 23 Oktober 2015, 20:23:16

@volschin: Danke für die Rückmeldung. Nur was meinst Du genau mit Ja...
Ja, es ist bei Dir genauso oder ja es liegt an iOS8?

Danke & VG

volschin · 23 Oktober 2015, 20:24:05

iOS 9 hat eine erweiterte API.

mad24 · 23 Oktober 2015, 21:03:28

Danke - dann werd ich wohl doch demnächst den Schritt auf iOS9 wagen müssen...

Posti123 · 23 Oktober 2015, 21:32:55

Zitat von: PsychoD am 20 Oktober 2015, 01:14:17
Hi zusammen

@Alle
Siri und ich habe gerade eine Krise - wir verstehen uns normalerweise relativ gut, aber wenn es um das Wohnzimmer geht will sie micht nicht verstehen - bietet mir sogar Hotels in der Umgebung an! Dabei geht es noch, wenn ich will dass sie das Licht anmacht, aber wenn es um die Musikanlage oder den Fernseher geht versteht sie gar nix mehr. Habt ihr ähnliche Probleme mit Siri im Wohnzimmer? Im Eve kann ich alles wunderbar schalten.

Viele Grüße
Damian

Genau das Problem habe ich gerade auch "Schalte das Licht im Wohnzimmer an" --> "Ich habe 2 Hotels in der Nähe gefunden"...

na vielen Dank auch

Mitch · 23 Oktober 2015, 23:16:58

Zitat von: Posti123 am 23 Oktober 2015, 19:22:57
den Port von Homebridge

Also die 51826?
Aber so steht es dch im Wiki?

Ich habe es jetzt mal am Laufen gehabt und konnte auch EVE konfigurieren.
Habe dann Homebrdge beendet und neu gestartet, jetzt kommt es nicht mehr hoch und bringt folgenden Fehler:

Code Auswählen

TypeError: Cannot set property 'value' of undefined
    at Object.FHEMAccessory.getServices (/home/markus/homebridge/platforms/FHEM.js:1560:30)
    at createAccessory (/home/markus/homebridge/app.js:146:36)
    at /home/markus/homebridge/app.js:132:27
    at /home/markus/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
    at Object.<anonymous> (/home/markus/homebridge/platforms/FHEM.js:623:22)
    at Request.self.callback (/home/markus/homebridge/node_modules/request/request.js:373:22)
    at Request.EventEmitter.emit (events.js:98:17)
    at Request.<anonymous> (/home/markus/homebridge/node_modules/request/request.js:1318:14)
    at Request.EventEmitter.emit (events.js:117:20)
    at IncomingMessage.<anonymous> (/home/markus/homebridge/node_modules/request/request.js:1266:12)

Mitch · 23 Oktober 2015, 23:42:37

So, habe den Fehler selber gefunden.

Hatte erst nur einen HM Stecker drinnen, da ging es.
Dann habe ich eine FS20 Steckdose und eine FB DECT mit rein genommen, dann startet Homebridge nicht mehr.

justme1968 · 24 Oktober 2015, 09:59:34

bitte zeig mal mehr vom log und ein jsonlist2 vom device das probleme macht.

gruss
andre

Mitch · 24 Oktober 2015, 12:58:59

Hier bitte:

Code Auswählen

{ 
  "Arg":"FBDECT_Barlicht", 
  "Results": [ 
  { 
    "Name":"FBDECT_Barlicht", 
    "PossibleSets":"msgInterval off on on-till-overnight toggle blink on-for-timer off-for-timer off-till off-till-overnight on-till intervals", 
    "PossibleAttrs":"verbose:0,1,2,3,4,5 room group comment:textField-long alias eventMap userReadings IODev do_not_notify:1,0 ignore:1,0 dummy:1,0 showtime:1,0 event-on-change-reading event-on-update-reading event-aggregator event-min-interval stateFormat model:CometDECT,Dect200,Powerline546E DbLogExclude DbLogInclude cmdIcon devStateIcon devStateStyle device_timeout fm_fav fm_groups fm_name fm_order fm_type fm_view fp_back1 fp_status icon sortby sortbystructexclude webCmd widgetOverride Licht Licht_map structexclude userattr", 
    "Internals": { 
      ".lastTimeenergy": "1445684062.41492", 
      ".lastTimepower": "1445684061.95293", 
      ".lastTimetemperature": "1445684062.16015", 
      "CHANGED": "null", 
      "DEF": "16 switch", 
      "Fritzi_MSGCNT": "5850", 
      "Fritzi_RAWMSG": "0703001c000000f3001000000000000c000000160004000000000000", 
      "Fritzi_TIME": "2015-10-24 12:56:21", 
      "LASTInputDev": "Fritzi", 
      "MSGCNT": "5850", 
      "NAME": "FBDECT_Barlicht", 
      "NR": "177", 
      "STATE": "off", 
      "TYPE": "FBDECT", 
      "id": "16", 
      "props": "switch" 
    }, 
    "Readings": { 
      "control": { "Value":"on fn=1 > 0.00 delay:0sec do:state off", "Time":"2015-10-11 23:17:27" }, 
      "current": { "Value":"0.0000 A", "Time":"2015-10-24 12:56:21" }, 
      "energy": { "Value":"9848 Wh", "Time":"2015-10-24 12:56:21" }, 
      "options": { "Value":"powerOnState:last,lock:none", "Time":"2015-10-11 23:17:26" }, 
      "power": { "Value":"0.00 W", "Time":"2015-10-24 12:56:21" }, 
      "powerFactor": { "Value":"0.000", "Time":"2015-10-24 12:56:21" }, 
      "state": { "Value":"off", "Time":"2015-10-24 12:56:21" }, 
      "tempadjust": { "Value":"0.0 C", "Time":"2015-10-11 23:17:26" }, 
      "temperature": { "Value":"24.0 C (measured)", "Time":"2015-10-24 12:56:21" }, 
      "voltage": { "Value":"227.698 V", "Time":"2015-10-24 12:56:21" } 
    }, 
    "Attributes": { 
      "IODev": "Fritzi", 
      "Licht": "Lichter", 
      "alias": "Barlicht", 
      "event-min-interval": "power:120,temperature:120,energy:120", 
      "event-on-change-reading": "power,temperature,energy,state", 
      "event-on-update-reading": "power", 
      "fm_type": "offbutton,onbutton,current,power,voltage", 
      "group": "Licht Küchenbereich", 
      "icon": "light_party", 
      "model": "Dect200", 
      "room": "Wohnzimmer", 
      "userattr": "Licht Licht_map structexclude" 
    } 
  }  ], 
  "totalResultsReturned":1 
}

Wir macht ihr das denn mit der Namensvergabe?
Meine Siri funktioniert nicht wirklich. Wenn ich nach der Temperatur im Wohnzimmer frage, bringt Sie den Wetterbericht.

Posti123 · 24 Oktober 2015, 15:03:02

Zitat von: Mitch am 24 Oktober 2015, 12:58:59

Wir macht ihr das denn mit der Namensvergabe?
Meine Siri funktioniert nicht wirklich. Wenn ich nach der Temperatur im Wohnzi, mmer frage, bringt Sie den Wetterbericht.

Also Siri versteht mich nur wenn ich frage: "Wie warm ist es im Wohnzimmer?", allerdings antwortet Siri "Die Temperatur (Wohnzimmer) ist derzeit auf 23.8°C gestellt. Gestellt ist sie allerdings auf 16 Grad, die gemessene ist 23.8 ;)W

Dem Gerät habe ich keinen Namen gegeben. Es ist der FHEM name (WTO.HZ_Climate). Das geht halt solange gut, solange auch nur ein Thermostat im Raum ist oder nur eine Lampe.

Marie · 24 Oktober 2015, 16:14:49

@justme

Hallo Andre, scheinbar läuft die Homebridge jetzt durch, hatte noch einen falschen Parameter drin.
Aber es gibt noch ein anderes Problem: ich generiere aus einem device mit Hilfe von readingsproxy einzelne Temperaturen. Diese funktionieren in FHEM super, EVE bzw. HomeKit erkennt sie auch. Aber: die Werte werden nur beim Start von Homebridge einmal gelesen und danach nicht mehr aktualisiert. Um aktuelle Werte zu erhalten muss man Homebridge immer neu starten.
Temperatur-Readings die aus einem FHT80 kommen, funktionieren dagegen einwandfrei.
Hast du da vielleicht eine Idee dazu??

LG

Marie

dev0 · 24 Oktober 2015, 17:44:54

Werden denn für die einzelnen Temperaturen Events erzeugt?

Marie · 24 Oktober 2015, 18:29:32

Ich habe einfach nur ein readingsproxy für eine Messung erzeugt. Events wurden nicht explizit erzeugt. Die sollen ja lt. Beschreibung automatisch produziert werden. Ich habe jetzt mal Event-on-Change für die Temperatur gemacht, mal sehen
...

LG

Marie

Zu früh gefreut....eve findet mal wieder die devices nicht....

bigdane · 25 Oktober 2015, 11:37:33

Hallo Zusammen,

leider habe ich mein MAX Heizungsthermostat immer noch nicht zum laufen gebracht, Eve sagt beim Koppeln "Fehlgeschlagen".

Gibt es hier denn jemand bei dem das MAX Thermostat in Eve erkannt wurde bzw. das koppeln damit funktioniert?
Mich würde mal interessieren wie das MAX in FHEM angelegt wurde etc...

Ich habe es nochmal komplett aus FHEM entfernt und neu angelernt, sieht in FHEM in der config nun wie folgt aus:

Code Auswählen


define MAX_0ddc22 MAX HeatingThermostat 0ddc22
attr MAX_0ddc22 IODev cm
attr MAX_0ddc22 room MAX
define FileLog_MAX_0ddc22 FileLog ./log/MAX_0ddc22-%Y.log MAX_0ddc22
attr FileLog_MAX_0ddc22 logtype text
attr FileLog_MAX_0ddc22 room logfiles

Die json Abfrage sieht wie folgt aus:

Code Auswählen

{
  "Arg":"room=MAX",
  "Results": [
  {
    "Name":"MAX_0ddc22",
    "PossibleSets":"wakeUp factoryReset groupid associate:MAX_0ddae3,MAX_0c868e,MAX_0dd96c,MAX_0ddad1,fakeWallThermostat,fakeShutterContact deassociate:MAX_0ddae3,MAX_0c868e,MAX_0dd96c,MAX_0ddad1,fakeWallThermostat,fakeShutterContact desiredTemperature:eco,comfort,boost,auto,off,5.0,5.5,6.0,6.5,7.0,7.5,8.0,8.5,9.0,9.5,10.0,10.5,11.0,11.5,12.0,12.5,13.0,13.5,14.0,14.5,15.0,15.5,16.0,16.5,17.0,17.5,18.0,18.5,19.0,19.5,20.0,20.5,21.0,21.5,22.0,22.5,23.0,23.5,24.0,24.5,25.0,25.5,26.0,26.5,27.0,27.5,28.0,28.5,29.0,29.5,30.0,on ecoTemperature:off,5.0,5.5,6.0,6.5,7.0,7.5,8.0,8.5,9.0,9.5,10.0,10.5,11.0,11.5,12.0,12.5,13.0,13.5,14.0,14.5,15.0,15.5,16.0,16.5,17.0,17.5,18.0,18.5,19.0,19.5,20.0,20.5,21.0,21.5,22.0,22.5,23.0,23.5,24.0,24.5,25.0,25.5,26.0,26.5,27.0,27.5,28.0,28.5,29.0,29.5,30.0,on comfortTemperature:off,5.0,5.5,6.0,6.5,7.0,7.5,8.0,8.5,9.0,9.5,10.0,10.5,11.0,11.5,12.0,12.5,13.0,13.5,14.0,14.5,15.0,15.5,16.0,16.5,17.0,17.5,18.0,18.5,19.0,19.5,20.0,20.5,21.0,21.5,22.0,22.5,23.0,23.5,24.0,24.5,25.0,25.5,26.0,26.5,27.0,27.5,28.0,28.5,29.0,29.5,30.0,on measurementOffset:-3.5,-3.0,-2.5,-2.0,-1.5,-1.0,-0.5,0.0,0.5,1.0,1.5,2.0,2.5,3.0,3.5 maximumTemperature:off,5.0,5.5,6.0,6.5,7.0,7.5,8.0,8.5,9.0,9.5,10.0,10.5,11.0,11.5,12.0,12.5,13.0,13.5,14.0,14.5,15.0,15.5,16.0,16.5,17.0,17.5,18.0,18.5,19.0,19.5,20.0,20.5,21.0,21.5,22.0,22.5,23.0,23.5,24.0,24.5,25.0,25.5,26.0,26.5,27.0,27.5,28.0,28.5,29.0,29.5,30.0,on minimumTemperature:off,5.0,5.5,6.0,6.5,7.0,7.5,8.0,8.5,9.0,9.5,10.0,10.5,11.0,11.5,12.0,12.5,13.0,13.5,14.0,14.5,15.0,15.5,16.0,16.5,17.0,17.5,18.0,18.5,19.0,19.5,20.0,20.5,21.0,21.5,22.0,22.5,23.0,23.5,24.0,24.5,25.0,25.5,26.0,26.5,27.0,27.5,28.0,28.5,29.0,29.5,30.0,on windowOpenTemperature:off,5.0,5.5,6.0,6.5,7.0,7.5,8.0,8.5,9.0,9.5,10.0,10.5,11.0,11.5,12.0,12.5,13.0,13.5,14.0,14.5,15.0,15.5,16.0,16.5,17.0,17.5,18.0,18.5,19.0,19.5,20.0,20.5,21.0,21.5,22.0,22.5,23.0,23.5,24.0,24.5,25.0,25.5,26.0,26.5,27.0,27.5,28.0,28.5,29.0,29.5,30.0,on windowOpenDuration boostDuration:30,15,60,10,5,20,0,25 boostValveposition decalcification maxValveSetting valveOffset weekProfile",
    "PossibleAttrs":"verbose:0,1,2,3,4,5 room group comment:textField-long alias eventMap userReadings IODev do_not_notify:1,0 ignore:0,1 dummy:0,1 showtime:1,0 keepAuto:0,1 scanTemp:0,1 event-on-change-reading event-on-update-reading event-aggregator event-min-interval stateFormat devStateIcon devStateStyle fp_Grundriss icon sortby webCmd widgetOverride genericDeviceType:switch,outlet,light,blind,speaker,thermostat,thermometer userattr",
    "Internals": {
      "DEF": "HeatingThermostat 0ddc22",
      "LASTInputDev": "cm",
      "MSGCNT": "4",
      "NAME": "MAX_0ddc22",
      "NR": "334",
      "RSSI": "-81",
      "STATE": "20.0 °C",
      "TYPE": "MAX",
      "addr": "0ddc22",
      "backend": "cm",
      "cm_MSGCNT": "4",
      "cm_TIME": "2015-10-25 11:32:19",
      "dstsetting": "1",
      "mode": "1",
      "rferror": "0",
      "type": "HeatingThermostat"
    },
    "Readings": {
      "RSSI": { "Value":"-81", "Time":"2015-10-25 11:32:19" },
      "TimeInformationHour": { "Value":"4", "Time":"2015-10-25 11:26:43" },
      "battery": { "Value":"ok", "Time":"2015-10-25 11:32:19" },
      "boostDuration": { "Value":"25", "Time":"2015-10-25 11:25:15" },
      "boostValveposition": { "Value":"80", "Time":"2015-10-25 11:25:15" },
      "comfortTemperature": { "Value":"21.0", "Time":"2015-10-25 11:25:15" },
      "decalcification": { "Value":"Sat 12:00", "Time":"2015-10-25 11:25:15" },
      "desiredTemperature": { "Value":"20.0", "Time":"2015-10-25 11:32:19" },
      "ecoTemperature": { "Value":"17.0", "Time":"2015-10-25 11:25:15" },
      "firmware": { "Value":"1.0", "Time":"2015-10-25 11:25:14" },
      "maxValveSetting": { "Value":"100", "Time":"2015-10-25 11:25:15" },
      "maximumTemperature": { "Value":"on", "Time":"2015-10-25 11:25:15" },
      "measurementOffset": { "Value":"0.0", "Time":"2015-10-25 11:25:15" },
      "minimumTemperature": { "Value":"off", "Time":"2015-10-25 11:25:15" },
      "mode": { "Value":"manual", "Time":"2015-10-25 11:32:19" },
      "msgcnt": { "Value":"4", "Time":"2015-10-25 11:27:20" },
      "state": { "Value":"20.0 °C", "Time":"2015-10-25 11:32:19" },
      "temperature": { "Value":"21.5", "Time":"2015-10-25 11:32:19" },
      "testresult": { "Value":"160", "Time":"2015-10-25 11:25:14" },
      "valveOffset": { "Value":"0", "Time":"2015-10-25 11:25:15" },
      "valveposition": { "Value":"8", "Time":"2015-10-25 11:32:19" },
      "weekprofile-0-Sat-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-0-Sat-time": { "Value":"00:00-06:00  /  06:00-22:00  /  22:00-00:00", "Time":"2015-10-25 11:25:15" },
      "weekprofile-1-Sun-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-1-Sun-time": { "Value":"00:00-06:00  /  06:00-22:00  /  22:00-00:00", "Time":"2015-10-25 11:25:15" },
      "weekprofile-2-Mon-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-2-Mon-time": { "Value":"00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-00:00", "Time":"2015-10-25 11:25:15" },
      "weekprofile-3-Tue-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-3-Tue-time": { "Value":"00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-00:00", "Time":"2015-10-25 11:25:15" },
      "weekprofile-4-Wed-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-4-Wed-time": { "Value":"00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-00:00", "Time":"2015-10-25 11:25:15" },
      "weekprofile-5-Thu-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-5-Thu-time": { "Value":"00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-00:00", "Time":"2015-10-25 11:25:15" },
      "weekprofile-6-Fri-temp": { "Value":"17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C", "Time":"2015-10-25 11:25:15" },
      "weekprofile-6-Fri-time": { "Value":"00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-00:00", "Time":"2015-10-25 11:25:15" },
      "windowOpenDuration": { "Value":"15", "Time":"2015-10-25 11:25:15" },
      "windowOpenTemperature": { "Value":"12.0", "Time":"2015-10-25 11:25:15" }
    },
    "Attributes": {
      "IODev": "cm",
      "room": "MAX"
    }
  }  ],
  "totalResultsReturned":1
}

Und Homebridge sagt beim Start und versuchtem Koppeln folgendes:

Code Auswählen

pi@raspberrypi ~/homebridge $ npm run start

> homebridge@0.1.1 start /home/pi/homebridge
> DEBUG=* node app.js || true

*** 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>
Starting HomeBridge server...
_____________________________________________________________________
IMPORTANT: Homebridge is in the middle of some big changes.
           Read more about it here:
           https://github.com/nfarina/homebridge/wiki/Migration-Guide
_____________________________________________________________________

Loading 1 platforms...
[FHEMWEB] Initializing FHEM platform...
starting longpoll: http://192.168.2.5:8083/fhem.pl?XHR=1&inform=type=status;filter=.*;since=null;fmt=JSON&timestamp=1445768913317
[FHEMWEB] Fetching FHEM switchable devices...
[FHEMWEB] fetching: http://192.168.2.5:8083/fhem?cmd=jsonlist2%20room=MAX&XHR=1
Loading 0 accessories...
Server listening on: http://<ip>:8081
[FHEMWEB] got: 1 results
[FHEMWEB] MAX_0ddc22 is thermostat [desiredTemperature;5.0-30.0:0.5]
[FHEMWEB] MAX_0ddc22 has thermostat mode [mode;desiredTemperature]
[FHEMWEB] MAX_0ddc22 has temperature [temperature]
[FHEMWEB] MAX_0ddc22 has battery [battery]
[FHEMWEB] Initializing platform accessory 'MAX_0ddc22'...
[FHEMWEB] creating services for MAX_0ddc22
[FHEMWEB]   information service for MAX_0ddc22
[FHEMWEB]   thermostat service for MAX_0ddc22
[FHEMWEB]     temperature characteristic for MAX_0ddc22
[FHEMWEB]     battery status characteristic for MAX_0ddc22
[FHEMWEB]     target temperature characteristic for MAX_0ddc22
Scan this code with your HomeKit App on your iOS device:
                       
    ┌────────────┐     
    │ 031-45-154 │     
    └────────────┘     
                       
  Accessory [Homebridge] Creating new AccessoryInfo for our HAP server +0ms
  Accessory [Homebridge] Creating new IdentifierCache +32ms
  EventedHTTPServer Server listening on port 51826 +49ms
  EventedHTTPServer [192.168.2.101] New connection from client +53s
  EventedHTTPServer [192.168.2.101] HTTP server listening on port 54826 +3ms
  EventedHTTPServer [192.168.2.101] HTTP request: /identify +21ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /identify +2ms
  Accessory [Homebridge] Identification request +7ms
  Accessory [Homebridge] Identification request ignored; no listeners to 'identify' event +1ms
  HAPServer [CC:22:3D:E3:CE:61] Identification success +1ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +10ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-setup +4s
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-setup +2ms
  HAPServer [CC:22:3D:E3:CE:61] Pair step 1/5 +8ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +435ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-setup +18s
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-setup +1ms
  HAPServer [CC:22:3D:E3:CE:61] Pair step 2/5 +6ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +515ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-setup +31ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-setup +1ms
  HAPServer [CC:22:3D:E3:CE:61] Pair step 3/5 +4ms
  HAPServer [CC:22:3D:E3:CE:61] Pair step 4/5 +48ms
  HAPServer [CC:22:3D:E3:CE:61] Pair step 5/5 +10ms
  Accessory [Homebridge] Paired with client 254BFC25-18B0-4465-B484-E3FDF548206C +22ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +32ms
  EventedHTTPServer [192.168.2.101] Client connection closed +74ms
  EventedHTTPServer [192.168.2.101] New connection from client +7ms
  EventedHTTPServer [192.168.2.101] HTTP server listening on port 54827 +2ms
  EventedHTTPServer [192.168.2.101] HTTP connection was closed +8ms
  EventedHTTPServer [192.168.2.101] HTTP server was closed +3ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-verify +7ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-verify +1ms
  HAPServer [CC:22:3D:E3:CE:61] Pair verify step 1/2 +6ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +65ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-verify +24ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-verify +1ms
  HAPServer [CC:22:3D:E3:CE:61] Pair verify step 2/2 +5ms
  HAPServer [CC:22:3D:E3:CE:61] Client 254BFC25-18B0-4465-B484-E3FDF548206C verification complete +9ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +2ms
  EventedHTTPServer [192.168.2.101] HTTP request: /accessories +40ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: GET /accessories +1ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +34ms
  EventedHTTPServer [192.168.2.101] Client connection closed +112ms
  EventedHTTPServer [192.168.2.101] HTTP connection was closed +4ms
  EventedHTTPServer [192.168.2.101] HTTP server was closed +1ms
  EventedHTTPServer [192.168.2.101] New connection from client +2s
  EventedHTTPServer [192.168.2.101] HTTP server listening on port 54826 +2ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-verify +8ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-verify +1ms
  HAPServer [CC:22:3D:E3:CE:61] Pair verify step 1/2 +3ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +38ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-verify +36ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-verify +1ms
  HAPServer [CC:22:3D:E3:CE:61] Pair verify step 2/2 +4ms
  HAPServer [CC:22:3D:E3:CE:61] Client 254BFC25-18B0-4465-B484-E3FDF548206C verification complete +10ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +2ms
  EventedHTTPServer [192.168.2.101] HTTP request: /accessories +147ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: GET /accessories +0ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +41ms
  EventedHTTPServer [192.168.2.101] Client connection closed +105ms
  EventedHTTPServer [192.168.2.101] HTTP connection was closed +3ms
  EventedHTTPServer [192.168.2.101] HTTP server was closed +1ms
  EventedHTTPServer [192.168.2.101] New connection from client +2s
  EventedHTTPServer [192.168.2.101] HTTP server listening on port 54826 +2ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-verify +6ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-verify +8ms
  HAPServer [CC:22:3D:E3:CE:61] Pair verify step 1/2 +8ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +37ms
  EventedHTTPServer [192.168.2.101] HTTP request: /pair-verify +47ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: POST /pair-verify +0ms
  HAPServer [CC:22:3D:E3:CE:61] Pair verify step 2/2 +3ms
  HAPServer [CC:22:3D:E3:CE:61] Client 254BFC25-18B0-4465-B484-E3FDF548206C verification complete +8ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +1ms
  EventedHTTPServer [192.168.2.101] HTTP request: /accessories +49ms
  HAPServer [CC:22:3D:E3:CE:61] HAP Request: GET /accessories +1ms
  EventedHTTPServer [192.168.2.101] HTTP Repsonse is finished +8ms
  EventedHTTPServer [192.168.2.101] Client connection closed +71ms
  EventedHTTPServer [192.168.2.101] HTTP connection was closed +2ms
  EventedHTTPServer [192.168.2.101] HTTP server was closed +2ms

Vielen lieben Dank vorab

Grüße

bigdane