Homematic CCU3 Adapter
-
hallo, ich benötige mal wieder etwas Hilfe , ich versuche seit TAGEN DIE HOMEMATIC CCU3 in den iobroker zu installieren.
muss ich in der ccu3 etwas einstellen ? ichnhabe mal einige Fotos angehängt, ich weis wirklich nicht woran es liegen kann
-
@tmischek sagte in Homematic CCU3 Adapter:
muss ich in der ccu3 etwas einstellen ? i
ja! die Firewall
PS ich hab auch was angehängt
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1 -
@homoran danke für die schnelle Antwort, firewall hatte ich alle möglichen Kombination bis zum vollzugrif ausprobiert, leider ohne erfolg.
-
-
-
@tmischek sagte in Homematic CCU3 Adapter:
bitte keine Screenshots sondern text in code-tags
näheres hier
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1 -
2023-09-10 22:03:00.581 - info: hm-rpc.0 (10297) xmlrpc -> 192.168.178.134:2001/ init ["http://192.168.178.119:2001",""] 2023-09-10 22:03:00.586 - error: hm-rpc.0 (10297) Cannot call init: [http://192.168.178.119:2001, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:00.590 - info: hm-rpc.0 (10297) terminating 2023-09-10 22:03:00.590 - info: hm-rpc.0 (10297) Terminated (NO_ERROR): Without reason 2023-09-10 22:03:01.115 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR) 2023-09-10 22:03:01.115 - info: host.buanet-iobroker Restart adapter system.adapter.hm-rpc.0 because enabled 2023-09-10 22:03:01.773 - error: hm-rpc.1 (10312) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:01.778 - info: hm-rpc.1 (10312) xmlrpc -> 192.168.178.134:2010/ init ["http://192.168.178.120:2010",""] 2023-09-10 22:03:01.783 - error: hm-rpc.1 (10312) Cannot call init: [http://192.168.178.120:2010, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:01.825 - info: hm-rpc.1 (10312) terminating 2023-09-10 22:03:01.826 - info: hm-rpc.1 (10312) Terminated (NO_ERROR): Without reason 2023-09-10 22:03:02.351 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR) 2023-09-10 22:03:02.352 - info: host.buanet-iobroker Restart adapter system.adapter.hm-rpc.1 because enabled 2023-09-10 22:03:21.721 - info: hm-rega.0 (10037) ReGaHSS 192.168.178.134 up 2023-09-10 22:03:21.735 - error: hm-rega.0 (10037) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 2023-09-10 22:03:21.735 - error: hm-rega.0 (10037) ReGaHSS 192.168.178.134 down 2023-09-10 22:03:29.604 - info: admin.0 (910) <== Disconnect system.user.admin from ::ffff:192.168.178.51 2023-09-10 22:03:31.144 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 started with pid 10376 2023-09-10 22:03:32.316 - info: hm-rpc.0 (10376) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:03:32.386 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 started with pid 10391 2023-09-10 22:03:32.417 - info: hm-rpc.0 (10376) xmlrpc server is trying to listen on 192.168.178.119:2001 2023-09-10 22:03:32.418 - info: hm-rpc.0 (10376) xmlrpc client is trying to connect to 192.168.178.134:2001/ with ["http://192.168.178.119:2001","buanet-iobroker:hm-rpc.0:acce64c607d33bd4c445f4e3bb1de731"] 2023-09-10 22:03:32.439 - error: hm-rpc.0 (10376) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:33.357 - info: hm-rpc.1 (10391) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:03:33.420 - info: hm-rpc.1 (10391) xmlrpc server is trying to listen on 192.168.178.120:2010 2023-09-10 22:03:33.421 - info: hm-rpc.1 (10391) xmlrpc client is trying to connect to 192.168.178.134:2010/ with ["http://192.168.178.120:2010","buanet-iobroker:hm-rpc.1:76fc2a99a01d93259b609250e6eecb80"] 2023-09-10 22:03:33.440 - error: hm-rpc.1 (10391) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:35.538 - info: host.buanet-iobroker stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2023-09-10 22:03:35.540 - info: hm-rega.0 (10037) Got terminate signal TERMINATE_YOURSELF 2023-09-10 22:03:35.562 - info: hm-rega.0 (10037) terminating 2023-09-10 22:03:35.563 - info: hm-rega.0 (10037) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-09-10 22:03:35.580 - info: host.buanet-iobroker stopInstance system.adapter.hm-rega.0 send kill signal 2023-09-10 22:03:36.087 - info: host.buanet-iobroker instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-09-10 22:03:36.319 - info: host.buanet-iobroker stopInstance system.adapter.hm-rpc.0 (force=false, process=true) 2023-09-10 22:03:36.323 - info: hm-rpc.0 (10376) Got terminate signal TERMINATE_YOURSELF 2023-09-10 22:03:36.324 - info: hm-rpc.0 (10376) xmlrpc -> 192.168.178.134:2001/ init ["http://192.168.178.119:2001",""] 2023-09-10 22:03:36.329 - error: hm-rpc.0 (10376) Cannot call init: [http://192.168.178.119:2001, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:36.329 - info: hm-rpc.0 (10376) terminating 2023-09-10 22:03:36.330 - info: hm-rpc.0 (10376) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-09-10 22:03:36.374 - info: host.buanet-iobroker stopInstance system.adapter.hm-rpc.0 send kill signal 2023-09-10 22:03:36.856 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-09-10 22:03:37.699 - info: host.buanet-iobroker stopInstance system.adapter.hm-rpc.1 (force=false, process=true) 2023-09-10 22:03:37.701 - info: hm-rpc.1 (10391) Got terminate signal TERMINATE_YOURSELF 2023-09-10 22:03:37.702 - info: hm-rpc.1 (10391) xmlrpc -> 192.168.178.134:2010/ init ["http://192.168.178.120:2010",""] 2023-09-10 22:03:37.708 - error: hm-rpc.1 (10391) Cannot call init: [http://192.168.178.120:2010, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:37.708 - info: hm-rpc.1 (10391) terminating 2023-09-10 22:03:37.709 - info: hm-rpc.1 (10391) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-09-10 22:03:37.741 - info: host.buanet-iobroker stopInstance system.adapter.hm-rpc.1 send kill signal 2023-09-10 22:03:38.234 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-09-10 22:03:38.610 - info: host.buanet-iobroker instance system.adapter.hm-rega.0 started with pid 10406 2023-09-10 22:03:39.934 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 started with pid 10417 2023-09-10 22:03:40.129 - info: hm-rega.0 (10406) starting. Version 3.0.47 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:03:40.232 - info: hm-rega.0 (10406) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT 2023-09-10 22:03:40.312 - info: hm-rega.0 (10406) ReGaHSS 192.168.178.134 up 2023-09-10 22:03:40.420 - error: hm-rega.0 (10406) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 2023-09-10 22:03:40.421 - error: hm-rega.0 (10406) ReGaHSS 192.168.178.134 down 2023-09-10 22:03:41.187 - info: hm-rpc.0 (10417) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:03:41.255 - info: hm-rpc.0 (10417) xmlrpc server is trying to listen on 192.168.178.119:2001 2023-09-10 22:03:41.256 - info: hm-rpc.0 (10417) xmlrpc client is trying to connect to 192.168.178.134:2001/ with ["http://192.168.178.119:2001","buanet-iobroker:hm-rpc.0:418a6c26e8106b95bc957468d0f71137"] 2023-09-10 22:03:41.277 - error: hm-rpc.0 (10417) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:03:41.279 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 started with pid 10436 2023-09-10 22:03:42.217 - info: hm-rpc.1 (10436) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:03:42.278 - info: hm-rpc.1 (10436) xmlrpc server is trying to listen on 192.168.178.120:2010 2023-09-10 22:03:42.279 - info: hm-rpc.1 (10436) xmlrpc client is trying to connect to 192.168.178.134:2010/ with ["http://192.168.178.120:2010","buanet-iobroker:hm-rpc.1:9cfc8cb537a9960629311509e5496e7e"] 2023-09-10 22:03:42.298 - error: hm-rpc.1 (10436) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:04:10.461 - info: hm-rega.0 (10406) ReGaHSS 192.168.178.134 up 2023-09-10 22:04:10.474 - error: hm-rega.0 (10406) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 2023-09-10 22:04:10.474 - error: hm-rega.0 (10406) ReGaHSS 192.168.178.134 down 2023-09-10 22:04:11.272 - error: hm-rpc.0 (10417) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:04:11.279 - info: hm-rpc.0 (10417) xmlrpc -> 192.168.178.134:2001/ init ["http://192.168.178.119:2001",""] 2023-09-10 22:04:11.286 - error: hm-rpc.0 (10417) Cannot call init: [http://192.168.178.119:2001, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:04:11.327 - info: hm-rpc.0 (10417) terminating 2023-09-10 22:04:11.328 - info: hm-rpc.0 (10417) Terminated (NO_ERROR): Without reason 2023-09-10 22:04:11.858 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR) 2023-09-10 22:04:11.859 - info: host.buanet-iobroker Restart adapter system.adapter.hm-rpc.0 because enabled 2023-09-10 22:04:12.295 - error: hm-rpc.1 (10436) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:04:12.299 - info: hm-rpc.1 (10436) xmlrpc -> 192.168.178.134:2010/ init ["http://192.168.178.120:2010",""] 2023-09-10 22:04:12.304 - error: hm-rpc.1 (10436) Cannot call init: [http://192.168.178.120:2010, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:04:12.346 - info: hm-rpc.1 (10436) terminating 2023-09-10 22:04:12.347 - info: hm-rpc.1 (10436) Terminated (NO_ERROR): Without reason 2023-09-10 22:04:12.877 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR) 2023-09-10 22:04:12.877 - info: host.buanet-iobroker Restart adapter system.adapter.hm-rpc.1 because enabled 2023-09-10 22:04:40.511 - info: hm-rega.0 (10406) ReGaHSS 192.168.178.134 up 2023-09-10 22:04:40.523 - error: hm-rega.0 (10406) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 2023-09-10 22:04:40.524 - error: hm-rega.0 (10406) ReGaHSS 192.168.178.134 down 2023-09-10 22:04:41.886 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 started with pid 10499 2023-09-10 22:04:42.827 - info: hm-rpc.0 (10499) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:04:42.893 - info: hm-rpc.0 (10499) xmlrpc server is trying to listen on 192.168.178.119:2001 2023-09-10 22:04:42.893 - info: hm-rpc.0 (10499) xmlrpc client is trying to connect to 192.168.178.134:2001/ with ["http://192.168.178.119:2001","buanet-iobroker:hm-rpc.0:e08bed3ab52b15c42940d68fe3ba7033"] 2023-09-10 22:04:42.915 - error: hm-rpc.0 (10499) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:04:42.917 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 started with pid 10514 2023-09-10 22:04:43.892 - info: hm-rpc.1 (10514) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:04:43.959 - info: hm-rpc.1 (10514) xmlrpc server is trying to listen on 192.168.178.120:2010 2023-09-10 22:04:43.959 - info: hm-rpc.1 (10514) xmlrpc client is trying to connect to 192.168.178.134:2010/ with ["http://192.168.178.120:2010","buanet-iobroker:hm-rpc.1:b92744cc3571f30412c8f28fa202a933"] 2023-09-10 22:04:43.979 - error: hm-rpc.1 (10514) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:05:10.557 - info: hm-rega.0 (10406) ReGaHSS 192.168.178.134 up 2023-09-10 22:05:10.568 - error: hm-rega.0 (10406) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 2023-09-10 22:05:10.569 - error: hm-rega.0 (10406) ReGaHSS 192.168.178.134 down 2023-09-10 22:05:12.913 - error: hm-rpc.0 (10499) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:05:12.917 - info: hm-rpc.0 (10499) xmlrpc -> 192.168.178.134:2001/ init ["http://192.168.178.119:2001",""] 2023-09-10 22:05:12.921 - error: hm-rpc.0 (10499) Cannot call init: [http://192.168.178.119:2001, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:05:12.963 - info: hm-rpc.0 (10499) terminating 2023-09-10 22:05:12.964 - info: hm-rpc.0 (10499) Terminated (NO_ERROR): Without reason 2023-09-10 22:05:13.495 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR) 2023-09-10 22:05:13.495 - info: host.buanet-iobroker Restart adapter system.adapter.hm-rpc.0 because enabled 2023-09-10 22:05:13.975 - error: hm-rpc.1 (10514) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:05:13.981 - info: hm-rpc.1 (10514) xmlrpc -> 192.168.178.134:2010/ init ["http://192.168.178.120:2010",""] 2023-09-10 22:05:13.986 - error: hm-rpc.1 (10514) Cannot call init: [http://192.168.178.120:2010, ""] Unknown XML-RPC tag 'TITLE' 2023-09-10 22:05:14.027 - info: hm-rpc.1 (10514) terminating 2023-09-10 22:05:14.028 - info: hm-rpc.1 (10514) Terminated (NO_ERROR): Without reason 2023-09-10 22:05:14.557 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR) 2023-09-10 22:05:14.558 - info: host.buanet-iobroker Restart adapter system.adapter.hm-rpc.1 because enabled 2023-09-10 22:05:40.608 - info: hm-rega.0 (10406) ReGaHSS 192.168.178.134 up 2023-09-10 22:05:40.620 - error: hm-rega.0 (10406) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 2023-09-10 22:05:40.621 - error: hm-rega.0 (10406) ReGaHSS 192.168.178.134 down 2023-09-10 22:05:43.524 - info: host.buanet-iobroker instance system.adapter.hm-rpc.0 started with pid 10577 2023-09-10 22:05:44.465 - info: hm-rpc.0 (10577) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:05:44.530 - info: hm-rpc.0 (10577) xmlrpc server is trying to listen on 192.168.178.119:2001 2023-09-10 22:05:44.531 - info: hm-rpc.0 (10577) xmlrpc client is trying to connect to 192.168.178.134:2001/ with ["http://192.168.178.119:2001","buanet-iobroker:hm-rpc.0:cbdffbe9222740edddf5852624dc92c5"] 2023-09-10 22:05:44.550 - error: hm-rpc.0 (10577) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:05:44.585 - info: host.buanet-iobroker instance system.adapter.hm-rpc.1 started with pid 10592 2023-09-10 22:05:45.533 - info: hm-rpc.1 (10592) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.17.1, js-controller: 4.0.24 2023-09-10 22:05:45.625 - info: hm-rpc.1 (10592) xmlrpc server is trying to listen on 192.168.178.120:2010 2023-09-10 22:05:45.625 - info: hm-rpc.1 (10592) xmlrpc client is trying to connect to 192.168.178.134:2010/ with ["http://192.168.178.120:2010","buanet-iobroker:hm-rpc.1:8d6f9810697b1876418be6232f1a2c3b"] 2023-09-10 22:05:45.645 - error: hm-rpc.1 (10592) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE' 2023-09-10 22:06:10.654 - info: hm-rega.0 (10406) ReGaHSS 192.168.178.134 up 2023-09-10 22:06:10.666 - error: hm-rega.0 (10406) <-- invalid response: "\n\n\n \n \n \n \n 401 - Unauthorized \n \n\n" 202 -
@tmischek
Hättest Du das jetzt noch - wie von @Homoran geschrieben - in Code-Tags gepackt, wäre das auch lesbar.
-
@codierknecht sagte in Homematic CCU3 Adapter:
Hättest Du
hatte er, aber nach dem Mention keinen Zeilenumbruch
-
@tmischek sagte in Homematic CCU3 Adapter:
host.buanet-iobroker
wo stand denn bisher etwas von Docker?
@tmischek sagte in Homematic CCU3 Adapter:
401 - Unauthorizedda stimmen dann deine Berechtigungen wohl nicht.
hast du https?hast du sonst noch etwas nich erwähnt?
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1
-
@homoran das ganze läuft auf einer synologi, ich habe jetzt wirklich vieles probiert , komme aber nicht wirklich weiter. https hatte ich auch schon getestet.
-
@tmischek sagte in Homematic CCU3 Adapter:
das ganze läuft auf einer synologi,
das ist doch wieder nur die halbe Wahrheit.
da läuft doch sicher Docker.bitte gib uns alle Informationen!
callback adresse?
alle ports durchgeführt?und was bei so einer komplexen Installation alles sonst noch zu beachten ist.
