HMCCU und 2.47.20

[doman75]

Hallo,

ich habe heute bei der CCU auf 2.47.20 geupdate (vorher 2.47.15), erst ging nach dem Update wie es soll. Nach einem Neustart von FHEM bleibt aber die HMCCU auf initialized stehen und bei allen Geräten (egal ob RF oder IP) steht pending. das CCUflag der HMCCU steht auch auf notinitialupdate und reconnect, aber dieses mal will er sich irgendwo nicht verbinden. Im log steht aber nur sowas wie:

HMCCU: [HMCCU2] HMCCU: Initializing devices
2019.10.25 17:38:09.009 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:8181/tclrega.exe
2019.10.25 17:38:13.011 2: HMCCU: [HMCCU2] HMScript failed. http://192.168.0.4:8181/tclrega.exe: Select timeout/error:
2019.10.25 17:38:13.011 1: HMCCU: [HMCCU2] HMCCU: Error while reading device list from CCU 192.168.0.4
2019.10.25 17:38:13.158 1: [Freezemon] myFreezemon: possible freeze starting at 17:38:10, delay is 3.158 possibly caused by: tmr-HMCCU_InitDevice(HMCCU2)
2019.10.25 17:38:31.864 2: HMCCU: [HMCCU2] Get RPC device for interface BidCos-RF
2019.10.25 17:38:31.864 0: HMCCU: [HMCCU2] Definition of some RPC devices failed

Das list von der hmccu sieht so aus:

Code Auswählen Erweitern


Internals:
   .triggerUsed 1
   CCUNum     1
   Clients    :HMCCUDEV:HMCCUCHN:HMCCURPC:HMCCURPCPROC:
   DEF        192.168.0.4
   FUUID      5c42db4d-f33f-5c7c-5aec-65364bfe07b6fdc5
   NAME       HMCCU2
   NOTIFYDEV  global,TYPE=(HMCCU|HMCCUDEV|HMCCUCHN)
   NR         483
   NTFY_ORDER 50-HMCCU2
   RPCState   inactive
   STATE      inactive/Error
   TYPE       HMCCU
   ccuip      192.168.0.4
   ccustate   active
   ccutype    CCU2/3
   host       192.168.0.4
   prot       http
   version    4.3.018
   .attraggr:
   .attrminint:
   READINGS:
     2018-09-24 14:10:07   Anwesenheit     true
     2019-10-25 08:35:32   Presence        false
     2019-10-25 10:16:07   count_channels  569
     2019-10-25 10:16:07   count_devices   70
     2019-10-25 10:16:07   count_groups    1
     2019-10-25 10:16:07   count_interfaces 4
     2019-10-25 10:16:07   count_programs  57
     2017-12-26 16:17:11   iface_addr_1    OEQ0460083
     2017-12-26 16:17:11   iface_addr_2    3014F711A000035709906D33
     2017-12-26 16:17:11   iface_conn_1    1
     2017-12-26 16:17:11   iface_conn_2    1
     2017-12-26 16:17:11   iface_ducy_1    3
     2017-12-26 16:17:11   iface_ducy_2    4
     2017-12-26 16:17:11   iface_type_1    CCU2
     2017-12-26 16:17:11   iface_type_2    HMIP_CCU2
     2018-05-25 08:37:26   myTwilight      6.000000
     2019-10-25 17:35:09   rpcstate        inactive
     2019-10-25 17:42:56   state           Error
   hmccu:
     defInterface BidCos-RF
     defPort    2001
     evtime     0
     evtimeout  0
     rpccount   0
     rpcports   
     updatetime 0
     adr:
     ccu:
       delay      180
       delayed    1
       timeout    1
     dev:
     ifports:
     interfaces:
     rpc:
Attributes:
   ccuflags   procrpc,noInitialUpdate,nonBlocking,reconnect
   room       Homematic,IO
   rpcinterfaces BidCos-RF,HmIP-RF,VirtualDevices
   rpcport    2001,2010,9292
   rpcqueue   /tmp/ccuqueue
   rpcserver  on
   stateFormat rpcstate/state
   verbose    5

Kann mir jemand helfen?

Grüße
Swen

[doman75]

auf der CCU selber stehen viele solche Meldungen:

Oct 25 17:59:49 homematic-ccu2 local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Oct 25 17:59:50 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=IEC_ENERGY_COUNTER failed getting physical value.
Oct 25 17:59:50 homematic-ccu2 local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:2001, params: {"MEQ0705699:2","IEC_ENERGY_COUNTER"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Oct 25 17:59:50 homematic-ccu2 local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"MEQ0705699:2","IEC_ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Oct 25 17:59:50 homematic-ccu2 local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Oct 25 17:59:50 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=IEC_POWER failed getting physical value.
Oct 25 17:59:50 homematic-ccu2 local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:2001, params: {"MEQ0705699:2","IEC_POWER"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Oct 25 17:59:50 homematic-ccu2 local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"MEQ0705699:2","IEC_POWER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Oct 25 17:59:50 homematic-ccu2 local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]

[zap]

Ich würde mal FHEM stoppen.
Dann die CCU neu starten und mindestens 10 Minuten warten.
Dann FHEM wieder starten.

Wenn HMCCU trotzdem nicht richtig initialisiert wird, bitte mal alle HMCCU/HMCCURPCPROC Meldungen aus dem Logfile posten.

[doman75]

Hab FHEM ausgemacht, dann CCU2 mal stromlos und dann neugestartet, nach ca. 30 minuten FHem Server rebooted. Selbes Verhalten wie vorher:

Steht aber auch nicht sonderlich viel in der Log, wenn ich das http://192.168.0.4:8181/tclrega.exe im Browser eingebe kommt folgendes:

<xml>
<exec>/tclrega.exe</exec>
<sessionId/>
<httpUserAgent>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
</httpUserAgent>
</xml

LOGs für HMCCU

2019.10.25 19:36:16.611 0: HMCCU: [HMCCU2] Definition of some RPC devices failed
2019.10.25 19:36:16.611 2: HMCCU: [HMCCU2] Get RPC device for interface BidCos-RF
2019.10.25 19:35:56.643 1: HMCCU: [HMCCU2] HMCCU: Error while reading device list from CCU 192.168.0.4
2019.10.25 19:35:56.643 2: HMCCU: [HMCCU2] HMScript failed. http://192.168.0.4:8181/tclrega.exe: Select timeout/error:
2019.10.25 19:35:52.638 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:8181/tclrega.exe
2019.10.25 19:35:52.636 1: HMCCU: [HMCCU2] HMCCU: Initializing devices
2019.10.25 19:32:56.610 0: HMCCU: Start of RPC server after FHEM initialization in 200 seconds
2019.10.25 19:32:56.268 2: HMCCUCHN: [HmIP_GarageLichtKL] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:56.266 2: HMCCUCHN: [StromverbrauchLichtGarageKL] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:56.263 2: HMCCUCHN: [HMIP_Pumpe3] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.485 2: HMCCUCHN: [StromverbrauchWaschDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.483 2: HMCCUCHN: [HmIP_WaschLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.474 2: HMCCUCHN: [HM_Terasse6_6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.454 2: HMCCUCHN: [StromverbrauchHeizungDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.453 2: HMCCUCHN: [HmIP_HeizungLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.451 2: HMCCUDEV: [HM_HmIP_WFAussenlichtkom] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.450 2: HMCCUCHN: [StromverbrauchAnkleideSchuheDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.448 2: HMCCUCHN: [HM_ANSCDeckenlicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.447 2: HMCCUCHN: [StromverbrauchAnkleideDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.443 2: HMCCUCHN: [HM_ANDeckenlicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.364 2: HMCCUDEV: [HM_MZ6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.363 2: HMCCUCHN: [SverbrauchMaedchenzimmer] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.360 2: HMCCUDEV: [HMIP_Maedchenzimmer] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.358 2: HMCCUCHN: [Terasse_rechts_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.356 2: HMCCUCHN: [Terasse_rechts_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.355 2: HMCCUDEV: [BUHHK] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.353 2: HMCCUDEV: [HMIP_BUHHKR] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.351 2: HMCCUDEV: [HMIP_BUHHKL] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.335 2: HMCCUCHN: [StromverbrauchWFAussenHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.332 2: HMCCUCHN: [HM_WindfangAussenLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.329 2: HMCCUCHN: [StromverbrauchPumpe3HMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.323 2: HMCCUCHN: [StromverbrauchBaduntenWandLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.318 2: HMCCUCHN: [HM_BaduntenWandLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.309 2: HMCCUCHN: [StromverbrauchTrocknerHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.306 2: HMCCUDEV: [HMIP_Trockner] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.302 2: HMCCUCHN: [StromverbrauchWaschmaschineHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.299 2: HMCCUDEV: [HMIP_Waschmaschine] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.298 2: HMCCUDEV: [HM_WDS40Garage] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.289 2: HMCCUCHN: [HMIP_SZ8_8] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.288 2: HMCCUCHN: [HMIP_SZ8_7] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.279 2: HMCCUCHN: [HMIP_SZ8_4] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.278 2: HMCCUCHN: [HMIP_SZ8_3] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.274 2: HMCCUCHN: [HMIP_SZ8_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.273 2: HMCCUDEV: [HM_HmIP_RolloHZ] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:55.167 2: HMCCUDEV: [HM_PresenceTaster] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:54.662 2: HMCCUDEV: [HmIP_PCBS] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:54.661 2: HMCCUDEV: [HM_Kueche6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:54.659 2: HMCCUCHN: [HMIP_Kueche6_4] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:54.657 2: HMCCUCHN: [HMIP_Kueche6_3] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:54.259 2: HMCCUDEV: [HM_Terasse6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:54.257 2: HMCCUCHN: [HmIPSTHWZ1_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.799 2: HMCCUCHN: [StromverbrauchBadobenDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.770 2: HMCCUCHN: [StromverbrauchBaduntenDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.767 2: HMCCUCHN: [HM_BUDeckenlicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.765 2: HMCCUCHN: [StromverbrauchMZDeckenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.763 2: HMCCUCHN: [HM_MZDeckenlicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.760 2: HMCCUCHN: [StromverbrauchFluruntenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.753 2: HMCCUCHN: [HM_Fluruntenlicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.752 2: HMCCUCHN: [StromverbrauchWFAussenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.751 2: HMCCUCHN: [HM_WindfangAussen] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.750 2: HMCCUCHN: [StromverbrauchWFInnenLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.748 2: HMCCUCHN: [HM_WindfangInnenDeckenLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.747 2: HMCCUCHN: [StromverbrauchHmIP_LichtSuZDecke] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.745 2: HMCCUCHN: [HmIP_LichtSuZDecke] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.742 2: HMCCUCHN: [StromverbrauchBadobenWandLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.740 2: HMCCUCHN: [HM_BadobenWandLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.685 2: HMCCUCHN: [HM_BadobenDeckenLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.661 2: HMCCUCHN: [StromverbrauchKinderzimmerLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.660 2: HMCCUCHN: [HM_KinderzimmerLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.659 2: HMCCUDEV: [HM_test2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.658 2: HMCCUDEV: [HM_test] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.656 2: HMCCUCHN: [StromverbrauchPumpe2HMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.654 2: HMCCUCHN: [HMIP_Pumpe2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.652 2: HMCCUCHN: [StromverbrauchAussenSTRasenHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.651 2: HMCCUCHN: [HMIP_AussensteckdoseRasen] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.650 2: HMCCUCHN: [StromverbrauchAussenSTWFHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.649 2: HMCCUCHN: [HMIP_AussensteckdoseWF] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.629 2: HMCCUCHN: [StromverbrauchPumpe1HMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.628 2: HMCCUCHN: [HMIP_Pumpe1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.620 2: HMCCUCHN: [HM_KuecheLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.619 2: HMCCUCHN: [StromverbrauchKuecheLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.615 2: HMCCUCHN: [HM_SZTaster_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.611 2: HMCCUCHN: [HM_Stube6_6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.607 2: HMCCUCHN: [HMIP_Kueche6_6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.597 2: HMCCUCHN: [HMIP_Kueche6_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.595 2: HMCCUCHN: [HM_Esstischlampe_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.594 2: HMCCUCHN: [HM_Esstischlampe_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:53.374 2: HMCCUDEV: [HM_HmIP_SPDR] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.722 2: HMCCUDEV: [HM_HmIP_Presence2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.721 2: HMCCUDEV: [HM_HmIP_BWAussen1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.717 2: HMCCUCHN: [HM_Stube6_5] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.716 2: HMCCUCHN: [HM_Stube6_3] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.715 2: HMCCUCHN: [HM_Stube6_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.715 2: HMCCUDEV: [HM_Stube6] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.714 2: HMCCUCHN: [HM_Stube6_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.712 2: HMCCUCHN: [StromverbrauchGaesteWCLichtHMIP] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.710 2: HMCCUCHN: [HM_GaesteWCLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.708 2: HMCCUCHN: [Boden_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.706 2: HMCCUCHN: [Boden_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.704 2: HMCCUCHN: [StromverbrauchKuehlschrankuntenHM] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.703 2: HMCCUCHN: [HM_Kuehlschrankunten1_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.702 2: HMCCUDEV: [HM_HmIP_Presence1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.700 2: HMCCUDEV: [HM_FlurLichtoben] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.696 2: HMCCUDEV: [HM_AlarmSirene] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.690 2: HMCCUDEV: [HM_StromverbrauchHaus] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.689 2: HMCCUCHN: [StromverbrauchHeizungHM] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.687 2: HMCCUCHN: [HM_Heizung_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.685 2: HMCCUDEV: [HM_Wandlampe] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.684 2: HMCCUCHN: [Garage4fA_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.682 2: HMCCUCHN: [Terasse_2] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.681 2: HMCCUCHN: [Terasse_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.679 2: HMCCUCHN: [TerasseSeite_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.667 2: HMCCUDEV: [HM_AnjaFB] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.666 2: HMCCUDEV: [HM_SwenFB] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.663 2: HMCCUDEV: [HM_Haustuerschloss] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.661 2: HMCCUDEV: [HM_WegLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.654 2: HMCCUDEV: [HM_SZLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.650 2: HMCCUDEV: [HM_FlurLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 19:32:52.636 1: HMCCU: [HMCCU2] Scheduling delayed initialization in 180 seconds
2019.10.25 19:32:52.635 1: HMCCU: [HMCCU2] HMCCU: Error while reading device list from CCU 192.168.0.4
2019.10.25 19:32:52.635 2: HMCCU: [HMCCU2] HMScript failed. http://192.168.0.4:8181/tclrega.exe: Select timeout/error:
2019.10.25 19:32:48.630 1: HMCCU: [HMCCU2] HMCCU: Initializing device
2019.10.25 19:32:48.630 1: HMCCU: [HMCCU2] Initialized version 4.3.018

[zap]

Das sieht doch eigentlich gut aus. Die Devices bleiben auf pending, weil du noinitialupdate gesetzt hast. Wenn du jetzt die RPC Server startest, sollten die Devices nach und nach aktualisiert werden.

[doman75]

Wie starte ich den die rpc Server. Das Attribut steht auf on, da sollte er doch die rpc Server selber starten oder?

[amenomade]

Wie starte ich den die rpc Server. Das Attribut steht auf on, da sollte er doch die rpc Server selber starten oder?

Code Auswählen Erweitern

set HMCCU2 rpcserver on
Das Attribut kommt nur im Einsatz beim Start von FHEM

[zap]

Er startet FHEM ja, von daher müssten Meldungen von HMCCURPCPROC im Log zu finden sein. Gar keine ist seltsam

[doman75]

Genau ich habe FHEM neu gestartet, also sollte durch das attribut die RCP Server ja starten. Beim händischen Versuch rpcserver on kam auch ein Fehler, denn ich aber jetzt nicht mehr nachvollziehen kann, da es seit gestern 20:49 wieder geht.

Ich habe 20:46 den FHEM nochmal restarted dann stand erstmal wieder der timeout Fehler da, aber nach 180 Sekunden kam dann das:

2019.10.25 21:10:00.947 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2001
2019.10.25 21:05:00.941 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2001
2019.10.25 21:00:00.935 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2001
2019.10.25 20:58:32.666 1: [Freezemon] myFreezemon: possible freeze starting at 20:58:30, delay is 2.666 possibly caused by: tmr-statistics_PeriodChange(Statistik)
2019.10.25 20:55:00.928 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2001
2019.10.25 20:51:40.809 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:51:00.938 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:51:00.936 2: HMCCU: [HMCCU2] FormatReadingValue: sn = null, Value false 66616c7365 not changed
2019.10.25 20:51:00.936 2: HMCCU: [HMCCU2] GetAttrStripNumber: stripnumber = null
2019.10.25 20:51:00.924 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:8181/tclrega.exe
2019.10.25 20:50:01.117 2: CCURPC: [d_rpc000004BidCos_RF] CB2001000003000004 NewDevice received 164 device and channel specifications
2019.10.25 20:50:00.929 1: [Freezemon] myFreezemon: possible freeze starting at 20:49:51, delay is 9.929 possibly caused by: no bad guy found
2019.10.25 20:50:00.927 1: HMCCURPCPROC: [d_rpc000004BidCos_RF] Scheduled CCU ping every 300 seconds
2019.10.25 20:50:00.925 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:50:00.923 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:50:00.922 1: HMCCU: [HMCCU2] All RPC servers running
2019.10.25 20:50:00.922 4: HMCCU: [HMCCU2] Set rpcstate to running
2019.10.25 20:50:00.921 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:50:00.917 1: HMCCURPCPROC: [d_rpc000004BidCos_RF] RPC server CB2001000003000004 running
2019.10.25 20:50:00.362 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2001
2019.10.25 20:50:00.362 2: HMCCURPCPROC: [d_rpc000004BidCos_RF] Registering callback http://192.168.0.3:7411/fh2001 of type A with ID CB2001000003000004 at http://192.168.0.4:2001
2019.10.25 20:50:00.362 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2001
2019.10.25 20:50:00.361 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:50:00.360 2: HMCCURPCPROC: [d_rpc000004BidCos_RF] RPC server CB2001000003000004 enters server loop
2019.10.25 20:50:00.312 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:50:00.311 1: HMCCURPCPROC: [d_rpc000004VirtualDevices] RPC server CB9292000003000004 running
2019.10.25 20:49:53.237 2: CCURPC: [d_rpc000004HmIP_RF] CB2010000003000004 NewDevice received 432 device and channel specifications
2019.10.25 20:49:51.166 2: CCURPC: [d_rpc000004VirtualDevices] CB9292000003000004 NewDevice received 7 device and channel specifications
2019.10.25 20:49:50.080 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:9292/groups
2019.10.25 20:49:50.080 2: HMCCURPCPROC: [d_rpc000004VirtualDevices] Registering callback http://192.168.0.3:14702/fh9292 of type A with ID CB9292000003000004 at http://192.168.0.4:9292/groups
2019.10.25 20:49:50.080 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:9292/groups
2019.10.25 20:49:50.079 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:49:50.078 2: HMCCURPCPROC: [d_rpc000004VirtualDevices] RPC server CB9292000003000004 enters server loop
2019.10.25 20:49:50.072 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:49:50.071 1: HMCCURPCPROC: [d_rpc000004HmIP_RF] RPC server CB2010000003000004 running
2019.10.25 20:49:50.027 2: CCURPC: [d_rpc000004VirtualDevices] CB9292000003000004 accepting connections. PID=20376
2019.10.25 20:49:50.027 2: HMCCURPCPROC: [d_rpc000004VirtualDevices] Callback server CB9292000003000004 created. Listening on port 14702
2019.10.25 20:49:50.000 2: CCURPC: [d_rpc000004BidCos_RF] CB2001000003000004 accepting connections. PID=20374
2019.10.25 20:49:50.000 2: HMCCURPCPROC: [d_rpc000004BidCos_RF] Callback server CB2001000003000004 created. Listening on port 7411
2019.10.25 20:49:50.000 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2010
2019.10.25 20:49:49.999 2: HMCCURPCPROC: [d_rpc000004HmIP_RF] Registering callback http://192.168.0.3:7420/fh2010 of type A with ID CB2010000003000004 at http://192.168.0.4:2010
2019.10.25 20:49:49.999 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:2010
2019.10.25 20:49:49.999 2: HMCCURPCPROC: [d_rpc000004HmIP_RF] RPC server CB2010000003000004 enters server loop
2019.10.25 20:49:49.998 2: CCURPC: [d_rpc000004VirtualDevices] Initializing RPC server CB9292000003000004 for interface VirtualDevices
2019.10.25 20:49:49.997 2: CCURPC: [d_rpc000004HmIP_RF] CB2010000003000004 accepting connections. PID=20375
2019.10.25 20:49:49.996 2: HMCCURPCPROC: [d_rpc000004HmIP_RF] Callback server CB2010000003000004 created. Listening on port 7420
2019.10.25 20:49:49.965 1: HMCCURPCPROC: [d_rpc000004VirtualDevices] RPC server starting
2019.10.25 20:49:49.951 2: HMCCURPCPROC: [d_rpc000004VirtualDevices] RPC server process started for interface VirtualDevices with PID=20376
2019.10.25 20:49:49.940 2: CCURPC: [d_rpc000004HmIP_RF] Initializing RPC server CB2010000003000004 for interface HmIP-RF
2019.10.25 20:49:49.939 1: HMCCURPCPROC: [d_rpc000004HmIP_RF] RPC server starting
2019.10.25 20:49:49.930 2: HMCCURPCPROC: [d_rpc000004HmIP_RF] RPC server process started for interface HmIP-RF with PID=20375
2019.10.25 20:49:49.921 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:49:49.918 1: HMCCURPCPROC: [d_rpc000004BidCos_RF] RPC server starting
2019.10.25 20:49:49.918 2: CCURPC: [d_rpc000004BidCos_RF] Initializing RPC server CB2001000003000004 for interface BidCos-RF
2019.10.25 20:49:49.913 2: HMCCURPCPROC: [d_rpc000004BidCos_RF] RPC server process started for interface BidCos-RF with PID=20374
2019.10.25 20:49:49.908 1: HMCCU: [HMCCU2] Saving FHEM config
2019.10.25 20:49:49.803 1: HMCCURPCPROC: [d_rpc000004VirtualDevices] Initialized version 1.8 for interface VirtualDevices with I/O device HMCCU2
2019.10.25 20:49:49.801 1: HMCCU: [HMCCU2] Creating new RPC device d_rpc000004VirtualDevices
2019.10.25 20:49:49.801 1: HMCCU: [HMCCU2] No RPC device defined for interface VirtualDevices
2019.10.25 20:49:49.799 2: HMCCU: [HMCCU2] Get RPC device for interface VirtualDevices
2019.10.25 20:49:49.676 1: HMCCURPCPROC: [d_rpc000004HmIP_RF] Initialized version 1.8 for interface HmIP-RF with I/O device HMCCU2
2019.10.25 20:49:49.674 1: HMCCU: [HMCCU2] Creating new RPC device d_rpc000004HmIP_RF
2019.10.25 20:49:49.674 1: HMCCU: [HMCCU2] No RPC device defined for interface HmIP-RF
2019.10.25 20:49:49.673 2: HMCCU: [HMCCU2] Get RPC device for interface HmIP-RF
2019.10.25 20:49:49.526 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:49:49.523 1: HMCCURPCPROC: [d_rpc000004BidCos_RF] Initialized version 1.8 for interface BidCos-RF with I/O device HMCCU2
2019.10.25 20:49:49.502 1: HMCCU: [HMCCU2] Creating new RPC device d_rpc000004BidCos_RF
2019.10.25 20:49:49.502 1: HMCCU: [HMCCU2] No RPC device defined for interface BidCos-RF
2019.10.25 20:49:49.501 2: HMCCU: [HMCCU2] Get RPC device for interface BidCos-RF
2019.10.25 20:49:33.379 1: [Freezemon] myFreezemon: possible freeze starting at 20:49:26, delay is 7.378 possibly caused by: tmr-HMCCU_InitDevice(HMCCU2)
2019.10.25 20:49:33.194 1: HMCCU: [HMCCU2] HMCCU: Read 1 virtual groups from CCU 192.168.0.4
2019.10.25 20:49:33.194 1: HMCCU: [HMCCU2] HMCCU: Read 57 programs from CCU 192.168.0.4
2019.10.25 20:49:33.194 1: HMCCU: [HMCCU2] HMCCU: Read 4 interfaces from CCU 192.168.0.4
2019.10.25 20:49:33.194 1: HMCCU: [HMCCU2] HMCCU: Read 70 devices with 569 channels from CCU 192.168.0.4
2019.10.25 20:49:33.190 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
2019.10.25 20:49:31.346 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:8181/tclrega.exe
2019.10.25 20:49:30.066 3: HMCCU: [HMCCU2] Can't initialize client device BUHHK
2019.10.25 20:49:30.060 1: Windfanglicht: 'set HM_WindfangInnenDeckenLicht ?' returned undef
2019.10.25 20:49:29.944 3: HMCCU: [HMCCU2] Can't initialize client device HM_test2
2019.10.25 20:49:29.656 1: Aussenlicht: 'set HM_WegLicht ?' returned undef
2019.10.25 20:49:29.656 1: Aussenlicht: 'set Terasse_1 ?' returned undef
2019.10.25 20:49:29.656 1: Aussenlicht: 'set TerasseSeite_1 ?' returned undef
2019.10.25 20:49:29.656 1: Aussenlicht: 'set Terasse_2 ?' returned undef
2019.10.25 20:49:29.655 1: Heizunglicht: 'set HmIP_WaschLicht ?' returned undef
2019.10.25 20:49:29.655 1: Heizunglicht: 'set HmIP_HeizungLicht ?' returned undef
2019.10.25 20:49:29.655 1: ANlicht: 'set HM_ANSCDeckenlicht ?' returned undef
2019.10.25 20:49:29.655 1: ANlicht: 'set HM_ANDeckenlicht ?' returned undef
2019.10.25 20:49:29.655 1: BUlicht: 'set HM_BaduntenWandLicht ?' returned undef
2019.10.25 20:49:29.655 1: BUlicht: 'set HM_BUDeckenlicht ?' returned undef
2019.10.25 20:49:29.655 1: MZlicht: 'set HM_MZDeckenlicht ?' returned undef
2019.10.25 20:49:29.655 1: Untergeschosslicht: 'set HM_Fluruntenlicht ?' returned undef
2019.10.25 20:49:29.654 1: Dachgeschosslicht: 'set Boden_2 ?' returned undef
2019.10.25 20:49:29.654 1: Dachgeschosslicht: 'set Boden_1 ?' returned undef
2019.10.25 20:49:29.654 1: Schulzimmerlicht: 'set HmIP_LichtSuZDecke ?' returned undef
2019.10.25 20:49:29.654 1: Obergeschosslicht: 'set HM_FlurLichtoben ?' returned undef
2019.10.25 20:49:29.654 1: Badobenlicht: 'set HM_BadobenWandLicht ?' returned undef
2019.10.25 20:49:29.654 1: Badobenlicht: 'set HM_BadobenDeckenLicht ?' returned undef
2019.10.25 20:49:29.654 1: Schlafzimmerlicht: 'set HM_SZLicht ?' returned undef
2019.10.25 20:49:29.653 1: Kinderzimmerlicht: 'set HM_KinderzimmerLicht ?' returned undef
2019.10.25 20:49:29.653 1: Stubenlicht: 'set HM_Wandlampe ?' returned undef
2019.10.25 20:49:29.652 1: Stubenlicht: 'set HM_Esstischlampe_2 ?' returned undef
2019.10.25 20:49:29.652 1: Stubenlicht: 'set HM_Esstischlampe_1 ?' returned undef
2019.10.25 20:49:29.651 1: Kuechenlicht: 'set HM_KuecheLicht ?' returned undef
2019.10.25 20:49:29.651 1: GaesteWClicht: 'set HM_GaesteWCLicht ?' returned undef
2019.10.25 20:49:29.650 1: Flurlicht: 'set HM_FlurLicht ?' returned undef
2019.10.25 20:49:29.645 2: HMCCU: [HMCCU2] Initializing 111 client devices in state 'pending'
2019.10.25 20:49:29.581 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:8181/tclrega.exe
2019.10.25 20:49:25.891 4: HMCCU: [HMCCU2] Build URL = http://192.168.0.4:8181/tclrega.exe
2019.10.25 20:49:25.889 1: HMCCU: [HMCCU2] HMCCU: Initializing devices
2019.10.25 20:47:03.029 2: HMCCU: [HMCCU2] GetAttrSubstitute: subst =
....
2019.10.25 20:46:25.918 2: HMCCUCHN: [TerasseSeite_1] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.910 2: HMCCUDEV: [HM_AnjaFB] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.909 2: HMCCUDEV: [HM_SwenFB] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.908 2: HMCCUDEV: [HM_Haustuerschloss] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.906 2: HMCCUDEV: [HM_WegLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.902 2: HMCCUDEV: [HM_SZLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.900 2: HMCCUDEV: [HM_FlurLicht] Cannot detect IO device, maybe CCU not ready. Trying later ...
2019.10.25 20:46:25.888 1: HMCCU: [HMCCU2] Scheduling delayed initialization in 180 seconds
2019.10.25 20:46:25.888 1: HMCCU: [HMCCU2] HMCCU: Error while reading device list from CCU 192.168.0.4
2019.10.25 20:46:25.888 2: HMCCU: [HMCCU2] HMScript failed. http://192.168.0.4:8181/tclrega.exe: Select timeout/error:
2019.10.25 20:46:21.883 1: HMCCU: [HMCCU2] HMCCU: Initializing device
2019.10.25 20:46:21.883 1: HMCCU: [HMCCU2] Initialized version 4.3.018

Danach standen auch alle 3 RPC Dienste wieder da mit running/OK und die Geräte wurden langsam wieder befüllt.

Was da jetzt anders war als die Stunden zuvor wo beim tclrega immer timeout kam, weiß ich nicht.
Auf der CCU war um die Zeit jedenfalls auch nix anderes zu sehen.

VG
Swen

[zap]

Ich vermute, die CCU2 ist nach einem Update bzw einem Neustart ziemlich lange mit sich selbst beschäftigt. Dazu kommt, dass EQ3 mit den letzten Firmware Updates an den Timeouts rumgespielt hat. Das wurde mit .20 zwar wieder (alles?) zurückgenommen bzw. Entschärft, aber trauen würde ich dem ganzen trotzdem nicht.
Vielleicht wäre eine CCU3 bzw ein Raspi doch mal eine Überlegung wert ...