Homekit

[Teknox]

Ich will Fhem mit HomeKit verwenden doch wenn ich die Homebridge starten will kommt folgende Fehlermeldung:
Job for homebridge.service failed. See 'systemctl status homebridge.service' and 'journalctl -xn' for details.
Verwendet jemand Apple Homekit mit Fhem oder kennt das Problem?

[amenomade]

systemctl status homebridge.service' and 'journalctl -xn' for details.

Und was sagen die?

[Teknox]

Wie und wo kann ich das Aufrufen?

[amenomade]

In einem Terminal

[Teknox]

systemctl:

UNIT                       LOAD   ACTIVE SUB       DESCRIPTION
  proc-sys-fs-binfmt_misc.automount loaded active waiting   Arbitrary Executable
  sys-devices-platform-soc-3f201000.serial-tty-ttyAMA0-hci0-rfkill1.device loade
  sys-devices-platform-soc-3f201000.serial-tty-ttyAMA0-hci0.device loaded active
  sys-devices-platform-soc-3f201000.serial-tty-ttyAMA0.device loaded active plug
  sys-devices-platform-soc-3f202000.sdhost-mmc_host-mmc0-mmc0:aaaa-block-mmcblk0
  sys-devices-platform-soc-3f202000.sdhost-mmc_host-mmc0-mmc0:aaaa-block-mmcblk0
  sys-devices-platform-soc-3f202000.sdhost-mmc_host-mmc0-mmc0:aaaa-block-mmcblk0
  sys-devices-platform-soc-3f300000.mmc-mmc_host-mmc1-mmc1:0001-mmc1:0001:1-ieee
  sys-devices-platform-soc-3f300000.mmc-mmc_host-mmc1-mmc1:0001-mmc1:0001:1-net-
  sys-devices-platform-soc-3f980000.usb-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-net-et
  sys-devices-platform-soc-3f980000.usb-usb1-1\x2d1-1\x2d1.2-1\x2d1.2:1.0-tty-tt
  sys-devices-platform-soc-soc:audio-sound-card0.device loaded active plugged   
  sys-devices-virtual-tty-ttyprintk.device loaded active plugged   /sys/devices/
  sys-module-configfs.device loaded active plugged   /sys/module/configfs
  sys-module-fuse.device     loaded active plugged   /sys/module/fuse
  sys-subsystem-bluetooth-devices-hci0.device loaded active plugged   /sys/subsy
  sys-subsystem-net-devices-eth0.device loaded active plugged   SMSC9512/9514 Fa
  sys-subsystem-net-devices-wlan0.device loaded active plugged   /sys/subsystem/
  -.mount                    loaded active mounted   /
  boot.mount                 loaded active mounted   /boot
  dev-mqueue.mount           loaded active mounted   POSIX Message Queue File Sy
  etc-machine\x2did.mount    loaded active mounted   /etc/machine-id

journalctl -xn:

-- Logs begin at So 2017-08-13 21:09:24 CEST, end at Di 2017-08-15 17:57:25 CEST
Aug 15 17:56:13 raspberrypi systemd[7752]: Starting Sockets.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 15 17:56:13 raspberrypi systemd[7752]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 15 17:56:13 raspberrypi systemd[7752]: Starting Basic System.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 15 17:56:13 raspberrypi systemd[7752]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up

[amenomade]

Sorry. Mach lieber

Code Auswählen Erweitern

sudo journalctl -u homebridge

[Teknox]

Logs begin at So 2017-08-13 21:09:24 CEST, end at Di 2017-08-15 18:46:20 CEST
Aug 15 16:56:04 raspberrypi systemd[1]: Starting SYSV: Enable service provided b
Aug 15 16:56:04 raspberrypi systemd[1]: homebridge.service: control process exit
Aug 15 16:56:04 raspberrypi systemd[1]: Failed to start SYSV: Enable service pro
Aug 15 16:56:04 raspberrypi systemd[1]: Unit homebridge.service entered failed s
Aug 15 16:57:41 raspberrypi systemd[1]: Starting SYSV: Enable service provided b
Aug 15 16:57:41 raspberrypi systemd[1]: homebridge.service: control process exit
Aug 15 16:57:41 raspberrypi systemd[1]: Failed to start SYSV: Enable service pro
Aug 15 16:57:41 raspberrypi systemd[1]: Unit homebridge.service entered failed s

[amenomade]

Da fehlt aber die rechte Hälfte von jeder Nachricht!

Entweders ein grösseres Terminalfenster, oder mach

Code Auswählen Erweitern

sudo journalctl -u homebridge | more dann mit Leerzeichen nach und nach scrollen.

Oder

Code Auswählen Erweitern

sudo journalctl -u homebridge > log.txt Und log.txt hier anhängen oder kopieren.

[Teknox]

Mehr als das kommt da nicht bei deinem Befehl kommt das selbe wie zuvor:
systemctl:

-- Logs begin at Di 2017-08-15 20:09:54 CEST, end at Di 2017-08-15 20:27:35 CEST. --
Aug 15 20:24:33 raspberrypi sudo[1552]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -u homebridge
Aug 15 20:24:33 raspberrypi sudo[1552]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Aug 15 20:24:33 raspberrypi sudo[1552]: pam_unix(sudo:session): session closed for user root
Aug 15 20:25:02 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Aug 15 20:25:02 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.
Aug 15 20:27:27 raspberrypi sudo[1563]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -u homebridge
Aug 15 20:27:27 raspberrypi sudo[1563]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Aug 15 20:27:27 raspberrypi sudo[1563]: pam_unix(sudo:session): session closed for user root
Aug 15 20:27:35 raspberrypi sudo[1573]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xn
Aug 15 20:27:35 raspberrypi sudo[1573]: pam_unix(sudo:session): session opened for user root by pi(uid=0)

journalctl.xn:

● homebridge.service - SYSV: Enable service provided by daemon.
   Loaded: loaded (/etc/init.d/homebridge)
   Active: failed (Result: exit-code) since Di 2017-08-15 20:21:59 CEST; 6min ago
  Process: 1502 ExecStart=/etc/init.d/homebridge start (code=exited, status=203/EXEC)

Aug 15 20:21:59 raspberrypi systemd[1]: homebridge.service: control process exited, code=exited status=203
Aug 15 20:21:59 raspberrypi systemd[1]: Failed to start SYSV: Enable service provided by daemon..
Aug 15 20:21:59 raspberrypi systemd[1]: Unit homebridge.service entered failed state.

[amenomade]

Aaah das ist viel besser. Jetzt sieht man das Ende des Befehls, mit Fehlercode:

Aug 15 20:21:59 raspberrypi systemd[1]: homebridge.service: control process exited, code=exited status=203

Und damit kann man ein bisschen untersuchen.
Wo liegt dein config.json? Und was hat die Datei für Berechitungen?

[Teknox]

Im Ordner homebridge unter Benutzer pi und Sie hat erstmal alle Berechtigungen bekommen

[amenomade]

Das heisst in /home/pi/homebridge mit rwxrwxrwx?

Dann zeig bitte jetzt /etc/systemd/system/homebridge.service

[Teknox]

Verzeichnis nicht gefunden oder welchen Befehl brauche ich?

[amenomade]

Hmmm. Nach welcher Anleitung hast Du homebridge eingestellt?

[Teknox]

https://www.youtube.com/watch?v=dL35MdnLcZY&index=17&list=PLcXIjZgo0R3CyA42uH6oOlHCEohL4EZTB
Hab das Tutorial verwendet um HomeKit verwenden zu können. Nur das mit dem fhem Benutzer (Ab der 5. Minute im Video) hat nicht geklappt weshalb ich einfach ganz normal weiter gemacht habe. Bin noch recht neu was den Pi und Shem angeht und kenne daher leider noch nicht alle Grundlagen.