Guten Morgen,
nach dem Update habe ich das Problem, das alle meine HomematicIP-Geräte den Status "Störung Gerätekommunikation" anzeigen. Erst durch, entfernen oder Sicherung rausmachen und neu mit Strom versorgen, werden diese wieder gefunden.
In den Logs habe ich mal nachgeschaut, bei der Wetterstation habe ich folgendes gefunden:
Code: Alles auswählen
Jun 24 08:53:51 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D8A9910EA5:6","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jun 24 08:53:51 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: ExecuteScript: id = 2442; ticks = 17 [Execute():iseRTScheduler.cpp:604]
Jun 24 08:53:51 homematic-raspi user.debug rfd: GetAvailableFirmware for HM-LC-Sw1-Ba-PCB
Jun 24 08:53:51 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00185709ACB1D1:1","RAIN_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: RAIN_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jun 24 08:53:51 homematic-raspi user.debug rfd: GetAvailableFirmware for HM-PB-6-WM55
Jun 24 08:53:51 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00185709ACB1D1:1","RAIN_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jun 24 08:53:51 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: DP_VALUE_CHECK_UPDATE is set, condition = 1 [CheckCondition2Data():iseCondition.cpp:510]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: type = DP_GREATEROREQUAL, condition valL = 0.000000 valR1 = 0.000000 [Evaluate():iseCondition.cpp:324]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: sc = 0, condition result = 1 [Evaluate():iseCondition.cpp:1123]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: c = 0, condition result = 1 [Evaluate():iseRule.cpp:235]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: Rule evaluated state is TRUE by Program ID = 4353 'prgRainCounter_4306_00185709ACB1D1:1'; Destination ID = 4355 [SetState():iseDOMPrg.cpp:501]
Jun 24 08:53:51 homematic-raspi local0.info ReGaHss: Info: Program ID = 4353 'prgRainCounter_4306_00185709ACB1D1:1', rule's trigger flags = 2 [SetState():iseDOMPrg.cpp:515]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: execute Program ID = 4353 'prgRainCounter_4306_00185709ACB1D1:1'; Destination ID = 4355 [Execute():iseDOMPrg.cpp:611]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: start execute Destination within the trigger delay 0 [Execute():iseDOMPrg.cpp:615]
Jun 24 08:53:51 homematic-raspi local0.info ReGaHss: Info: added script element id= 4355; time= 0 [Add():iseRTScheduler.cpp:341]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: ExecuteDestination succeeded from Program ID = 4353 'prgRainCounter_4306_00185709ACB1D1:1' with valNew = '' [Execute():iseDOMPrg.cpp:625]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: initialize program 1695 (prgSunshineCounter_1645_00185709ACB1D1:1) [ThreadFunction():iseRTPrg.cpp:90]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: called Program ID = 1695 'prgSunshineCounter_1645_00185709ACB1D1:1' with valNew = '' ; oidTrigger = 65535 [SetState():iseDOMPrg.cpp:478]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: c = 0, condition result = 1 [Evaluate():iseRule.cpp:235]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: Rule evaluated state is TRUE by Program ID = 1695 'prgSunshineCounter_1645_00185709ACB1D1:1'; Destination ID = 1697 [SetState():iseDOMPrg.cpp:501]
Jun 24 08:53:51 homematic-raspi local0.info ReGaHss: Info: Program ID = 1695 'prgSunshineCounter_1645_00185709ACB1D1:1', rule's trigger flags = 2 [SetState():iseDOMPrg.cpp:515]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: execute Program ID = 1695 'prgSunshineCounter_1645_00185709ACB1D1:1'; Destination ID = 1697 [Execute():iseDOMPrg.cpp:611]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: start execute Destination within the trigger delay 0 [Execute():iseDOMPrg.cpp:615]
Jun 24 08:53:51 homematic-raspi local0.info ReGaHss: Info: added script element id= 1697; time= 0 [Add():iseRTScheduler.cpp:341]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: ExecuteDestination succeeded from Program ID = 1695 'prgSunshineCounter_1645_00185709ACB1D1:1' with valNew = '' [Execute():iseDOMPrg.cpp:625]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: initialize program 4338 (prgSunshineCounter_4306_00185709ACB1D1:1) [ThreadFunction():iseRTPrg.cpp:90]
Jun 24 08:53:51 homematic-raspi local0.debug ReGaHss: Verbose: called Program ID = 4338 'prgSunshineCounter_4306_00185709ACB1D1:1' with valNew = '' ; oidTrigger = 65535 [SetState():iseDOMPrg.cpp:478]
Jun 24 08:53:51 homematic-raspi local0.info ReGaHss: Info: interface name= HmIP-RF for ID=1009 [GetInterfaceByID():iseXmlRpc.cpp:2552]
Jun 24 08:53:51 homematic-raspi user.debug rfd: GetAvailableFirmware for HM-RC-Key4-3
Jun 24 08:53:51 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001397099C464E:0","ERROR_OVERHEAT"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ERROR_OVERHEAT"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jun 24 08:53:51 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"001397099C464E:0","ERROR_OVERHEAT"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jun 24 08:53:51 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jun 24 08:53:51 homematic-raspi local0.info ReGaHss: Info: interface name= HmIP-RF for ID=1009 [GetInterfaceByID():iseXmlRpc.cpp:
Kann mir da jemand helfen, hätte gerne mal das Problem weg, da es bei jedem Update auftritt.
Gruß,
Sascha