Autor Thema: HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar  (Gelesen 8691 mal)

Offline bruece-lee

  • Jr. Member
  • **
  • Beiträge: 79
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #135 am: 12 Juli 2018, 19:04:02 »
Hallo zap!

Danke für die Erweiterung bei ccuscaleval! Funktioniert prima!

 :)

Gruß, Bruece-Lee

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #136 am: 13 Juli 2018, 13:48:01 »
Ein Hinweis an alle, die noch den externen RPC Server vom Typ HMCCURPC benutzen: Dieser wird mit der nächsten Version von HMCCU (voraussichtlich Ende nächster Woche) deaktiviert.

Beim Neustart von FHEM wird das Device vom Typ HMCCURPC deaktiviert und durch Devices vom Typ HMCCURPCPROC ersetzt.

Wer noch HMCCURPC nutzt (ccuflags im IO-Device = extrpc), kann das vorab schon auf HMCCURPCPROC umstellen, indem er das Attribut ccuflags im IO-Device auf procrpc setzt. Beim nächsten Start des RPC Servers werden dann die RPC Server Devices automatisch angelegt. Danach kann das alte HMCCURPC Device gelöscht werden.

Der interne RPC Server wird noch eine Weile unterstützt, da ich nicht zu viel auf einmal ändern möchte.
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #137 am: 16 Juli 2018, 18:52:59 »
Hallo zap,
ich versuche gerade, den RPC Server von extprc auf procprc umzustellen. Die 2 neuen Devices für BidCos-RF und VirtualDevices wurden angelegt und das alte Device habe ich gelöscht.
Während BidCos-RF nun running/OK anzeigt, zeigt VirtualDevices inactive/OK an und ich habe im Log Fehler gefunden.
Was mache ich falsch?

...
2018.07.16 18:15:53 1: HMCCU: Device HM_HomeMatic__Zentrale2__HMCCU. Initialized version 4.2.008
2018.07.16 18:15:53 1: HMCCU: Read 41 devices with 232 channels from CCU 192.168.1.38
2018.07.16 18:15:53 1: HMCCU: Read 3 interfaces from CCU 192.168.1.38
...
2018.07.16 18:15:56 1: HMCCURPCPROC: [d_rpcBidCos_RF] Initialized version 1.0.006 for interface BidCos-RF with I/O device HM_HomeMatic__Zentrale2__HMCCU
2018.07.16 18:15:56 1: HMCCURPCPROC: [d_rpcVirtualDevices] Initialized version 1.0.006 for interface VirtualDevices with I/O device HM_HomeMatic__Zentrale2__HMCCU
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4326, <$fh> line 40.
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value in string ne at ./FHEM/88_HMCCU.pm line 2247, <$fh> line 40.
2018.07.16 18:15:56 1: ERROR: empty name in readingsBeginUpdate
2018.07.16 18:15:56 1: stacktrace:
2018.07.16 18:15:56 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.16 18:15:56 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:15:56 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:15:56 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (667)
2018.07.16 18:15:56 1:     main::HMCCURPCPROC_ResetRPCState    called by ./FHEM/88_HMCCURPCPROC.pm (307)
2018.07.16 18:15:56 1:     main::HMCCURPCPROC_Define           called by fhem.pl (3584)
2018.07.16 18:15:56 1:     main::CallFn                        called by fhem.pl (1974)
2018.07.16 18:15:56 1:     main::CommandDefine                 called by fhem.pl (1209)
2018.07.16 18:15:56 1:     main::AnalyzeCommand                called by fhem.pl (1059)
2018.07.16 18:15:56 1:     main::AnalyzeCommandChain           called by fhem.pl (1347)
2018.07.16 18:15:56 1:     main::CommandInclude                called by fhem.pl (577)
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at fhem.pl line 4566, <$fh> line 40.
2018.07.16 18:15:56 1: readingsUpdate(,rpcstate,inactive) missed to call readingsBeginUpdate first.
2018.07.16 18:15:56 1: stacktrace:
2018.07.16 18:15:56 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.16 18:15:56 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:15:56 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:15:56 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (667)
2018.07.16 18:15:56 1:     main::HMCCURPCPROC_ResetRPCState    called by ./FHEM/88_HMCCURPCPROC.pm (307)
2018.07.16 18:15:56 1:     main::HMCCURPCPROC_Define           called by fhem.pl (3584)
2018.07.16 18:15:56 1:     main::CallFn                        called by fhem.pl (1974)
2018.07.16 18:15:56 1:     main::CommandDefine                 called by fhem.pl (1209)
2018.07.16 18:15:56 1:     main::AnalyzeCommand                called by fhem.pl (1059)
2018.07.16 18:15:56 1:     main::AnalyzeCommandChain           called by fhem.pl (1347)
2018.07.16 18:15:56 1:     main::CommandInclude                called by fhem.pl (577)
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value $type in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162, <$fh> line 40.
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162, <$fh> line 40.
2018.07.16 18:15:56 1: : [] All RPC servers inactive
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value $dev in hash element at fhem.pl line 3456, <$fh> line 40.
2018.07.16 18:15:56 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/88_HMCCU.pm line 2220, <$fh> line 40.
...
2018.07.16 18:15:57 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
...
2018.07.16 18:15:59 0: Featurelevel: 5.8
2018.07.16 18:15:59 0: Server started with 365 defined entities (fhem.pl:16866/2018-06-14 perl:5.024001 os:linux user:fhem pid:27815)
2018.07.16 18:15:59 1: PERL WARNING: Argument ".*" isn't numeric in numeric lt (<) at fhem.pl line 4610.
...
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server process started for interface BidCos-RF with PID=27828
2018.07.16 18:16:09 2: CCURPC: [d_rpcBidCos_RF] Initializing RPC server CB2001001024 for interface BidCos-RF
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Set state to busy
2018.07.16 18:16:09 1: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server starting
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Set rpcstate to starting
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4326.
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $interface in concatenation (.) or string at ./FHEM/88_HMCCURPCPROC.pm line 1206.
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server process started for interface  with PID=27829
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $iface in concatenation (.) or string at ./FHEM/88_HMCCURPCPROC.pm line 1626.
2018.07.16 18:16:09 2: CCURPC: [d_rpcVirtualDevices] Initializing RPC server CB9292001024 for interface
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $prot in string eq at ./FHEM/88_HMCCURPCPROC.pm line 1031.
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set state to busy
2018.07.16 18:16:09 1: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server starting
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set rpcstate to starting
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value in string ne at ./FHEM/88_HMCCU.pm line 2247.
2018.07.16 18:16:09 1: ERROR: empty name in readingsBeginUpdate
2018.07.16 18:16:09 1: stacktrace:
2018.07.16 18:16:09 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.16 18:16:09 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:09 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1228)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_StartRPCServer   called by ./FHEM/88_HMCCU.pm (3190)
2018.07.16 18:16:09 1:     main::HMCCU_StartExtRPCServer       called by fhem.pl (3127)
2018.07.16 18:16:09 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at fhem.pl line 4566.
2018.07.16 18:16:09 1: readingsUpdate(,rpcstate,starting) missed to call readingsBeginUpdate first.
2018.07.16 18:16:09 1: stacktrace:
2018.07.16 18:16:09 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.16 18:16:09 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:09 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1228)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_StartRPCServer   called by ./FHEM/88_HMCCU.pm (3190)
2018.07.16 18:16:09 1:     main::HMCCU_StartExtRPCServer       called by fhem.pl (3127)
2018.07.16 18:16:09 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $dev in hash element at fhem.pl line 3456.
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $type in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162.
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 2162.
2018.07.16 18:16:09 1: : [] All RPC servers starting
2018.07.16 18:16:09 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/88_HMCCU.pm line 2220.
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcBidCos_RF] Callback server CB2001001024 created. Listening on port 7411
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for events for server CB2001001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for new devices for server CB2001001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for deleted devices for server CB2001001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for modified devices for server CB2001001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for replaced devices for server CB2001001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for readded devices for server CB2001001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Adding callback for list devices for server CB2001001024
2018.07.16 18:16:09 2: CCURPC: [d_rpcBidCos_RF] CB2001001024 accepting connections. PID=27828
2018.07.16 18:16:09 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server CB2001001024 enters server loop
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Set rpcstate to working
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcBidCos_RF] Registering callback http://192.168.1.24:7411/fh2001 of type A with ID CB2001001024 at http://192.168.1.38:2001
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Send ASCII RPC request init to http://192.168.1.38:2001
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcVirtualDevices] Callback server CB9292001024 created. Listening on port 14702
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for events for server CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for new devices for server CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for deleted devices for server CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for modified devices for server CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for replaced devices for server CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for readded devices for server CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Adding callback for list devices for server CB9292001024
2018.07.16 18:16:09 2: CCURPC: [d_rpcVirtualDevices] CB9292001024 accepting connections. PID=27829
2018.07.16 18:16:09 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:09 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:09 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:09 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:09 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:09 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:09 1: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server CB2001001024 running
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Set rpcstate to running
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Set state to OK
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 1 events read: no data
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Read called
2018.07.16 18:16:09 2: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server CB9292001024 enters server loop
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set rpcstate to working
2018.07.16 18:16:09 1: ERROR: empty name in readingsBeginUpdate
2018.07.16 18:16:09 1: stacktrace:
2018.07.16 18:16:09 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.16 18:16:09 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:09 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (773)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.16 18:16:09 1:     main::CallFn                        called by fhem.pl (723)
2018.07.16 18:16:09 1: readingsUpdate(,rpcstate,working) missed to call readingsBeginUpdate first.
2018.07.16 18:16:09 1: stacktrace:
2018.07.16 18:16:09 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.16 18:16:09 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:09 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (773)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.16 18:16:09 1:     main::CallFn                        called by fhem.pl (723)
2018.07.16 18:16:09 1: : [] All RPC servers working
2018.07.16 18:16:09 1: HMCCURPCPROC: [d_rpcVirtualDevices] Can't get RPC parameters for ID CB9292001024
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set rpcstate to error
2018.07.16 18:16:09 1: ERROR: empty name in readingsBeginUpdate
2018.07.16 18:16:09 1: stacktrace:
2018.07.16 18:16:09 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.16 18:16:09 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:09 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (776)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.16 18:16:09 1:     main::CallFn                        called by fhem.pl (723)
2018.07.16 18:16:09 1: readingsUpdate(,rpcstate,error) missed to call readingsBeginUpdate first.
2018.07.16 18:16:09 1: stacktrace:
2018.07.16 18:16:09 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.16 18:16:09 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:09 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (776)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_ProcessEvent     called by ./FHEM/88_HMCCURPCPROC.pm (531)
2018.07.16 18:16:09 1:     main::HMCCURPCPROC_Read             called by fhem.pl (3584)
2018.07.16 18:16:09 1:     main::CallFn                        called by fhem.pl (723)
2018.07.16 18:16:09 1: : [] All RPC servers error
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Read stopped after 1 events read: no data
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcVirtualDevices] Read finished
2018.07.16 18:16:09 2: CCURPC: [d_rpcBidCos_RF] CB2001001024 NewDevice received 233 device and channel specifications
2018.07.16 18:16:09 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 sending data to FHEM
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:09 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:09 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 70 events read: no data
2018.07.16 18:16:09 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 sending data to FHEM
2018.07.16 18:16:09 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:09 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 79 events read: no data
2018.07.16 18:16:10 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:10 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:10 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 sending data to FHEM
2018.07.16 18:16:10 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:10 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:10 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 70 events read: no data
2018.07.16 18:16:10 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:11 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:11 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 sending data to FHEM
2018.07.16 18:16:11 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:11 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:11 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 23 events read: no data
2018.07.16 18:16:11 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:12 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:12 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:13 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:13 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:14 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:14 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:15 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:15 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:16 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:16 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:17 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:17 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:18 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:18 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:18 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:18 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:19 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 2 events read: no data
2018.07.16 18:16:19 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:19 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:19 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 14 events read: no data
2018.07.16 18:16:19 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:19 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:20 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:20 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:21 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:21 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:21 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:21 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:21 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 1 events read: no data
2018.07.16 18:16:21 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:21 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:21 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 15 events read: no data
2018.07.16 18:16:21 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:22 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:22 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:23 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:23 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:24 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:24 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:25 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:25 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:25 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 1 events read: no data
2018.07.16 18:16:25 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:25 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:25 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 15 events read: no data
2018.07.16 18:16:25 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:25 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:26 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:26 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:27 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:27 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:27 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:27 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 4 events read: no data
2018.07.16 18:16:27 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:27 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:27 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 2 events read: no data
2018.07.16 18:16:27 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:27 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:28 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:28 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:29 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:29 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:30 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:30 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:30 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:30 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:30 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 6 events read: no data
2018.07.16 18:16:30 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
2018.07.16 18:16:31 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:31 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:32 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:32 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:33 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:33 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:34 2: HMCCURPCPROC: [d_rpcVirtualDevices] Checking if RPC server process is running
2018.07.16 18:16:34 1: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server process not running. Cleaning up
2018.07.16 18:16:34 1: HMCCURPCPROC: [d_rpcVirtualDevices] Housekeeping called. Cleaning up RPC environment
2018.07.16 18:16:34 5: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 accepting connections
2018.07.16 18:16:34 2: HMCCURPCPROC: [d_rpcVirtualDevices] Sending signal INT to RPC server process CB9292001024 with PID=27829
2018.07.16 18:16:34 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set rpcstate to stopping
2018.07.16 18:16:34 1: ERROR: empty name in readingsBeginUpdate
2018.07.16 18:16:34 1: stacktrace:
2018.07.16 18:16:34 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.16 18:16:34 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:34 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1328)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_TerminateProcess called by ./FHEM/88_HMCCURPCPROC.pm (1433)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.16 18:16:34 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.16 18:16:34 1: readingsUpdate(,rpcstate,stopping) missed to call readingsBeginUpdate first.
2018.07.16 18:16:34 1: stacktrace:
2018.07.16 18:16:34 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.16 18:16:34 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:34 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1328)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_TerminateProcess called by ./FHEM/88_HMCCURPCPROC.pm (1433)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.16 18:16:34 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.16 18:16:34 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.16 18:16:34 1: : [] All RPC servers stopping
2018.07.16 18:16:34 2: CCURPC: [d_rpcVirtualDevices] CB9292001024 received signal INT
2018.07.16 18:16:34 1: CCURPC: [d_rpcVirtualDevices] RPC server CB9292001024 stopped handling connections. PID=27829
2018.07.16 18:16:34 1: PERL WARNING: Use of uninitialized value $prot in string eq at ./FHEM/88_HMCCURPCPROC.pm line 1709.
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] Event statistics = 1|0|0|0|0|0|0|0|0|1|0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = EV: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = ND: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = DD: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = RD: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = RA: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = UD: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = IN: 0
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = EX: 1
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = SL: 1
2018.07.16 18:16:34 4: CCURPC: [d_rpcVirtualDevices] CB9292001024 event type = TO: 0
2018.07.16 18:16:34 2: CCURPC: [d_rpcVirtualDevices] Number of I/O errors = 0
2018.07.16 18:16:34 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:34 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:35 5: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 accepting connections
2018.07.16 18:16:36 4: CCURPC: [d_rpcBidCos_RF] RPC server CB2001001024 processing request
2018.07.16 18:16:36 2: HMCCURPCPROC: [d_rpcVirtualDevices] RPC server process CB9292001024 deleted
2018.07.16 18:16:36 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set rpcstate to inactive
2018.07.16 18:16:36 1: ERROR: empty name in readingsBeginUpdate
2018.07.16 18:16:36 1: stacktrace:
2018.07.16 18:16:36 1:     main::readingsBeginUpdate           called by fhem.pl (4711)
2018.07.16 18:16:36 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:36 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1363)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_CleanupProcess   called by ./FHEM/88_HMCCURPCPROC.pm (1276)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_RPCServerStopped called by ./FHEM/88_HMCCURPCPROC.pm (1436)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.16 18:16:36 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.16 18:16:36 1: readingsUpdate(,rpcstate,inactive) missed to call readingsBeginUpdate first.
2018.07.16 18:16:36 1: stacktrace:
2018.07.16 18:16:36 1:     main::readingsBulkUpdate            called by fhem.pl (4712)
2018.07.16 18:16:36 1:     main::readingsSingleUpdate          called by ./FHEM/88_HMCCU.pm (2249)
2018.07.16 18:16:36 1:     main::HMCCU_SetRPCState             called by ./FHEM/88_HMCCURPCPROC.pm (645)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_SetRPCState      called by ./FHEM/88_HMCCURPCPROC.pm (1363)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_CleanupProcess   called by ./FHEM/88_HMCCURPCPROC.pm (1276)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_RPCServerStopped called by ./FHEM/88_HMCCURPCPROC.pm (1436)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_Housekeeping     called by ./FHEM/88_HMCCURPCPROC.pm (1410)
2018.07.16 18:16:36 1:     main::HMCCURPCPROC_IsRPCServerRunning called by fhem.pl (3127)
2018.07.16 18:16:36 1:     main::HandleTimeout                 called by fhem.pl (646)
2018.07.16 18:16:36 1: : [] All RPC servers inactive
2018.07.16 18:16:36 2: HMCCURPCPROC: [d_rpcVirtualDevices] Stop I/O handling
2018.07.16 18:16:36 3: HMCCURPCPROC: [d_rpcVirtualDevices] Close child socket
2018.07.16 18:16:36 3: HMCCURPCPROC: [d_rpcVirtualDevices] Close parent socket
2018.07.16 18:16:36 4: HMCCURPCPROC: [d_rpcVirtualDevices] Reset RPC state
2018.07.16 18:16:36 4: HMCCURPCPROC: [d_rpcVirtualDevices] Set state to OK
2018.07.16 18:16:36 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read called
2018.07.16 18:16:36 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read stopped after 9 events read: no data
2018.07.16 18:16:36 4: HMCCURPCPROC: [d_rpcBidCos_RF] Read finished
...

Vielen Dank für Deine Hilfe im Voraus und Grüße
Christian

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #138 am: 16 Juli 2018, 21:48:35 »
Hast Du die Config mal gespeichert und FHEM neu gestartet? Irgendwie scheint da ein Device nicht korrekt initialisiert / definiert zu sein. Der Fehler kommt daher, dass wohl $hash->{TYPE} nicht definiert ist. Das müsste es aber sein bei korrekt definierten Devices.

Wichtig ist, dass in der fhem.cfg das IO Device (HMCCU) vor den beiden HMCCURPCPROC Devices steht. Das sollte so sein, wenn man das einmal speichert und die fhem.cfg nicht manuell editiert.

« Letzte Änderung: 16 Juli 2018, 21:51:35 von zap »
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #139 am: 16 Juli 2018, 21:55:01 »
Config habe ich gespeichert und FHEM neu gestartet.
Welche Devices meinst Du mit "nicht korrekt initialisiert / definiert"? Die IO und RPCPROC Devices?

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #140 am: 16 Juli 2018, 22:37:20 »
Ehrlich gesagt, keine Ahnung was da schief läuft.

Du kannst mal folgendes versuchen:
- Bei gestopptem RPC Server die beiden HMCCURPCPROC Devices löschen
- Im IO Device das Attribut rpcserver auf "off" (Autostart RPC Server aus)
- Dann die Config speichern
- FHEM neu starten
- RPC Server manuell starten (im IO device set rpcserver on) => HMCCURPCPROC Devices werden neu angelegt.
- Config speichern
- FHEM neu starten
- RPC Server starten
- Wenn alles gut geht, kannst Du rpcserver wieder auf on setzen
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #141 am: 16 Juli 2018, 23:27:34 »
Hallo zap,

ich habe jetzt alles noch einmal durchprobiert, einschließlich alte cfg zurück kopieren und noch einmal von vorne anfangen - leider ohne Erfolg. Die Reihenfolge der Devices in der cfg stimmt auch.

Bei allen Versuchen läuft und funktioniert der BidCos-RF RPC immer und der VirtualDevices RPC eben nicht.

Das einzige was mir noch Einfällt, ist, dass ich anstelle einer echten CCU2 eine virtuelle piVCCU auf dem Raspberry laufen habe. Die hat aber mit dem extrpc die ganze Zeit problemlos funktioniert.

Ich bleibe jetzt erst einmal beim extrpc. Vielleicht fällt Dir ja doch noch etwas ein. Gib einfach Bescheid, dann probiere ich es aus.

Viele Grüße
Christian

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #142 am: Gestern um 11:30:50 »
Hast du denn in der CCU eine oder mehrere virtuelle Gruppen definiert?
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #143 am: Gestern um 11:35:36 »
Ich habe mehrere Gruppen definiert.

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #144 am: Gestern um 18:26:16 »
Hast Du mehrere HMCCU Devices definiert? Das Device für den RPC Server (Virtual) scheint kein I/O Device zu haben. Daher das Problem.

« Letzte Änderung: Gestern um 18:32:06 von zap »
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #145 am: Gestern um 22:02:39 »
Hallo zap,

ich habe nur ein HMCCU Device. Was meinst Du mit "I/O Device"? Ist das ein Attribut?

Vor der Umstellung mit extrpc:

define HM_HomeMatic__Zentrale2__HMCCU HMCCU 192.168.1.38
attr HM_HomeMatic__Zentrale2__HMCCU alias HM HomeMatic
attr HM_HomeMatic__Zentrale2__HMCCU ccudef-readingformat name
attr HM_HomeMatic__Zentrale2__HMCCU ccuflags extrpc,nohmstate
attr HM_HomeMatic__Zentrale2__HMCCU event-on-change-reading rpcstate
attr HM_HomeMatic__Zentrale2__HMCCU group - Zentrale
attr HM_HomeMatic__Zentrale2__HMCCU room HM HomeMatic
attr HM_HomeMatic__Zentrale2__HMCCU rpcinterfaces BidCos-RF,VirtualDevices
attr HM_HomeMatic__Zentrale2__HMCCU rpcport 2001,9292
attr HM_HomeMatic__Zentrale2__HMCCU rpcqueue /tmp/ccuqueue
attr HM_HomeMatic__Zentrale2__HMCCU rpcserver on
attr HM_HomeMatic__Zentrale2__HMCCU stateFormat rpcstate

define HM_HomeMatic__Zentrale2__HMCCU_rpc HMCCURPC 192.168.1.38
attr HM_HomeMatic__Zentrale2__HMCCU_rpc alias HM HomeMatic RPC
attr HM_HomeMatic__Zentrale2__HMCCU_rpc event-on-change-reading rpcstate
attr HM_HomeMatic__Zentrale2__HMCCU_rpc group - Zentrale
attr HM_HomeMatic__Zentrale2__HMCCU_rpc room HM HomeMatic
attr HM_HomeMatic__Zentrale2__HMCCU_rpc stateFormat rpcstate
attr HM_HomeMatic__Zentrale2__HMCCU_rpc verbose 2

Und nach der Umstellung auf procrpc:

define HM_HomeMatic__Zentrale2__HMCCU HMCCU 192.168.1.38
attr HM_HomeMatic__Zentrale2__HMCCU alias HM HomeMatic
attr HM_HomeMatic__Zentrale2__HMCCU ccudef-readingformat name
attr HM_HomeMatic__Zentrale2__HMCCU ccuflags procrpc,nohmstate
attr HM_HomeMatic__Zentrale2__HMCCU event-on-change-reading rpcstate
attr HM_HomeMatic__Zentrale2__HMCCU group - Zentrale
attr HM_HomeMatic__Zentrale2__HMCCU room HM HomeMatic
attr HM_HomeMatic__Zentrale2__HMCCU rpcinterfaces BidCos-RF,VirtualDevices
attr HM_HomeMatic__Zentrale2__HMCCU rpcport 2001,9292
attr HM_HomeMatic__Zentrale2__HMCCU rpcqueue /tmp/ccuqueue
attr HM_HomeMatic__Zentrale2__HMCCU rpcserver on
attr HM_HomeMatic__Zentrale2__HMCCU stateFormat rpcstate

define d_rpcBidCos_RF HMCCURPCPROC 192.168.1.38 BidCos-RF
attr d_rpcBidCos_RF alias CCU RPC BidCos-RF
attr d_rpcBidCos_RF eventMap /rpcserver on:on/rpcserver off:off/
attr d_rpcBidCos_RF group - Zentrale
attr d_rpcBidCos_RF room HM HomeMatic
attr d_rpcBidCos_RF stateFormat rpcstate/state
attr d_rpcBidCos_RF verbose 2

define d_rpcVirtualDevices HMCCURPCPROC 192.168.1.38 VirtualDevices
attr d_rpcVirtualDevices alias CCU RPC VirtualDevices
attr d_rpcVirtualDevices eventMap /rpcserver on:on/rpcserver off:off/
attr d_rpcVirtualDevices group - Zentrale
attr d_rpcVirtualDevices room HM HomeMatic
attr d_rpcVirtualDevices stateFormat rpcstate/state
attr d_rpcVirtualDevices verbose 2

Viele Grüße
Christian
« Letzte Änderung: Gestern um 22:05:02 von cho »
Hilfreich Hilfreich x 1 Liste anzeigen

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #146 am: Gestern um 22:22:01 »
Interessant wäre ein

list d_rpcVirtualDevices
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #147 am: Gestern um 22:26:29 »
Internals:
   CCUNum     1
   CFGFN      ./myconfig/cfg/HM_HomeMatic.cfg
   DEF        192.168.1.38 VirtualDevices
   NAME       d_rpcVirtualDevices
   NR         795
   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-17 22:12:30   rpcstate        inactive
     2018-07-17 22:12:30   state           OK
   hmccu:
     defaultaddr 192.168.1.24
     evtime     0
     localaddr  192.168.1.24
     rpcstarttime 0
     rpc:
       cbport     14702
       clkey     
       evtime     1531858323
       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:
   alias      CCU RPC VirtualDevices
   eventMap   /rpcserver on:on/rpcserver off:off/
   group      - Zentrale
   room       HM HomeMatic
   stateFormat rpcstate/state
   verbose    2

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2104
    • HMCCU
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #148 am: Heute um 08:58:25 »
Und so müsste es aussehen, damit es funktioniert:

Internals:
   CCUNum     1
   CFGFN      ./myconfig/cfg/HM_HomeMatic.cfg
   DEF        192.168.1.38 VirtualDevices
   IODev   HM_HomeMatic__Zentrale2__HMCCU
   NAME       d_rpcVirtualDevices
   ...

Wie vermutet, fehlt IODev. Jetzt muss ich nur noch rausfinden warum.
Ich nehme an, beim Rpc für BidCos ist IODev beim list vorhanden?

Vermutlich wird es nach einer kleinen Änderung der Devicedefinition funktionieren (als Workaround):

define d_rpcVirtualDevices HMCCURPCPROC iodev=HM_HomeMatic__Zentrale2__HMCCU VirtualDevices
« Letzte Änderung: Heute um 09:41:45 von zap »
CCU2 mit diversen Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für den Rest (Sonos, AVR, Meteohub, Beacons, Heizung, Hue)
HMCCU: Schnittstelle CCU2 - FHEM (best of both worlds approach)

Offline cho

  • New Member
  • *
  • Beiträge: 45
Antw:HMCCU: Neue Version 4.2 mit neuem RPC Server verfügbar
« Antwort #149 am: Heute um 10:06:54 »
Wenn ich Dein Workarount define ... absetzte bekomme ich aber folgendes:

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