Homematic RPC mit CCU3: Kein Update auf virtuelle Devices

Bongo

Ich hatte heute einen unerwarteten Server shutdown auf meiner Synology. Das habe ich leider ein oder zwei Mal im Jahr ohne dass ich bisher das Problem gefunden habe.

Nach dem Neustart werden die Temperaturen, geöffnete Fenster, usw von Virtuellen Devices (Homematic Gruppen) werden nicht mehr upgedatet. Die Daten der nicht virtuellen Geräte (Temperatur, geöffnete Fenster, usw.) werden korrekt upgedatet. Bringt aber für die die Heizungssteuerung nichts.

Das Debug-Log sagt alle 3 Minuten:

2024-02-09 09:42:24.365 - debug: hm-rpc.2 (26998) [KEEPALIVE] Check if connection is alive
2024-02-09 09:42:24.365 - debug: hm-rpc.2 (26998) [KEEPALIVE] Connection timed out, initializing new connection
2024-02-09 09:42:24.366 - debug: hm-rpc.2 (26998) Connect...
2024-02-09 09:42:24.367 - debug: hm-rpc.2 (26998) clear ping interval
2024-02-09 09:42:24.367 - debug: hm-rpc.2 (26998) start connecting interval
2024-02-09 09:42:54.368 - debug: hm-rpc.2 (26998) xmlrpc -> 192.168.178.22:9292/groups/ init ["http://192.168.178.28:9292","iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
2024-02-09 09:42:54.390 - info: hm-rpc.2 (26998) xmlrpc <- listDevices ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
2024-02-09 09:42:54.393 - debug: hm-rpc.2 (26998) No suitable Lua script, fallback to keys!: function(doc) {
if (doc._id.match(/^hm-rpc\.[0-9]+\.\*?[A-Za-z0-9_-]+(\.[0-9]+)?$/)) {
emit(doc._id, {ADDRESS:(doc.native?doc.native.ADDRESS:''),VERSION:(doc.native?doc.native.VERSION:'')});
}
}
2024-02-09 09:42:54.549 - info: hm-rpc.2 (26998) xmlrpc -> 104 devices
2024-02-09 09:42:54.869 - info: hm-rpc.2 (26998) xmlrpc <- newDevices 104
2024-02-09 09:42:54.886 - debug: hm-rpc.2 (26998) No suitable Lua script, fallback to keys!: function(doc) {
if (doc._id.match(/^hm-rpc\.[0-9]+\.\*?[A-Za-z0-9_-]+(\.[0-9]+)?$/)) {
emit(doc._id, {ADDRESS:(doc.native?doc.native.ADDRESS:''),VERSION:(doc.native?doc.native.VERSION:'')});
}
}
2024-02-09 09:42:55.008 - info: hm-rpc.2 (26998) new virtual-devices devices/channels after filter: 0
2024-02-09 09:42:55.024 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000002"]
2024-02-09 09:42:55.032 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000003"]
2024-02-09 09:42:55.041 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000004"]
2024-02-09 09:42:55.047 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000005"]
2024-02-09 09:42:55.054 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000006"]
2024-02-09 09:42:55.060 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000007"]
2024-02-09 09:42:55.066 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000008"]
2024-02-09 09:42:55.083 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000009"]
2024-02-09 09:42:55.092 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000010"]
2024-02-09 09:42:55.100 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000011"]
2024-02-09 09:42:55.107 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000012"]
2024-02-09 09:42:55.113 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000013"]
2024-02-09 09:42:55.121 - info: hm-rpc.2 (26998) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","INT0000014"]
2024-02-09 09:43:04.385 - debug: hm-rpc.2 (26998) clear connecting interval
2024-02-09 09:43:04.386 - debug: hm-rpc.2 (26998) start ping interval

Im Log der CCU3:

http://192.168.178.28:2001/RPC2:
Feb  9 04:52:31 ccu3-webui user.err rfd: XmlRpc transport error
Feb  9 04:52:51 ccu3-webui user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","ERROR",0}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","LOWBAT",false}]}) on http://192.168.178.28:2001/RPC2:
Feb  9 04:52:51 ccu3-webui user.err rfd: XmlRpc transport error
Feb  9 05:45:47 ccu3-webui user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","STATE",false}]}) on http://192.168.178.28:2001/RPC2:
Feb  9 05:45:47 ccu3-webui user.err rfd: XmlRpc transport error
Feb  9 05:46:08 ccu3-webui user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","ERROR",0}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","LOWBAT",false}]}) on http://192.168.178.28:2001/RPC2:
Feb  9 05:46:08 ccu3-webui user.err rfd: XmlRpc transport error
Feb  9 06:43:41 ccu3-webui user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","STATE",false}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","ERROR",0}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0203556:1","LOWBAT",false}]}) on http://192.168.178.28:2001/RPC2:
Feb  9 06:43:41 ccu3-webui user.err rfd: XmlRpc transport error
Feb  9 07:01:01 ccu3-webui user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0437285:1","PRESS_SHORT",true}]}) on http://192.168.178.28:2001/RPC2:
Feb  9 07:01:01 ccu3-webui user.err rfd: XmlRpc transport error
Feb  9 07:01:21 ccu3-webui user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0437285:1","INSTALL_TEST",true}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0437285:1","PRESS_SHORT",true}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0437285:1","INSTALL_TEST",true}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0437285:1","PRESS_SHORT",true}],[methodName:"event",params:{"iobroker:hm-rpc.0:xxxxxxxxxxxxxxxxxxxxxxxxxxxx","OEQ0437285:1","INSTALL_TEST",true}]}) on http://192.168.178.28:2001/RPC2:
Feb  9 07:01:21 ccu3-webui user.err rfd: XmlRpc transport error

Neustart der Instanz bringt keine Besserung. Erst wenn ich die CCU3 neu starte funktioniert es wieder.
Ich vermute irgendein xmlrpc-Protokollproblem.

hm-rpc.2.info.connection = true
Müsste aber meiner Meinung nach false sein. Dann würde zumindest Device-Watcher eine Meldung machen.

Oder gibt es noch eine Einstellung, damit es gar nicht so weit kommt?
Vielleicht in der CCU3?

Meine Konfiguration:

Adaptername: hm-rpc
Link zu Adapterrepository: https://github.com/ioBroker/ioBroker.hm-rpc
Adapterversion: v1.16.0
js-controller Version: ...
Admin Version: v6.12.0
Hardwaresystem: Synology DS918+
Arbeitsspeicher: 16GB
Festplattenart: HDD
Betriebssystem: Synology DSM
Nodejs-Version: v18.18.2
NPM-Version: 9.8.1
Installationsart: Skript oder Manuell ?
Image, Docker genutzt: Ja
Ort, Name der Imagedatei: Buanet

Community Forum

NEWS

Homematic RPC mit CCU3: Kein Update auf virtuelle Devices

Support us

670

32.6k

82.2k

1.3m