Apple Homekit: die Hoffnung stirbt zuletzt

volschin · 23 September 2015, 14:52:55

Der HM-LC-BL1-FM ist natürlich ein Rollladenschalter, auch wenn ich den für meine Kinoleinwand missbrauche.

justme1968 · 23 September 2015, 14:54:16

so lange er ein set on und set off kennt kannst du ihn zumindest mit FHEM.js über genericType switch zum einfachen schalter machen und dann auch per siri bedienen.

flurin · 23 September 2015, 15:19:46

Zitat von: volschin am 23 September 2015, 14:44:56
@flurin: Du hast doch mit den Blinds schon eine ganze Menge experimentiert. Ich habe mir ganz neu einen HM-LC-BL1-FM zugelegt, der meine Beamer-Leinwand steuert. Ich habe jetzt in FHEM eingerichtet und experimentiert. Ich brauche nur on/off. Es wäre aber schön, wenn Siri auch auf
hört.
hast Du einen Tipp, wie ich es am besten einrichte, dass das klappt.
Prozentstellungen etc. sind bei mir alles Overhead.

Gruß
Veit

Was Siri in diesem Zusammenhang versteht (wenigstens von mir), ist Brightness.
Am Anfang hatte ich:

Code Auswählen


  .addCharacteristic(Characteristic.Brightness)

hinzugefügt. Dann versteht Siri z.B. "set the dining room brightness to 20".
Bei WindowCovering "fehlen" noch die entsprechenden Befehle. Aber man kann Szenen definieren.
Z.B. Szene "wallscreenup" > position 100.
Dann einfach: "Hey Siri, wallscreenup" - Siri : "You got it. Your digs are now ready for wallscreenup"

Dido für "wallscreendown".

Gruss
flurin

... screenshot im Anhang

Edit: statt Position kann man auch Power ON OFF definieren.

Posti123 · 23 September 2015, 19:15:01

wird denn on-for-timer von Homekit unterstützt?

Zum Beispiel "Schalte das Licht im Garten für 5min an"

Hauswart · 23 September 2015, 19:53:01

Jetzt brauche ich nur noch ein gutes Startskript damit Homebridge beim Starten automatisch startet

dev0 · 23 September 2015, 20:03:20

Mehrere Ansätze bzw. auch eine fertige Lösung sind in diesem Thread beschrieben.

matzel · 23 September 2015, 23:41:21

Habe HAP-NodeJS manuel ausgeheckt.
Bekomme aber mit der neuen FHEM.js immer in EVE die Meldung: Hinzufügen fehlgeschlagen. Verbindung mit Zubehör nicht möglich.

Code Auswählen


  Accessory [Homebridge] Creating new AccessoryInfo for our HAP server +0ms
  Accessory [Homebridge] Creating new IdentifierCache +3ms
  EventedHTTPServer Server listening on port 51826 +10ms
  EventedHTTPServer [::ffff:192.168.178.24] New connection from client +6s
  EventedHTTPServer [::ffff:192.168.178.24] HTTP server listening on port 54826 +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-setup +6ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms
  HAPServer [CC:22:3D:E3:CE:30] Pair step 1/5 +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +11ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-setup +10s
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms
  HAPServer [CC:22:3D:E3:CE:30] Pair step 2/5 +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +19ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-setup +9ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms
  HAPServer [CC:22:3D:E3:CE:30] Pair step 3/5 +1ms
  HAPServer [CC:22:3D:E3:CE:30] Pair step 4/5 +13ms
  HAPServer [CC:22:3D:E3:CE:30] Pair step 5/5 +1ms
  Accessory [Homebridge] Paired with client 423754DB-6498-4976-B412-A659442A8120 +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +4ms
  EventedHTTPServer [::ffff:192.168.178.24] Client connection closed +31ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP connection was closed +2ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP server was closed +0ms
  EventedHTTPServer [::ffff:192.168.178.24] New connection from client +2ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP server listening on port 54826 +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-verify +2ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms
  HAPServer [CC:22:3D:E3:CE:30] Pair verify step 1/2 +2ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +2ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-verify +11ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms
  HAPServer [CC:22:3D:E3:CE:30] Pair verify step 2/2 +1ms
  HAPServer [CC:22:3D:E3:CE:30] Client 423754DB-6498-4976-B412-A659442A8120 verification complete +2ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /accessories +7ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /accessories +0ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +7ms
  EventedHTTPServer [::ffff:192.168.178.24] Client connection closed +85ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP connection was closed +1ms
  EventedHTTPServer [::ffff:192.168.178.24] HTTP server was closed +0ms

Mit der alten FHEM.js funktioniert es...

Zetti · 24 September 2015, 15:24:35

Hallo bin absoluter leie währe schön wenn mir jemand nen tip geben könnte wonach ich noch suchen könnte das Homebridge startret!

0 info it worked if it ends with ok
1 verbose cli [ '/root/.nvm/versions/v0.12.6/bin/node',
1 verbose cli '/root/.nvm/versions/v0.12.6/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start' ]
2 info using npm@2.11.2
3 info using node@v0.12.6
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart homebridge@0.0.0
6 info start homebridge@0.0.0
7 verbose unsafe-perm in lifecycle true
8 info homebridge@0.0.0 Failed to exec start script
9 verbose stack Error: homebridge@0.0.0 start: `node app.js`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (/root/.nvm/versions/v0.12.6/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
9 verbose stack at EventEmitter.emit (events.js:110:17)
9 verbose stack at ChildProcess.<anonymous> (/root/.nvm/versions/v0.12.6/lib/node_modules/npm/lib/utils/spawn.js:24:14)
9 verbose stack at ChildProcess.emit (events.js:110:17)
9 verbose stack at maybeClose (child_process.js:1015:16)
9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
10 verbose pkgid homebridge@0.0.0
11 verbose cwd /home/zetti/homebridge
12 error Linux 3.16.0-4-amd64
13 error argv "/root/.nvm/versions/v0.12.6/bin/node" "/root/.nvm/versions/v0.12.6/bin/npm" "run" "start"
14 error node v0.12.6
15 error npm v2.11.2
16 error code ELIFECYCLE
17 error homebridge@0.0.0 start: `node app.js`
17 error Exit status 1
18 error Failed at the homebridge@0.0.0 start script 'node app.js'.
18 error This is most likely a problem with the homebridge package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error node app.js
18 error You can get their info via:
18 error npm owner ls homebridge
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

root@FHEMSERVER8:/home/zetti/homebridge# npm run start
> homebridge@0.0.0 start /home/zetti/homebridge
> node app.js

Starting HomeBridge server...
undefined:10
}
^
SyntaxError: Unexpected token }
at Object.parse (native)
at Object.<anonymous> (/home/zetti/homebridge/app.js:21:19)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3

npm ERR! Linux 3.16.0-4-amd64
npm ERR! argv "/root/.nvm/versions/v0.12.6/bin/node" "/root/.nvm/versions/v0.12.6/bin/npm" "run" "start"
npm ERR! node v0.12.6
npm ERR! npm v2.11.2
npm ERR! code ELIFECYCLE
npm ERR! homebridge@0.0.0 start: `node app.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the homebridge@0.0.0 start script 'node app.js'.
npm ERR! This is most likely a problem with the homebridge package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node app.js
npm ERR! You can get their info via:
npm ERR! npm owner ls homebridge
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/zetti/homebridge/npm-debug.log

Meine Config.json

{

"platforms": [
{
"platform": "FHEM",
"name": "FHEMSERVER8",
"server": "192.168.XXX.XX",
"port": "8083",

}
],

"accessories": []

vielen vielen dank schon im Vorraus

Posti123 · 24 September 2015, 16:26:30

Zitat von: matzel am 23 September 2015, 23:41:21
Habe HAP-NodeJS manuel ausgeheckt.
Bekomme aber mit der neuen FHEM.js immer in EVE die Meldung: Hinzufügen fehlgeschlagen. Verbindung mit Zubehör nicht möglich.

Code Auswählen Erweitern
Accessory [Homebridge] Creating new AccessoryInfo for our HAP server +0ms Accessory [Homebridge] Creating new IdentifierCache +3ms EventedHTTPServer Server listening on port 51826 +10ms EventedHTTPServer [::ffff:192.168.178.24] New connection from client +6s EventedHTTPServer [::ffff:192.168.178.24] HTTP server listening on port 54826 +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-setup +6ms HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms HAPServer [CC:22:3D:E3:CE:30] Pair step 1/5 +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +11ms EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-setup +10s HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms HAPServer [CC:22:3D:E3:CE:30] Pair step 2/5 +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +19ms EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-setup +9ms HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms HAPServer [CC:22:3D:E3:CE:30] Pair step 3/5 +1ms HAPServer [CC:22:3D:E3:CE:30] Pair step 4/5 +13ms HAPServer [CC:22:3D:E3:CE:30] Pair step 5/5 +1ms Accessory [Homebridge] Paired with client 423754DB-6498-4976-B412-A659442A8120 +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +4ms EventedHTTPServer [::ffff:192.168.178.24] Client connection closed +31ms EventedHTTPServer [::ffff:192.168.178.24] HTTP connection was closed +2ms EventedHTTPServer [::ffff:192.168.178.24] HTTP server was closed +0ms EventedHTTPServer [::ffff:192.168.178.24] New connection from client +2ms EventedHTTPServer [::ffff:192.168.178.24] HTTP server listening on port 54826 +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-verify +2ms HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms HAPServer [CC:22:3D:E3:CE:30] Pair verify step 1/2 +2ms EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +2ms EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /pair-verify +11ms HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms HAPServer [CC:22:3D:E3:CE:30] Pair verify step 2/2 +1ms HAPServer [CC:22:3D:E3:CE:30] Client 423754DB-6498-4976-B412-A659442A8120 verification complete +2ms EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP request: /accessories +7ms HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /accessories +0ms EventedHTTPServer [::ffff:192.168.178.24] HTTP Repsonse is finished +7ms EventedHTTPServer [::ffff:192.168.178.24] Client connection closed +85ms EventedHTTPServer [::ffff:192.168.178.24] HTTP connection was closed +1ms EventedHTTPServer [::ffff:192.168.178.24] HTTP server was closed +0ms

Mit der alten FHEM.js funktioniert es...

Hatte genau das gleiche Problem. Mach mal ein Filter in der config.json auf einen Raum.
Danach konnte ich pairen. Anscheinend ist die Geräteanzahl ein Problem

Posti123 · 24 September 2015, 16:31:06

Zitat von: Zetti am 24 September 2015, 15:24:35
Hallo bin absoluter leie währe schön wenn mir jemand nen tip geben könnte wonach ich noch suchen könnte das Homebridge startret!

0 info it worked if it ends with ok
1 verbose cli [ '/root/.nvm/versions/v0.12.6/bin/node',
1 verbose cli '/root/.nvm/versions/v0.12.6/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start' ]
2 info using npm@2.11.2
3 info using node@v0.12.6
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart homebridge@0.0.0
6 info start homebridge@0.0.0
7 verbose unsafe-perm in lifecycle true
8 info homebridge@0.0.0 Failed to exec start script
9 verbose stack Error: homebridge@0.0.0 start: `node app.js`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (/root/.nvm/versions/v0.12.6/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
9 verbose stack at EventEmitter.emit (events.js:110:17)
9 verbose stack at ChildProcess.<anonymous> (/root/.nvm/versions/v0.12.6/lib/node_modules/npm/lib/utils/spawn.js:24:14)
9 verbose stack at ChildProcess.emit (events.js:110:17)
9 verbose stack at maybeClose (child_process.js:1015:16)
9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
10 verbose pkgid homebridge@0.0.0
11 verbose cwd /home/zetti/homebridge
12 error Linux 3.16.0-4-amd64
13 error argv "/root/.nvm/versions/v0.12.6/bin/node" "/root/.nvm/versions/v0.12.6/bin/npm" "run" "start"
14 error node v0.12.6
15 error npm v2.11.2
16 error code ELIFECYCLE
17 error homebridge@0.0.0 start: `node app.js`
17 error Exit status 1
18 error Failed at the homebridge@0.0.0 start script 'node app.js'.
18 error This is most likely a problem with the homebridge package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error node app.js
18 error You can get their info via:
18 error npm owner ls homebridge
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

root@FHEMSERVER8:/home/zetti/homebridge# npm run start
> homebridge@0.0.0 start /home/zetti/homebridge
> node app.js

Starting HomeBridge server...
undefined:10
}
^
SyntaxError: Unexpected token }
at Object.parse (native)
at Object.<anonymous> (/home/zetti/homebridge/app.js:21:19)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3

npm ERR! Linux 3.16.0-4-amd64
npm ERR! argv "/root/.nvm/versions/v0.12.6/bin/node" "/root/.nvm/versions/v0.12.6/bin/npm" "run" "start"
npm ERR! node v0.12.6
npm ERR! npm v2.11.2
npm ERR! code ELIFECYCLE
npm ERR! homebridge@0.0.0 start: `node app.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the homebridge@0.0.0 start script 'node app.js'.
npm ERR! This is most likely a problem with the homebridge package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node app.js
npm ERR! You can get their info via:
npm ERR! npm owner ls homebridge
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/zetti/homebridge/npm-debug.log

Meine Config.json

{

"platforms": [
{
"platform": "FHEM",
"name": "FHEMSERVER8",
"server": "192.168.XXX.XX",
"port": "8083",

}
],

"accessories": []

vielen vielen dank schon im Vorraus

Das Komma nach "8083" entfernen

Hauswart · 24 September 2015, 17:48:30

Klammer zu am Ende }

bzw ] fehlt auch noch vor Access....

Gesendet von iPad mit Tapatalk

flurin · 24 September 2015, 17:53:54

Für alle, die nicht sicher sind, ob "config.json" richtig ist, es ist ganz einfach -> hier validieren:

http://jsonlint.com/

Zetti · 24 September 2015, 18:43:46

Vielen Dank an alle läuft jetzt

thoffma3 · 24 September 2015, 19:20:20

was mach ich nur falsch. Wiki Anleitung hat bei mir prima funktioniert und Homebridge läuft.Siehe hier:

Code Auswählen

Loading 1 platforms...
[FHEM] Initializing FHEM platform...
starting longpoll: http://192.168.178.50:80/fhem.pl?XHR=1&inform=type=status;filter=.*;since=null;fmt=JSON&timestamp=1443114938841
[FHEM] Fetching FHEM switchable devices...
[FHEM] fetching: http://192.168.178.50:80/fhem?cmd=jsonlist2%20room=Wohnzimmer&XHR=1
Loading 0 accessories...
Server listening on: http://<ip>:8081
[FHEM] got: 8 results
[FHEM] ignoring Fernseher
[FHEM] ignoring FileLog_PIONEERAVRZONE_zone2
[FHEM] PIONEERAVRZONE_zone2 is switchable
[FHEM] PIONEERAVRZONE_zone2 has onOff [state;on,off]
[FHEM] ignoring Roll_WZ
[FHEM] VSX923 is switchable
[FHEM] VSX923 has onOff [state;on,off]
[FHEM] steckdoseA is switchable
[FHEM] steckdoseA has onOff [state;on,off]
[FHEM] steckdoseB is switchable
[FHEM] steckdoseB has onOff [state;on,off]
[FHEM] steckdoseC is switchable
[FHEM] steckdoseC has onOff [state;on,off]
[FHEM] Initializing platform accessory 'PIONEERAVRZONE_zone2'...
[FHEM] creating services for PIONEERAVRZONE_zone2
[FHEM]   information service for PIONEERAVRZONE_zone2
[FHEM]   switch service for PIONEERAVRZONE_zone2
[FHEM]     power characteristic for PIONEERAVRZONE_zone2
[FHEM]     custom volume characteristic for PIONEERAVRZONE_zone2
[FHEM] Initializing platform accessory 'VSX923'...
[FHEM] creating services for VSX923
[FHEM]   information service for VSX923
[FHEM]   switch service for VSX923
[FHEM]     power characteristic for VSX923
[FHEM]     custom volume characteristic for VSX923
[FHEM] Initializing platform accessory 'steckdoseA'...
[FHEM] creating services for steckdoseA
[FHEM]   information service for steckdoseA
[FHEM]   switch service for steckdoseA
[FHEM]     power characteristic for steckdoseA
[FHEM] Initializing platform accessory 'steckdoseB'...
[FHEM] creating services for steckdoseB
[FHEM]   information service for steckdoseB
[FHEM]   switch service for steckdoseB
[FHEM]     power characteristic for steckdoseB
[FHEM] Initializing platform accessory 'steckdoseC'...
[FHEM] creating services for steckdoseC
[FHEM]   information service for steckdoseC
[FHEM]   switch service for steckdoseC
[FHEM]     power characteristic for steckdoseC
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 +82ms
  EventedHTTPServer Server listening on port 51826 +242ms

Leider finden meine Iphone (die sich im gleichen Netzwerk befinden) mit EVE nichts. Woran könnte das liegen. Einmal wurde mir das Homekit in EVE angezeigt und ich wurde aufgefordert den Schlüssel einzugeben. Danach hat man im Log des Homekits auch gesehen das die Validierung erfolgreich war. Aber Geräte wurden in EVE nicht angezeigt. Dort sah es so aus als würde die Identifizierung niemals abgeschlossen sein.

Wenn ich jetzt EVE öffne (auf verschiedenen IPHones getestet, sucht er ewig, findet aber keine Homebridge. Im Log bewegt sich gar ncihts.

Hat jemand eine Idee?

Vielen Dank schonmal

Posti123 · 24 September 2015, 19:22:39

Welche Node Version hast du?

Node -v