Neues Modul HMCCU für Homematic CCU

Begonnen von zap, 19 August 2015, 19:45:30

Vorheriges Thema - Nächstes Thema
Drucken
Nach unten Seiten 1 ... 88 89 90 91 92 ... 103
Benutzer-Aktionen

zap

#1335
13 März 2017, 07:35:11
Also nach einem manuellen get Update funktioniert dann auch die automatische Aktualisierung über den RPC Server?

Gibt es Fehlermeldungen im Log?
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

zap

#1336
13 März 2017, 19:26:45 Letzte Bearbeitung: 13 März 2017, 19:28:48 von zap
Zitat von: wolfgang99 am 12 März 2017, 18:52:10
Ich betreibe (sehr gerne) HMCCU mit einer CCU2 parallel zu einem HMLAN.
Analysiere dabei laufend und sporadisch Funkprobleme der HMLAN-Devices (Lampe steht auf ioerr etc)

Analyse per apptime zeigt eigentlich nur den folgenden bemerkenswerten Eintrag:
tmr-HMCCU_ReadRPCQueue      HASH(0x2defb98)    2605     65     8431   129.71   2514     HASH(d_ccu)
HMLAN1                                      HMLAN_Ready        3004     25     3124   124.96      0        HASH(HMLAN1)
logdb                                          DbLog_Log             1554     62     7597   122.53      0        HASH(logdb); HASH(eg_wz_sensor)

Ist der maxDLY für HMCCU normal? Oder legt mir hier HMCCU mein restliches FHEM lahm?
Muss ich für den Parallelbetrieb speziell etwas berücksichtigen?
Danke für Hinweise.

Hier die Werte, die ich bei mir gemessen habe:

Code Auswählen

                                name             function    max  count    total  average maxDly
              tmr-HMCCU_ReadRPCQueue      HASH(0x3da6640)   1439    341     5560    16.30    418 HASH(d_ccu)
             tmr-HUEBridge_GetUpdate      HASH(0x53f0840)     76      6      222    37.00      3 HASH(d_hue)
      tmr-PIONEERAVR_checkConnection      HASH(0x24e9c48)     60      3      132    44.00      3 HASH(d_avr)
                          TCM_ESP3_2             TCM_Read     27     43      202     4.70      0 HASH(TCM_ESP3_2)


m.E. zeigt ein hoher MaxDelay Wert, dass FHEM grundsätzlich einiges zu tun hat. Die Ausführungszeit von ReadRPCQueue ist hingegen sehr kurz. Ich denke nicht, dass es an der Funktion liegt.
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

aski71

#1337
14 März 2017, 12:39:38
Zitat von: zap am 13 März 2017, 07:35:11
Also nach einem manuellen get Update funktioniert dann auch die automatische Aktualisierung über den RPC Server?

Gibt es Fehlermeldungen im Log?

Ja. Genau so ist es.
Fehlermeldungen im Log sehe ich keine.
Außer besagte mit "Activated", die ich schon geschickt hatte. Ich habe keine Ahnung, worauf die sich bezieht. Nur war sie vorher eben nicht da.

zap

#1338
14 März 2017, 18:34:26
ok, wenn Du nicht so viele HMCCUDEV und HMCCUCHN Devices hast, gib mir bitte mal ein list von denen, insbesondere wenn Du das Attribut ccuscaleval verwendest.

Außerdem bitte die Attribute des I/O Device.
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

aski71

#1339
14 März 2017, 18:39:23
Zitat von: zap am 14 März 2017, 18:34:26
ok, wenn Du nicht so viele HMCCUDEV und HMCCUCHN Devices hast, gib mir bitte mal ein list von denen, insbesondere wenn Du das Attribut ccuscaleval verwendest.

Außerdem bitte die Attribute des I/O Device.

ccuscaleval benutze ich nirgendwo.

IO Device sieht so aus:

Code Auswählen
define ccu2 HMCCU 192.168.2.63
attr ccu2 ccuflags intrpc
attr ccu2 room Zentral
attr ccu2 rpcinterval 3
attr ccu2 rpcserver on
attr ccu2 stateFormat rpcstate/state
attr ccu2 stripnumber 2

CCUDEVs und CCHCHNs hab ich fast ausschließlich, also jede Menge davon. Was meinst Du mit list? Was genau soll ich Dir schicken?

zap

#1340
14 März 2017, 19:48:11
Wenn Du z.B. ein HMCCUDEV mit dem Namen "mein_dev" definiert hast, mach mal beispielhaft für eines dieser Devices:
Code Auswählen

list mein_dev


Außerdem bitte alle "HMCCU" und "CCURPC" Meldungen, die während dem Start von FHEM bzw. dem RPC-Server im Log auftauchen.

In etwa:
Code Auswählen

grep "CCU" fhem-xxxxx.log

2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

aski71

#1341
14 März 2017, 21:03:41
Zitat von: zap am 14 März 2017, 19:48:11
Wenn Du z.B. ein HMCCUDEV mit dem Namen "mein_dev" definiert hast, mach mal beispielhaft für eines dieser Devices:
Code Auswählen

list mein_dev


Außerdem bitte alle "HMCCU" und "CCURPC" Meldungen, die während dem Start von FHEM bzw. dem RPC-Server im Log auftauchen.

In etwa:
Code Auswählen

grep "CCU" fhem-xxxxx.log


Gerne.

Device:
Code Auswählen
Internals:
   CHANGED
   DEF        W-Vitrine
   IODev      ccu2
   NAME       Vitrine
   NR         45
   STATE      on
   TYPE       HMCCUDEV
   ccuaddr    LEQ1068630
   ccudevstate Active
   ccuif      BidCos-RF
   ccuname    W-Vitrine
   ccutype    HM-LC-Sw1-Pl-2
   channels   2
   statevals  devstate|on|off
   Readings:
     2017-03-14 19:07:52   1.STATE         on
     2017-03-14 21:02:09   hmstate         on
     2017-03-14 19:07:52   state           on
   Hmccu:
     Dp:
       0.aes_key:
         VAL        1
       0.config_pending:
         VAL        false
       0.dutycycle:
         VAL        false
       0.lowbat:
         VAL        false
       0.rssi_device:
         VAL        1
       0.rssi_peer:
         VAL        69
       0.sticky_unreach:
         VAL        false
       0.unreach:
         VAL        false
       1.inhibit:
         VAL        false
       1.state:
         VAL        1
       1.working:
         VAL        0
Attributes:
   IODev      ccu2
   ccureadingfilter (STATE|ON_TIME)
   ccureadings 1
   devStateIcon on:vitrine_on@green off:vitrine_off@black Initialized:10px-kreis-gelb
   event-on-change-reading .*
   fp_Home3D  339,315,0, ,Vitrine
   group      Lichter
   room       HomekitLights,Wohnzimmer
   statechannel 1
   statevals  on:true,off:false
   substitute STATE!true:on,false:off,1:on,0:off
   userattr   lightSceneParamsToSave lightSceneRestoreOnlyIfChanged:1,0


Logs:
Code Auswählen
2017.03.11 16:07:27 1: UPD FHEM/88_HMCCU.pm
2017.03.11 16:07:28 1: UPD FHEM/HMCCUConf.pm
2017.03.11 16:07:30 1:   - bugfix:  88_HMCCU: Fixed toggle bug
2017.03.11 16:07:30 1:   - update:  88_HMCCU: added tracing for RPC set config
2017.03.11 16:09:41 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.11 16:09:41 0: HMCCU: Stopping RPC server CB2001 with PID 9491
2017.03.11 16:09:41 0: CCURPC: CB2001 Server loop terminated
2017.03.11 16:09:41 2: CCURPC: Eventcount DD = 0
2017.03.11 16:09:41 2: CCURPC: Eventcount EV = 453494
2017.03.11 16:09:41 2: CCURPC: Eventcount EX = 1
2017.03.11 16:09:41 2: CCURPC: Eventcount IN = 1
2017.03.11 16:09:41 2: CCURPC: Eventcount ND = 208
2017.03.11 16:09:41 2: CCURPC: Eventcount RA = 0
2017.03.11 16:09:41 2: CCURPC: Eventcount RD = 0
2017.03.11 16:09:41 2: CCURPC: Eventcount SL = 1
2017.03.11 16:09:41 2: CCURPC: Eventcount ST = 906
2017.03.11 16:09:41 2: CCURPC: Eventcount UD = 0
2017.03.11 16:09:41 2: CCURPC: Eventcount total = 454611
2017.03.11 16:09:41 2: CCURPC: Eventcount writeerror = 0
2017.03.11 16:09:59 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2017.03.11 16:10:11 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.11 16:10:11 0: HMCCU: Child process for server CB2001 started with PID 9352
2017.03.11 16:10:11 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.11 16:10:11 0: CCURPC: Initializing RPC server CB2001
2017.03.11 16:10:12 0: CCURPC: Callback server created listening on port 7411
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for events
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for new devices
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for list devices
2017.03.11 16:10:12 1: CCURPC: CB2001 Adding callback for event query
2017.03.11 16:10:12 0: CCURPC: CB2001 Entering server loop
2017.03.11 16:10:14 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.11 16:10:21 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.11 16:10:21 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.11 16:10:22 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.11 16:10:23 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.11 16:10:25 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.11 16:10:28 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.11 16:10:28 1: HMCCU: All RPC servers running
2017.03.11 16:38:52 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 16:44:08 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.11 16:44:08 0: HMCCU: Stopping RPC server CB2001 with PID 9352
2017.03.11 16:44:08 0: CCURPC: CB2001 Server loop terminated
2017.03.11 16:44:08 2: CCURPC: Eventcount DD = 0
2017.03.11 16:44:08 2: CCURPC: Eventcount EV = 573
2017.03.11 16:44:08 2: CCURPC: Eventcount EX = 1
2017.03.11 16:44:08 2: CCURPC: Eventcount IN = 1
2017.03.11 16:44:08 2: CCURPC: Eventcount ND = 208
2017.03.11 16:44:08 2: CCURPC: Eventcount RA = 0
2017.03.11 16:44:08 2: CCURPC: Eventcount RD = 0
2017.03.11 16:44:08 2: CCURPC: Eventcount SL = 1
2017.03.11 16:44:08 2: CCURPC: Eventcount ST = 1
2017.03.11 16:44:08 2: CCURPC: Eventcount UD = 0
2017.03.11 16:44:08 2: CCURPC: Eventcount total = 785
2017.03.11 16:44:08 2: CCURPC: Eventcount writeerror = 0
2017.03.11 16:44:44 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2017.03.11 16:44:56 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.11 16:44:56 0: HMCCU: Child process for server CB2001 started with PID 9484
2017.03.11 16:44:56 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.11 16:44:56 0: CCURPC: Initializing RPC server CB2001
2017.03.11 16:44:56 0: CCURPC: Callback server created listening on port 7411
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for events
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for new devices
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for list devices
2017.03.11 16:44:56 1: CCURPC: CB2001 Adding callback for event query
2017.03.11 16:44:56 0: CCURPC: CB2001 Entering server loop
2017.03.11 16:44:59 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.11 16:45:06 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.11 16:45:06 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.11 16:45:07 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.11 16:45:08 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.11 16:45:10 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.11 16:45:12 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.11 16:45:12 1: HMCCU: All RPC servers running
2017.03.11 16:46:46 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.11 16:46:46 0: HMCCU: Stopping RPC server CB2001 with PID 9484
2017.03.11 16:46:46 0: CCURPC: CB2001 Server loop terminated
2017.03.11 16:46:46 2: CCURPC: Eventcount DD = 0
2017.03.11 16:46:46 2: CCURPC: Eventcount EV = 30
2017.03.11 16:46:46 2: CCURPC: Eventcount EX = 1
2017.03.11 16:46:46 2: CCURPC: Eventcount IN = 1
2017.03.11 16:46:46 2: CCURPC: Eventcount ND = 208
2017.03.11 16:46:46 2: CCURPC: Eventcount RA = 0
2017.03.11 16:46:46 2: CCURPC: Eventcount RD = 0
2017.03.11 16:46:46 2: CCURPC: Eventcount SL = 1
2017.03.11 16:46:46 2: CCURPC: Eventcount UD = 0
2017.03.11 16:46:46 2: CCURPC: Eventcount total = 241
2017.03.11 16:46:46 2: CCURPC: Eventcount writeerror = 0
2017.03.11 16:46:48 0: HMCCU: Received EX event. RPC server CB2001 terminated.
2017.03.11 16:46:48 0: HMCCU: RPC server(s) with PID(s) 9484 shut down. f=1
2017.03.11 16:46:48 2: HMCCU: Eventcount DD = 0
2017.03.11 16:46:48 2: HMCCU: Eventcount EV = 30
2017.03.11 16:46:48 2: HMCCU: Eventcount EX = 1
2017.03.11 16:46:48 2: HMCCU: Eventcount IN = 1
2017.03.11 16:46:48 2: HMCCU: Eventcount ND = 208
2017.03.11 16:46:48 2: HMCCU: Eventcount RA = 0
2017.03.11 16:46:48 2: HMCCU: Eventcount RD = 0
2017.03.11 16:46:48 2: HMCCU: Eventcount SL = 1
2017.03.11 16:46:48 2: HMCCU: Eventcount ST = 0
2017.03.11 16:46:48 2: HMCCU: Eventcount UD = 0
2017.03.11 16:46:48 2: HMCCU: Eventcount total = 241
2017.03.11 16:46:48 0: HMCCU: Periodical check found no RPC Servers
2017.03.11 16:46:48 0: HMCCU: All RPC servers stopped
2017.03.11 16:47:03 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.11 16:47:03 0: HMCCU: Child process for server CB2001 started with PID 9491
2017.03.11 16:47:03 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.11 16:47:03 0: CCURPC: Initializing RPC server CB2001
2017.03.11 16:47:04 0: CCURPC: Callback server created listening on port 7411
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for events
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for new devices
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for list devices
2017.03.11 16:47:04 1: CCURPC: CB2001 Adding callback for event query
2017.03.11 16:47:04 0: CCURPC: CB2001 Entering server loop
2017.03.11 16:47:06 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.11 16:47:13 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.11 16:47:13 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.11 16:47:14 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.11 16:47:15 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.11 16:47:17 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.11 16:47:19 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.11 16:47:19 1: HMCCU: All RPC servers running
2017.03.11 16:56:24 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.11 16:56:24 0: HMCCU: Stopping RPC server CB2001 with PID 9491
2017.03.11 16:56:24 0: CCURPC: CB2001 Server loop terminated
2017.03.11 16:56:24 2: CCURPC: Eventcount DD = 0
2017.03.11 16:56:24 2: CCURPC: Eventcount EV = 114
2017.03.11 16:56:24 2: CCURPC: Eventcount EX = 1
2017.03.11 16:56:24 2: CCURPC: Eventcount IN = 1
2017.03.11 16:56:24 2: CCURPC: Eventcount ND = 208
2017.03.11 16:56:24 2: CCURPC: Eventcount RA = 0
2017.03.11 16:56:24 2: CCURPC: Eventcount RD = 0
2017.03.11 16:56:24 2: CCURPC: Eventcount SL = 1
2017.03.11 16:56:24 2: CCURPC: Eventcount UD = 0
2017.03.11 16:56:24 2: CCURPC: Eventcount total = 325
2017.03.11 16:56:24 2: CCURPC: Eventcount writeerror = 0
2017.03.11 16:56:59 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2017.03.11 16:57:11 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.11 16:57:11 0: HMCCU: Child process for server CB2001 started with PID 9553
2017.03.11 16:57:11 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.11 16:57:11 0: CCURPC: Initializing RPC server CB2001
2017.03.11 16:57:11 0: CCURPC: Callback server created listening on port 7411
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for events
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for new devices
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for list devices
2017.03.11 16:57:11 1: CCURPC: CB2001 Adding callback for event query
2017.03.11 16:57:11 0: CCURPC: CB2001 Entering server loop
2017.03.11 16:57:14 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.11 16:57:21 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.11 16:57:21 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.11 16:57:22 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.11 16:57:23 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.11 16:57:25 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.11 16:57:28 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.11 16:57:28 1: HMCCU: All RPC servers running
2017.03.11 17:17:29 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.11 17:17:29 0: HMCCU: Stopping RPC server CB2001 with PID 9553
2017.03.11 17:17:29 0: CCURPC: CB2001 Server loop terminated
2017.03.11 17:17:29 2: CCURPC: Eventcount DD = 0
2017.03.11 17:17:29 2: CCURPC: Eventcount EV = 319
2017.03.11 17:17:29 2: CCURPC: Eventcount EX = 1
2017.03.11 17:17:29 2: CCURPC: Eventcount IN = 1
2017.03.11 17:17:29 2: CCURPC: Eventcount ND = 208
2017.03.11 17:17:29 2: CCURPC: Eventcount RA = 0
2017.03.11 17:17:29 2: CCURPC: Eventcount RD = 0
2017.03.11 17:17:29 2: CCURPC: Eventcount SL = 1
2017.03.11 17:17:29 2: CCURPC: Eventcount UD = 0
2017.03.11 17:17:29 2: CCURPC: Eventcount total = 530
2017.03.11 17:17:29 2: CCURPC: Eventcount writeerror = 0
2017.03.11 17:18:06 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2017.03.11 17:18:18 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.11 17:18:18 0: HMCCU: Child process for server CB2001 started with PID 9759
2017.03.11 17:18:18 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.11 17:18:18 0: CCURPC: Initializing RPC server CB2001
2017.03.11 17:18:18 0: CCURPC: Callback server created listening on port 7411
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for events
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for new devices
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for list devices
2017.03.11 17:18:18 1: CCURPC: CB2001 Adding callback for event query
2017.03.11 17:18:18 0: CCURPC: CB2001 Entering server loop
2017.03.11 17:18:21 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.11 17:18:28 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.11 17:18:28 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.11 17:18:28 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.11 17:18:30 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.11 17:18:31 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.11 17:18:33 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.11 17:18:33 1: HMCCU: All RPC servers running
2017.03.11 17:44:35 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 18:07:39 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 18:34:07 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 19:07:47 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 19:43:18 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 20:18:57 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 20:53:17 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 21:28:49 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 22:06:09 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 22:41:46 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 23:16:13 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.11 23:50:08 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 00:25:41 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 00:57:03 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 01:14:19 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 01:44:12 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 02:20:05 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 02:54:43 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 03:30:13 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 04:05:33 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 04:40:42 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 05:15:29 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 05:51:31 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 06:25:59 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 07:00:37 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 07:37:10 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 08:12:38 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 08:44:46 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 09:03:07 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 09:31:57 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 10:02:54 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 10:36:46 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 11:08:40 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 11:36:15 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 12:04:59 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 12:36:24 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 13:05:38 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 13:35:54 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 14:06:28 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 14:34:48 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 15:02:18 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 15:34:50 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 16:07:18 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 16:40:32 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 17:08:28 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 17:31:57 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 17:59:34 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 18:30:28 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 19:05:17 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 19:36:25 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 20:11:48 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 20:32:23 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.12 20:32:23 0: HMCCU: Stopping RPC server CB2001 with PID 9759
2017.03.12 20:32:23 0: CCURPC: CB2001 Server loop terminated
2017.03.12 20:32:23 2: CCURPC: Eventcount DD = 0
2017.03.12 20:32:23 2: CCURPC: Eventcount EV = 25978
2017.03.12 20:32:23 2: CCURPC: Eventcount EX = 1
2017.03.12 20:32:23 2: CCURPC: Eventcount IN = 1
2017.03.12 20:32:23 2: CCURPC: Eventcount ND = 208
2017.03.12 20:32:23 2: CCURPC: Eventcount RA = 0
2017.03.12 20:32:23 2: CCURPC: Eventcount RD = 0
2017.03.12 20:32:23 2: CCURPC: Eventcount SL = 1
2017.03.12 20:32:23 2: CCURPC: Eventcount ST = 51
2017.03.12 20:32:23 2: CCURPC: Eventcount UD = 0
2017.03.12 20:32:23 2: CCURPC: Eventcount total = 26240
2017.03.12 20:32:23 2: CCURPC: Eventcount writeerror = 0
2017.03.12 20:33:19 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2017.03.12 20:33:31 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.12 20:33:31 0: HMCCU: Child process for server CB2001 started with PID 16197
2017.03.12 20:33:31 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.12 20:33:31 0: CCURPC: Initializing RPC server CB2001
2017.03.12 20:33:31 0: CCURPC: Callback server created listening on port 7411
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for events
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for new devices
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for list devices
2017.03.12 20:33:31 1: CCURPC: CB2001 Adding callback for event query
2017.03.12 20:33:31 0: CCURPC: CB2001 Entering server loop
2017.03.12 20:33:34 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.12 20:33:41 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.12 20:33:44 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.12 20:33:44 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.12 20:33:45 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.12 20:33:47 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.12 20:33:49 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.12 20:33:49 1: HMCCU: All RPC servers running
2017.03.12 20:57:53 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 21:32:05 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 22:07:02 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 22:37:01 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 23:05:35 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.12 23:38:38 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 00:14:19 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 00:48:53 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 01:24:04 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 01:59:33 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 02:36:51 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 03:13:00 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 03:45:57 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 04:22:00 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 04:57:19 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 05:32:28 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 06:08:05 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 06:43:16 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 07:02:53 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 07:26:08 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 07:51:10 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 08:26:38 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 08:57:04 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 09:17:51 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 09:47:58 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 10:17:37 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 10:50:06 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 11:24:20 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 11:52:29 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 12:29:56 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 13:06:14 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 13:43:24 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 14:17:01 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 14:53:01 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 15:29:47 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 16:02:04 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 16:38:13 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 17:12:30 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 17:46:18 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 18:20:17 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 18:48:17 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 19:10:17 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 19:34:21 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 20:03:20 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 20:39:08 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 21:13:20 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 21:47:16 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 22:12:26 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 22:33:40 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 23:03:43 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.13 23:38:27 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 00:12:09 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 00:48:07 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 01:19:40 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 01:53:08 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 02:28:26 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 03:04:10 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 03:41:08 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 04:16:28 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 04:52:42 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 05:28:00 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 06:03:12 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 06:39:31 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 07:01:02 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 07:26:10 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 07:55:17 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 08:28:18 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 08:59:48 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 09:35:27 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 10:10:56 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 10:46:14 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 11:21:39 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 11:57:30 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 12:32:51 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 13:05:11 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 13:40:29 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 14:15:37 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 14:42:41 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 15:04:52 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 15:37:24 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 16:10:26 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 16:39:43 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 17:03:40 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 17:33:24 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 18:07:54 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 18:40:15 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 19:04:35 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 19:32:45 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 20:05:22 3: CCURPC: CB2001 Received 500 events from CCU since last check
2017.03.14 20:37:54 3: CCURPC: CB2001 Received 500 events from CCU since last check

zap

#1342
15 März 2017, 07:19:58
Auf den ersten Blick sieht das alles gut aus, bis auf die Meldungen, dass seit xx Sekunden keine Events von der CCU kamen.

Vorschlag: RPC Server stoppen, CCU neu starten, RPC Server starten
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

aski71

#1343
15 März 2017, 09:29:27
Zitat von: zap am 15 März 2017, 07:19:58
Auf den ersten Blick sieht das alles gut aus, bis auf die Meldungen, dass seit xx Sekunden keine Events von der CCU kamen.

Vorschlag: RPC Server stoppen, CCU neu starten, RPC Server starten

Gerade probiert:
set ccu2 rpcserver off
Dann: CCU neu gestartet
Dann: set ccu2 rpcserver on

Ergebnis:
Alle Geräte bleiben auf "Activated".

Nach einem get update auf die ccu2 geht's wieder.

Logging:
Code Auswählen
2017.03.15 09:06:10 1: HMCCU: Deregistering RPC server http://192.168.2.67:7411/fh2001 at http://192.168.2.63:2001/
2017.03.15 09:06:10 0: HMCCU: Stopping RPC server CB2001 with PID 16197
2017.03.15 09:06:10 0: CCURPC: CB2001 Server loop terminated
2017.03.15 09:06:11 2: CCURPC: Eventcount DD = 0
2017.03.15 09:06:11 2: CCURPC: Eventcount EV = 56460
2017.03.15 09:06:11 2: CCURPC: Eventcount EX = 1
2017.03.15 09:06:11 2: CCURPC: Eventcount IN = 1
2017.03.15 09:06:11 2: CCURPC: Eventcount ND = 208
2017.03.15 09:06:11 2: CCURPC: Eventcount RA = 0
2017.03.15 09:06:11 2: CCURPC: Eventcount RD = 0
2017.03.15 09:06:11 2: CCURPC: Eventcount SL = 1
2017.03.15 09:06:11 2: CCURPC: Eventcount ST = 112
2017.03.15 09:06:11 2: CCURPC: Eventcount UD = 0
2017.03.15 09:06:11 2: CCURPC: Eventcount total = 56783
2017.03.15 09:06:11 2: CCURPC: Eventcount writeerror = 0
2017.03.15 09:06:13 0: HMCCU: Received EX event. RPC server CB2001 terminated.
2017.03.15 09:06:13 0: HMCCU: RPC server(s) with PID(s) 16197 shut down. f=1
2017.03.15 09:06:13 2: HMCCU: Eventcount DD = 0
2017.03.15 09:06:13 2: HMCCU: Eventcount EV = 56459
2017.03.15 09:06:13 2: HMCCU: Eventcount EX = 1
2017.03.15 09:06:13 2: HMCCU: Eventcount IN = 1
2017.03.15 09:06:13 2: HMCCU: Eventcount ND = 208
2017.03.15 09:06:13 2: HMCCU: Eventcount RA = 0
2017.03.15 09:06:13 2: HMCCU: Eventcount RD = 0
2017.03.15 09:06:13 2: HMCCU: Eventcount SL = 1
2017.03.15 09:06:13 2: HMCCU: Eventcount ST = 112
2017.03.15 09:06:13 2: HMCCU: Eventcount UD = 0
2017.03.15 09:06:13 2: HMCCU: Eventcount total = 56782
2017.03.15 09:06:13 0: HMCCU: Periodical check found no RPC Servers
2017.03.15 09:06:13 0: HMCCU: All RPC servers stopped
2017.03.15 09:27:10 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2017.03.15 09:27:10 0: HMCCU: Child process for server CB2001 started with PID 29799
2017.03.15 09:27:10 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2017.03.15 09:27:10 0: CCURPC: Initializing RPC server CB2001
2017.03.15 09:27:10 0: RPC server(s) starting
2017.03.15 09:27:10 0: CCURPC: Callback server created listening on port 7411
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for events
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for new devices
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for deleted devices
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for modified devices
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for replaced devices
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for readded devices
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for list devices
2017.03.15 09:27:10 1: CCURPC: CB2001 Adding callback for event query
2017.03.15 09:27:10 0: CCURPC: CB2001 Entering server loop
2017.03.15 09:27:13 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2017.03.15 09:27:22 1: HMCCU: Registering callback http://192.168.2.67:7411/fh2001 with ID CB2001 at http://192.168.2.63:2001/
2017.03.15 09:27:22 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.15 09:27:22 1: HMCCU: RPC callback with URL http://192.168.2.67:7411/fh2001 initialized
2017.03.15 09:27:24 2: CCURPC: CB2001 NewDevice received 208 device specifications
2017.03.15 09:27:25 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2017.03.15 09:27:26 2: 41
2017.03.15 09:27:28 2: HMCCU: Updated devices. Success=39 Failed=0
2017.03.15 09:27:28 1: HMCCU: All RPC servers running
2017.03.15 09:27:28 1: PERL WARNING: Argument "Activated" isn't numeric in multiplication (*) at (eval 73346) line 1.
2017.03.15 09:27:28 1: PERL WARNING: Argument "Activated" isn't numeric in sprintf at (eval 73348) line 1.
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 41
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 100
2017.03.15 09:27:35 2: 60
2017.03.15 09:27:35 2: 74
2017.03.15 09:27:35 2: 78
2017.03.15 09:27:35 2: 22
2017.03.15 09:27:51 1: PERL WARNING: Argument "Activated" isn't numeric in multiplication (*) at (eval 73451) line 1.
2017.03.15 09:28:07 1: PERL WARNING: Argument "Activated" isn't numeric in multiplication (*) at (eval 73456) line 1.
2017.03.15 09:28:23 1: PERL WARNING: Argument "Activated" isn't numeric in multiplication (*) at (eval 73461) line 1.
2017.03.15 09:28:33 1: PERL WARNING: Argument "Activated" isn't numeric in multiplication (*) at (eval 73467) line 1.

Chris8888

#1344
15 März 2017, 15:06:44 Letzte Bearbeitung: 15 März 2017, 15:09:41 von Chris8888
Hallo,

für die CC2 ist jetzt die 2.27.7. draussen.
http://www.eq-3.de/Downloads/Software/HM-CCU2-Firmware_Updates/HM-CCU2-2.27.7/HM-CCU2-Changelog.2.27.7.pdf

Hat das schon jemand ausprobiert? Gibt es Probleme mit der Abnindung über HMCCU?

Es scheint ja auch eine neue Doku (V2.15) für die RPC-Schnittstelle zu geben...
http://www.eq-3.de/Downloads/eq3/download%20bereich/hm_web_ui_doku/HM_XmlRpc_API.pdf

VG
Christian
FHEM 6.0 auf einem PI4 mit div. Homematic-Komponenten, Alexa, Tablet-UI und Homebridge...und läuft einfach. Erweitert mit CCU3 und Homematic-IP...und läuft immer noch.

zap

#1345
15 März 2017, 16:59:29
@chris8888: meistens ist es besser, die Reaktionen im Homematic Forum auf eine neue Firmware abzuwarten. Wenn dort keine Probleme gemeldet werden, kann man es mal installieren (Backup nicht vergessen).
Schwerpunkt der Changes scheint HM-IP zu sein. Möglicherweise wird das eine oder andere Problem gelöst, das mancher hier mit HM-IP Thermostaten hatte.

@aski71: langsam gehen mir die Ideen aus. Zumal Du der einzige mit diesen Problemen bist. Sind alle Versionen der Module aktuell (Einfach mal die Dateien öffnen und in den Header schauen)?

88_HMCCU.pm >= 3.9.007
88_HMCCUDEV.pm 3.9
88_HMCCUCHN.pm 3.9.003

Das "Argument Activated isn't numeric" ist mir auch ein Rätsel. Hast Du userreadings definiert?
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

aski71

#1346
15 März 2017, 17:36:03
Zitat von: zap am 15 März 2017, 16:59:29
@chris8888: meistens ist es besser, die Reaktionen im Homematic Forum auf eine neue Firmware abzuwarten. Wenn dort keine Probleme gemeldet werden, kann man es mal installieren (Backup nicht vergessen).
Schwerpunkt der Changes scheint HM-IP zu sein. Möglicherweise wird das eine oder andere Problem gelöst, das mancher hier mit HM-IP Thermostaten hatte.

@aski71: langsam gehen mir die Ideen aus. Zumal Du der einzige mit diesen Problemen bist. Sind alle Versionen der Module aktuell (Einfach mal die Dateien öffnen und in den Header schauen)?

88_HMCCU.pm >= 3.9.007
88_HMCCUDEV.pm 3.9
88_HMCCUCHN.pm 3.9.003

Das "Argument Activated isn't numeric" ist mir auch ein Rätsel. Hast Du userreadings definiert?

User-Readings: Ich glaube ja. Für Batterie oder so hatte ich mal was gemacht. Weiß das aber nicht mehr auswendig.

Module aktuell: Habe heute nochmal einen Update Check gemacht. Da gibt's inzwischen wieder neuere Module. Komme aber gerade nicht zum Updaten. Mache ich nochmal und schaue, was dann passiert.

Chris8888

#1347
15 März 2017, 17:53:58
Hallo,

ich habe das Update auf 2.27.7 einfach mal eingespielt. Auf den ersten Blick scheint alles wie vorher zu funktionieren.
Keine besonderen Log-Einträge, die RPC-Schnittstelle scheint in beide Richtungen zu laufen.

Ich beobachte das mal...

VG
Christian
FHEM 6.0 auf einem PI4 mit div. Homematic-Komponenten, Alexa, Tablet-UI und Homebridge...und läuft einfach. Erweitert mit CCU3 und Homematic-IP...und läuft immer noch.

aski71

#1348
17 März 2017, 13:33:54
Zitat von: aski71 am 15 März 2017, 17:36:03
User-Readings: Ich glaube ja. Für Batterie oder so hatte ich mal was gemacht. Weiß das aber nicht mehr auswendig.

Module aktuell: Habe heute nochmal einen Update Check gemacht. Da gibt's inzwischen wieder neuere Module. Komme aber gerade nicht zum Updaten. Mache ich nochmal und schaue, was dann passiert.

Heute auf die neuesten Module upgedated: Jetzt geht's wieder!
Danke!

mrfloppy

#1349
21 März 2017, 16:09:52
Ich habe nach dem Update auf die CCU2 2.27 Firmware ein Mega Probleme.
Ich wollte ein paar weitere Devices in fhem anlegen.
Bei einem get devicelist schmierte mir fhem irgendwie ab.
Der RPC wurde beendet.
Durch einen Neustart hat Fhem gemeint es gibt kein IODEV für die Homematic Geräte
und hat die bereits vorhandenen aus der fhem.cfg rausgelöscht.
Dieses Verhalten war auch nach mehreren Starts der Fall.
Update der CCU2 retour auf 2.25 und jetzt geht wieder alles wie vorher.

Bin nur ich alleine mit dem Fehler? Oder habe ich wo einen Blödsinn gemacht?

LG Thomas
RaspiMatic, RFXtrx433 E USB, Div. Thermostate, CUL433, Fhemduino, Signalduino, Temp/luftfeuchesensoren,Fensterkontakte,Intertechno Schalter,....... HM-IP
Drucken
Nach oben Seiten 1 ... 88 89 90 91 92 ... 103
Benutzer-Aktionen