HM Rega: timed out after 90 seconds

[fleck.a87]

Servus Zusammen,

ich bin letzte Woche von debmatic auf RapberryMatic umgezogen.
Nach ein paar anfänglichen schwierigkeiten mit portfreigaben usw. lief alles ohne Probleme.

Nun hab ich heute in das Log des REGA Adapters geschaut und bekomme im ca 90 Sekunden Rythmus die Fehlermeldung```

hm-rega.0
2023-12-18 11:26:30.350	debug	--> Write(system.Date("%F %X").ToTime().ToInteger());

hm-rega.0
2023-12-18 11:26:30.350	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuRegaUp:{"val":true,"ack":true,"ts":1702895190349,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895190349}

hm-rega.0
2023-12-18 11:26:30.348	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuReachable:{"val":true,"ack":true,"ts":1702895190347,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895190347}

hm-rega.0
2023-12-18 11:26:30.303	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.connection:{"val":true,"ack":true,"ts":1702895190302,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895190302}

hm-rega.0
2023-12-18 11:26:30.301	info	ReGaHSS 192.168.0.118 up

hm-rega.0
2023-12-18 11:26:20.307	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuRegaUp:{"val":false,"ack":true,"ts":1702895180283,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895180283}

hm-rega.0
2023-12-18 11:26:20.239	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuReachable:{"val":false,"ack":true,"ts":1702895180238,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895180238}

hm-rega.0
2023-12-18 11:26:20.237	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.connection:{"val":false,"ack":true,"ts":1702895180236,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895180236}

hm-rega.0
2023-12-18 11:26:20.207	error	CCU 192.168.0.118 unreachable

hm-rega.0
2023-12-18 11:26:20.207	error	post request error: Aborted due to timeout

hm-rega.0
2023-12-18 11:26:20.207	warn	"Write(system.Date("%F %X").ToTime().ToInteger());" timed out after 90 seconds

hm-rega.0
2023-12-18 11:24:50.206	debug	--> Write(system.Date("%F %X").ToTime().ToInteger());

hm-rega.0
2023-12-18 11:24:50.205	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuRegaUp:{"val":true,"ack":true,"ts":1702895090203,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895090203}

hm-rega.0
2023-12-18 11:24:50.160	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuReachable:{"val":true,"ack":true,"ts":1702895090159,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895090159}

hm-rega.0
2023-12-18 11:24:50.157	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.connection:{"val":true,"ack":true,"ts":1702895090156,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895090156}

hm-rega.0
2023-12-18 11:24:50.152	info	ReGaHSS 192.168.0.118 up

hm-rega.0
2023-12-18 11:24:40.106	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuRegaUp:{"val":false,"ack":true,"ts":1702895080105,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895080105}

hm-rega.0
2023-12-18 11:24:40.104	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.ccuReachable:{"val":false,"ack":true,"ts":1702895080103,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895080103}

hm-rega.0
2023-12-18 11:24:40.059	silly	States user redis pmessage hm-rega.0.*/hm-rega.0.info.connection:{"val":false,"ack":true,"ts":1702895080058,"q":0,"from":"system.adapter.hm-rega.0","user":"system.user.admin","lc":1702895080058}

hm-rega.0
2023-12-18 11:24:40.056	error	CCU 192.168.0.118 unreachable

hm-rega.0
2023-12-18 11:24:40.056	error	post request error: Aborted due to timeout

hm-rega.0
2023-12-18 11:24:40.056	warn	"Write(system.Date("%F %X").ToTime().ToInteger());" timed out after 90 seconds

Zuvor war der RapBerry mit WLAN angebunden. Hab hier mal gelesen, das es ein Problem sein könnte. Aber bei LAN das gleiche ergebniss.

Ein Problem das sich mein Rega Adapter generell nicht mit der Rasspberrymatic verbinden kann, kann ich mir auch nicht vorstellen, da die anderen Datenpunkte ja auch aktualisert werden.

In der RaspberryMatic habe ich mal die komplette firewall deaktiviert:

Kann mir evtl. jemand noch n tipp geben an was das liegen könnte?

Gruß Andi