Hallo,
ich hatte Homebridge vor einigen Monaten am Laufen. Mittlereweile bekomme ich jedoch keine Verbindung/Antwort mehr.
Homebridge sollte auf meinem FHEM Server laufen.
Der Dienst läuft auch soweit:
sudo service homebridge status
● homebridge.service - LSB: Start daemon at boot time for homebridge
Loaded: loaded (/etc/init.d/homebridge; bad; vendor preset: enabled)
Active: active (exited) since Mi 2017-08-23 17:17:09 CEST; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 2378 ExecStop=/etc/init.d/homebridge stop (code=exited, status=0/SUCCESS)
Process: 10653 ExecStart=/etc/init.d/homebridge start (code=exited, status=0/SUCCESS)
Aug 23 17:17:07 FHEM systemd[1]: Starting LSB: Start daemon at boot time for homebridge...
Aug 23 17:17:07 FHEM su[10658]: Successful su for tim by root
Aug 23 17:17:07 FHEM su[10658]: + ??? root:tim
Aug 23 17:17:07 FHEM su[10658]: pam_unix(su:session): session opened for user tim by (uid=0)
Aug 23 17:17:07 FHEM homebridge[10653]: Homebridge starting
Aug 23 17:17:09 FHEM homebridge[10653]: Homebridge is running PID 10662
Aug 23 17:17:09 FHEM systemd[1]: Started LSB: Start daemon at boot time for homebridge.
tim@FHEM:/opt/fhem/homebridge$
Starte ich homebridge erscheint das im Log
homebridge
*** 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>
[2017-8-23 17:23:26] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-fhem' since we already loaded the same plugin from '/usr/lib/node_modules/homebridge-fhem'.
[2017-8-23 17:23:26] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-http' since we already loaded the same plugin from '/usr/lib/node_modules/homebridge-http'.
[2017-8-23 17:23:26] Loaded plugin: homebridge-fhem
homebridge API version: 2.2
this homebridge-fhem 0.3.7
[2017-8-23 17:23:26] Registering platform 'homebridge-fhem.FHEM'
[2017-8-23 17:23:26] ---
[2017-8-23 17:23:26] Loaded plugin: homebridge-http
[2017-8-23 17:23:26] Registering accessory 'homebridge-http.Http'
[2017-8-23 17:23:26] ---
[2017-8-23 17:23:26] Loaded config.json with 0 accessories and 1 platforms.
[2017-8-23 17:23:26] ---
[2017-8-23 17:23:26] Loading 1 platforms...
[2017-8-23 17:23:26] [FHEM] Initializing FHEM platform...
starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1503501806630
[2017-8-23 17:23:26] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:26] Loading 0 accessories...
Server error: Error: listen EADDRINUSE :::8282
Server listening on: http://<ip>:8283
[2017-8-23 17:23:27] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:27] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:28] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:28] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:29] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:29] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:30] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:30] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:31] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:31] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:32] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:32] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:33] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:33] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:34] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:34] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:35] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:35] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:36] [FHEM] Fetching FHEM devices...
[2017-8-23 17:23:36] [FHEM] Fetching FHEM devices...
Inhalt meiner /opt/fhem/homebridge/homebridge
SSL und Auth verwende ich nicht. Dazu den Port 8085.
{
"bridge": {
"name": "FHEM",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "111-22-333"
},
"platforms": [
{
"platform": "FHEM",
"name": "FHEM",
"server": "127.0.0.1",
"port": "8085",
"filter": "room=Homekit"
}
],
"accessories": []
}
Wie kann man in der Home App einen neuen Pin für ein neues Haus eingeben?
Gruß
TWART016
ZitatServer error: Error: listen EADDRINUSE :::8282
Wenn Du homebridge zum Test manuell startest, stoppe zuerst den Dienst. Sonst sind 2 Prozessen am lauschen.
Mit stoppen und starten habe ich probiert, gleiches Verhalten. Für mich sieht das auch nicht nach dem Problem aus.
Es kommen ganz viele Zeilen
Fetching FHEM devices...
Jedoch wird nichts gefunden.
1. Dienst stoppen
2. homebridge manuell starten
3. Log posten
Anbei das Log
tim@FHEM:/opt/fhem/homebridge$ sudo service homebridge stop
tim@FHEM:/opt/fhem/homebridge$ sudo service homebridge start
tim@FHEM:/opt/fhem/homebridge$ homebridge --debug
*** 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>
[2017-8-25 00:55:55] Loaded plugin: homebridge-fhem
homebridge API version: 2.2
this homebridge-fhem 0.3.7
[2017-8-25 00:55:55] Registering platform 'homebridge-fhem.FHEM'
[2017-8-25 00:55:55] ---
[2017-8-25 00:55:55] Loaded plugin: homebridge-http
[2017-8-25 00:55:55] Registering accessory 'homebridge-http.Http'
[2017-8-25 00:55:55] ---
[2017-8-25 00:55:55] Loaded config.json with 0 accessories and 1 platforms.
[2017-8-25 00:55:55] ---
[2017-8-25 00:55:55] Loading 1 platforms...
[2017-8-25 00:55:55] [FHEM] Initializing FHEM platform...
starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1503615355700
[2017-8-25 00:55:55] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:55] Loading 0 accessories...
Server error: Error: listen EADDRINUSE :::8282
Server listening on: http://<ip>:8283
[2017-8-25 00:55:56] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:56] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:57] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:57] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:58] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:58] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:59] [FHEM] Fetching FHEM devices...
[2017-8-25 00:55:59] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:00] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:00] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:01] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:01] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:02] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:02] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:03] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:03] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:04] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:04] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:05] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:05] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:06] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:06] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:07] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:07] [FHEM] Fetching FHEM devices...
[2017-8-25 00:56:08] [FHEM] Fetching FHEM devices...
^C[2017-8-25 00:56:08] Got SIGINT, shutting down Homebridge...
avahi-daemon ist bereits installiert.
ZitatServer error: Error: listen EADDRINUSE :::8282
Server listening on: http://<ip>:8283
Du hast immer noch etwas anderes, das auf dem Port lauscht.
Mit lsof kannst Du den Prozess identifizieren.
sudo apt-get install lsof
sudo lsof -i :8282
Wenn alle Prozesse gestoppt (oder gekillt) sind, das persist Verzeichnis löschen. Dann homebridge manuell starten.
Das kommt bei lsof -i :8282
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
homebridg 31355 tim 10u IPv6 1650907 0t0 TCP *:8282 (LISTEN)
Was meinst du mit persist Verzeichnis?
Siehst Du? Eine Instanz von homebridge läuft schon. ProzessID = 31355
persist = ~/.homebridge/persist
Gleiche Ergebnis:
tim@FHEM:~/.homebridge$ sudo service homebridge stop
tim@FHEM:~/.homebridge$ sudo lsof -i :8282
tim@FHEM:~/.homebridge$ rm -R persist/
tim@FHEM:~/.homebridge$ ls
accessories config.json
tim@FHEM:~/.homebridge$ sudo service homebridge start
tim@FHEM:~/.homebridge$ homebridge --debug
*** 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>
[2017-8-25 02:06:18] Loaded plugin: homebridge-fhem
homebridge API version: 2.2
this homebridge-fhem 0.3.7
[2017-8-25 02:06:18] Registering platform 'homebridge-fhem.FHEM'
[2017-8-25 02:06:18] ---
[2017-8-25 02:06:18] Loaded plugin: homebridge-http
[2017-8-25 02:06:18] Registering accessory 'homebridge-http.Http'
[2017-8-25 02:06:18] ---
[2017-8-25 02:06:18] Loaded config.json with 0 accessories and 1 platforms.
[2017-8-25 02:06:18] ---
[2017-8-25 02:06:18] Loading 1 platforms...
[2017-8-25 02:06:18] [FHEM] Initializing FHEM platform...
starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1503619578936
[2017-8-25 02:06:18] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:18] Loading 0 accessories...
Server error: Error: listen EADDRINUSE :::8282
Server listening on: http://<ip>:8283
[2017-8-25 02:06:19] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:19] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:20] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:20] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:21] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:21] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:22] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:22] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:23] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:23] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:24] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:24] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:25] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:25] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:26] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:26] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:27] [FHEM] Fetching FHEM devices...
[2017-8-25 02:06:27] [FHEM] Fetching FHEM devices...
Hihi ;D
tim@FHEM:~/.homebridge$ sudo service homebridge start
tim@FHEM:~/.homebridge$ homebridge --debug
Somit hast Du wiederum 2x homebridge gestartet, einaml als Dienst, einmal manuell. ;) Mach nur die zweite!
Jetzt aber
tim@FHEM:~/.homebridge$ sudo service homebridge stop
tim@FHEM:~/.homebridge$ sudo lsof -i :8282
tim@FHEM:~/.homebridge$ rm -R persist/
tim@FHEM:~/.homebridge$ homebridge --debug
*** 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>
[2017-8-25 02:19:59] Loaded plugin: homebridge-fhem
homebridge API version: 2.2
this homebridge-fhem 0.3.7
[2017-8-25 02:19:59] Registering platform 'homebridge-fhem.FHEM'
[2017-8-25 02:19:59] ---
[2017-8-25 02:19:59] Loaded plugin: homebridge-http
[2017-8-25 02:19:59] Registering accessory 'homebridge-http.Http'
[2017-8-25 02:19:59] ---
[2017-8-25 02:19:59] Loaded config.json with 0 accessories and 1 platforms.
[2017-8-25 02:19:59] ---
[2017-8-25 02:19:59] Loading 1 platforms...
[2017-8-25 02:19:59] [FHEM] Initializing FHEM platform...
starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1503620399879
[2017-8-25 02:19:59] [FHEM] Fetching FHEM devices...
[2017-8-25 02:19:59] Loading 0 accessories...
Server listening on: http://<ip>:8282
[2017-8-25 02:20:00] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:00] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:01] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:01] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:02] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:02] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:03] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:03] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:04] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:04] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:05] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:05] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:06] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:06] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:07] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:07] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:08] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:08] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:09] [FHEM] Fetching FHEM devices...
[2017-8-25 02:20:09] [FHEM] Fetching FHEM devices...
Sooo... jetzt kann man sauber anfangen ;)
Jetzt verstehe ich etwas nicht.
Zitatstarting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1503620399879
Aber Du hast gesagt, du nutzt SSL nicht? Tatsächlich in deinem config.json ist kein SSL zu finden, aber der Port 8085, nicht 8083!
Und jetzt sehe ich, dass du die Datei /opt/fhem/homebridge/homebridge gezeigt hättest.
ZitatInhalt meiner /opt/fhem/homebridge/homebridge
SSL und Auth verwende ich nicht. Dazu den Port 8085.
Aber Du startest manuell von dem user pi aus. Was hast Du als config.json in /home/pi/.homebridge?
Zitat von: amenomade am 25 August 2017, 09:11:41
Und jetzt sehe ich, dass du die Datei /opt/fhem/homebridge/homebridge gezeigt hättest. Aber Du startest manuell von dem user pi aus. Was hast Du als config.json in /home/pi/.homebridge?
Daran lag es. Ich wollte eigentlich einen anderen Pfad verlinken. Wie kann ich /opt/fhem/homebridge als Pfad nehmen anstelle von ~/.homebridge?
tim@FHEM:~/.homebridge$ homebridge --debug
*** 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>
[2017-8-25 16:04:58] Loaded plugin: homebridge-fhem
homebridge API version: 2.2
this homebridge-fhem 0.3.7
[2017-8-25 16:04:58] Registering platform 'homebridge-fhem.FHEM'
[2017-8-25 16:04:58] ---
[2017-8-25 16:04:59] Loaded plugin: homebridge-http
[2017-8-25 16:04:59] Registering accessory 'homebridge-http.Http'
[2017-8-25 16:04:59] ---
[2017-8-25 16:04:59] Loaded config.json with 0 accessories and 1 platforms.
[2017-8-25 16:04:59] ---
[2017-8-25 16:04:59] Loading 1 platforms...
[2017-8-25 16:04:59] [FHEM] Initializing FHEM platform...
starting longpoll: http://127.0.0.1:8085/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1503669899354
[2017-8-25 16:04:59] [FHEM] Fetching FHEM devices...
[2017-8-25 16:04:59] Loading 0 accessories...
Server listening on: http://<ip>:8282
[2017-8-25 16:04:59] [FHEM] Checking devices and attributes...
[2017-8-25 16:04:59] [FHEM] executing: http://127.0.0.1:8085/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[2017-8-25 16:04:59] [FHEM] executing: http://127.0.0.1:8085/fhem?cmd=jsonlist2%20TYPE=siri&XHR=1
[2017-8-25 16:04:59] [FHEM] siri device is siri
[2017-8-25 16:04:59] [FHEM] executing: http://127.0.0.1:8085/fhem?cmd=%7B$defs%7Bsiri%7D-%3E%7B%22homebridge-fhem%20version%22%7D%20=%20%220.3.7%22%7D&XHR=1
[2017-8-25 16:04:59] [FHEM] Fetching FHEM devices...
[2017-8-25 16:04:59] [FHEM] fetching: http://127.0.0.1:8085/fhem?cmd=jsonlist2%20room=Homekit&XHR=1
[2017-8-25 16:04:59] [FHEM] got: 7 results
[2017-8-25 16:04:59] [FHEM] mappings for HD_Receiver_Autostart: { On:
{ reading: 'state',
valueOff: '/off|A0|000000/',
cmdOn: 'on',
cmdOff: 'off' } }
[2017-8-25 16:04:59] [FHEM] HD_Receiver_Autostart is switch
[2017-8-25 16:04:59] [FHEM] HD_Receiver_Autostart has
[2017-8-25 16:04:59] [FHEM] On [state;on,off]
2017-08-25 16:04:59 caching: HD_Receiver_Autostart-state: off
[2017-8-25 16:04:59] [FHEM] HD_Receiver_Autostart-state valueOn/valueOff: value off mapped to 0
[2017-8-25 16:04:59] [FHEM] caching: On: false (as boolean; from 'off')
[2017-8-25 16:04:59] [FHEM] mappings for NichtSchalten: { On:
{ reading: 'state',
valueOff: '/off|A0|000000/',
cmdOn: 'on',
cmdOff: 'off' } }
[2017-8-25 16:04:59] [FHEM] On characteristic for Steckdose_Kueche_links:state
[2017-8-25 16:04:59] [FHEM] initial value is: false (boolean)
[2017-8-25 16:04:59] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[2017-8-25 16:04:59] [FHEM] Initializing platform accessory 'Steckdose_Licht_Wohnwand'...
[2017-8-25 16:04:59] [FHEM] creating services for Steckdose_Licht_Wohnwand
[2017-8-25 16:04:59] [FHEM] information service for Steckdose_Licht_Wohnwand
[2017-8-25 16:04:59] [FHEM] manufacturer, model and serial number characteristics for Steckdose_Licht_Wohnwand
[2017-8-25 16:04:59] [FHEM] Switch service for Steckdose_Licht_Wohnwand
[2017-8-25 16:04:59] [FHEM] On characteristic for Steckdose_Licht_Wohnwand:state
[2017-8-25 16:04:59] [FHEM] initial value is: false (boolean)
[2017-8-25 16:04:59] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
Ebenso wird der Hauscode nun im Log angezeigt. Die Geräte in der Home App sind nach wie vor offline (keine Antwort).
Wie kann ich ein neues Haus mit einem neuen Hauscode erstellen?
M.A. ist das beste ein symlink.
Du gehst im /home/pi/.homebridge Verzeichnis, löschst alle config.json dort, und machst ein symlink auf dem config.json vom fhem User in /opt/fhem:
ln -s /opt/fhem/.homebridge/config.json
So kannst Du mit einem einzigen config.json entweder mit User fhem oder mit User pi deinen Hombridge starten.
Alles klar mit dem anderen Ort.
Aber wie bekomme ich eine Verbindung von den Geräten zu Siri? Jetzt steht nur "Keine Antwort" da.
Jetzt kenne ich Siri und iOs leider nicht genug. Wenn nix anderes in der Log (du hast nicht die vollständige Log gezeigt, ich kann nicht sagen, ob alles i.O. ist), würde ich versuchen irgendwie die Sachen in der App zu löschen und neu anlegen.
Vielleicht kann das helfen? https://eve.help.elgato.com/customer/en/portal/articles/2075645-setting-up-an-eve-device-in-another-home?b_id=13397