...als ich jetzt das aufrufen der Seite nochmals versucht habe, hat es plötzlich funktioniert?!
Also jetzt erscheint die Login Seite an der ich mich anmelden kann...
Wie kommt das denn und was haben die Eingaben bewirkt.
...als ich jetzt das aufrufen der Seite nochmals versucht habe, hat es plötzlich funktioniert?!
Also jetzt erscheint die Login Seite an der ich mich anmelden kann...
Wie kommt das denn und was haben die Eingaben bewirkt.
Die Eingaben haben gar nichts bewirkt. Sie haben nur einen Status angezeigt.
nc -zv localhost 8080 versucht sich auf Port 8080 zu connecten und scheitert. So wie du es beschrieben hast, als du es mit dem Browser versucht hast.
ps aux | grep homebridge zeigt genau das gleiche. Der Befehl zeigt die Prozessliste an, wobei er alle Ausgaben, in denen der Begriff homebridge nicht vorkommt, wegfiltert. Zu sehen sein müsste zusätzlich homebridge-config-ui-x.
sudo netstat -tulpen sagt das auch. Dieser Befehl zeigt alle offenen Port an. Port 8080 fehlt.
Eindeutig. Der Kram läuft nicht. Aber dann kommt das homebridge-Log. Und das sagt um 12:48:46 klar, das homebridge-config-ui-x geladen wird:
Nov 21 12:48:46 raspberrypi homebridge[21983]: [11/21/2018, 12:48:46 PM] Loaded config.json with 0 accessories and 1 platforms.
Nov 21 12:48:46 raspberrypi homebridge[21983]: [11/21/2018, 12:48:46 PM] ---
Nov 21 12:48:46 raspberrypi homebridge[21983]: [11/21/2018, 12:48:46 PM] Loaded plugin: homebridge-config-ui-x
Und es kommt noch besser - drei Sekunden später sagt das Log, das homebridge-config-ui-x läuft:
Nov 21 12:48:49 raspberrypi homebridge[21983]: [11/21/2018, 12:48:49 PM] [Config] Console v3.9.0 is listening on port 8080.
Die obigen drei Befehle müssten nun eine andere Ausgabe ergeben. Ich kann dir nicht sagen, warum das nicht ging und jetzt doch. Ich war's nicht!
Könnte es sein, dass vielleicht homebridge-config-ui-x nach einer Weile aufhört zu funktionieren? Hoffentlich nicht, denn darauf hätte ich auch keine Antwort. Offenbar musste man nur mal dagegentreten.
Stefan
Hallo, endlich habe ich einen Beitrag mit dem selben Problem gefunden. Einzige Unterschied ist bei mir nur, dass die Info
[Config] Console v3.9.0 is listening on port 8080.
im homebridge-Log zu finden ist. Ebenso fehlt bei sudo netstat -tulpen der port 8080 bei mir.
Was kann ich dagegen tun?
Zusätzlich nochmal die Log:
pi@raspberrypi:~ $ nc -zv localhost 8080
nc: connect to localhost port 8080 (tcp) failed: Connection refused
nc: connect to localhost port 8080 (tcp) failed: Connection refused
pi@raspberrypi:~ $ ps aux | grep homebridge
homebri+ 27553 0.0 2.9 85072 27820 ? Rsl 16:52 0:00 homebridge
pi 27561 0.0 0.0 4372 544 pts/1 R+ 16:52 0:00 grep --color=auto homebridge
pi@raspberrypi:~ $ sudo netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 1000 129884 16865/Xtightvnc
tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 1000 129882 16865/Xtightvnc
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 78086 23580/sshd
tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1000 131981 18516/node-red
tcp6 0 0 :::22 :::* LISTEN 0 78088 23580/sshd
udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12676 341/dhcpcd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 9561 290/avahi-daemon: r
udp 0 0 0.0.0.0:46882 0.0.0.0:* 108 9563 290/avahi-daemon: r
udp6 0 0 :::42455 :::* 108 9564 290/avahi-daemon: r
udp6 0 0 :::546 :::* 0 13392 341/dhcpcd
udp6 0 0 :::5353 :::* 108 9562 290/avahi-daemon: r
pi@raspberrypi:~ $ sudo systemctl restart homebridge; sudo journalctl -fau homebridge
-- Logs begin at Mon 2019-02-25 12:54:43 CET. --
Feb 25 16:52:46 raspberrypi homebridge[27660]: at tryModuleLoad (internal/modules/cjs/loader.js:566:12)
Feb 25 16:52:46 raspberrypi homebridge[27660]: at Function.Module._load (internal/modules/cjs/loader.js:558:3)
Feb 25 16:52:46 raspberrypi homebridge[27660]: at Function.Module.runMain (internal/modules/cjs/loader.js:797:12)
Feb 25 16:52:46 raspberrypi homebridge[27660]: at executeUserCode (internal/bootstrap/node.js:526:15)
Feb 25 16:52:46 raspberrypi homebridge[27660]: at startMainThreadExecution (internal/bootstrap/node.js:439:3)
Feb 25 16:52:46 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=1/FAILURE
Feb 25 16:52:46 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
Feb 25 16:52:46 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
Feb 25 16:52:48 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
Feb 25 16:52:48 raspberrypi systemd[1]: Started Node.js HomeKit Server.
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Loaded config.json with 2 accessories and 2 platforms.
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] ---
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Loaded plugin: homebridge-config-ui-x
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Registering platform 'homebridge-config-ui-x.config'
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] ---
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Loaded plugin: homebridge-homematic
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Registering platform 'homebridge-homematic.HomeMatic'
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] ---
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Loaded plugin: homebridge-iobroker
Feb 25 16:52:50 raspberrypi homebridge[27698]: homebridge API version: 2.3
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Registering platform 'homebridge-iobroker.iobroker'
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] ---
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Loaded plugin: homebridge-magichome
Feb 25 16:52:50 raspberrypi homebridge[27698]: homebridge API version: 2.3
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Registering accessory 'homebridge-magichome.MagicHome'
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] ---
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Loaded plugin: homebridge-milight
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] Registering platform 'homebridge-milight.MiLight'
Feb 25 16:52:50 raspberrypi homebridge[27698]: [2/25/2019, 4:52:50 PM] ---
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] Loaded plugin: homebridge-some-smartshades
Feb 25 16:52:51 raspberrypi homebridge[27698]: homebridge API version: 2.3
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] Registering accessory 'homebridge-soma-smartshades.SmartShades'
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] ---
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] Loading 2 platforms...
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [Config] Initializing config platform...
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [Config] Spawning homebridge-config-ui-x with PID 27750
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] Initializing HomeMatic platform...
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] Homematic Plugin Version 0.1.1
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] Plugin by thkl https://github.com/thkl
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] Homematic is a registered trademark of the EQ-3 AG
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] Please report any issues to https://github.com/thkl/homebridge-homematic/issues
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] running in production mode
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] will connect to your ccu at 192.168.0.213
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] using xmprpc for communication with BidCos-RF
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] init RPC for BidCos-RF.
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] local ip used : 192.168.0.67. you may change that with local_ip parameter in config
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] init RPC for VirtualDevices.
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [HomeMatic CCU] local ip used : 192.168.0.67. you may change that with local_ip parameter in config
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] Loading 2 accessories...
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [Spiegel LED] Initializing MagicHome accessory...
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [LED] Initializing MagicHome accessory...
Feb 25 16:52:51 raspberrypi homebridge[27698]: Load homebridge-iobroker.iobroker
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [homebridge-iobroker.iobroker] iobroker Init
Feb 25 16:52:51 raspberrypi homebridge[27698]: /usr/local/lib/node_modules/homebridge-iobroker/index.js:29
Feb 25 16:52:51 raspberrypi homebridge[27698]: this.host = config.host;
Feb 25 16:52:51 raspberrypi homebridge[27698]: ^
Feb 25 16:52:51 raspberrypi homebridge[27698]: TypeError: Cannot read property 'host' of null
Feb 25 16:52:51 raspberrypi homebridge[27698]: at new iobroker (/usr/local/lib/node_modules/homebridge-iobroker/index.js:29:22)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Server._loadDynamicPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:347:30)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:88:8)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Module._compile (internal/modules/cjs/loader.js:734:30)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:745:10)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Module.load (internal/modules/cjs/loader.js:626:32)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at tryModuleLoad (internal/modules/cjs/loader.js:566:12)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Function.Module._load (internal/modules/cjs/loader.js:558:3)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at Function.Module.runMain (internal/modules/cjs/loader.js:797:12)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at executeUserCode (internal/bootstrap/node.js:526:15)
Feb 25 16:52:51 raspberrypi homebridge[27698]: at startMainThreadExecution (internal/bootstrap/node.js:439:3)
Alles anzeigenFeb 25 16:52:51 raspberrypi homebridge[27698]: Load homebridge-iobroker.iobroker
Feb 25 16:52:51 raspberrypi homebridge[27698]: [2/25/2019, 4:52:51 PM] [homebridge-iobroker.iobroker] iobroker Init
Feb 25 16:52:51 raspberrypi homebridge[27698]: /usr/local/lib/node_modules/homebridge-iobroker/index.js:29
Feb 25 16:52:51 raspberrypi homebridge[27698]: this.host = config.host;
Feb 25 16:52:51 raspberrypi homebridge[27698]: ^
Feb 25 16:52:51 raspberrypi homebridge[27698]: TypeError: Cannot read property 'host' of null
Und schon erledigt. Homebridge startet nicht. Ich habe keine Ahnung von iobroker, dem zugehörigen Plugin oder was du da treiben willst, aber offenbar fehlt in config.json die Konfiguration von host. Behauptet zumindest die Fehlermeldung.
{
"platform" : "homebridge-iobroker.iobroker",
"name" : "iobroker",
"host": "http://localhost:8084",
"filter": "*",
"switches": [
"adapter.0.object_1",
"adapter.0.object_2",
"adapter.0.object_3",
...
]
}
Alles anzeigen
Stefan