HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar

zap · 18 Juli 2018, 11:03:05

Führe mal bitte im FHEM Eingabefenster folgendes aus:

{IsDisabled("HM_HomeMatic__Zentrale2__HMCCU")}

Da müsste eine Zahl von 0-3 ausgegeben werden.

cho · 18 Juli 2018, 11:09:43

3

zap · 18 Juli 2018, 11:15:10

Zitat von: cho am 18 Juli 2018, 11:09:43
3

Das ist das Problem. Bei der Zuordnung des IO Device prüft FHEM, ob das IO Device disabled ist. Das ist nicht nur dann der Fall, wenn disabled=1 ist, sondern auch, wenn der STATE oder das Reading state auf "inactive" steht (müsste bei dir so sein). Leider nutzt HMCCU inactive als Status des RPC Servers. Je nachdem, welchen Status HM_HomeMatic__Zentrale2__HMCCU gerade hat, funktioniert die Definition des VirtualDevice oder nicht.

Was mich wundert: im d_rpcVirtualDevice müsste entweder das Internal IODevMissing auf 1 stehen oder im Logfile müsste es eine Meldung geben "No I/O device found for ..."

cho · 18 Juli 2018, 11:56:46

stimmt, das I/O Device ist inactive:

Code Auswählen


Internals:
   CCUNum     1
   CFGFN      ./myconfig/cfg/HM_HomeMatic.cfg
   CHANGED    
   Clients    :HMCCUDEV:HMCCUCHN:HMCCURPC:HMCCURPCPROC:
   DEF        192.168.1.38
   NAME       HM_HomeMatic__Zentrale2__HMCCU
   NOTIFYDEV  global,TYPE=(HMCCU|HMCCUDEV|HMCCUCHN)
   NR         789
   NTFY_ORDER 50-HM_HomeMatic__Zentrale2__HMCCU
   RPCState   inactive
   STATE      inactive
   TYPE       HMCCU
   ccuaddr    BidCoS-RF
   ccuchannels 232
   ccudevices 41
   ccuif      BidCos-RF
   ccuinterfaces VirtualDevices,BidCos-RF,HmIP-RF
   ccuip      192.168.1.38
   ccuname    HM-RCV-50_BidCoS-RF
   ccustate   active
   ccutype    CCU2
   host       192.168.1.38
   version    4.2.008
   READINGS:
     2018-07-18 09:23:25   rpcstate        inactive
     2018-07-18 09:23:42   state           OK
   hmccu:
     evtime     0
     evtimeout  0
     rpccount   0
     rpcports   2001,9292
     updatetime 0
     adr:
...
       INT0000001:
         addtype    dev
         channels   3
         chndir     0
         interface  VirtualDevices
         name       HM-CC-VG-1_INT0000001
         type       HM-CC-VG-1
         valid      1
       INT0000001:0:
         addtype    chn
         channels   1
         chndir     0
         name       HM-CC-VG-1_INT0000001:0
         valid      1
       INT0000001:1:
         addtype    chn
         channels   1
         chndir     0
         name       HM-CC-VG-1_INT0000001:1
         valid      1
...
     ifports:
       2001       BidCos-RF
       2010       HmIP-RF
       9292       VirtualDevices
     interfaces:
       BidCos-RF:
         device     HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC
         flags      forceASCII
         host       192.168.1.38
         manager    HMCCU
         port       2001
         prot       http
         state      running
         type       A
         url        http://192.168.1.38:2001
       HmIP-RF:
         flags      _
         host       192.168.1.38
         manager    null
         port       2010
         prot       http
         state      inactive
         type       A
         url        http://192.168.1.38:2010
       VirtualDevices:
         device     d_rpcVirtualDevices
         flags      _
         host       192.168.1.38
         manager    HMCCU
         port       9292
         prot       http
         state      inactive
         type       A
         url        http://192.168.1.38:9292/groups
     rpc:
Attributes:
   alias      HM HomeMatic
   ccudef-readingformat name
   ccuflags   procrpc,nohmstate
   event-on-change-reading rpcstate
   group      - Zentrale
   room       HM HomeMatic
   rpcinterfaces BidCos-RF,VirtualDevices
   rpcport    2001,9292
   rpcqueue   /tmp/ccuqueue
   rpcserver  on
   stateFormat rpcstate

im d_rpcVirtualDevices gibt es kein Internal IODevMissing:

Code Auswählen


Internals:
   CCUNum     1
   DEF        iodev=HM_HomeMatic__Zentrale2__HMCCU VirtualDevices
   NAME       d_rpcVirtualDevices
   NR         2193
   RPCPID     0
   RPCState   inactive
   STATE      inactive/OK
   TYPE       HMCCURPCPROC
   ccuip      192.168.1.38
   ccustate   active
   ccutype    CCU2
   host       192.168.1.38
   rpcid      001024
   rpcinterface VirtualDevices
   rpcip      192.168.1.38
   rpcport    9292
   version    1.0.006
   READINGS:
     2018-07-18 09:24:08   rpcstate        inactive
     2018-07-18 09:24:08   state           OK
   hmccu:
     defaultaddr 192.168.1.24
     evtime     0
     localaddr  192.168.1.24
     rpcstarttime 0
     rpc:
       cbport     14702
       clkey      
       evtime     1531898622
       pid        
       state      inactive
       sumdelay   0
       rec:
         DD         0
         EV         0
         EX         0
         IN         0
         ND         0
         RA         0
         RD         0
         SL         1
         TO         0
         UD         0
       snd:
         DD         0
         EV         0
         EX         0
         IN         0
         ND         0
         RA         0
         RD         0
         SL         0
         TO         0
         UD         0
Attributes:
   group      - Zentrale
   room       HM HomeMatic
   stateFormat rpcstate/state
   verbose    2

und im Logfile gibt es keine Meldung "No I/O device found for ..."

Code Auswählen


2018.07.18 09:23:21 1: Including fhem.cfg
...
2018.07.18 09:23:25 1: HMCCU: Device HM_HomeMatic__Zentrale2__HMCCU. Initialized version 4.2.008
2018.07.18 09:23:25 1: HMCCU: Read 41 devices with 232 channels from CCU 192.168.1.38
2018.07.18 09:23:25 1: HMCCU: Read 3 interfaces from CCU 192.168.1.38
2018.07.18 09:23:25 1: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] Initialized version 1.0.006 for interface BidCos-RF with I/O device HM_HomeMatic__Zentrale2__HMCCU
...
2018.07.18 09:23:28 1: HMCCURPCPROC: [d_rpcVirtualDevices] Initialized version 1.0.006 for interface VirtualDevices with I/O device HM_HomeMatic__Zentrale2__HMCCU
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4326, <$fh> line 40.
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value in string ne at ./FHEM/88_HMCCU.pm line 2247, <$fh> line 40.
2018.07.18 09:23:28 1: ERROR: empty name in readingsBeginUpdate
2018.07.18 09:23:28 1: stacktrace:
2018.07.18 09:23:28 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.18 09:23:28 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:28 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:28 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (667)
2018.07.18 09:23:28 1:     main::HMCCURPCPROC_ResetRPCState    called by ./FHEM/88_HMCCURPCPROC.pm (307)
2018.07.18 09:23:28 1:     main::HMCCURPCPROC_Define           called by fhem.pl (3584)
2018.07.18 09:23:28 1:     main::CallFn                        called by fhem.pl (1974)
2018.07.18 09:23:28 1:     main::CommandDefine                 called by fhem.pl (1209)
2018.07.18 09:23:28 1:     main::AnalyzeCommand                called by fhem.pl (1059)
2018.07.18 09:23:28 1:     main::AnalyzeCommandChain           called by fhem.pl (1347)
2018.07.18 09:23:28 1:     main::CommandInclude                called by fhem.pl (577)
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at fhem.pl line 4566, <$fh> line 40.
2018.07.18 09:23:28 1: readingsUpdate(,rpcstate,inactive) missed to call readingsBeginUpdate first.
2018.07.18 09:23:28 1: stacktrace:
2018.07.18 09:23:28 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.18 09:23:28 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:28 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:28 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (667)
2018.07.18 09:23:28 1:     main::HMCCURPCPROC_ResetRPCState    called by ./FHEM/88_HMCCURPCPROC.pm (307)
2018.07.18 09:23:28 1:     main::HMCCURPCPROC_Define           called by fhem.pl (3584)
2018.07.18 09:23:28 1:     main::CallFn                        called by fhem.pl (1974)
2018.07.18 09:23:28 1:     main::CommandDefine                 called by fhem.pl (1209)
2018.07.18 09:23:28 1:     main::AnalyzeCommand                called by fhem.pl (1059)
2018.07.18 09:23:28 1:     main::AnalyzeCommandChain           called by fhem.pl (1347)
2018.07.18 09:23:28 1:     main::CommandInclude                called by fhem.pl (577)
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value $type in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162, <$fh> line 40.
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162, <$fh> line 40.
2018.07.18 09:23:28 1: : [] All RPC servers inactive
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value $dev in hash element at fhem.pl line 3456, <$fh> line 40.
2018.07.18 09:23:28 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/88_HMCCU.pm line 2220, <$fh> line 40.
...
2018.07.18 09:23:29 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
...
2018.07.18 09:23:31 0: Featurelevel: 5.8
2018.07.18 09:23:31 0: Server started with 365 defined entities (fhem.pl:16866/2018-06-14 perl:5.024001 os:linux user:fhem pid:13550)
2018.07.18 09:23:32 1: PERL WARNING: Argument ".*" isn't numeric in numeric lt (<) at fhem.pl line 4610.
...
2018.07.18 09:23:41 2: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] RPC server process started for interface BidCos-RF with PID=13563
2018.07.18 09:23:41 2: CCURPC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] Initializing RPC server CB2001001024 for interface BidCos-RF
2018.07.18 09:23:41 1: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] RPC server starting
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4326.
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $interface in concatenation (.) or string at ./FHEM/88_HMCCURPCPROC.pm line 1206.
2018.07.18 09:23:41 2: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server process started for interface  with PID=13564
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $iface in concatenation (.) or string at ./FHEM/88_HMCCURPCPROC.pm line 1626.
2018.07.18 09:23:41 2: CCURPC: [d_rpcVirtualDevices] Initializing RPC server CB9292001024 for interface 
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $prot in string eq at ./FHEM/88_HMCCURPCPROC.pm line 1031.
2018.07.18 09:23:41 1: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server starting
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value in string ne at ./FHEM/88_HMCCU.pm line 2247.
2018.07.18 09:23:41 1: ERROR: empty name in readingsBeginUpdate
2018.07.18 09:23:41 1: stacktrace:
2018.07.18 09:23:41 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.18 09:23:41 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:41 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:41 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1228)
2018.07.18 09:23:41 1:     main::HMCCURPCPROC_StartRPCServer   called by ./FHEM/88_HMCCU.pm (3190)
2018.07.18 09:23:41 1:     main::HMCCU_StartExtRPCServer       called by fhem.pl (3127)
2018.07.18 09:23:41 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at fhem.pl line 4566.
2018.07.18 09:23:41 1: readingsUpdate(,rpcstate,starting) missed to call readingsBeginUpdate first.
2018.07.18 09:23:41 1: stacktrace:
2018.07.18 09:23:41 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.18 09:23:41 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:41 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:41 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1228)
2018.07.18 09:23:41 1:     main::HMCCURPCPROC_StartRPCServer   called by ./FHEM/88_HMCCU.pm (3190)
2018.07.18 09:23:41 1:     main::HMCCU_StartExtRPCServer       called by fhem.pl (3127)
2018.07.18 09:23:41 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $dev in hash element at fhem.pl line 3456.
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $type in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162.
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162.
2018.07.18 09:23:41 1: : [] All RPC servers starting
2018.07.18 09:23:41 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/88_HMCCU.pm line 2220.
2018.07.18 09:23:41 2: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] Callback server CB2001001024 created. Listening on port 7411
2018.07.18 09:23:41 2: CCURPC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] CB2001001024 accepting connections. PID=13563
2018.07.18 09:23:41 2: HMCCURPCPROC: [d_rpcVirtualDevices] Callback server CB9292001024 created. Listening on port 14702
2018.07.18 09:23:41 2: CCURPC: [d_rpcVirtualDevices] CB9292001024 accepting connections. PID=13564
2018.07.18 09:23:42 2: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server CB9292001024 enters server loop
2018.07.18 09:23:42 1: ERROR: empty name in readingsBeginUpdate
2018.07.18 09:23:42 1: stacktrace:
2018.07.18 09:23:42 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.18 09:23:42 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:42 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (773)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.18 09:23:42 1:     main::CallFn                        called by fhem.pl (723)
2018.07.18 09:23:42 1: readingsUpdate(,rpcstate,working) missed to call readingsBeginUpdate first.
2018.07.18 09:23:42 1: stacktrace:
2018.07.18 09:23:42 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.18 09:23:42 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:42 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (773)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.18 09:23:42 1:     main::CallFn                        called by fhem.pl (723)
2018.07.18 09:23:42 1: : [] All RPC servers working
2018.07.18 09:23:42 1: HMCCURPCPROC: [d_rpcVirtualDevices] Can't get RPC parameters for ID CB9292001024
2018.07.18 09:23:42 1: ERROR: empty name in readingsBeginUpdate
2018.07.18 09:23:42 1: stacktrace:
2018.07.18 09:23:42 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.18 09:23:42 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:42 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (776)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.18 09:23:42 1:     main::CallFn                        called by fhem.pl (723)
2018.07.18 09:23:42 1: readingsUpdate(,rpcstate,error) missed to call readingsBeginUpdate first.
2018.07.18 09:23:42 1: stacktrace:
2018.07.18 09:23:42 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.18 09:23:42 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:23:42 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (776)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.18 09:23:42 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.18 09:23:42 1:     main::CallFn                        called by fhem.pl (723)
2018.07.18 09:23:42 1: : [] All RPC servers error
2018.07.18 09:23:42 2: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] RPC server CB2001001024 enters server loop
2018.07.18 09:23:42 2: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] Registering callback http://192.168.1.24:7411/fh2001 of type A with ID CB2001001024 at http://192.168.1.38:2001
2018.07.18 09:23:42 1: HMCCURPCPROC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] RPC server CB2001001024 running
2018.07.18 09:23:43 2: CCURPC: [HM_HomeMatic__rpcBidCos_RF__HMCCURPCPROC] CB2001001024 NewDevice received 233 device and channel specifications
2018.07.18 09:24:06 2: HMCCURPCPROC: [d_rpcVirtualDevices] Checking if RPC server process is running
2018.07.18 09:24:06 1: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server process not running. Cleaning up
2018.07.18 09:24:06 1: HMCCURPCPROC: [d_rpcVirtualDevices] Housekeeping called. Cleaning up RPC environment
2018.07.18 09:24:06 2: HMCCURPCPROC: [d_rpcVirtualDevices] Sending signal INT to RPC server process CB9292001024 with PID=13564
2018.07.18 09:24:06 1: ERROR: empty name in readingsBeginUpdate
2018.07.18 09:24:06 1: stacktrace:
2018.07.18 09:24:06 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.18 09:24:06 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:24:06 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1328)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_TerminateProcess called by ./FHEM/88_HMCCURPCPROC.pm (1433)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.18 09:24:06 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.18 09:24:06 1: readingsUpdate(,rpcstate,stopping) missed to call readingsBeginUpdate first.
2018.07.18 09:24:06 1: stacktrace:
2018.07.18 09:24:06 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.18 09:24:06 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:24:06 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1328)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_TerminateProcess called by ./FHEM/88_HMCCURPCPROC.pm (1433)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.18 09:24:06 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.18 09:24:06 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.18 09:24:06 1: : [] All RPC servers stopping
2018.07.18 09:24:06 2: CCURPC: [d_rpcVirtualDevices] CB9292001024 received signal INT
2018.07.18 09:24:06 1: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 stopped handling connections. PID=13564
2018.07.18 09:24:06 1: PERL WARNING: Use of uninitialized value $prot in string eq at ./FHEM/88_HMCCURPCPROC.pm line 1709.
2018.07.18 09:24:06 2: CCURPC: [d_rpcVirtualDevices] Number of I/O errors = 0
2018.07.18 09:24:08 2: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server process CB9292001024 deleted
2018.07.18 09:24:08 1: ERROR: empty name in readingsBeginUpdate
2018.07.18 09:24:08 1: stacktrace:
2018.07.18 09:24:08 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.18 09:24:08 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:24:08 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1363)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_CleanupProcess   called by ./FHEM/88_HMCCURPCPROC.pm (1276)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_RPCServerStopped called by ./FHEM/88_HMCCURPCPROC.pm (1436)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.18 09:24:08 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.18 09:24:08 1: readingsUpdate(,rpcstate,inactive) missed to call readingsBeginUpdate first.
2018.07.18 09:24:08 1: stacktrace:
2018.07.18 09:24:08 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.18 09:24:08 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.18 09:24:08 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1363)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_CleanupProcess   called by ./FHEM/88_HMCCURPCPROC.pm (1276)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_RPCServerStopped called by ./FHEM/88_HMCCURPCPROC.pm (1436)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.18 09:24:08 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.18 09:24:08 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.18 09:24:08 1: : [] All RPC servers inactive
2018.07.18 09:24:08 2: HMCCURPCPROC: [d_rpcVirtualDevices] Stop I/O handling

zap · 18 Juli 2018, 12:41:35

Abhilfe wird vermutlich schaffen, wenn Du das Attribut stateFormate im IO Device auf "rpcstate/state" setzt.

Oder du wartest auf das nächste Update. Ich muss mir aber erst mal einen einigermaßen schlauen Weg überlegen, wie ich FHEM hier austricksen kann.

Die Fehlermeldung "No I/O device" kommt nur bei Verbose >= 3. Daher siehst Du die nicht.

cho · 18 Juli 2018, 12:56:33

Ich habe das Attribut stateFormate jetzt auf "rpcstate/state" gesetzt und damit funktioniert es.

Vielen Dank noch einmal für Deine Hilfe!!!

cho · 18 Juli 2018, 13:23:18

übrigens funktioniert es so auch mit
define ... HMCCURPCPROC 192.168.1.38 VirtualDevices
also ohne iodev= Parameter

zap · 20 Juli 2018, 09:09:41

In fhem.pl wurde inzwischen die entsprechende Funktion angepasst. Nach dem nächsten FHEM Update sollte also auch Deine bisherige stateFormat Angabe funktionieren.

Chris8888 · 26 Juli 2018, 00:04:51

Hallo zusammen,

ich habe heute versucht einen neuen HmIP-SLO (Lichtsensor) in Betrieb zu nehmen. Die CCU2 erkennt ihn und ich kann ihn ganz normal anlernen, konfigurieren etc.
Über HMCCU will sich das Gerät nicht anlegen lassen.
Ein get devicelist create HM_Lichtsensor f=HmIP-Lichtsensor
führt zu einem:
Read 30 devices with 220 channels from CCU
Created 0 client devices

Das Gerät gibt es nicht...selbst mit duplicates wird nichts angelegt.

Das Gerät kann ich mir aber per DeviceInfo anzeigen lassen:

Code Auswählen

CHN 000D58A98FACC8:0 HmIP-Lichtsensor:0
  DPT {b} HmIP-RF.000D58A98FACC8:0.CONFIG_PENDING = false [RE]
  DPT {b} HmIP-RF.000D58A98FACC8:0.DUTY_CYCLE = false [RE]
  DPT {b} HmIP-RF.000D58A98FACC8:0.INSTALL_TEST = false [RW]
  DPT {b} HmIP-RF.000D58A98FACC8:0.LOW_BAT = false [RE]
  DPT {f} HmIP-RF.000D58A98FACC8:0.OPERATING_VOLTAGE = 3.100000 [RE]
  DPT {i} HmIP-RF.000D58A98FACC8:0.OPERATING_VOLTAGE_STATUS = 0 [RE]
  DPT {n} HmIP-RF.000D58A98FACC8:0.RSSI_DEVICE = 203 [RE]
  DPT {n} HmIP-RF.000D58A98FACC8:0.RSSI_PEER = 0 [RE]
  DPT {b} HmIP-RF.000D58A98FACC8:0.UNREACH = false [RE]
  DPT {b} HmIP-RF.000D58A98FACC8:0.UPDATE_PENDING = false [RE]
CHN 000D58A98FACC8:1 HmIP-SLO 000D58A98FACC8:1
  DPT {f} HmIP-RF.000D58A98FACC8:1.AVERAGE_ILLUMINATION = 0.280000 [RE]
  DPT {i} HmIP-RF.000D58A98FACC8:1.AVERAGE_ILLUMINATION_STATUS = 0 [RE]
  DPT {f} HmIP-RF.000D58A98FACC8:1.CURRENT_ILLUMINATION = 0.280000 [RE]
  DPT {i} HmIP-RF.000D58A98FACC8:1.CURRENT_ILLUMINATION_STATUS = 0 [RE]
  DPT {f} HmIP-RF.000D58A98FACC8:1.HIGHEST_ILLUMINATION = 0.290000 [RE]
  DPT {i} HmIP-RF.000D58A98FACC8:1.HIGHEST_ILLUMINATION_STATUS = 0 [RE]
  DPT {f} HmIP-RF.000D58A98FACC8:1.LOWEST_ILLUMINATION = 0.280000 [RE]
  DPT {i} HmIP-RF.000D58A98FACC8:1.LOWEST_ILLUMINATION_STATUS = 0 [RE]

Im Log ist nichts ....

Wo ist mein Denkfehler? Liegt es am Device? An HMCCU (4.2.008)? An mir?

Danke für einen Schubser!

Viele Grüße
Christian

zap · 26 Juli 2018, 07:02:53

Der heißt tatsächlich HmIP-Lichtsensor in der CCU? Aus der Deviceinfo kann ich nur die Namen der Kanäle entnehmen.

Funktioniert ein

define HM_Lichtsensor HMCCUDEV HmIP-Lichtsensor

?

Chris8888 · 26 Juli 2018, 09:15:10

Guten Morgen,

ja, so heißt er. Sieht man auch immer am Namen von Kanal 0: CHN 000D58A98FACC8:0 HmIP-Lichtsensor:0

Sehr seltsam. Per Define hat es sofort geklappt.

Muss ich das verstehen?

Und noch 2 Fragen:
Ich dachte immer "Stripnumber 0" schneidet alle Nachkommastellen ab.
Aktuell werden - zumindest bei diesem Sensor - alle 5 Nachkommastellen angezeigt.
Bei "Stripnumber 1" wird korrekterweise genau 1 Stelle angezeigt.

Als CCUREADINGFILTER "^AVERAGE_ILLUMINATION" zeigt beide Readings (1.AVERAGE_ILLUMINATION und 1.AVERAGE_ILLUMINATION_STATUS). Soweit korrekt.
Als CCUREADINGFILTER "1.AVERAGE_ILLUMINATION" werden aber beide Readings rausgefiltert..jetzt bin ich verwirrt.

Ist bei mir ein Geist eingezogen?

zap · 26 Juli 2018, 10:31:26

Zitat von: Chris8888 am 26 Juli 2018, 09:15:10
Ich dachte immer "Stripnumber 0" schneidet alle Nachkommastellen ab.
Aktuell werden - zumindest bei diesem Sensor - alle 5 Nachkommastellen angezeigt.
Bei "Stripnumber 1" wird korrekterweise genau 1 Stelle angezeigt.

0 bedeutet: Lass alles so wie es ist.
Mit -0 wird auf 0 Nachkommastellen gerundet.

Ich werde das aber anpassen:

0 = Schneide alle Nachkommastellen ab
-0 = Runde auf 0 Nachkommastellen

Chris8888 · 26 Juli 2018, 22:25:48

wieder was gelernt. Danke!

Hast du zu dem Rest eine Idee?

VG
Christian

Chris8888 · 27 Juli 2018, 14:14:52

Hallo Zap,

ich habe aktuell ein paar seltsame Anzeigen über HMCCU und dem neuen IP-Lichtsensor.

ccureadingsname mit "1.CURRENT_ILLUMINATION:+luminosity" erzeugt doch ein zusätzliches Reading "luminosity" mit dem gleichen Inhalt wie 1.CURRENT_ILLUMINATION?

Aus dem Eventmonitor:

Code Auswählen

2018-07-27 14:04:02 HMCCUDEV HM_Lichtsensor 1.CURRENT_ILLUMINATION: 37370
2018-07-27 14:04:02 HMCCUDEV HM_Lichtsensor luminosity: 37370
2018-07-27 14:04:02 HMCCUDEV HM_Lichtsensor control: 37370
2018-07-27 14:04:02 HMCCUDEV HM_Lichtsensor 37370
2018-07-27 14:04:02 HMCCUDEV HM_Lichtsensor luminosity: 0
2018-07-27 14:04:02 HMCCUDEV HM_Lichtsensor hmstate: 37370

Bei jedem 2-3 Event ist das Reading luminosity aber "0", anstatt (wie hier) 37370.

2 Minuten später:

Code Auswählen

2018-07-27 14:06:52 HMCCUDEV HM_Lichtsensor 1.CURRENT_ILLUMINATION: 37830
2018-07-27 14:06:52 HMCCUDEV HM_Lichtsensor luminosity: 37830
2018-07-27 14:06:52 HMCCUDEV HM_Lichtsensor control: 37830
2018-07-27 14:06:52 HMCCUDEV HM_Lichtsensor 37830
2018-07-27 14:06:52 HMCCUDEV HM_Lichtsensor hmstate: 37830

Alles richtig.

Das verstehe ich nicht.

Weiterhin bekomme ich den Readingfilter nicht hin.
Als CCUREADINGFILTER "^AVERAGE_ILLUMINATION" zeigt beide Readings (1.AVERAGE_ILLUMINATION und 1.AVERAGE_ILLUMINATION_STATUS). Soweit korrekt.
Als CCUREADINGFILTER "1.AVERAGE_ILLUMINATION" werden aber beide Readings rausgefiltert....
Ich möchte gerne das Reading "1.AVERAGE_ILLUMINATION" anzeigen, das Reading "1.AVERAGE_ILLUMINATION_STATUS" rausfiltern.

Wo liegt mein Fehler?

Ist mir zur zu warm?

Danke vorab für einen Tipp!

Viele Grüße
Christian

zap · 27 Juli 2018, 17:34:02

Mir ist auch warm

Möglicherweise gibts einen Bug wenn man die Kanalnummer im Readingfilter angibt.

Workaround im konkreten Fall: ^AVERAGE_ILLUMINATION$

Muss das mal testen mit der Kanalnummer. Bin gerade von ner Radtour gekommen bei gefühlt 50 Grad und kaum in der Lage, das Tablet zu halten geschweige denn am PC irgendwas auszuprobieren $:-\$