Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. HM RPC (HM IP) - Keine Verbindung HM RPC & CCU3

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    HM RPC (HM IP) - Keine Verbindung HM RPC & CCU3

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators @Gurke258 last edited by

      @gurke258 sagte in HM RCP (HM IP) - Keine Verbindung HM RCP & CCU3:

      Ich hänge hier das LOG an

      bitte die relevanten Abschnitte hier in code-tags posten!

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

      Gurke258 1 Reply Last reply Reply Quote 0
      • Gurke258
        Gurke258 @Homoran last edited by Gurke258

        @homoran

        Es ist doch das ganze Log interressanter um den Zusammenhang zu verstehen... zumindest verlangen wir von unseren Kunden immer das komplett Log und ich habe hier schon einiges bereinigt. Aber ich schicke gern nochmal die relevanten in code Tags 😉

        024-10-16 16:56:20.527 - debug: hm-rega.0 (245545) --> !# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin
        2024-10-16 16:56:20.536 - debug: hm-rega.0 (245545) <-- {"2006":{"Name":"%24%7BruleTmpProgramName%7D","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
        "1580":{"Name":"%24%7BruleTmpProgramName%7D%201","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
        "2782":{"Name":"Arbeitszimmer","TypeName":"PROGRAM","PrgInfo":"", "Active":true,"Timestamp":"1970-01-01 01:00:00"},
        "2774":{"Name":"Schlafzimmer","TypeName":"PROGRAM","PrgInfo":"", "Active":true,"Timestamp":"1970-01-01 01:00:00"}}
        2024-10-16 16:56:37.584 - debug: hm-rpc.0 (292803) xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:fec6d81eae5d06120cab8b6eb7a76133"]
        2024-10-16 16:56:47.612 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:50.481 - debug: hm-rega.0 (245545) --> polling.fn
        2024-10-16 16:56:50.482 - debug: hm-rega.0 (245545) --> programs.fn
        2024-10-16 16:56:50.486 - debug: hm-rega.0 (245545) --> !# polling.fn 1.3 !# !# Dieses Script gibt die Werte aller Systemvariablen als J
        2024-10-16 16:56:50.512 - debug: hm-rega.0 (245545) <-- {"1236":[false,"1970-01-01 01:00:00"],
        "950":[true,"2024-10-15 18:10:29"],
        "2904":[4.000000,"2024-10-16 16:36:06"],
        "40":[2,"2024-10-16 16:31:55"],
        "41":[3,"2024-10-16 16:54:40"]}
        2024-10-16 16:56:50.527 - debug: hm-rega.0 (245545) --> !# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin
        2024-10-16 16:56:50.534 - debug: hm-rega.0 (245545) <-- {"2006":{"Name":"%24%7BruleTmpProgramName%7D","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
        "1580":{"Name":"%24%7BruleTmpProgramName%7D%201","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
        "2782":{"Name":"Arbeitszimmer","TypeName":"PROGRAM","PrgInfo":"", "Active":true,"Timestamp":"1970-01-01 01:00:00"},
        "2774":{"Name":"Schlafzimmer","TypeName":"PROGRAM","PrgInfo":"", "Active":true,"Timestamp":"1970-01-01 01:00:00"}}
        2024-10-16 16:56:56.492 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.516 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.531 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.545 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.558 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.573 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.586 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.598 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.610 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.623 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.630 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.639 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.646 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.654 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.661 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.669 - error: hm-rpc.0 (292803) Ping error [HomePi:hm-rpc.0:fec6d81eae5d06120cab8b6eb7a76133]: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.680 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.688 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.692 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.700 - error: hm-rpc.0 (292803) Ping error [HomePi:hm-rpc.0:fec6d81eae5d06120cab8b6eb7a76133]: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.707 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.714 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.723 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.731 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.739 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.746 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.753 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.760 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.770 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.777 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:56:56.789 - error: hm-rpc.0 (292803) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        2024-10-16 16:57:07.585 - debug: hm-rpc.0 (292803) xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:fec6d81eae5d06120cab8b6eb7a76133"]
        2024-10-16 16:57:17.617 - info: hm-rpc.0 (292803) xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001",""]
        2024-10-16 16:57:18.630 - info: hm-rpc.0 (292803) terminating
        2024-10-16 16:57:18.632 - info: hm-rpc.0 (292803) Terminated (NO_ERROR): Without reason
        2024-10-16 16:57:19.373 - info: host.HomePi instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
        2024-10-16 16:57:19.373 - info: host.HomePi Restart adapter system.adapter.hm-rpc.0 because enabled
        2024-10-16 16:57:20.482 - debug: hm-rega.0 (245545) --> polling.fn
        2024-10-16 16:57:20.482 - debug: hm-rega.0 (245545) --> programs.fn
        2024-10-16 16:57:20.484 - debug: hm-rega.0 (245545) --> !# polling.fn 1.3 !# !# Dieses Script gibt die Werte aller Systemvariablen als J
        2024-10-16 16:57:20.517 - debug: hm-rega.0 (245545) <-- {"1236":[false,"1970-01-01 01:00:00"],
        "950":[true,"2024-10-15 18:10:29"],
        "2904":[4.000000,"2024-10-16 16:36:06"],
        "40":[2,"2024-10-16 16:31:55"],
        "41":[3,"2024-10-16 16:54:40"]}
        2024-10-16 16:57:20.527 - debug: hm-rega.0 (245545) --> !# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin
        2024-10-16 16:57:20.534 - debug: hm-rega.0 (245545) <-- {"2006":{"Name":"%24%7BruleTmpProgramName%7D","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
        "1580":{"Name":"%24%7BruleTmpProgramName%7D%201","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
        "2782":{"Name":"Arbeitszimmer","TypeName":"PROGRAM","PrgInfo":"", "Active":true,"Timestamp":"1970-01-01 01:00:00"},
        "2774":{"Name":"Schlafzimmer","TypeName":"PROGRAM","PrgInfo":"", "Active":true,"Timestamp":"1970-01-01 01:00:00"}}
        2024-10-16 16:57:50.286 - info: host.HomePi instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 294483
        2024-10-16 16:57:50.483 - debug: hm-rega.0 (245545) --> polling.fn
        2024-10-16 16:57:50.484 - debug: hm-rega.0 (245545) --> programs.fn
        2024-10-16 16:57:50.488 - debug: hm-rega.0 (245545) --> !# polling.fn 1.3 !# !# Dieses Script gibt die Werte aller Systemvariablen als J
        2024-10-16 16:57:50.522 - debug: hm-rega.0 (245545) <-- {"1236":[false,"1970-01-01 01:00:00"],
        "950":[true,"2024-10-15 18:10:29"],
        "2904":[4.000000,"2024-10-16 16:36:06"],
        "40":[2,"2024-10-16 16:57:44"],
        "41":[3,"2024-10-16 16:54:40"]}
        
        hm-rpc.0
        2024-10-16 17:21:43.149	info	Terminated (NO_ERROR): Without reason
        
        hm-rpc.0
        2024-10-16 17:21:43.147	info	terminating
        
        hm-rpc.0
        2024-10-16 17:21:43.121	error	Cannot call init: [http://192.168.178.75:2001, ""] Unknown XML-RPC tag 'TITLE'
        
        hm-rpc.0
        2024-10-16 17:21:43.118	info	Disconnected
        
        hm-rpc.0
        2024-10-16 17:21:43.089	info	xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001",""]
        
        hm-rpc.0
        2024-10-16 17:21:43.033	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        
        hm-rpc.0
        2024-10-16 17:21:33.004	debug	xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:3d5c59dcb7e693588d1286fb42c0e817"]
        
        hm-rpc.0
        2024-10-16 17:21:13.084	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
        
        hm-rpc.0
        2024-10-16 17:21:03.003	debug	xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:3d5c59dcb7e693588d1286fb42c0e817"]
        
        hm-rpc.0
        2024-10-16 17:20:33.002	debug	start connecting interval
        
        hm-rpc.0
        2024-10-16 17:20:33.001	debug	clear ping interval
        
        hm-rpc.0
        2024-10-16 17:20:33.001	debug	Connect...
        
        hm-rpc.0
        2024-10-16 17:20:33.000	debug	[KEEPALIVE] Connection timed out, initializing new connection
        
        hm-rpc.0
        2024-10-16 17:20:33.000	debug	[KEEPALIVE] Check if connection is alive
        
        hm-rpc.0
        2024-10-16 17:19:03.000	debug	Send PING...
        
        hm-rpc.0
        2024-10-16 17:19:02.999	debug	[KEEPALIVE] Check if connection is alive
        
        hm-rpc.0
        2024-10-16 17:17:32.997	debug	start ping interval
        
        hm-rpc.0
        2024-10-16 17:17:32.997	debug	clear connecting interval
        
        hm-rpc.0
        2024-10-16 17:17:32.668	debug	xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:3d5c59dcb7e693588d1286fb42c0e817"]
        
        hm-rpc.0
        2024-10-16 17:17:02.667	debug	xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:3d5c59dcb7e693588d1286fb42c0e817"]
        
        hm-rpc.0
        2024-10-16 17:16:32.665	debug	xmlrpc -> 192.168.178.56:2001/ init ["http://192.168.178.75:2001","HomePi:hm-rpc.0:3d5c59dcb7e693588d1286fb42c0e817"]
        
        hm-rpc.0
        2024-10-16 17:16:02.664	debug	start connecting interval
        
        hm-rpc.0
        2024-10-16 17:16:02.664	debug	clear ping interval
        
        hm-rpc.0
        2024-10-16 17:16:02.664	debug	Connect...
        
        hm-rpc.0
        2024-10-16 17:16:02.663	debug	[KEEPALIVE] Connection timed out, initializing new connection
        
        hm-rpc.0
        2024-10-16 17:16:02.662	debug	[KEEPALIVE] Check if connection is alive
        
        hm-rpc.0
        2024-10-16 17:14:32.663	debug	Send PING...
        
        hm-rpc.0
        2024-10-16 17:14:32.663	debug	[KEEPALIVE] Check if connection is alive
        
        hm-rpc.0
        2024-10-16 17:13:02.662	debug	start ping interval
        
        t 16 17:32:41 ccu3-webui user.info monit[1925]: Starting Monit 5.33.0 daemon with http interface at /var/run/monit.sock
        Oct 16 17:32:41 ccu3-webui user.info monit[1925]: 'ccu3-webui' Monit 5.33.0 started
        Oct 16 17:32:46 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
        Oct 16 17:32:46 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ1483860:7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2618]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"LEQ1483860:7","DECISION_VALUE"}) [CallGetValue():iseXmlRpc.cpp:1445]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
        Oct 16 17:32:46 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
        Oct 16 17:32:46 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ1483715:7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2618]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"LEQ1483715:7","DECISION_VALUE"}) [CallGetValue():iseXmlRpc.cpp:1445]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
        Oct 16 17:32:46 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
        Oct 16 17:32:46 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ1483890:7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2618]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"LEQ1483890:7","DECISION_VALUE"}) [CallGetValue():iseXmlRpc.cpp:1445]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
        Oct 16 17:32:46 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
        Oct 16 17:32:46 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ1483852:7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2618]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"LEQ1483852:7","DECISION_VALUE"}) [CallGetValue():iseXmlRpc.cpp:1445]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
        Oct 16 17:32:46 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
        Oct 16 17:32:46 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ1483769:7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2618]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"LEQ1483769:7","DECISION_VALUE"}) [CallGetValue():iseXmlRpc.cpp:1445]
        Oct 16 17:32:46 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
        Oct 16 17:32:48 ccu3-webui daemon.info chronyd[1387]: Selected source 2001:41d0:700:49bc::7 (2.de.pool.ntp.org)
        
        ***** /var/log/hmserver.log *****
        2024-10-16 17:32:34,121 de.eq3.lib.datalogging.rrd.RrdDatalogging ERROR [Thread-1] Could not initialize rrd database 
        java.lang.IndexOutOfBoundsException: null
        	at java.nio.Buffer.checkIndex(Unknown Source) ~[?:?]
        	at java.nio.DirectByteBuffer.getInt(Unknown Source) ~[?:?]
        	at org.rrd4j.core.ByteBufferBackend.readInt(ByteBufferBackend.java:130) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdPrimitive.readInt(RrdPrimitive.java:38) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdInt.get(RrdInt.java:35) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.Archive.<init>(Archive.java:45) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdDb.<init>(RrdDb.java:646) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdDb.<init>(RrdDb.java:587) ~[HMIPServer.jar:?]
        	at de.eq3.lib.datalogging.rrd.RrdDatalogging.initialize(RrdDatalogging.java:459) ~[HMIPServer.jar:?]
        	at de.eq3.lib.measurement.MeasurementService.isDataloggingInitialized(MeasurementService.java:192) ~[HMIPServer.jar:?]
        	at de.eq3.lib.measurement.MeasurementService.init(MeasurementService.java:164) ~[HMIPServer.jar:?]
        	at de.eq3.ccu.server.BaseHMServer.initializeMeasurement(BaseHMServer.java:199) ~[HMIPServer.jar:?]
        	at de.eq3.ccu.server.ip.HMIPServer.initialize(HMIPServer.java:199) ~[HMIPServer.jar:?]
        	at de.eq3.ccu.server.ip.HMIPServer.<init>(HMIPServer.java:56) ~[HMIPServer.jar:?]
        	at de.eq3.ccu.server.ip.HMIPServer.lambda$main$2(HMIPServer.java:153) ~[HMIPServer.jar:?]
        	at java.lang.Thread.run(Unknown Source) ~[?:?]
        2024-10-16 17:32:44,165 de.eq3.lib.datalogging.rrd.RrdDatalogging ERROR [Timer-0] Could not initialize rrd database 
        java.lang.IndexOutOfBoundsException: null
        	at java.nio.Buffer.checkIndex(Unknown Source) ~[?:?]
        	at java.nio.DirectByteBuffer.getInt(Unknown Source) ~[?:?]
        	at org.rrd4j.core.ByteBufferBackend.readInt(ByteBufferBackend.java:130) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdPrimitive.readInt(RrdPrimitive.java:38) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdInt.get(RrdInt.java:35) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.Archive.<init>(Archive.java:45) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdDb.<init>(RrdDb.java:646) ~[HMIPServer.jar:?]
        	at org.rrd4j.core.RrdDb.<init>(RrdDb.java:587) ~[HMIPServer.jar:?]
        	at de.eq3.lib.datalogging.rrd.RrdDatalogging.initialize(RrdDatalogging.java:459) ~[HMIPServer.jar:?]
        	at de.eq3.lib.measurement.MeasurementService.isDataloggingInitialized(MeasurementService.java:192) ~[HMIPServer.jar:?]
        	at de.eq3.lib.measurement.MeasurementService.writeLogValues(MeasurementService.java:793) ~[HMIPServer.jar:?]
        	at de.eq3.lib.measurement.MeasurementService$EventTimerTask.run(MeasurementService.java:121) ~[HMIPServer.jar:?]
        	at java.util.TimerThread.mainLoop(Unknown Source) ~[?:?]
        	at java.util.TimerThread.run(Unknown Source) ~[?:?]
        
        

        Komisch ist auch was ich noch festgestellt habe, wenn die Adapter dann ne weile auf Stopp waren und ich sie später erneut gestartet habe sind alle für ne weile grün und i.wann geht der hm-rpc.0 wieder auf Gelb.

        Hier auch nochmal der Auszug von iob diag

        ======================= SUMMARY =======================
                                v.2024-08-12
        
        
         Static hostname: HomePi
               Icon name: computer
        Operating System: Debian GNU/Linux 12 (bookworm)
                  Kernel: Linux 6.6.51+rpt-rpi-v8
            Architecture: arm64
        
        Installation:           native
        Kernel:                 aarch64
        Userland:               64 bit
        Timezone:               Europe/Berlin (CEST, +0200)
        User-ID:                1000
        Display-Server:         true
        Boot Target:            graphical.target
        
        Pending OS-Updates:     6
        Pending iob updates:    0
        
        Nodejs-Installation:
        /usr/bin/nodejs         v20.18.0
        /usr/bin/node           v20.18.0
        /usr/bin/npm            10.8.2
        /usr/bin/npx            10.8.2
        /usr/bin/corepack       0.29.3
        
        Recommended versions are nodejs 20.18.0 and npm 10.8.2
        Your nodejs installation is correct
        
        MEMORY:
                       total        used        free      shared  buff/cache   available
        Mem:            4.0G        2.7G        289M        138M        1.2G        1.3G
        Swap:           209M        209M          0B
        Total:          4.2G        2.9G        289M
        
        Active iob-Instances:   24
        Upgrade policy: none
        
        ioBroker Core:          js-controller           6.0.11
                                admin                   7.1.5
        
        ioBroker Status:        iobroker is running on this host.
        
        
        Objects type: jsonl
        States  type: jsonl
        
        Status admin and web instance:
        + system.adapter.admin.0                  : admin                 : HomePi                                   -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.web.0                    : web                   : HomePi                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        
        Objects:                14869
        States:                 12822
        
        Size of iob-Database:
        
        43M     /opt/iobroker/iobroker-data/objects.jsonl
        29M     /opt/iobroker/iobroker-data/states.jsonl
        
        
        
        =================== END OF SUMMARY ====================
        
        Samson71 1 Reply Last reply Reply Quote 0
        • Samson71
          Samson71 Global Moderator @Gurke258 last edited by Samson71

          @Gurke258

          Komisch ist auch was ich noch festgestellt habe, wenn die Adapter dann ne weile auf Stopp waren und ich sie später erneut gestartet habe sind alle für ne weile grün und i.wann geht der hm-rpc.0 wieder auf Gelb.

          Mal Skripte etc. kontrolliert? Haut da was auf die CCU ein und treibt sie damit in den DutyCycle? Das würde dazu passen.

          EDIT
          Lt. Screenshot von der CCU stürzt der rfd ab.

          Gurke258 1 Reply Last reply Reply Quote 0
          • Gurke258
            Gurke258 @Samson71 last edited by Gurke258

            @samson71

            ich hab da keine Scripte laufen. Nur direkte Verknüpfungen und 2 kleine Programme. Der Duty Cycle ist bei 2 % ohne IoBroker und mit IoBroker bei ca. 7 - 8%

            Samson71 1 Reply Last reply Reply Quote 0
            • Samson71
              Samson71 Global Moderator @Gurke258 last edited by

              @gurke258
              Mal in der CCU die Ports aufmachen (unabhängig einzelner Freigaben). Die stehen auf blockiert. Callback-Adresse prüfen. Bei mir ist die leer. Braucht man glaube ich nur bei Einsatz im Container/Docker.

              Gurke258 1 Reply Last reply Reply Quote 0
              • Gurke258
                Gurke258 @Samson71 last edited by

                @samson71

                hab ich gemacht.. leider immer noch gelb der Adapter (hm-rpc.0)

                1 Reply Last reply Reply Quote 0
                • wendy2702
                  wendy2702 last edited by

                  Ist das hier noch ne Leiche:

                  
                  "1580":{"Name":"%24%7BruleTmpProgramName%7D%201","TypeName":"PROGRAM","PrgInfo":"", "Active":false,"Timestamp":"1970-01-01 01:00:00"},
                  
                  

                  Bin nur am Handy da ist das log schwer zu lesen. Sorry falls Blödsinn.

                  Gurke258 1 Reply Last reply Reply Quote 0
                  • Gurke258
                    Gurke258 @wendy2702 last edited by

                    @wendy2702

                    Ja sieht so aus ^^.. habs mal gelöscht aber denke nicht das es daran liegt ^^

                    1 Reply Last reply Reply Quote 0
                    • Gurke258
                      Gurke258 last edited by Gurke258

                      Lag leider nicht daran 😕

                      So wie ich gelesen habe, kann es ja auch keine Störung der Funkfrequenz sein, da die adapter ja schon erreichbar sind.

                      Ich hab den Telegram adapter dran und habe die Möglichkeit den Status der Temperatur der einzelnen Räume abzufragen.

                      black.falcon87 1 Reply Last reply Reply Quote 0
                      • black.falcon87
                        black.falcon87 @Gurke258 last edited by

                        @gurke258 sagte in HM RCP (HM IP) - Keine Verbindung HM RCP & CCU3:

                        Kann es sein das dieses hier mit rein spielt?

                        Ich hab den Telegram adapter dran und habe die Möglichkeit den Status der Temperatur der einzelnen Räume abzufragen.

                        Das ist der Javascript Code dahinter. Das Skript läuft aber auch schon einige Jahre...

                        Kannst du den Telegram Adapter nicht einfach für einen Tag abstellen? Oder für ein paar Stunden? Dann siehst du ja ob die Probleme wieder kommen oder fern bleiben?

                        Gurke258 1 Reply Last reply Reply Quote 0
                        • Gurke258
                          Gurke258 @black.falcon87 last edited by Gurke258

                          @black-falcon87

                          hab ich jetzt mal 30 min zum test ^^ Telegram Adaper aus und alles neu gestartet...

                          leider immer noch fehler:

                          
                          
                          hm-rpc.0
                          2024-10-17 21:34:41.512	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rpc.0
                          2024-10-17 21:34:11.490	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rpc.0
                          2024-10-17 21:33:31.501	error	Ping error [HomePi:hm-rpc.0:8e1410a114aa517d8367771426da82f1]: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rpc.0
                          2024-10-17 21:06:45.183	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rpc.0
                          2024-10-17 21:06:25.614	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rega.0
                          2024-10-17 21:06:03.641	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 21:06:03.640	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 21:06:03.638	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rpc.0
                          2024-10-17 21:05:39.771	error	Cannot call init: [http://192.168.178.75:2001, ""] Unknown XML-RPC tag 'TITLE'
                          
                          hm-rpc.0
                          2024-10-17 21:05:38.687	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rpc.0
                          2024-10-17 21:05:09.748	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
                          
                          hm-rega.0
                          2024-10-17 21:04:02.596	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 21:04:02.590	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 21:04:02.589	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 21:02:01.759	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 21:02:01.759	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 21:02:01.757	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 21:00:00.772	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 21:00:00.771	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 21:00:00.768	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 20:57:59.837	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 20:57:59.837	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 20:57:59.834	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 20:55:58.676	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 20:55:58.675	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 20:55:58.673	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 20:53:57.787	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 20:53:57.787	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 20:53:57.784	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 20:51:56.032	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 20:51:56.031	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 20:51:56.027	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          hm-rega.0
                          2024-10-17 20:49:55.061	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 20:49:55.060	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 20:49:55.050	warn	"!# dutycycle.fn 0.3 string stderr; string stdout; system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          host.HomePi
                          2024-10-17 20:48:22.176	warn	instance system.adapter.hm-rpc.0 terminated due to SIGKILL
                          
                          hm-rega.0
                          2024-10-17 20:47:50.999	error	CCU 192.168.178.56 unreachable
                          
                          hm-rega.0
                          2024-10-17 20:47:50.998	error	post request error: Aborted due to timeout
                          
                          hm-rega.0
                          2024-10-17 20:47:50.995	warn	"!# dutycycle.fn 0.3string stderr;string stdout;system.Exec("/bin/sh -c '" # '" timed out after 90 seconds
                          
                          telegram.0
                          2024-10-17 20:47:31.360	error	Failed sending [chatId - 1046316506]: Error: ETELEGRAM: 403 Forbidden: user is deactivated
                          
                          hm-rega.0
                          2024-10-17 20:47:22.399	warn	Script "!# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin" ignored, because still pending.
                          
                          hm-rega.0
                          2024-10-17 20:47:22.358	warn	Script "!# polling.fn 1.3 !# !# Dieses Script gibt die Werte aller Systemvariablen als J" ignored, because still pending.
                          
                          hm-rega.0
                          2024-10-17 20:46:52.399	warn	Script "!# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin" ignored, because still pending.
                          
                          hm-rega.0
                          2024-10-17 20:46:52.359	warn	Script "!# polling.fn 1.3 !# !# Dieses Script gibt die Werte aller Systemvariablen als J" ignored, because still pending.
                          
                          1 Reply Last reply Reply Quote 0
                          • black.falcon87
                            black.falcon87 last edited by

                            Denke dann würde ich versuchen den Übeltäter mittels Ausschlussverfahren zu finden.
                            Also im Zweifel alle Adapter die irgendwas mit der CCU zu tun haben könnten mal deaktivieren.

                            Dann kannst du es vielleicht irgendwie eingrenzen. Du sagst ja das Problem erscheint schon nach 30 Minuten daher ist der Test ja recht schnell erfolgt 😉

                            Gurke258 1 Reply Last reply Reply Quote 0
                            • Gurke258
                              Gurke258 @black.falcon87 last edited by Gurke258

                              @black-falcon87

                              hab ich gemacht,, sind nur der telegram adapter und die beiden VIS.. wobei ich jetzt VIS 2 komplett aus habe und nur wie früher VIS 1 läuft.

                              Komisch ist auch das es nur den rfd Daemon betrifft und nicht und nicht den Homatic IP...

                              Ich schalte zum test mal den rfd komplett aus um zusehen, ob es besser wird.

                              Gurke258 1 Reply Last reply Reply Quote 0
                              • Gurke258
                                Gurke258 @Gurke258 last edited by

                                Also es scheint wirklich an diesem Adapter nur zu liegen...

                                habe diesen ausgeschaltet und es läuft jetzt seit 2 stunden ohne Fehler...

                                Samson71 1 Reply Last reply Reply Quote 0
                                • Samson71
                                  Samson71 Global Moderator @Gurke258 last edited by

                                  @gurke258
                                  Lt. den Screenshots oben ist das ja der hm-rpc.0

                                  Was mir im Vergleich zu meinem rfd auffällt:

                                  Bei Callback Adresse habe ich z.B. nichts eingetragen.
                                  Wenn auf der CCU "Vollzugriff" aktiviert ist, müssten Benutzername/Passwort leer bleiben können.
                                  Bei mir sind sie das. Mal rausnehmen, da ja Authentifizierung nicht aktiv ist.

                                  Gurke258 1 Reply Last reply Reply Quote 0
                                  • Gurke258
                                    Gurke258 @Samson71 last edited by

                                    @samson71

                                    hab ich gemacht und der Adapter bleibt auf "Gelb"..

                                    er brauchte auch 4 min bis er Connected war:

                                    
                                    hm-rpc.0
                                    2024-10-19 16:14:31.796	info	Connected
                                    
                                    hm-rpc.0
                                    2024-10-19 16:10:01.702	info	xmlrpc client is trying to connect to 192.168.178.56:2001/ with ["http://192.168.178.73:2001","HomePi:hm-rpc.0:7b92d9fea1bb1862e79f130533d2608c"]
                                    
                                    hm-rpc.0
                                    2024-10-19 16:10:01.701	info	xmlrpc server is trying to listen on 192.168.178.73:2001
                                    
                                    hm-rpc.0
                                    2024-10-19 16:10:01.432	info	starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.0, js-controller: 6.0.11
                                    

                                    Aber die Oberfläche der CCU hängt trotzdem und verbindet sich nicht wenn ich die IP eingebe und aufrufen will..

                                    39a84545-e08a-4a13-8d4b-d43ca83f53cb-image.png

                                    Samson71 1 Reply Last reply Reply Quote 0
                                    • Samson71
                                      Samson71 Global Moderator @Gurke258 last edited by Samson71

                                      @gurke258 sagte in HM RCP (HM IP) - Keine Verbindung HM RCP & CCU3:

                                      hm-rpc.0
                                      2024-10-19 16:10:01.702	info	xmlrpc client is trying to connect to 192.168.178.56:2001/ with ["http://192.168.178.73:2001","HomePi:hm-rpc.0:7b92d9fea1bb1862e79f130533d2608c"]
                                      
                                      hm-rpc.0
                                      2024-10-19 16:10:01.701	info	xmlrpc server is trying to listen on 192.168.178.73:2001
                                      

                                      Wo kommt die .73 plötzlich her? Waren das nicht auf den Screenshots oben die .56 und die .75

                                      Gurke258 1 Reply Last reply Reply Quote 0
                                      • Gurke258
                                        Gurke258 @Samson71 last edited by

                                        @samson71

                                        75 ist LAN und 73 ist Wlan vom raspberry wo IObroker läuft.

                                        Ich habe auch mal beides ausprobiert um zu sehen ob villt daran liegt.

                                        Gurke258 1 Reply Last reply Reply Quote 0
                                        • Gurke258
                                          Gurke258 @Gurke258 last edited by

                                          Keiner ne weitere Idee? 😕

                                          1 Reply Last reply Reply Quote 0
                                          • Meister Mopper
                                            Meister Mopper @Gurke258 last edited by

                                            @gurke258

                                            Auch wenn es jetzt nicht wirklich hilft, wäre es hilfreich, wenn du im Thread-Titel aus RCP das richtige RPC machst.

                                            Sollte dein thread hoffentlich gelöst werden, können ihn Leute mit gleichen Problemen wesentlich leichter finden.

                                            Schönen Gruß
                                            Thomas

                                            Gurke258 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            422
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            ccu3 homematic ccu3 iobroker ccu ccu3 raspberrymatic
                                            9
                                            133
                                            6483
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo