[gelöst] Zweiter Homematic-Adapter startet nicht

automatix

@samson71 gemacht, keine Änderung

Homoran

@automatix und was steht im log beim Neustart der Instanz?

automatix

@homoran : steh gerade auf der leitung. Wo finde ich die?

automatix

@automatix habe es gefunden, schau gerade mal nach und poste dann

automatix

@automatix

Hier das Ende der Logdatei:

2023-12-08 20:15:28.439  - [32minfo[39m: hm-rega.1 (4979) update favorites to enum.favorites
2023-12-08 20:15:33.653  - [32minfo[39m: hm-rpc.1 (5009) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:15:33.726  - [32minfo[39m: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:15:33.830  - [31merror[39m: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:15:33.832  - [31merror[39m: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:15:34.133  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc server is trying to listen on 192.168.178.108:8082
2023-12-08 20:15:34.135  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc client is trying to connect to 192.168.178.45:2001/ with ["http://192.168.178.108:8082","iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.222  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc <- system.listMethods ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.252  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc <- listDevices ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.406  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc -> 189 devices
2023-12-08 20:15:34.507  - [32minfo[39m: hm-rpc.1 (5009) Connected
2023-12-08 20:15:55.064  - [31merror[39m: hm-rpc.0 (4994) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.082  - [32minfo[39m: hm-rpc.0 (4994) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:15:55.096  - [31merror[39m: hm-rpc.0 (4994) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.111  - [32minfo[39m: hm-rpc.0 (4994) terminating
2023-12-08 20:15:55.115  - [32minfo[39m: hm-rpc.0 (4994) Terminated (NO_ERROR): Without reason
2023-12-08 20:16:03.882  - [32minfo[39m: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:03.925  - [31merror[39m: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:03.926  - [31merror[39m: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:16:26.052  - [32minfo[39m: hm-rega.0 (4964) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:26.177  - [32minfo[39m: hm-rega.0 (4964) terminating
2023-12-08 20:16:26.181  - [32minfo[39m: hm-rega.0 (4964) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:26.556  - [32minfo[39m: hm-rega.0 (4964) terminating
2023-12-08 20:16:29.858  - [32minfo[39m: hm-rpc.0 (5024) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:30.264  - [32minfo[39m: hm-rpc.0 (5024) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:30.267  - [32minfo[39m: hm-rpc.0 (5024) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:672a253d77e59472513d027b6e1395e7"]
2023-12-08 20:16:30.339  - [31merror[39m: hm-rpc.0 (5024) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:33.363  - [32minfo[39m: hm-rega.0 (5035) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:33.585  - [32minfo[39m: hm-rega.0 (5035) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:16:33.715  - [32minfo[39m: hm-rega.0 (5035) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:33.820  - [31merror[39m: hm-rega.0 (5035) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:33.822  - [31merror[39m: hm-rega.0 (5035) CCU 192.168.178.46 unreachable
2023-12-08 20:16:36.276  - [32minfo[39m: hm-rpc.0 (5024) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:36.285  - [32minfo[39m: hm-rpc.0 (5024) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:16:36.303  - [31merror[39m: hm-rpc.0 (5024) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:36.306  - [32minfo[39m: hm-rpc.0 (5024) terminating
2023-12-08 20:16:36.313  - [32minfo[39m: hm-rpc.0 (5024) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:43.781  - [32minfo[39m: hm-rpc.0 (5054) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:44.123  - [32minfo[39m: hm-rpc.0 (5054) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:44.124  - [32minfo[39m: hm-rpc.0 (5054) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:b12b2759017f42979ace9bd39aca4d0d"]
2023-12-08 20:16:44.173  - [31merror[39m: hm-rpc.0 (5054) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001

MOD-EDIT: Code in code-tags gesetzt!

automatix

@homoran : Hier das Ende der Logdatei

2023-12-08 20:15:28.439  - [32minfo[39m: hm-rega.1 (4979) update favorites to enum.favorites
2023-12-08 20:15:33.653  - [32minfo[39m: hm-rpc.1 (5009) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:15:33.726  - [32minfo[39m: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:15:33.830  - [31merror[39m: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:15:33.832  - [31merror[39m: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:15:34.133  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc server is trying to listen on 192.168.178.108:8082
2023-12-08 20:15:34.135  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc client is trying to connect to 192.168.178.45:2001/ with ["http://192.168.178.108:8082","iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.222  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc <- system.listMethods ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.252  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc <- listDevices ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.406  - [32minfo[39m: hm-rpc.1 (5009) xmlrpc -> 189 devices
2023-12-08 20:15:34.507  - [32minfo[39m: hm-rpc.1 (5009) Connected
2023-12-08 20:15:55.064  - [31merror[39m: hm-rpc.0 (4994) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.082  - [32minfo[39m: hm-rpc.0 (4994) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:15:55.096  - [31merror[39m: hm-rpc.0 (4994) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.111  - [32minfo[39m: hm-rpc.0 (4994) terminating
2023-12-08 20:15:55.115  - [32minfo[39m: hm-rpc.0 (4994) Terminated (NO_ERROR): Without reason
2023-12-08 20:16:03.882  - [32minfo[39m: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:03.925  - [31merror[39m: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:03.926  - [31merror[39m: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:16:26.052  - [32minfo[39m: hm-rega.0 (4964) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:26.177  - [32minfo[39m: hm-rega.0 (4964) terminating
2023-12-08 20:16:26.181  - [32minfo[39m: hm-rega.0 (4964) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:26.556  - [32minfo[39m: hm-rega.0 (4964) terminating
2023-12-08 20:16:29.858  - [32minfo[39m: hm-rpc.0 (5024) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:30.264  - [32minfo[39m: hm-rpc.0 (5024) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:30.267  - [32minfo[39m: hm-rpc.0 (5024) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:672a253d77e59472513d027b6e1395e7"]
2023-12-08 20:16:30.339  - [31merror[39m: hm-rpc.0 (5024) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:33.363  - [32minfo[39m: hm-rega.0 (5035) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:33.585  - [32minfo[39m: hm-rega.0 (5035) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:16:33.715  - [32minfo[39m: hm-rega.0 (5035) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:33.820  - [31merror[39m: hm-rega.0 (5035) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:33.822  - [31merror[39m: hm-rega.0 (5035) CCU 192.168.178.46 unreachable
2023-12-08 20:16:36.276  - [32minfo[39m: hm-rpc.0 (5024) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:36.285  - [32minfo[39m: hm-rpc.0 (5024) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:16:36.303  - [31merror[39m: hm-rpc.0 (5024) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:36.306  - [32minfo[39m: hm-rpc.0 (5024) terminating
2023-12-08 20:16:36.313  - [32minfo[39m: hm-rpc.0 (5024) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:43.781  - [32minfo[39m: hm-rpc.0 (5054) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:44.123  - [32minfo[39m: hm-rpc.0 (5054) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:44.124  - [32minfo[39m: hm-rpc.0 (5054) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:b12b2759017f42979ace9bd39aca4d0d"]
2023-12-08 20:16:44.173  - [31merror[39m: hm-rpc.0 (5054) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001

Homoran

@automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

ECONNREFUSED 192.168.178.46:8181

da musst du dir wohl mal due Firewall näher Ansehen

automatix

@homoran : habe jetzt in der Raspberrymatic die Ports 2001 und 8182 freigegeben. Läuft aber immer noch nicht. Hier der Log:

2023-12-08 20:40:10.110  - [32minfo[39m: hm-rpc.0 (5503) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:40:10.506  - [32minfo[39m: hm-rpc.0 (5503) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:40:10.508  - [32minfo[39m: hm-rpc.0 (5503) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:aad9c8421ebcb8242ae91fe4458f8df1"]
2023-12-08 20:40:10.580  - [31merror[39m: hm-rpc.0 (5503) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
2023-12-08 20:40:22.099  - [32minfo[39m: hm-rpc.0 (5503) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:40:22.108  - [32minfo[39m: hm-rpc.0 (5503) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:40:22.135  - [31merror[39m: hm-rpc.0 (5503) Cannot call init: [http://192.168.178.108:2001, ""] Unknown XML-RPC tag 'TITLE'
2023-12-08 20:40:22.137  - [32minfo[39m: hm-rpc.0 (5503) terminating
2023-12-08 20:40:22.140  - [32minfo[39m: hm-rpc.0 (5503) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:40:29.608  - [32minfo[39m: hm-rpc.0 (5518) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:40:29.947  - [32minfo[39m: hm-rpc.0 (5518) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:40:29.949  - [32minfo[39m: hm-rpc.0 (5518) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:837cd7bdb32389d29a5b6cf12e3f4e5c"]
2023-12-08 20:40:30.021  - [31merror[39m: hm-rpc.0 (5518) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
2023-12-08 20:40:41.010  - [32minfo[39m: hm-rega.0 (5534) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:40:41.231  - [32minfo[39m: hm-rega.0 (5534) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:40:41.359  - [32minfo[39m: hm-rega.0 (5534) ReGaHSS 192.168.178.46 up
2023-12-08 20:40:41.485  - [31merror[39m: hm-rega.0 (5534) <-- invalid response: "<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n         \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\">\n <head>\n  <title>401 Unauthorized</title>\n </head>\n <body>\n  <h1>401 Unauthorized</h1>\n </body>\n</html>\n"
2023-12-08 20:40:41.487  - [31merror[39m: hm-rega.0 (5534) ReGaHSS 192.168.178.46 down

MOD-EDIT: Code in code-tags gesetzt!

Homoran

@automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

going to stop: Unknown XML-RPC tag 'TITLE'

Immer noch die Firewall!

@automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

habe jetzt in der Raspberrymatic die Ports 2001 und 8182 freigegeben.

warum die?

automatix

@homoran : Sorry, 2001 und 8181.

Jetzt folgender log:

2023-12-08 20:53:03.402  - [32minfo[39m: hm-rpc.0 (5767) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:53:03.740  - [32minfo[39m: hm-rpc.0 (5767) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:53:03.742  - [32minfo[39m: hm-rpc.0 (5767) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:8e301537134b939773d413fcfcd396ac"]
2023-12-08 20:53:03.826  - [31merror[39m: hm-rpc.0 (5767) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
2023-12-08 20:53:08.532  - [32minfo[39m: hm-rega.0 (5782) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:53:08.753  - [32minfo[39m: hm-rega.0 (5782) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:53:08.884  - [32minfo[39m: hm-rega.0 (5782) ReGaHSS 192.168.178.46 up
2023-12-08 20:53:09.000  - [31merror[39m: hm-rega.0 (5782) <-- invalid response: "<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n         \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\">\n <head>\n  <title>401 Unauthorized</title>\n </head>\n <body>\n  <h1>401 Unauthorized</h1>\n </body>\n</html>\n"
2023-12-08 20:53:09.001  - [31merror[39m: hm-rega.0 (5782) ReGaHSS 192.168.178.46 down

MOD-EDIT: Code in code-tags gesetzt!

Homoran

@automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

, 2001 und 8181.

https://www.iobroker.net/#de/adapters/adapterref/iobroker.hm-rpc/README.md?homematicport

automatix

@homoran Danke für den Link, ich schaue mir morgen mal die Firewall der Raspberrymatic noch mal genauer an.

Homoran

@automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

@homoran Danke für den Link, ich schaue mir morgen mal die Firewall der Raspberrymatic noch mal genauer an.

und das hier
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

Samson71

@automatix
Mach die doch einfach zum Testen mal für den Moment ganz aus. Wenn es dann geht ist zumindest klar woran es liegt.

Homoran

@samson71 sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

@automatix
Mach die doch einfach zum Testen mal für den Moment ganz aus. Wenn es dann geht ist zumindest klar woran es liegt.

@automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

Unauthorized

automatix

@samson71
habe die Firewall im Raspi komplett ausgemacht:

keine Änderung

der Zugriff über den Link geht:

automatix

@homoran

hier der aktuelle Eintrag in der Logdatei:

2023-12-10 14:44:24.841  - [34mdebug[39m: hm-rpc.2 (1277) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-12-10 14:44:24.904  - [34mdebug[39m: hm-rpc.2 (1277) Objects client ready ... initialize now
2023-12-10 14:44:24.909  - [34mdebug[39m: hm-rpc.2 (1277) Objects create System PubSub Client
2023-12-10 14:44:24.912  - [34mdebug[39m: hm-rpc.2 (1277) Objects create User PubSub Client
2023-12-10 14:44:24.971  - [34mdebug[39m: hm-rpc.2 (1277) Objects client initialize lua scripts
2023-12-10 14:44:24.987  - [34mdebug[39m: hm-rpc.2 (1277) Objects connected to redis: 127.0.0.1:9001
2023-12-10 14:44:25.038  - [34mdebug[39m: hm-rpc.2 (1277) Redis States: Use Redis connection: 127.0.0.1:9000
2023-12-10 14:44:25.062  - [34mdebug[39m: hm-rpc.2 (1277) States create System PubSub Client
2023-12-10 14:44:25.064  - [34mdebug[39m: hm-rpc.2 (1277) States create User PubSub Client
2023-12-10 14:44:25.134  - [34mdebug[39m: hm-rpc.2 (1277) States connected to redis: 127.0.0.1:9000
2023-12-10 14:44:25.200  - [34mdebug[39m: hm-rpc.2 (1277) Plugin sentry Initialize Plugin (enabled=true)
2023-12-10 14:44:26.018  - [32minfo[39m: hm-rpc.2 (1277) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-10 14:44:26.230  - [32minfo[39m: hm-rpc.2 (1277) xmlrpc server is trying to listen on 192.168.178.108:8081
2023-12-10 14:44:26.233  - [32minfo[39m: hm-rpc.2 (1277) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.1:8081","iobroker:hm-rpc.2:a24f120b5aed6aac0b2e30891de7b91c"]
2023-12-10 14:44:26.235  - [34mdebug[39m: hm-rpc.2 (1277) Connect...
2023-12-10 14:44:26.237  - [34mdebug[39m: hm-rpc.2 (1277) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.1:8081","iobroker:hm-rpc.2:a24f120b5aed6aac0b2e30891de7b91c"]
2023-12-10 14:44:26.266  - [34mdebug[39m: hm-rpc.2 (1277) start connecting interval
2023-12-10 14:44:26.309  - [31merror[39m: hm-rpc.2 (1277) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'

Zeile 16 / 17 liegt wohl der fehler, kann mir aber nicht erklären warum. Wenn ich dem Adapterpaar 2 die IP-Adresse des Adapterpaar 1 gebe und Adapterpaar 1 abschalte dann funktioniert es. Kann also nicht mit der Einstellung im Raspberrymatic zu tun haben.

automatix

@automatix

Der Schluss im letzten Satz stimmt nicht. Hat doch was mit der Rasperrymatic zu tun. Werde die mal neu aufsetzen.

automatix

@automatix

Ich habe jetzt die Raspberrymatic neu aufgesetzt und die Firewall wie folgt konfiguriert:

Jetzt funktionieren auch die neu hinzugekommenen Adapter für die zweite CCU. Danke für die Unterstützung und Geduld.

Community Forum

NEWS

[gelöst] Zweiter Homematic-Adapter startet nicht

Support us

635

32.7k

82.4k

1.3m