seit dem heutigem Update, Fehler in Presence-Modul!

Begonnen von Tom111, 03 Oktober 2017, 17:44:59

Vorheriges Thema - Nächstes Thema

Tom111

Nachdem ich heute das Update durchlaufen gelassen habe, kommt es zu jeder Menge Meldungen im Log (siehe unten):

2017.10.03 08:47:21 1: UPD ./CHANGED
2017.10.03 08:47:21 1: UPD FHEM/01_FHEMWEB.pm
2017.10.03 08:47:21 1: UPD FHEM/10_CUL_HM.pm
2017.10.03 08:47:21 1: UPD FHEM/59_Wunderground.pm
2017.10.03 08:47:21 1: UPD FHEM/73_GardenaSmartBridge.pm
2017.10.03 08:47:21 1: UPD FHEM/93_DbRep.pm
2017.10.03 08:47:21 1: UPD FHEM/Blocking.pm
2017.10.03 08:47:21 1: UPD FHEM/msgSchema.pm
2017.10.03 08:47:22 1: UPD www/pgm2/fhemweb.js
2017.10.03 08:47:22 1: UPD www/pgm2/fhemweb_uzsu.js
2017.10.03 08:47:22 1: saving fhem.cfg
2017.10.03 08:47:22 1: saving ./log/fhem.save
2017.10.03 08:47:22 1:
2017.10.03 08:47:22 1: New entries in the CHANGED file:
2017.10.03 08:47:22 1:   - bugfix:  93_DbRep: V5.6.3, crash due to wrong timestamp calc (Forum:#77328)
2017.10.03 08:47:22 1:   - change:  01_FHEMWEB.js: on demand loading of fhemweb_*.js (Forum #76868)
2017.10.03 08:47:22 1:   - bugfix:  73_GardenaSmartBridge: fix part of code
2017.10.03 08:47:22 1: Calling /usr/bin/perl ./contrib/commandref_join.pl -noWarnings, this may take a while
2017.10.03 08:47:53 3: FHEMWEB WEB CSRF error: csrf_252667282572800 ne csrf_196285545131037 for client WEB_192.168.178.13_47463. For details see the csrfToken FHEMWEB attribute.
2017.10.03 08:47:53 3: FS20 set Sleep_DVBT off
2017.10.03 08:48:04 1:
2017.10.03 08:48:04 1: update finished, "shutdown restart" is needed to activate the changes.
2017.10.03 08:48:06 0: Server shutdown
2017.10.03 08:48:09 1: Including fhem.cfg
2017.10.03 08:48:09 3: telnetPort: port 7072 opened
2017.10.03 08:48:09 3: WEB: port 8083 opened
2017.10.03 08:48:09 3: WEBphone: port 8084 opened
2017.10.03 08:48:09 3: WEBtablet: port 8085 opened
2017.10.03 08:48:10 2: eventTypes: loaded 1872 events from ./log/eventTypes.txt
2017.10.03 08:48:10 3: Opening CUL_0 device /dev/ttyACM0
2017.10.03 08:48:10 3: Setting CUL_0 serial parameters to 9600,8,N,1
2017.10.03 08:48:10 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2017.10.03 08:48:10 3: CUL_0 device opened
2017.10.03 08:48:18 1: Including ./log/fhem.save
2017.10.03 08:48:19 0: Featurelevel: 5.8
2017.10.03 08:48:19 0: Server started with 346 defined entities (fhem.pl:15112/2017-09-21 perl:5.014002 os:linux user:fhem pid:23892)
2017.10.03 08:48:20 3: telnetForBlockingFn_1507013300: port 37513 opened
2017.10.03 08:48:23 2: PRESENCE (CAM_02_Spuele) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_06_Keller) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_07_Kueche) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_09_Raspberry) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (Comp_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (DS716) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (FritzBox) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (Homepage) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (Lap_LAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (Powerline_Keller) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (Powerline_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_02_Spuele) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:23 2: PRESENCE (CAM_05_Schlafen) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_06_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:23 2: PRESENCE (Tablet_XORO) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_07_Kueche) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:23 2: PRESENCE (QNAP) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:23 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:23 2: PRESENCE (CAM_09_Raspberry) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:23 2: PRESENCE (DS716) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Comp_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 3: FS20 set Sleep_DVBT on
2017.10.03 08:48:24 2: PRESENCE (CAM_05_Schlafen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Homepage) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (FritzBox) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Powerline_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Tablet_XORO) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (QNAP) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Powerline_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Lap_LAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:24 2: PRESENCE (Raspberry_Pi) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:24 2: PRESENCE (Repeater_300E) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:24 2: PRESENCE (Tab_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:24 2: PRESENCE (Tablet_WLAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:24 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Tablet_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:24 2: PRESENCE (Tab_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:25 2: PRESENCE (Repeater_300E) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:25 2: PRESENCE (Raspberry_Pi) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:26 2: PRESENCE (CAM_03_Kueche) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:48:26 2: PRESENCE (CAM_03_Kueche) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:48:39 3: FS20 set Sleep_DVBT off
2017.10.03 08:50:10 3: FHEMWEB WEB CSRF error: csrf_196285545131037 ne csrf_38254144504474 for client WEB_192.168.178.13_47466. For details see the csrfToken FHEMWEB attribute.
2017.10.03 08:50:10 3: FBDECT set DECT_Refrigerator off
2017.10.03 08:50:17 2: PRESENCE (Tablet_XORO) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:50:17 2: PRESENCE (Tablet_XORO) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:50:48 3: FBDECT set DECT_Refrigerator on
2017.10.03 08:50:53 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:50:53 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 08:50:58 3: FBDECT set DECT_Refrigerator off
2017.10.03 08:51:41 3: FS20 set Kitchen_Dunstabzug off
2017.10.03 08:51:57 3: FBDECT set DECT_Refrigerator on
2017.10.03 08:52:05 3: FBDECT set DECT_Refrigerator off
2017.10.03 08:53:11 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 08:53:11 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 09:42:17 3: FS20 set Sleep_DVBT off
2017.10.03 09:44:17 3: FS20 set Sleep_tablet on
2017.10.03 09:54:05 2: PRESENCE (Repeater_300E) - device could not be checked (retrying in 10 seconds)
2017.10.03 09:54:05 2: PRESENCE (Repeater_300E) - check returned a valid result after 1 unsuccesful retry
2017.10.03 09:56:04 2: PRESENCE (Laptop_LAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 09:56:04 2: PRESENCE (Laptop_LAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 09:56:40 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 09:56:40 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 10:00:54 2: PRESENCE (Laptop_WLAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 10:00:54 2: PRESENCE (Laptop_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 10:23:56 2: PRESENCE (Repeater_300E) - device could not be checked (retrying in 10 seconds)
2017.10.03 10:23:56 2: PRESENCE (Repeater_300E) - check returned a valid result after 1 unsuccesful retry
2017.10.03 10:36:17 3: FS20 set Sleep_DVBT off
2017.10.03 10:38:04 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 10:38:04 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 10:40:17 3: FS20 set Sleep_tablet on
2017.10.03 11:23:10 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 11:23:10 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 11:30:17 3: FS20 set Sleep_DVBT off
2017.10.03 11:36:17 3: FS20 set Sleep_tablet on
2017.10.03 11:39:06 2: PRESENCE (DS716) - device could not be checked (retrying in 10 seconds)
2017.10.03 11:39:06 2: PRESENCE (DS716) - check returned a valid result after 1 unsuccesful retry
2017.10.03 11:43:50 2: PRESENCE (CAM_09_Raspberry) - device could not be checked (retrying in 10 seconds)
2017.10.03 11:43:50 2: PRESENCE (CAM_09_Raspberry) - check returned a valid result after 1 unsuccesful retry
2017.10.03 11:46:39 2: PRESENCE (QNAP) - device could not be checked (retrying in 10 seconds)
2017.10.03 11:46:39 2: PRESENCE (QNAP) - check returned a valid result after 1 unsuccesful retry
2017.10.03 12:24:17 3: FS20 set Sleep_DVBT off
2017.10.03 12:32:17 3: FS20 set Sleep_tablet on
2017.10.03 12:39:18 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 12:39:18 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 12:54:48 2: PRESENCE (Laptop_LAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 12:54:48 2: PRESENCE (Laptop_LAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:07:52 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:07:52 2: PRESENCE (CAM_04_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:07:52 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:07:52 2: PRESENCE (CAM_04_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:08:26 2: PRESENCE (CAM_06_Keller) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:08:26 2: PRESENCE (CAM_06_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:18:17 3: FS20 set Sleep_DVBT off
2017.10.03 13:22:36 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:22:36 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:25:18 2: PRESENCE (Homepage) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:25:18 2: PRESENCE (Homepage) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:26:05 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:26:05 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 13:28:17 3: FS20 set Sleep_tablet on
2017.10.03 13:33:16 3: FS20 set Ladegeraet_kitchen off
2017.10.03 13:57:57 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 13:57:57 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 14:12:17 3: FS20 set Sleep_DVBT off
2017.10.03 14:24:17 3: FS20 set Sleep_tablet on
2017.10.03 14:30:16 3: FS20 set Ladegeraet_kitchen off
2017.10.03 15:06:17 3: FS20 set Sleep_DVBT off
2017.10.03 15:12:17 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 15:12:17 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 15:15:10 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 15:15:10 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 15:20:17 3: FS20 set Sleep_tablet on
2017.10.03 15:21:39 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 15:21:39 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 15:24:07 2: PRESENCE (Homepage) - device could not be checked (retrying in 10 seconds)
2017.10.03 15:24:07 2: PRESENCE (Homepage) - check returned a valid result after 1 unsuccesful retry
2017.10.03 15:24:33 2: PRESENCE (CAM_03_Kueche) - device could not be checked (retrying in 10 seconds)
2017.10.03 15:24:33 2: PRESENCE (CAM_03_Kueche) - check returned a valid result after 1 unsuccesful retry
2017.10.03 15:27:16 3: FS20 set Ladegeraet_kitchen off
2017.10.03 16:00:17 3: FS20 set Sleep_DVBT off
2017.10.03 16:16:17 3: FS20 set Sleep_tablet on
2017.10.03 16:24:16 3: FS20 set Ladegeraet_kitchen off
2017.10.03 16:48:17 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 16:48:17 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 16:54:17 3: FS20 set Sleep_DVBT off
2017.10.03 16:59:54 2: PRESENCE (CAM_06_Keller) - device could not be checked (retrying in 10 seconds)
2017.10.03 16:59:54 2: PRESENCE (CAM_06_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:00:02 2: PRESENCE (CAM_07_Kueche) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:00:02 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:00:02 2: PRESENCE (CAM_07_Kueche) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:00:02 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:05:36 2: PRESENCE (Laptop_WLAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:05:36 2: PRESENCE (Laptop_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:06:45 2: PRESENCE (FritzBox) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:06:45 2: PRESENCE (FritzBox) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:09:09 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:09:09 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:12:17 3: FS20 set Sleep_tablet on
2017.10.03 17:21:16 3: FS20 set Ladegeraet_kitchen off
2017.10.03 17:36:36 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:36:36 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:36:55 1: UPD www/pgm2/fhemweb.js
2017.10.03 17:36:55 1: saving fhem.cfg
2017.10.03 17:36:55 1: saving ./log/fhem.save
2017.10.03 17:36:55 1:
2017.10.03 17:36:55 1: update finished, "shutdown restart" is needed to activate the changes.
2017.10.03 17:37:02 0: Server shutdown
2017.10.03 17:37:02 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37513: IO::Socket::INET: connect: Connection refused
2017.10.03 17:37:02 1: BlockingInformParent (PRESENCE_ProcessLocalScan): Can't connect to localhost:37513: IO::Socket::INET: connect: Connection refused
2017.10.03 17:37:04 1: Including fhem.cfg
2017.10.03 17:37:05 3: telnetPort: port 7072 opened
2017.10.03 17:37:05 3: WEB: port 8083 opened
2017.10.03 17:37:05 3: WEBphone: port 8084 opened
2017.10.03 17:37:05 3: WEBtablet: port 8085 opened
2017.10.03 17:37:05 2: eventTypes: loaded 1878 events from ./log/eventTypes.txt
2017.10.03 17:37:05 3: Opening CUL_0 device /dev/ttyACM0
2017.10.03 17:37:05 3: Setting CUL_0 serial parameters to 9600,8,N,1
2017.10.03 17:37:05 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2017.10.03 17:37:05 3: CUL_0 device opened
2017.10.03 17:37:14 1: Including ./log/fhem.save
2017.10.03 17:37:14 0: Featurelevel: 5.8
2017.10.03 17:37:14 0: Server started with 346 defined entities (fhem.pl:15112/2017-09-21 perl:5.014002 os:linux user:fhem pid:26397)
2017.10.03 17:37:15 3: telnetForBlockingFn_1507045035: port 44653 opened
2017.10.03 17:37:18 2: PRESENCE (CAM_02_Spuele) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:18 2: PRESENCE (CAM_06_Keller) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_07_Kueche) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_02_Spuele) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_09_Raspberry) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (Comp_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (DS716) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (FritzBox) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (Homepage) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (Powerline_Keller) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (Powerline_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_06_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_03_Kueche) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_04_Wohnen) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_05_Schlafen) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (Tab_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:19 2: PRESENCE (CAM_07_Kueche) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_09_Raspberry) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_03_Kueche) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (Comp_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 3: FS20 set Sleep_DVBT on
2017.10.03 17:37:19 3: FS20 set Sleep_tablet on
2017.10.03 17:37:19 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_05_Schlafen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (CAM_04_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (DS716) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (FritzBox) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (Homepage) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:19 2: PRESENCE (Tab_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Powerline_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Powerline_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Lap_LAN_2) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Laptop_LAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Laptop_WLAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (QNAP) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Raspberry_Pi) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Repeater_300E) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Tablet_WLAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Tablet_XORO) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:37:20 2: PRESENCE (Laptop_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Tablet_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Lap_LAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Repeater_300E) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Laptop_LAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Raspberry_Pi) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (QNAP) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:37:20 2: PRESENCE (Tablet_XORO) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:39:41 2: PRESENCE (Laptop_WLAN) - device could not be checked (retrying in 10 seconds)
2017.10.03 17:39:41 2: PRESENCE (Laptop_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.03 17:39:55 3: FHEMWEB WEB CSRF error: csrf_38254144504474 ne csrf_880030086438965 for client WEB_192.168.178.13_47507. For details see the csrfToken FHEMWEB attribute.
2017.10.03 17:39:56 3: FBDECT set DECT_Refrigerator off
FHEM 5.9 auf Raspberry Pi - 3B+ - Stretch-5.10.88+ | CUL868 CC1101 - USB - Lite module - V3 FW 1.67
Fritz!Box 7490 OS 07.29 / Fritz!Dect200 / Fritz!Powerline 546E
FS20ST-4/ FS20 DI-5/ FS20LS/ FS20 PIRI-2-KU/ FS20 TFK/ FS20S4A/FS20 SU-3/FS20 S20-3
HMS100TF/FHT80TF-2/ASH2200/S300TH/MiLight-Bridge V

CoolTux

Kannst du bitte einmal schauen ob Blocking.pm bei Dir aktuallisiert würde?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Tom111

FHEM 5.9 auf Raspberry Pi - 3B+ - Stretch-5.10.88+ | CUL868 CC1101 - USB - Lite module - V3 FW 1.67
Fritz!Box 7490 OS 07.29 / Fritz!Dect200 / Fritz!Powerline 546E
FS20ST-4/ FS20 DI-5/ FS20LS/ FS20 PIRI-2-KU/ FS20 TFK/ FS20S4A/FS20 SU-3/FS20 S20-3
HMS100TF/FHT80TF-2/ASH2200/S300TH/MiLight-Bridge V

CoolTux

Ist nur eine Vermutung. Rudi hat da in den letzten Tagen eine Erweiterung eingebaut. Eventuell besteht da ein Zusammenhang. Kannst Du Mal eine ältere Version des Modules einspielen?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Tom111

Ok, hab ich gemacht, scheint wieder i.O. zu sein, mit der alten Version von Blocking.pm!
Wird da jetzt noch was an Presence geändert oder muss Rudi an Blocking.pm arbeiten? :)
FHEM 5.9 auf Raspberry Pi - 3B+ - Stretch-5.10.88+ | CUL868 CC1101 - USB - Lite module - V3 FW 1.67
Fritz!Box 7490 OS 07.29 / Fritz!Dect200 / Fritz!Powerline 546E
FS20ST-4/ FS20 DI-5/ FS20LS/ FS20 PIRI-2-KU/ FS20 TFK/ FS20S4A/FS20 SU-3/FS20 S20-3
HMS100TF/FHT80TF-2/ASH2200/S300TH/MiLight-Bridge V

CoolTux

Erstmal muss Rudi darauf aufmerksam gemacht werden. Schau bitte in welchen Forum Blocking.pm diskutiert wird und mach dort noch mal einen Thread auf.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Tom111

FHEM 5.9 auf Raspberry Pi - 3B+ - Stretch-5.10.88+ | CUL868 CC1101 - USB - Lite module - V3 FW 1.67
Fritz!Box 7490 OS 07.29 / Fritz!Dect200 / Fritz!Powerline 546E
FS20ST-4/ FS20 DI-5/ FS20LS/ FS20 PIRI-2-KU/ FS20 TFK/ FS20S4A/FS20 SU-3/FS20 S20-3
HMS100TF/FHT80TF-2/ASH2200/S300TH/MiLight-Bridge V

CoolTux

Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rudolfkoenig

ZitatOk, hab ich gemacht, scheint wieder i.O. zu sein, mit der alten Version von Blocking.pm!
Die letzte Aenderung in Blocking.pm ruft abortFn auf, falls die von BlockingCall aufgerufene Perl-Funktion exit() aufruft (oder anderweitig den Perl-Interpreter beendet), statt was zurueckzuliefern, jedenfalls war das meine Absicht. Weiterhin wird abortFn mit einem zweiten Argument aufgerufen, was die Ursache des Aufrufs (timeout oder toter Prozess) in Klartext enthaelt.

Falls ich was aendern soll, brauche ich mehr Details ueber das, was Probleme bereitet.

CoolTux

Dann müssen wir warten bis Markus vorbei schaut.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Markus Bloch

Hallo zusammen,

das ist so gewollt. Die Änderung im Rahmen von https://svn.fhem.de/trac/changeset/15172/ führt dazu, dass die Probleme unter https://forum.fhem.de/index.php/topic,74214.0.html nicht mehr auftreten. Du scheinst dieses Problem ebenfalls gehabt zu haben. Insbesondere bei eine Vielzahl ein PRESENCE-Definitionen kann es beim Start zu Problemen kommen, wenn plötzlich alle Definitionen sofort anfangen zu checken, wodurch einige Checks in einen Timeout laufen oder dergleichen. Dieser Umstand wird unter Verbose-Level 2 mitgeteilt, dass der letzte Check unvollständig abgebrochen wurde und erst beim X.ten mal wieder erfolgreich lief. Da du sehr viele PRESENCE-Definitionen konfiguriert hast, ist dein Log zum Anfang entsprechend voll. Das sollte sich aber nach einiger Zeit nach dem Start wieder normalisieren.

Gruß
Markus
Developer für Module: YAMAHA_AVR, YAMAHA_BD, FB_CALLMONITOR, FB_CALLLIST, PRESENCE, Pushsafer, LGTV_IP12, version

aktives Mitglied des FHEM e.V. (Technik)

Markus Bloch

Bitte probiert mal aus das globale Attribut "blockingCallMax" zwischen 5 und 10 setzen und dann FHEM neustarten. Dannach sollten theoretisch die Meldungen aufhören. Evtl. mal etwas mit den Werten spielen.

Gruß
Markus
Developer für Module: YAMAHA_AVR, YAMAHA_BD, FB_CALLMONITOR, FB_CALLLIST, PRESENCE, Pushsafer, LGTV_IP12, version

aktives Mitglied des FHEM e.V. (Technik)

fhemxperte

Leider keine Besserung. Weder mit 5,8,10,20 oder 200 ... weiterhin das gleiche Bild, werde heute dann nochmal zur alten Version zurückkehren.

2017.10.04 19:41:48 2: PRESENCE (PS_Andreas_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:41:48 2: PRESENCE (PS_Karin_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:41:48 2: PRESENCE (PS_Manfred_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:41:48 2: PRESENCE (PS_Andreas_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:41:48 2: PRESENCE (PS_Michael_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:41:48 2: PRESENCE (PS_Karin_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:41:48 2: PRESENCE (PS_Manfred_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:41:48 2: PRESENCE (PS_Michael_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:42:48 2: PRESENCE (PS_Andreas_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:42:48 2: PRESENCE (PS_Karin_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:42:48 2: PRESENCE (PS_Manfred_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:42:48 2: PRESENCE (PS_Andreas_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:42:48 2: PRESENCE (PS_Michael_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:42:48 2: PRESENCE (PS_Karin_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:42:48 2: PRESENCE (PS_Manfred_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:42:49 2: PRESENCE (PS_Michael_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:43:49 2: PRESENCE (PS_Andreas_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:43:49 2: PRESENCE (PS_Karin_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:43:49 2: PRESENCE (PS_Manfred_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:43:49 2: PRESENCE (PS_Andreas_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:43:49 2: PRESENCE (PS_Michael_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:43:49 2: PRESENCE (PS_Karin_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:43:49 2: PRESENCE (PS_Manfred_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:43:49 2: PRESENCE (PS_Michael_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:44:49 3: BlockingCall for WOL_SZ_Steamlink was aborted
2017.10.04 19:44:49 2: PRESENCE (PS_Andreas_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:44:49 2: PRESENCE (PS_Karin_Nexus5) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:44:49 2: PRESENCE (PS_Manfred_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:44:49 2: PRESENCE (PS_Andreas_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:44:49 2: PRESENCE (PS_Michael_Nexus5X) - device could not be checked (retrying in 10 seconds)
2017.10.04 19:44:49 2: PRESENCE (PS_Karin_Nexus5) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:44:49 2: PRESENCE (PS_Manfred_Nexus5X) - check returned a valid result after 1 unsuccesful retry
2017.10.04 19:44:49 2: PRESENCE (PS_Michael_Nexus5X) - check returned a valid result after 1 unsuccesful retry

knopf_piano

Ich habe das gleiche Problem. Bei mir hängt eine struct dahinter, was einen watchdog bedient. Ich geh auch erstmal auf die alte blocking.pm

Gesendet von meinem SM-J510FN mit Tapatalk

zotac nano mit proxmox und ganz viel zeug drauf

mkress

#14
Ich habe leider das gleiche Problem. Dabei spielt es keine Rolle, ob per lan-ping oder function (fritzbox-reading).
Läuft auf einem Raspberry Pi 2 - dumme Frage wie macht man denn ein downgrade (gibt es dafür einen Befehl in fhem)?


Server started with 169 defined entities (fhem.pl:15182/2017-10-03 perl:5.020002 os:linux user:fhem pid:31312)
2017.10.04 20:35:41 0: Featurelevel: 5.8

: WEB: port 8083 opened
2017.10.04 20:35:21 3: telnetPort: port 7072 opened
2017.10.04 20:35:21 1: Including fhem.cfg
2017.10.04 20:35:20 1: BlockingInformParent (PRESENCE_ProcessLocalScan): Can't connect to localhost:7072: IO::Socket::INET: connect: Verbindungsaufbau abgelehnt
2017.10.04 20:35:20 1: BlockingInformParent (BlockingStart): Can't connect to localhost:7072: IO::Socket::INET: connect: Verbindungsaufbau abgelehnt


2017.10.04 21:55:32 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:55:32 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:54:02 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:54:02 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:44:30 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:44:30 2: PRESENCE (HandyMarkus) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:44:30 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:44:30 2: PRESENCE (presence_YamahaAvr) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:44:30 2: PRESENCE (HandyMarkus) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:44:29 2: PRESENCE (presence_YamahaAvr) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:40:58 2: PRESENCE (presence_SamsungTv) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:40:58 2: PRESENCE (presence_SamsungTv) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:40:29 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:40:29 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:38:58 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:38:58 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:36:58 2: PRESENCE (HandyMarkus) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:36:58 2: PRESENCE (HandyMarkus) - device could not be checked (retrying in 10 seconds)
2017.10.04 21:35:58 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:35:58 2: PRESENCE (HandyMarkus) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:35:58 2: PRESENCE (presence_YamahaAvr) - check returned a valid result after 1 unsuccesful retry
2017.10.04 21:35:58 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)


Auch nach setzen von blockingCallMax auf 5 und restart:

Gibt es sofort Fehler - habe nur 5 presence Definitionen

PRESENCE (presence_YamahaAvr) - check returned a valid result after 1 unsuccesful retry
2017.10.04 22:12:25 2: PRESENCE (presence_YamahaAvr) - device could not be checked (retrying in 10 seconds)
2017.10.04 22:12:25 3: YAMAHA_AVR (AV_Receiver) - could not execute command on device AV_Receiver. Please turn on your device in case of deactivated network standby or check for correct hostaddress.
2017.10.04 22:12:19 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.04 22:12:19 2: PRESENCE (HandyMarkus) - check returned a valid result after 1 unsuccesful retry
2017.10.04 22:12:19 3: FritzBoxMonitor device opened
2017.10.04 22:12:18 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds)
2017.10.04 22:12:18 2: PRESENCE (Hand..