HMCCU: Version 4.3 verfügbar

[Wernieman]

Ich habe das Gefühl, das beim Start Deines Pi FHEM mit gestartet wird und gleich danach abschmiert. Ich weiß nicht, wie die RPC-Server damit "umgehen" ...

[zap]

Gar nicht, sie laufen weiter da es separate Prozesse sind. Ich würde aber tatsächlich mal die RPC Devices löschen, denn zumindest das HMIP RPC Devices hat einen seltsamen Namen.

[Wolle02]

Du könntest folgendes versuchen:

- RPC-Server anhalten
- Alle HMCCURPCPROC Devices löschen
- Im IO Device Attribut rpcserver erst mal auf off
- Config speichern
- FHEM neu starten
- Mit set <ioDev> rpcserver on die RPC Server starten (dabei werden die Devices neu angelegt)
- Config speichern

Ich hab das jetzt mal gemacht und mich minutiös an deine Vorgaben gehalten.

Hier der Logauszug von dem ganzen Vorgang:

Code Auswählen Erweitern

2020.04.01 17:03:04 1: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Stopping RPC server CB2001001009001020
2020.04.01 17:03:04 1: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Deregistering RPC server http://192.168.1.9:7411/fh2001 with ID CB2001001009001020 at http://192.168.1.20:2001
2020.04.01 17:03:05 1: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Callback for RPC server CB2001001009001020 deregistered
2020.04.01 17:03:05 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Sending signal INT to RPC server process CB2001001009001020 with PID=10678
2020.04.01 17:03:05 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Scheduling cleanup in 30 seconds
2020.04.01 17:03:05 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10678] CB2001001009001020 received signal INT
2020.04.01 17:03:05 1: HMCCURPCPROC: [d_rpcBidCos_RF : 10678] RPC server CB2001001009001020 stopped handling connections. PID=10678
2020.04.01 17:03:05 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10678] Number of I/O errors = 0
2020.04.01 17:03:06 1: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Stopping RPC server CB2010001009001020
2020.04.01 17:03:06 1: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Deregistering RPC server http://192.168.1.9:7420/fh2010 with ID CB2010001009001020 at http://192.168.1.20:2010
2020.04.01 17:03:06 1: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Callback for RPC server CB2010001009001020 deregistered
2020.04.01 17:03:06 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Sending signal INT to RPC server process CB2010001009001020 with PID=10679
2020.04.01 17:03:06 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Scheduling cleanup in 30 seconds
2020.04.01 17:03:06 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10679] CB2010001009001020 received signal INT
2020.04.01 17:03:06 1: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10679] RPC server CB2010001009001020 stopped handling connections. PID=10679
2020.04.01 17:03:06 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10679] Number of I/O errors = 99
2020.04.01 17:03:07 1: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] RPC server process CB2001001009001020 terminated.
2020.04.01 17:03:07 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Stop I/O handling
2020.04.01 17:03:07 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] RPC server stopped. Cancel delayed shutdown.
2020.04.01 17:03:07 1: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] RPC server process CB2010001009001020 terminated.
2020.04.01 17:03:07 1: HMCCU: [MyCCU3 : 10272] All RPC servers inactive
2020.04.01 17:03:07 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Stop I/O handling
2020.04.01 17:03:07 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] RPC server stopped. Cancel delayed shutdown.
2020.04.01 17:03:34 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Found no running processes. Cleaning up ...
2020.04.01 17:03:34 1: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] Housekeeping called. Cleaning up RPC environment
2020.04.01 17:03:34 2: HMCCURPCPROC: [d_rpcBidCos_RF : 10272] RPC server stopped. Cancel delayed shutdown.
2020.04.01 17:03:46 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Found no running processes. Cleaning up ...
2020.04.01 17:03:46 1: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] Housekeeping called. Cleaning up RPC environment
2020.04.01 17:03:47 2: HMCCURPCPROC: [d_rpc178020HmIP_RF : 10272] RPC server stopped. Cancel delayed shutdown.
2020.04.01 17:04:47 1: RMDIR: /opt/fhem/restoreDir/save/2020-03-27
2020.04.01 17:05:09 1: HMCCU: [MyCCU3 : 10272] Graceful shutdown in 8 seconds
2020.04.01 17:05:09 1: HMCCU: [MyCCU3 : 10272] No RPC device defined for interface BidCos-RF
2020.04.01 17:05:09 0: HMCCU: [MyCCU3 : 10272] HMCCU: Can't find RPC device
2020.04.01 17:05:09 1: HMCCU: [MyCCU3 : 10272] No RPC device defined for interface HmIP-RF
2020.04.01 17:05:09 0: HMCCU: [MyCCU3 : 10272] HMCCU: Can't find RPC device
2020.04.01 17:05:09 1: Server shutdown delayed due to MyCCU3 for max 10 sec
2020.04.01 17:05:28 0: Server shutdown
2020.04.01 17:05:28 1: HMCCU: [MyCCU3 : 10272] Graceful shutdown
2020.04.01 17:05:30 3: [UtilsHourCounter] Init Done with Version 1.0.1.0 - 10.12.2014 (john)
2020.04.01 17:05:31 1: Including fhem.cfg
2020.04.01 17:05:31 3: telnetPort: port 7072 opened
2020.04.01 17:05:31 3: WEB: port 8083 opened
2020.04.01 17:05:31 3: Opening CUL_0 device /dev/ttyACM0
2020.04.01 17:05:31 3: Setting CUL_0 serial parameters to 9600,8,N,1
2020.04.01 17:05:31 3: CUL_0: Possible commands: BCFiAZEGMRTVWXefmltux
2020.04.01 17:05:31 3: CUL_0 device opened
2020.04.01 17:05:33 1: HMCCU: [MyCCU3 : 29955] Initialized version 4.3.023
2020.04.01 17:05:33 1: HMCCU: [MyCCU3 : 29955] HMCCU: Initializing device
2020.04.01 17:05:33 1: HMCCU: [MyCCU3 : 29955] HMCCU: Read 16 devices with 293 channels from CCU 192.168.1.20
2020.04.01 17:05:33 1: HMCCU: [MyCCU3 : 29955] HMCCU: Read 3 interfaces from CCU 192.168.1.20
2020.04.01 17:05:33 1: HMCCU: [MyCCU3 : 29955] HMCCU: Read 6 programs from CCU 192.168.1.20
2020.04.01 17:05:33 1: HMCCU: [MyCCU3 : 29955] HMCCU: Read 0 virtual groups from CCU 192.168.1.20
2020.04.01 17:05:33 1: HMLAN_Parse: HMLAN1 new condition disconnected
2020.04.01 17:05:33 3: Opening HMLAN1 device 192.168.178.23:1000
2020.04.01 17:05:36 1: HMLAN1: Can't connect to 192.168.178.23:1000: No route to host
2020.04.01 17:05:37 2: eventTypes: loaded 0 events from /usr/local/fhem/opt/log/eventTypes.txt
2020.04.01 17:05:46 1: [Alarm_Define] data hash restored from save file with date 2020-03-06 13:31:03
2020.04.01 17:05:46 1: PERL WARNING: Odd number of elements in anonymous hash at (eval 288) line 2, <$fh> line 950.
2020.04.01 17:05:46 3: TABLETUI: new ext defined infix:ftui/: dir:/opt/fhem/www/tablet:
2020.04.01 17:05:46 3: Registering HTTPSRV TABLETUI for URL /ftui   and assigned link ftui/ ...
2020.04.01 17:05:53 1: define alexaFHEMlog FileLog %L/alexa-%Y-%m-%d.log fakelog: Can't open /mnt/Pegasus/root/volume1/Daten/Wolfgang/log/alexa-2020-04-01.log: No such file or directory
2020.04.01 17:05:53 3: defmod -temporary alexaFHEMlog FileLog %L/alexa-%Y-%m-%d.log fakelog : Can't open /mnt/Pegasus/root/volume1/Daten/Wolfgang/log/alexa-2020-04-01.log: No such file or directory
2020.04.01 17:05:53 1: define alexaFHEMlog FileLog %L/alexa-%Y-%m-%d.log fakelog: Can't open /mnt/Pegasus/root/volume1/Daten/Wolfgang/log/alexa-2020-04-01.log: No such file or directory
2020.04.01 17:05:53 3: defmod -temporary alexaFHEMlog FileLog %L/alexa-%Y-%m-%d.log fakelog : Can't open /mnt/Pegasus/root/volume1/Daten/Wolfgang/log/alexa-2020-04-01.log: No such file or directory
2020.04.01 17:05:57 1: HUEDevice3: no I/O device
2020.04.01 17:05:57 1: HUEDevice2: no I/O device
2020.04.01 17:05:57 1: WZ_Fensterlampe_Hue: no I/O device
2020.04.01 17:05:57 1: HUEGroup0: no I/O device
2020.04.01 17:05:57 1: HUEGroup1: no I/O device
2020.04.01 17:05:57 1: HUEGroup2: no I/O device
2020.04.01 17:06:01 3: AMADCommBridge (MyAMADBridge) - defined AMADCommBridge with Socketport 8090
2020.04.01 17:06:01 3: MyAMADBridge: port 8090 opened
2020.04.01 17:06:01 3: AMADCommBridge (MyAMADBridge) - Socket opened.
2020.04.01 17:06:02 3: AMADDevice (S4_mini) - I/O device is MyAMADBridge
2020.04.01 17:06:02 3: AMADDevice (S4_mini) - set remoteServer to TNES
2020.04.01 17:06:02 3: AMADDevice (S4_mini) - defined with AMAD_ID: 1521707012 on port 8765
2020.04.01 17:06:02 3: AMADDevice (S4_mini) - set remoteServer to TNES
2020.04.01 17:06:02 3: AMADDevice (Wolles_S7) - I/O device is MyAMADBridge
2020.04.01 17:06:02 3: AMADDevice (Wolles_S7) - set remoteServer to Autoremote
2020.04.01 17:06:02 3: AMADDevice (Wolles_S7) - defined with AMAD_ID: 1523533089 on port 1817
2020.04.01 17:06:02 3: AMADDevice (Wolles_S7) - set remoteServer to Autoremote
2020.04.01 17:06:03 3: TelegramBot_Define FHEM_TelegramBot: called
2020.04.01 17:06:03 0: MSGMail: SSL is available, provided by Net::SMTP
2020.04.01 17:06:03 4: RESIDENTStk rr_Wolle_wakeuptimer2: Wakeuptime recalculation triggered by at-device at_rr_Wolle_wakeuptimer2
2020.04.01 17:06:03 4: RESIDENTStk rr_Wolle_wakeuptimer2: wakeupGetBegin source: defaultValue
2020.04.01 17:06:03 4: RESIDENTStk rr_Wolle_wakeuptimer2: wakeupGetBegin result: 05:00 = 18000 s - 0 m = 05:00:00
2020.04.01 17:06:03 3: AMADDevice (Tanjas_S7) - I/O device is MyAMADBridge
2020.04.01 17:06:03 3: AMADDevice (Tanjas_S7) - set remoteServer to Autoremote
2020.04.01 17:06:03 3: AMADDevice (Tanjas_S7) - defined with AMAD_ID: 1531048515 on port 1817
2020.04.01 17:06:03 3: AMADDevice (Tanjas_S7) - set remoteServer to Autoremote
2020.04.01 17:06:03 3: httpmod_blitzer: interval is 0, no periodic updates will done.
2020.04.01 17:06:03 3: httpmod_blitzer: Defined with URL https://cdn2.atudo.net/api/1.0/vl.php?type=0,1,2,3,4,5,6&box=48.6971565,8.9277963,48.9579545,9.5126003 featurelevel 6
2020.04.01 17:06:04 3: Pegelstand_Heiligenhafen: interval is 0, no periodic updates will done.
2020.04.01 17:06:04 3: Pegelstand_Heiligenhafen: Defined with URL https://www.pegelonline.wsv.de/webservices/rest-api/v2/stations.json?ids=06219dd9-a2c4-463c-9619-623b3c026cbc&includeTimeseries=true&includeCharacteristicValues=true&includeCurrentMeasurement=true featurelevel 6
2020.04.01 17:06:04 3: Pegelstand_Plochingen: interval is 0, no periodic updates will done.
2020.04.01 17:06:04 3: Pegelstand_Plochingen: Defined with URL https://www.pegelonline.wsv.de/webservices/rest-api/v2/stations.json?ids=be7ce40e-5fff-42df-8386-b42694ca86da&includeTimeseries=true&includeCharacteristicValues=true&includeCurrentMeasurement=true featurelevel 6
2020.04.01 17:06:04 3: Pegelstand_Bodensee: interval is 0, no periodic updates will done.
2020.04.01 17:06:04 3: Pegelstand_Bodensee: Defined with URL https://www.pegelonline.wsv.de/webservices/rest-api/v2/stations.json?ids=aa9179c1-17ef-4c61-a48a-74193fa7bfdf&includeTimeseries=true&includeCharacteristicValues=true&includeCurrentMeasurement=true featurelevel 6
2020.04.01 17:06:04 3: test_traccar_json: interval is 0, no periodic updates will done.
2020.04.01 17:06:04 3: test_traccar_json: Defined with URL http://192.168.178.9:8082/api/session?token=xeP1pyzdCFAP3XODrQqd6hLY5Y3U73vI featurelevel 6
2020.04.01 17:06:04 3: positiontest_traccar: interval is 0, no periodic updates will done.
2020.04.01 17:06:04 3: positiontest_traccar: Defined with URL https://dieneffs.net/gps/api/positions?id=855362 featurelevel 6
2020.04.01 17:06:06 3: AptToDate (FHEMPI_Update) - defined
2020.04.01 17:06:06 3: AptToDate (AlexaproxyPi_Update) - defined
2020.04.01 17:06:06 3: AptToDate (NFCPi_Update) - defined
2020.04.01 17:06:07 1: PERL WARNING: "my" variable $fields masks earlier declaration in same scope at /opt/fhem/FHEM/42_FUIP.pm line 3679, <$fh> line 4711.
2020.04.01 17:06:07 3: FUIP: Registering FrontendUI for URL /frontendui
2020.04.01 17:06:07 1: PERL WARNING: Use of uninitialized value in lc at fhem.pl line 5400, <$fh> line 4711.
2020.04.01 17:06:07 3: HourCounter HourCounter Initialize.220 Init Done with Version 1.0.1.2 - 24.12.2014
2020.04.01 17:06:07 0: HourCounter CN.FB_Internet_connect Define.228 parameters: CN.FB_Internet_connect HourCounter FB_Internet_connect:presence:.present FB_Internet_connect:presence:.absent
2020.04.01 17:06:07 3: Opening USVControl device 192.168.1.5:3493
2020.04.01 17:06:07 3: USVControl device opened
2020.04.01 17:06:07 3: UnifiClient_Define - executed. 0
2020.04.01 17:06:07 2: HMCCUCHN: [HM_FL_Krz_Sch_3] Cannot detect IO device, maybe CCU not ready. Trying later ...
2020.04.01 17:06:07 2: HMCCUDEV: [KU_Fenster] Cannot detect IO device, maybe CCU not ready. Trying later ...
2020.04.01 17:06:07 3: UnifiClient_Define - executed. 0
2020.04.01 17:06:07 3: NotdienstApotheke: interval is 0, no periodic updates will done.
2020.04.01 17:06:07 3: NotdienstApotheke: Defined with URL http://apothekenfinder.mobi/interface/json.php?device=web&source=not&search=70191 featurelevel 6
2020.04.01 17:06:08 3: Brother_Drucker: interval is 0, no periodic updates will done.
2020.04.01 17:06:08 3: Brother_Drucker: Defined with URL http://192.168.178.143/general/information.html featurelevel 6
2020.04.01 17:06:08 3: Tankstellen_E10: interval is 0, no periodic updates will done.
2020.04.01 17:06:08 3: Tankstellen_E10: Defined with URL https://www.clever-tanken.de/tankstelle_liste?spritsorte=5&r=3&ort=70569 featurelevel 6
2020.04.01 17:06:08 3: UnifiClient_Define - executed. 0
2020.04.01 17:06:08 3: AMADDevice (AMAD_Wolles_S10) - I/O device is MyAMADBridge
2020.04.01 17:06:08 3: AMADDevice (AMAD_Wolles_S10) - set remoteServer to Autoremote
2020.04.01 17:06:08 3: AMADDevice (AMAD_Wolles_S10) - defined with AMAD_ID: 1562475816 on port 1817
2020.04.01 17:06:08 3: AMADDevice (AMAD_Wolles_S10) - set remoteServer to Autoremote
2020.04.01 17:06:08 1: Flur_Garderobenlampe: no I/O device
2020.04.01 17:06:08 1: HUEGroup3: no I/O device
2020.04.01 17:06:09 3: UnifiSwitch_Define - Adress: Switch_24_PoE
2020.04.01 17:06:27 1: Including /opt/fhem/log/fhem.save
2020.04.01 17:06:29 1: PERL WARNING: Argument ":0" isn't numeric in numeric gt (>) at /opt/fhem/FHEM/98_MSwitch.pm line 10326.
2020.04.01 17:06:29 3: Device Bewegungsmelder_1 added to ActionDetector with 000:12 time
2020.04.01 17:06:29 3: monitoring (Fenster_monitoring) set Fenster_monitoring active
2020.04.01 17:06:29 3: Opening Handy_Susl_bt device 192.168.178.107:5111
2020.04.01 17:06:32 1: Handy_Susl_bt: Can't connect to 192.168.178.107:5111: No route to host
2020.04.01 17:06:32 3: Opening Handy_Tanja_bt device 192.168.178.107:5111
2020.04.01 17:06:35 1: Handy_Tanja_bt: Can't connect to 192.168.178.107:5111: Connection timed out
2020.04.01 17:06:35 3: Opening Handy_Tilman_bt device 192.168.178.107:5111
2020.04.01 17:06:38 1: Handy_Tilman_bt: Can't connect to 192.168.178.107:5111: No route to host
2020.04.01 17:06:38 3: Opening Handy_Wolle_bt device 192.168.178.107:5111
2020.04.01 17:06:41 1: Handy_Wolle_bt: Can't connect to 192.168.178.107:5111: No route to host
2020.04.01 17:06:41 3: Opening Squeezebox device 192.168.1.5:9090
2020.04.01 17:06:41 3: SB_SERVER_DoInit(Squeezebox): state: opened power: ?
2020.04.01 17:06:41 3: SB_SERVER_DoInit(Squeezebox): SB-Server is back again.
2020.04.01 17:06:41 3: Squeezebox device opened
2020.04.01 17:06:41 3: SB_SERVER_Notify(Squeezebox): CONNECTED - STATE: opened power: ?
2020.04.01 17:06:41 1: HMCCU: [MyCCU3 : 29955] No RPC device defined for interface BidCos-RF
2020.04.01 17:06:41 1: HMCCU: [MyCCU3 : 29955] Creating new RPC device d_rpc001020BidCos_RF
2020.04.01 17:06:42 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Initialized version 1.9.001 for interface BidCos-RF with I/O device MyCCU3
2020.04.01 17:06:42 1: HMCCU: [MyCCU3 : 29955] No RPC device defined for interface HmIP-RF
2020.04.01 17:06:42 1: HMCCU: [MyCCU3 : 29955] Creating new RPC device d_rpc001020HmIP_RF
2020.04.01 17:06:42 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] Initialized version 1.9.001 for interface HmIP-RF with I/O device MyCCU3
2020.04.01 17:06:42 1: HMCCU: [MyCCU3 : 29955] Saving FHEM config
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server process started for interface BidCos-RF with PID=30031
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30031] Initializing RPC server CB2001001009001020 for interface BidCos-RF
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30031] Callback server CB2001001009001020 created. Listening on port 7411
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30031] CB2001001009001020 accepting connections. PID=30031
2020.04.01 17:06:42 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server starting
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server process started for interface HmIP-RF with PID=30032
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30032] Initializing RPC server CB2010001009001020 for interface HmIP-RF
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30032] Callback server CB2010001009001020 created. Listening on port 7420
2020.04.01 17:06:42 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30032] CB2010001009001020 accepting connections. PID=30032
2020.04.01 17:06:42 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server starting
2020.04.01 17:07:51 0: Featurelevel: 6
2020.04.01 17:07:51 0: Server started with 486 defined entities (fhem.pl:21524/2020-03-27 perl:5.024001 os:linux user:fhem pid:29955)
2020.04.01 17:07:51 4: RESIDENTStk rr_Wolle_wakeuptimer2: Wakeuptime recalculation triggered by at-device at_rr_Wolle_wakeuptimer2
2020.04.01 17:07:51 4: RESIDENTStk rr_Wolle_wakeuptimer2: wakeupGetBegin source: defaultValue
2020.04.01 17:07:51 4: RESIDENTStk rr_Wolle_wakeuptimer2: wakeupGetBegin result: 05:00 = 18000 s - 0 m = 05:00:00
2020.04.01 17:07:53 3: telnetForBlockingFn_1585753673: port 41413 opened
2020.04.01 17:07:54 3: NUT antwortet nicht
2020.04.01 17:07:54 1: 192.168.1.5:3493 disconnected, waiting to reappear (USVControl)
2020.04.01 17:07:54 1: 192.168.1.5:3493 reappeared (USVControl)
2020.04.01 17:07:54 0: HourCounter CN.FB_Internet_connect Run.598 first run done countsOverall:89
2020.04.01 17:07:54 3: SB_SERVER_CheckConnection(Squeezebox): STATE: opened power: ?
2020.04.01 17:07:54 3: SB_SERVER_CheckConnection(Squeezebox): forcing power on
2020.04.01 17:07:54 1: Timeout for PRESENCE_DoLocalFunctionScan reached, terminated process 29956
2020.04.01 17:07:54 2: PRESENCE (Handy_Wolle_wlan) - device could not be checked (retrying in 10 seconds): Timeout: process terminated
2020.04.01 17:07:54 1: Timeout for PRESENCE_DoLocalFunctionScan reached, terminated process 29957
2020.04.01 17:07:54 2: PRESENCE (Handy_Tanja_wlan) - device could not be checked (retrying in 10 seconds): Timeout: process terminated
2020.04.01 17:07:55 1: Timeout for PRESENCE_DoLocalFunctionScan reached, terminated process 29984
2020.04.01 17:07:55 2: PRESENCE (Handy_Susl_wlan) - device could not be checked (retrying in 10 seconds): Timeout: process terminated
2020.04.01 17:07:55 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Checking if RPC server process is running
2020.04.01 17:07:55 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server process not running. Cleaning up
2020.04.01 17:07:55 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Housekeeping called. Cleaning up RPC environment
2020.04.01 17:07:55 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Sending signal INT to RPC server process CB2001001009001020 with PID=30031
2020.04.01 17:07:55 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30031] CB2001001009001020 received signal INT
2020.04.01 17:07:55 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30031] RPC server CB2001001009001020 stopped handling connections. PID=30031
2020.04.01 17:07:55 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30031] Number of I/O errors = 0
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server process CB2001001009001020 deleted
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Stop I/O handling
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server stopped. Cancel delayed shutdown.
2020.04.01 17:07:57 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 29985
2020.04.01 17:07:57 2: PRESENCE (FB_Internet_connect) - device could not be checked (retrying in 10 seconds): Timeout: process terminated
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] Checking if RPC server process is running
2020.04.01 17:07:57 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server process not running. Cleaning up
2020.04.01 17:07:57 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] Housekeeping called. Cleaning up RPC environment
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] Sending signal INT to RPC server process CB2010001009001020 with PID=30032
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30032] CB2010001009001020 received signal INT
2020.04.01 17:07:57 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30032] RPC server CB2010001009001020 stopped handling connections. PID=30032
2020.04.01 17:07:57 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30032] Number of I/O errors = 0
2020.04.01 17:07:59 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server process CB2010001009001020 deleted
2020.04.01 17:07:59 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] Stop I/O handling
2020.04.01 17:07:59 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server stopped. Cancel delayed shutdown.

Obwohl das Attribut 'rpcserver' im I/O Device auf off steht, wurden die RPC Server beim Start scheinbar gestartet und neu angelegt; allerdings sind sie dann wohl gleich wieder gestorben. Nach einem manuellen Strat laut deiner Anleitung sind sie dann wieder gestartet und laufen nun:

Code Auswählen Erweitern

2020.04.01 17:12:13 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server process started for interface BidCos-RF with PID=30345
2020.04.01 17:12:13 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30345] Initializing RPC server CB2001001009001020 for interface BidCos-RF
2020.04.01 17:12:13 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30345] Callback server CB2001001009001020 created. Listening on port 7411
2020.04.01 17:12:13 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30345] CB2001001009001020 accepting connections. PID=30345
2020.04.01 17:12:13 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server starting
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server process started for interface HmIP-RF with PID=30346
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30346] Initializing RPC server CB2010001009001020 for interface HmIP-RF
2020.04.01 17:12:14 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server starting
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30346] Callback server CB2010001009001020 created. Listening on port 7420
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30346] CB2010001009001020 accepting connections. PID=30346
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server CB2001001009001020 enters server loop
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Registering callback http://192.168.1.9:7411/fh2001 of type A with ID CB2001001009001020 at http://192.168.1.20:2001
2020.04.01 17:12:14 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] RPC server CB2001001009001020 running
2020.04.01 17:12:14 1: HMCCURPCPROC: [d_rpc001020BidCos_RF : 29955] Scheduled CCU ping every 300 seconds
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020BidCos_RF : 30345] CB2001001009001020 NewDevice received 76 device and channel specifications
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server CB2010001009001020 enters server loop
2020.04.01 17:12:14 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] Registering callback http://192.168.1.9:7420/fh2010 of type A with ID CB2010001009001020 at http://192.168.1.20:2010
2020.04.01 17:12:14 1: HMCCURPCPROC: [d_rpc001020HmIP_RF : 29955] RPC server CB2010001009001020 running
2020.04.01 17:12:14 1: HMCCU: [MyCCU3 : 29955] All RPC servers running
2020.04.01 17:12:15 2: HMCCURPCPROC: [d_rpc001020HmIP_RF : 30346] CB2010001009001020 NewDevice received 233 device and channel specifications

[Ralli]

Hallo zap,

ich muss das folgende Thema noch mal hochholen:

Bei mir ist jetzt noch einmal das Problem aufgetaucht, dass HMCCU die Devices nach dem Start nicht richtig geupdatet hat. Du erinnerst dich, die folgende Meldung blieb einfach immer mal wieder nach einem Neustart aus:

Code Auswählen Erweitern


2020.01.03 18:53:23.215 2: HMCCU: [CCU2 : 3657] Update success=123 failed=0


Ich konnte jetzt mit mehreren Versuchen nachstellen und verifizieren, wann dieses Problem auftritt.

Das Problem tritt ausschließlich dann auf, wenn die CCU neu gestartet wurde und danach fhem bzw. HMCCU sich erstmals mit der CCU verbindet. Wenn ich danach dann ein shutdown restart von fhem durchführe oder sogar die fhem-Maschine neu starte, tritt das Problem nie mehr auf. Das Verhalten ist absolut gleich bei Einsatz einer CCU2 und einer (virtualisierten) CCU3 bzw. RaspberryMatic mit der gerade aktuellen Firmware.

Ich denke, es hat auch nichts mit den RPC-Servern zu tun, denn die Log-Mitteilung, die dann ausbleibt, wird ja vom HMCCU-Modul generiert und nicht von einem RPC-Thread.

Magst du hier nochmal nachschauen?

[zap]

Mit dem RPC Server hat es nichts zu tun. Das Update wird über die ReGa Schnittstelle der CCU ausgeführt.

Kannst Du mal schauen, ob zu diesem Zeitpunkt (wenn das Update aller Datenpunkte ausgeführt wird) irgendwelche Fehler in /var/log/messages auf der CCU auftauchen?

[Ralli]

Hallo zap,

messages:

Code Auswählen Erweitern


...
Apr  8 07:54:32 vCCU user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr  8 07:54:32 vCCU user.err rfd: HSSParameter::GetValue() id=LEVEL failed getting physical value.
Apr  8 07:54:32 vCCU local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ0126721:1","LEVEL"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  8 07:54:32 vCCU local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"LEQ0126721:1","LEVEL"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  8 07:54:32 vCCU local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  8 07:54:33 vCCU user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr  8 07:54:33 vCCU user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Apr  8 07:54:33 vCCU local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ0126721:1","DIRECTION"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  8 07:54:33 vCCU local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"LEQ0126721:1","DIRECTION"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  8 07:54:33 vCCU local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  8 07:54:33 vCCU user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr  8 07:54:33 vCCU user.err rfd: HSSParameter::GetValue() id=WORKING failed getting physical value.
Apr  8 07:54:33 vCCU local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"LEQ0126721:1","WORKING"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  8 07:54:33 vCCU local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"LEQ0126721:1","WORKING"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  8 07:54:33 vCCU local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
...
Apr  8 07:55:32 vCCU user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Apr  8 07:55:32 vCCU local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"NEQ0119267:1","BRIGHTNESS"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  8 07:55:32 vCCU local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"NEQ0119267:1","BRIGHTNESS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  8 07:55:32 vCCU local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  8 07:55:32 vCCU local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000915699D3918:0","DUTY_CYCLE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: DUTY_CYCLE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  8 07:55:32 vCCU local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 10582, params: {"000915699D3918:0","DUTY_CYCLE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  8 07:55:32 vCCU local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  8 07:55:32 vCCU local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000915699D3918:0","ERROR_CODE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ERROR_CODE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  8 07:55:32 vCCU local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 10582, params: {"000915699D3918:0","ERROR_CODE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  8 07:55:32 vCCU local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
...


hmserver.log:

Code Auswählen Erweitern


...
Apr 8 07:54:30 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://10.0.0.30:7420/fh2010
Apr 8 07:54:30 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished
Apr 8 07:54:30 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: CB2010000030000020
Apr 8 07:54:30 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-3] updateDevicesForClient CB2010000030000020 -> 105 device addresses will be added
Apr 8 07:55:26 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://10.0.0.30:7420/fh2010
Apr 8 07:55:26 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] Removed InterfaceId: CB2010000030000020
Apr 8 07:56:11 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://10.0.0.30:7420/fh2010
Apr 8 07:56:11 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished
Apr 8 07:56:11 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: CB2010000030000020
Apr 8 07:56:11 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient CB2010000030000020 -> 105 device addresses will be added
...


[Chris8888]

Hallo Zap,

ich nutze noch den 4.3. Ich habe angefangen mich ein wenig mit den Systemvariablen in der CCU zu beschäftigen.
Was mir aufgefallen ist:
Im DropdownMenü des CCU-Devices gibt es im SET-Bereich das Kommanda "var" nicht, dafür aber "avar".
Ich vermute hier einen Tippfehler, oder?

Viele Grüße
Christian

[zap]

Hallo Zap,

ich nutze noch den 4.3. Ich habe angefangen mich ein wenig mit den Systemvariablen in der CCU zu beschäftigen.
Was mir aufgefallen ist:
Im DropdownMenü des CCU-Devices gibt es im SET-Bereich das Kommanda "var" nicht, dafür aber "avar".
Ich vermute hier einen Tippfehler, oder?

Viele Grüße
Christian

Den Fehler gibt es tatsächlich immer noch. Ich dachte, den hätte ich schon letztes Jahr eliminiert. Betrifft nur das Dropdown. Der Set-Befehl lautet "set xy var" und funktioniert.

Update: Gefixt und eingecheckt.

[PEPITO82]

Ich habe leider ein Problem mit meinem Präsenzmelder HmIP-SPI nach dem Update meiner CCU2 und HMCCU.
In der CCU2 Oberfläche wird zuverlässig angezeigt, ob Präsenz da ist oder nicht.
In FHEM scheinen diese Updates aber nicht mehr anzukommen - nur wenn ich ein manuelles get update mache.

Das Gerät habe ich mit defaults angelegt.

EG_BWM_Eingang defaults

in den Attributes ist u.a.:

event-on-change-reading: .*

An der Konfig des HMCCUDEV habe ich seit langem nichts geändert.
Nach der letzten Updates hat es auf einmal nicht mehr funktioniert und ohne die state-Änderungen funktioniert geht das per DOIF gekoppelte Licht natürlich nicht mehr automatisch an.

Gibt es eine Lösung hierfür?

[zap]

Läuft denn der RPC-Server für HmIP? Gibt es irgendwelche Fehlermeldungen im Log?

[PEPITO82]

Ich habe die HMCCURPCPROC Devices gelöscht, nachdem es die Probleme gab.
Das habe ich jetzt nochmal gemacht und scheinbar wird automatisch immer nur eines angelegt für BidCos-RF:

Code Auswählen Erweitern

2020.04.14 13:48:19 2: HMCCU: [d_ccu : 18018] Get RPC device for interface BidCos-RF
2020.04.14 13:48:19 1: HMCCU: [d_ccu : 18018] No RPC device defined for interface BidCos-RF
2020.04.14 13:48:19 1: HMCCU: [d_ccu : 18018] Creating new RPC device d_rpc178011BidCos_RF
2020.04.14 13:48:19 1: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] Initialized version 1.9.001 for interface BidCos-RF with I/O device d_ccu
2020.04.14 13:48:19 1: HMCCU: [d_ccu : 18018] Saving FHEM config
2020.04.14 13:48:19 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] RPC server process started for interface BidCos-RF with PID=18118
2020.04.14 13:48:19 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18118] Initializing RPC server CB2001178024178011 for interface BidCos-RF
2020.04.14 13:48:19 1: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] RPC server starting
2020.04.14 13:48:19 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18118] Callback server CB2001178024178011 created. Listening on port 7411
2020.04.14 13:48:19 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18118] CB2001178024178011 accepting connections. PID=18118
2020.04.14 13:48:22 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] RPC server CB2001178024178011 enters server loop
2020.04.14 13:48:22 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] Registering callback http://192.168.178.24:7411/fh2001 of type A with ID CB2001178024178011 at http://192.168.178.11:2001
2020.04.14 13:48:22 1: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] RPC server CB2001178024178011 running
2020.04.14 13:48:22 1: HMCCU: [d_ccu : 18018] All RPC servers running
2020.04.14 13:48:22 2: HMCCU: [d_ccu : 18018] Updating 6 of 6 client devices matching devexp=.* filter=ccudevstate=active,ccuif=BidCos-RF
2020.04.14 13:48:22 1: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18018] Scheduled CCU ping every 300 seconds
2020.04.14 13:48:22 3: GardenaSmartBridge (myGardenaBridge) - fetch locations id
2020.04.14 13:48:23 2: HMCCURPCPROC: [d_rpc178011BidCos_RF : 18118] CB2001178024178011 NewDevice received 92 device and channel specifications
2020.04.14 13:48:23 2: HMCCU: [d_ccu : 18018] Update success=6 failed=0

Wie bekomme ich den RPC-Server für HmIP wieder zum Laufen?

[zap]

wie sieht denn das Attribut ccuinterfaces im I/O Device aus?

[PEPITO82]

Das sieht so aus:

ccuinferfaces: VirtualDevices,HmIP-RF,BidCos-RF

[PEPITO82]

Sorry, die Antwort war nicht korrekt.
Das steht so lediglich unter "Internals".

Bei Attributes hab ich das gar nicht definiert.

Nun nachgeholt und jetzt funktioniert wieder alles. Danke!

[zap]

Sorry, das Attribut heißt rpcinterfaces