und noch ein regelm. "Absturz" einer CCU2
Moderator: Co-Administratoren
Re: und noch ein regelm. "Absturz" einer CCU2
Spannend...der Speicher neigt sich dem Ende...
@Familienvater: Wie sieht denn Dein Speicherverbrauch aus ? Nehme mal an, dass Du eine ähnlich große Installation hast wie ich.
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
-
- Beiträge: 10765
- Registriert: 24.02.2011, 01:34
- System: CCU
- Hat sich bedankt: 65 Mal
- Danksagung erhalten: 675 Mal
Re: und noch ein regelm. "Absturz" einer CCU2
nix spannend, das ist normal.Pietro hat geschrieben:Spannend...der Speicher neigt sich dem Ende...
Bin zwar nicht Familienvater, aber 21 Tage nach letzten Reboot bin ich auf 13828 kB freien SpeicherPietro hat geschrieben: @Familienvater: Wie sieht denn Dein Speicherverbrauch aus ? Nehme mal an, dass Du eine ähnlich große Installation hast wie ich.
Alchy
Blacklist................... almost full
Ignoranz ist die Summe aller Maßnahmen die man ergreift, um bestehende Tatsachen nicht sehen zu müssen.
© Sandra Pulsfort (*1974)
Lies bitte die Logik von WebUI Programmen und die Tipps und Tricks für Anfänger.
Wichtig auch CUxD ersetzt System.exec. Die HM Script Doku (Downloadart Skripte) hilft auch weiter.
Zum Testen von Scripten den >> HomeMatic Script Executor << von Anli benutzen.
Re: und noch ein regelm. "Absturz" einer CCU2
Danke ! Ok, dann geht der freie Speicher scheinbar wirklich komplett in Richtung Cache.
Hab mich nur gewundert, da Bekannte von mir eine CCU-Laufzeit von mehreren Monaten haben und noch deutlichst mehr freien Speicher haben als ich....
lg Pietro
Hab mich nur gewundert, da Bekannte von mir eine CCU-Laufzeit von mehreren Monaten haben und noch deutlichst mehr freien Speicher haben als ich....
lg Pietro
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
Re: und noch ein regelm. "Absturz" einer CCU2
Update:
Immer noch kein Restart der EE, obwohl ich nun wieder alle Scripts aktiviert habe...sehr seltsam.
Allerdings habe ich nun einen neuen Verdacht der mir nach der Beobachtung des Duty-Cycles aufgefallen ist.
Hier der Duty-Cylce eines Funk-Gateways der letzten Tage: Interessant dabei ist der Duty-Cycle bis kurz nach Mitternacht am 19.7. - nämlich konstant NULL !
Und das obwohl die CCU der Meinung war, dass das Gateway "verbunden" ist und ich auch nicht überproportional mit Funkstörungen konfrontiert war.
Danach hab ich es mal stromlos gemacht und von nun an gab es wieder realistische Duty-Cycle-Einträge.
Seit diesem Zeitpunkt gab es keinen Restart mehr der EE - allerdings habe ich parallel auch einiges Umgebaut (immer zwei Tage auf einen Restart zu warten und erst dann wieder die nächtste Änderung zu machen ist einfach zu mühsam und schädigt auf Dauer den WAF).
Eine Theorie wäre nun, dass es durch den Hänger des Gateways ab und an zu einem Restart eines CCU-Services (aufgrund eines Timeouts?) gekommen ist und dies wiederum einen Restart der EE verursacht hat.
Wäre dies denkbar ?
Was ich nach wie vor im Syslog hab sind folgende Meldungen - und keinerlei Idee dazu:
Parallel dazu trace ich die grundsätzlichen Antwortzeiten der Gateways auf IP-Ebene, hier gab es keine Auffälligkeiten.
Na mal sehen was die neue Firmware bringt
Immer noch kein Restart der EE, obwohl ich nun wieder alle Scripts aktiviert habe...sehr seltsam.
Allerdings habe ich nun einen neuen Verdacht der mir nach der Beobachtung des Duty-Cycles aufgefallen ist.
Hier der Duty-Cylce eines Funk-Gateways der letzten Tage: Interessant dabei ist der Duty-Cycle bis kurz nach Mitternacht am 19.7. - nämlich konstant NULL !
Und das obwohl die CCU der Meinung war, dass das Gateway "verbunden" ist und ich auch nicht überproportional mit Funkstörungen konfrontiert war.
Danach hab ich es mal stromlos gemacht und von nun an gab es wieder realistische Duty-Cycle-Einträge.
Seit diesem Zeitpunkt gab es keinen Restart mehr der EE - allerdings habe ich parallel auch einiges Umgebaut (immer zwei Tage auf einen Restart zu warten und erst dann wieder die nächtste Änderung zu machen ist einfach zu mühsam und schädigt auf Dauer den WAF).
Eine Theorie wäre nun, dass es durch den Hänger des Gateways ab und an zu einem Restart eines CCU-Services (aufgrund eines Timeouts?) gekommen ist und dies wiederum einen Restart der EE verursacht hat.
Wäre dies denkbar ?
Was ich nach wie vor im Syslog hab sind folgende Meldungen - und keinerlei Idee dazu:
Code: Alles auswählen
Date,Time,Level,Host Name,Category,Program,Messages,
2016-07-22,12:55:38,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,12:17:54,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,12:17:14,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,08:59:10,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,08:48:48,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,08:30:39,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,08:26:49,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-22,08:25:02,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-22,08:23:48,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-22,08:23:09,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,05:42:41,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,04:30:07,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,03:10:25,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-22,02:53:12,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,23:51:58,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,18:46:28,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,17:20:38,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,17:13:38,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,16:48:28,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,11:55:28,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,11:08:57,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,02:03:31,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-21,01:05:03,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-21,00:40:23,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,00:39:50,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-21,00:33:43,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,23:56:47,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,19:25:07,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,18:05:57,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,14:09:53,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,13:41:17,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,06:30:38,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,05:56:57,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,05:37:17,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-20,04:51:49,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,23:45:52,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,23:43:37,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,23:40:54,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,22:12:19,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,22:11:19,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,22:10:46,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,20:46:42,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,16:57:26,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,15:46:58,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,13:29:50,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,13:07:13,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,12:58:53,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,12:21:41,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,12:14:22,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,12:14:06,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,12:14:06,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,11:46:00,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,11:14:12,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,10:48:48,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,08:50:03,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,07:53:22,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,07:52:53,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,07:50:15,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,07:08:42,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,06:54:55,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,06:07:44,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,05:50:53,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:49:53,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:45:54,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:45:05,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:40:56,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:40:05,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:35:57,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:35:13,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:30:58,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:30:09,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:26:00,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:24:13,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:21:01,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:19:33,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:16:03,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:14:25,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:11:04,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:08:14,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:06:05,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:03:17,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,05:01:07,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,04:58:18,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,04:56:08,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,04:55:41,Warning,homematic-ccu2.kuessel.lan,user,multimac,Bad cast: std::bad_cast
2016-07-19,03:47:26,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,03:32:22,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,02:50:02,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,02:40:10,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
2016-07-19,02:10:50,Warning,homematic-ccu2.kuessel.lan,user,multimac,Coprocessor is busy. Max response retry attempts reached.
Na mal sehen was die neue Firmware bringt
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
Re: und noch ein regelm. "Absturz" einer CCU2
zu früh gefreut - eben wieder mal ein Restart der EE kurz nach folgenden Events:
Code: Alles auswählen
Jul 22 13:38:21 homematic-ccu2 user.warn hs485d: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:21 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"70","JEQ0122797:21","VALUE",627.000000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:21 homematic-ccu2 user.err hs485d: XmlRpc transport error
Jul 22 13:38:24 homematic-ccu2 user.warn hs485d: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:24 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"70","JEQ0122797:16","FREQUENCY",925.000000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:24 homematic-ccu2 user.err hs485d: XmlRpc transport error
Jul 22 13:38:26 homematic-ccu2 user.warn hs485d: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:26 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"70","JEQ0122797:16","FREQUENCY",920.000000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:26 homematic-ccu2 user.err hs485d: XmlRpc transport error
Jul 22 13:38:27 homematic-ccu2 user.warn hs485d: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:27 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"70","JEQ0122797:21","VALUE",623.000000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:27 homematic-ccu2 user.err hs485d: XmlRpc transport error
Jul 22 13:38:28 homematic-ccu2 user.warn rfd: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:28 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"71","KEQ0971141:2","BOOT",true}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:28 homematic-ccu2 user.err rfd: XmlRpc transport error
Jul 22 13:38:28 homematic-ccu2 user.warn rfd: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:28 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"71","KEQ0971141:2","ENERGY_COUNTER",473245.500000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:28 homematic-ccu2 user.err rfd: XmlRpc transport error
Jul 22 13:38:28 homematic-ccu2 user.warn rfd: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:28 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"71","KEQ0971141:2","POWER",668.070000}],[methodName:"event",params:{"71","KEQ0971141:2","CURRENT",3271.000000}],[methodName:"event",params:{"71","KEQ0971141:2","VOLTAG
Jul 22 13:38:28 homematic-ccu2 user.err rfd: XmlRpc transport error
Jul 22 13:38:29 homematic-ccu2 user.warn rfd: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:29 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"71","LEQ0182508:2","BOOT",true}],[methodName:"event",params:{"71","LEQ0182508:2","ENERGY_COUNTER",19479.300000}],[methodName:"event",params:{"71","LEQ0182508:2","POWER
Jul 22 13:38:29 homematic-ccu2 user.err rfd: XmlRpc transport error
Jul 22 13:38:33 homematic-ccu2 user.warn hs485d: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:33 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"70","JEQ0122797:21","VALUE",620.000000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:33 homematic-ccu2 user.err hs485d: XmlRpc transport error
Jul 22 13:38:34 homematic-ccu2 user.warn hs485d: XmlRpc transport failed (first try), retrying...
Jul 22 13:38:34 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"70","JEQ0122797:16","FREQUENCY",915.000000}]}) on http://127.0.0.1:2110/RPC2:
Jul 22 13:38:34 homematic-ccu2 user.err hs485d: XmlRpc transport error
Jul 22 13:38:44 homematic-ccu2 user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Jul 22 13:38:47 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:47 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:48 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:48 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:48 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:48 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:49 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:49 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:49 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:49 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:49 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:50 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:50 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:50 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:50 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:51 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:51 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:51 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:51 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:51 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:52 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:52 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:52 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:52 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:53 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:53 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:53 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:53 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:53 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:54 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:54 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:54 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:54 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:54 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:55 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:55 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:55 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:55 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:56 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:56 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:56 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:56 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:57 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:57 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:57 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:57 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:58 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:58 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:58 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:58 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:58 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:59 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:59 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:59 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:38:59 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:38:59 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:00 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:00 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:00 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:00 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:01 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:01 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:01 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:01 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:02 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:02 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:02 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:02 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:02 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:03 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:06 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:06 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
Jul 22 13:39:07 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=CURRENT failed getting physical value.
Jul 22 13:39:07 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=ENERGY_COUNTER failed getting physical value.
Jul 22 13:39:07 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=FREQUENCY failed getting physical value.
Jul 22 13:39:11 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Retrying to send request (coprocessor was busy). Retry number 1
Jul 22 13:39:11 homematic-ccu2 user.info rfd: (KEQ1064779) CCU2CommController::sendBidcosRequest(): Got response after retry number 1
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------
535 Kanäle in 130 Geräten
--------------------------------------------