Freezes mit addtime auf die Spur kommen.

[Gunther]

Ich habe ständig freezes - gerade enorm (Wahrnehmungseffekt?  ).
Wie lange die Probleme bestehen kann ich nicht sagen.
In meinen Logs kann ich das natürlich nur zurückverfolgen bis zu dem Zeitpunkt wo ich perfmon mal installiert habe.

Jetzt stelle ich mir die Frage, wie ich die Probleme in den Griff bekomme.
Wie setze ich an? Ich habe in den letzten 3 Monaten verletzungsbedingt zu viel Zeit für FHEM gehabt  und daher natürlich viele Dinge umgesetzt.
Extrem problematisch ist es aber seit Anfang Dezember (laut Logs).

Meine Installation sieht laut fheminfo auf einem RPI3 so aus:
https://forum.fhem.de/index.php/topic,82140.msg742250.html#msg742250

Hier mal ein wahlloser Auszug aus meinem Log

Code Auswählen Erweitern

2018.01.06 13:56:24 1: Perfmon: possible freeze starting at 13:56:21, delay is 3.378
2018.01.06 13:56:35 1: Perfmon: possible freeze starting at 13:56:32, delay is 3.404
2018.01.06 13:56:46 1: Perfmon: possible freeze starting at 13:56:43, delay is 3.344
2018.01.06 13:56:57 1: Perfmon: possible freeze starting at 13:56:54, delay is 3.394
2018.01.06 13:57:02 1: Perfmon: possible freeze starting at 13:57:01, delay is 1.241
2018.01.06 13:57:06 1: Perfmon: possible freeze starting at 13:57:03, delay is 3.432
2018.01.06 13:57:21 1: Perfmon: possible freeze starting at 13:57:18, delay is 3.387
2018.01.06 13:57:32 1: Perfmon: possible freeze starting at 13:57:30, delay is 2.669
2018.01.06 13:57:46 1: Perfmon: possible freeze starting at 13:57:43, delay is 3.358
2018.01.06 13:57:49 1: Perfmon: possible freeze starting at 13:57:47, delay is 2.072
2018.01.06 13:57:53 1: Perfmon: possible freeze starting at 13:57:50, delay is 3.167
2018.01.06 13:57:55 1: Perfmon: possible freeze starting at 13:57:54, delay is 1.161
2018.01.06 13:58:14 1: Perfmon: possible freeze starting at 13:58:11, delay is 3.314
2018.01.06 13:58:24 1: Perfmon: possible freeze starting at 13:58:21, delay is 3.473
2018.01.06 13:58:46 1: Perfmon: possible freeze starting at 13:58:43, delay is 3.377
2018.01.06 13:58:56 1: Perfmon: possible freeze starting at 13:58:54, delay is 2.75
2018.01.06 13:59:06 1: Perfmon: possible freeze starting at 13:59:03, delay is 3.395
2018.01.06 13:59:08 1: Perfmon: possible freeze starting at 13:59:07, delay is 1.784
2018.01.06 13:59:15 1: Perfmon: possible freeze starting at 13:59:14, delay is 1.493
2018.01.06 13:59:21 1: Perfmon: possible freeze starting at 13:59:18, delay is 3.379
2018.01.06 13:59:23 1: Perfmon: possible freeze starting at 13:59:22, delay is 1.192
2018.01.06 13:59:32 1: Perfmon: possible freeze starting at 13:59:30, delay is 2.985
2018.01.06 13:59:36 3: ABFALL myAbfall - CALENDAR:Abfall triggered, updating ABFALL myAbfall ...
2018.01.06 13:59:36 3: ABFALL_UPDATE
2018.01.06 13:59:37 1: Perfmon: possible freeze starting at 13:59:36, delay is 1.486
2018.01.06 13:59:46 1: Perfmon: possible freeze starting at 13:59:43, delay is 3.359
2018.01.06 13:59:54 1: Perfmon: possible freeze starting at 13:59:51, delay is 3.178
2018.01.06 14:00:07 1: Perfmon: possible freeze starting at 13:59:55, delay is 12.707
2018.01.06 14:00:11 1: Perfmon: possible freeze starting at 14:00:08, delay is 3.365
2018.01.06 14:00:15 1: Perfmon: possible freeze starting at 14:00:12, delay is 3.511
2018.01.06 14:00:15 1: Timeout for WOL_Ping reached, terminated process 2506
2018.01.06 14:00:15 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.06 14:00:15 1: Timeout for WOL_Ping reached, terminated process 2507
2018.01.06 14:00:15 3: BlockingCall for IMAC was aborted
2018.01.06 14:00:25 1: Perfmon: possible freeze starting at 14:00:22, delay is 3.357
2018.01.06 14:00:27 1: Perfmon: possible freeze starting at 14:00:26, delay is 1.192
2018.01.06 14:00:29 1: Perfmon: possible freeze starting at 14:00:28, delay is 1.751
2018.01.06 14:00:42 1: Perfmon: possible freeze starting at 14:00:41, delay is 1.855
2018.01.06 14:00:46 1: Perfmon: possible freeze starting at 14:00:44, delay is 2.63
2018.01.06 14:00:57 1: Perfmon: possible freeze starting at 14:00:54, delay is 3.401
2018.01.06 14:01:06 1: Perfmon: possible freeze starting at 14:01:03, delay is 3.428
2018.01.06 14:01:21 1: Perfmon: possible freeze starting at 14:01:18, delay is 3.412
2018.01.06 14:01:34 1: Perfmon: possible freeze starting at 14:01:31, delay is 3.243
2018.01.06 14:01:46 1: Perfmon: possible freeze starting at 14:01:43, delay is 3.519
2018.01.06 14:01:46 1: Timeout for WOL_Ping reached, terminated process 2550
2018.01.06 14:01:46 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.06 14:01:54 1: Perfmon: possible freeze starting at 14:01:51, delay is 3.356
2018.01.06 14:01:58 1: Perfmon: possible freeze starting at 14:01:55, delay is 3.126
2018.01.06 14:01:58 1: Timeout for WOL_Ping reached, terminated process 2555
2018.01.06 14:01:58 3: BlockingCall for winserver was aborted
2018.01.06 14:02:15 1: Perfmon: possible freeze starting at 14:02:13, delay is 2.543
2018.01.06 14:02:25 1: Perfmon: possible freeze starting at 14:02:22, delay is 3.548
2018.01.06 14:02:26 1: Timeout for WOL_Ping reached, terminated process 2574
2018.01.06 14:02:26 3: BlockingCall for IMAC was aborted
2018.01.06 14:02:33 1: Perfmon: possible freeze starting at 14:02:30, delay is 3.393
2018.01.06 14:02:46 1: Perfmon: possible freeze starting at 14:02:43, delay is 3.427
2018.01.06 14:02:49 1: Perfmon: possible freeze starting at 14:02:47, delay is 2.223
2018.01.06 14:02:58 1: Perfmon: possible freeze starting at 14:02:55, delay is 3.411
2018.01.06 14:03:06 1: Perfmon: possible freeze starting at 14:03:03, delay is 3.409
2018.01.06 14:03:17 1: Perfmon: possible freeze starting at 14:03:16, delay is 1.196
2018.01.06 14:03:19 1: Perfmon: possible freeze starting at 14:03:18, delay is 1.408
2018.01.06 14:03:23 1: Perfmon: possible freeze starting at 14:03:20, delay is 3.227
2018.01.06 14:03:34 1: Perfmon: possible freeze starting at 14:03:31, delay is 3.425
2018.01.06 14:03:46 1: Perfmon: possible freeze starting at 14:03:44, delay is 2.521
2018.01.06 14:03:53 1: Perfmon: possible freeze starting at 14:03:51, delay is 2.736
2018.01.06 14:04:16 1: Perfmon: possible freeze starting at 14:04:13, delay is 3.208
2018.01.06 14:04:32 1: Perfmon: possible freeze starting at 14:04:30, delay is 2.734
2018.01.06 14:04:35 1: Perfmon: possible freeze starting at 14:04:33, delay is 2.628
2018.01.06 14:04:40 3: error while requesting https://www.verkehrsinfo.de/httpsmobil/index.php?c=staulist&street=A2&lat=&lon= - https://www.verkehrsinfo.de/httpsmobil/index.php?c=staulist&street=A2&lat=&lon=: Can't connect(2) to https://www.verkehrsinfo.de:443:  SSL connect attempt failed with unknown error error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
2018.01.06 14:04:42 3: CALVIEW Geburtstage - CALENDAR:GeburtstagsKalender triggered, updating CALVIEW Geburtstage ...
2018.01.06 14:04:42 1: Perfmon: possible freeze starting at 14:04:41, delay is 1.959
2018.01.06 14:04:44 1: Perfmon: possible freeze starting at 14:04:43, delay is 1.139
2018.01.06 14:04:47 1: Perfmon: possible freeze starting at 14:04:45, delay is 2.602
2018.01.06 14:04:57 1: Perfmon: possible freeze starting at 14:04:55, delay is 2.753
2018.01.06 14:04:59 1: Perfmon: possible freeze starting at 14:04:58, delay is 1.93
2018.01.06 14:05:05 1: Perfmon: possible freeze starting at 14:05:03, delay is 2.745
2018.01.06 14:05:14 1: Perfmon: possible freeze starting at 14:05:13, delay is 1.121
2018.01.06 14:05:22 1: Perfmon: possible freeze starting at 14:05:20, delay is 2.758
2018.01.06 14:05:24 1: Perfmon: possible freeze starting at 14:05:23, delay is 1.225
2018.01.06 14:05:33 1: Perfmon: possible freeze starting at 14:05:31, delay is 2.747
2018.01.06 14:05:46 1: Perfmon: possible freeze starting at 14:05:43, delay is 3.442
2018.01.06 14:05:55 1: Perfmon: possible freeze starting at 14:05:52, delay is 3.26
2018.01.06 14:06:16 1: Perfmon: possible freeze starting at 14:06:13, delay is 3.414
2018.01.06 14:06:19 1: Perfmon: possible freeze starting at 14:06:17, delay is 2.594
2018.01.06 14:06:33 1: Perfmon: possible freeze starting at 14:06:30, delay is 3.358
2018.01.06 14:06:35 1: Perfmon: possible freeze starting at 14:06:34, delay is 1.325
2018.01.06 14:06:45 1: Perfmon: possible freeze starting at 14:06:43, delay is 2.879
2018.01.06 14:06:58 1: Perfmon: possible freeze starting at 14:06:55, delay is 3.421
2018.01.06 14:07:00 1: Perfmon: possible freeze starting at 14:06:59, delay is 1.821
2018.01.06 14:07:03 1: Perfmon: possible freeze starting at 14:07:02, delay is 1.333
2018.01.06 14:07:07 1: Perfmon: possible freeze starting at 14:07:04, delay is 3.272
2018.01.06 14:07:08 3: CUL_HM set og_sz_JalousieLinks statusRequest
2018.01.06 14:07:12 1: Perfmon: possible freeze starting at 14:07:09, delay is 3.305
2018.01.06 14:07:23 1: Perfmon: possible freeze starting at 14:07:20, delay is 3.405
2018.01.06 14:07:30 1: Perfmon: possible freeze starting at 14:07:27, delay is 3.405
2018.01.06 14:07:33 1: Perfmon: possible freeze starting at 14:07:31, delay is 2.14
2018.01.06 14:07:47 1: Perfmon: possible freeze starting at 14:07:44, delay is 3.225
2018.01.06 14:07:55 1: Perfmon: possible freeze starting at 14:07:52, delay is 3.527
2018.01.06 14:07:59 1: Perfmon: possible freeze starting at 14:07:56, delay is 3.505
2018.01.06 14:08:12 1: Perfmon: possible freeze starting at 14:08:11, delay is 1.369
2018.01.06 14:08:16 1: Perfmon: possible freeze starting at 14:08:13, delay is 3.409
2018.01.06 14:08:44 1: Perfmon: possible freeze starting at 14:08:42, delay is 2.867
2018.01.06 14:08:58 1: Perfmon: possible freeze starting at 14:08:55, delay is 3.429
2018.01.06 14:09:06 1: Perfmon: possible freeze starting at 14:09:04, delay is 2.586
2018.01.06 14:09:09 1: Perfmon: possible freeze starting at 14:09:07, delay is 2.276
2018.01.06 14:09:13 1: Perfmon: possible freeze starting at 14:09:10, delay is 3.232
2018.01.06 14:09:23 1: Perfmon: possible freeze starting at 14:09:20, delay is 3.367
2018.01.06 14:09:30 1: Perfmon: possible freeze starting at 14:09:28, delay is 2.614
2018.01.06 14:09:36 3: ABFALL myAbfall - CALENDAR:Abfall triggered, updating ABFALL myAbfall ...
2018.01.06 14:09:36 3: ABFALL_UPDATE
2018.01.06 14:09:37 1: Perfmon: possible freeze starting at 14:09:35, delay is 2.38
2018.01.06 14:09:45 1: Perfmon: possible freeze starting at 14:09:42, delay is 3.399
2018.01.06 14:09:47 1: Perfmon: possible freeze starting at 14:09:46, delay is 1.355
2018.01.06 14:09:49 1: Timeout for WOL_Ping reached, terminated process 2873
2018.01.06 14:09:49 3: BlockingCall for IMAC was aborted
2018.01.06 14:09:55 1: Perfmon: possible freeze starting at 14:09:53, delay is 2.733
2018.01.06 14:10:16 1: Perfmon: possible freeze starting at 14:10:13, delay is 3.43
2018.01.06 14:10:44 1: Perfmon: possible freeze starting at 14:10:42, delay is 2.835
2018.01.06 14:10:56 1: Perfmon: possible freeze starting at 14:10:55, delay is 1.247
2018.01.06 14:11:00 1: Perfmon: possible freeze starting at 14:10:57, delay is 3.242
2018.01.06 14:11:07 1: Perfmon: possible freeze starting at 14:11:05, delay is 2.534
2018.01.06 14:11:13 1: Perfmon: possible freeze starting at 14:11:10, delay is 3.413
2018.01.06 14:11:21 1: Perfmon: possible freeze starting at 14:11:20, delay is 1.064
2018.01.06 14:11:25 1: Perfmon: possible freeze starting at 14:11:23, delay is 2.528
2018.01.06 14:11:31 1: Perfmon: possible freeze starting at 14:11:28, delay is 3.237
2018.01.06 14:11:45 1: Perfmon: possible freeze starting at 14:11:42, delay is 3.405
2018.01.06 14:11:48 1: Perfmon: possible freeze starting at 14:11:46, delay is 2.163
2018.01.06 14:11:56 1: Perfmon: possible freeze starting at 14:11:54, delay is 2.715
2018.01.06 14:11:57 1: Timeout for WOL_Ping reached, terminated process 2980
2018.01.06 14:11:57 3: BlockingCall for MacBookPro2017 was aborted
2018.01.06 14:11:57 1: Timeout for WOL_Ping reached, terminated process 2981
2018.01.06 14:11:57 3: BlockingCall for DS1010 was aborted
2018.01.06 14:11:57 1: Timeout for WOL_Ping reached, terminated process 2982
2018.01.06 14:11:57 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.06 14:12:04 1: Perfmon: possible freeze starting at 14:12:03, delay is 1.412
2018.01.06 14:12:16 1: Perfmon: possible freeze starting at 14:12:13, delay is 3.446
2018.01.06 14:12:21 1: Perfmon: possible freeze starting at 14:12:18, delay is 3.295
2018.01.06 14:12:23 1: Perfmon: possible freeze starting at 14:12:22, delay is 1.544
2018.01.06 14:12:45 1: Perfmon: possible freeze starting at 14:12:42, delay is 3.643
2018.01.06 14:13:01 1: Perfmon: possible freeze starting at 14:12:58, delay is 3.002
2018.01.06 14:13:08 1: Perfmon: possible freeze starting at 14:13:05, delay is 3.456
2018.01.06 14:13:10 1: Perfmon: possible freeze starting at 14:13:09, delay is 1.947
2018.01.06 14:13:14 1: Perfmon: possible freeze starting at 14:13:11, delay is 3.741
2018.01.06 14:13:29 1: Perfmon: possible freeze starting at 14:13:25, delay is 4.151
2018.01.06 14:13:29 1: Timeout for WOL_Ping reached, terminated process 3035
2018.01.06 14:13:29 3: BlockingCall for winserver was aborted
2018.01.06 14:13:45 1: Perfmon: possible freeze starting at 14:13:42, delay is 3.409
2018.01.06 14:13:57 1: Perfmon: possible freeze starting at 14:13:54, delay is 3.452
2018.01.06 14:13:59 1: Perfmon: possible freeze starting at 14:13:58, delay is 1.203
2018.01.06 14:14:13 1: Perfmon: possible freeze starting at 14:14:12, delay is 1.484
2018.01.06 14:14:17 1: Perfmon: possible freeze starting at 14:14:14, delay is 3.217
2018.01.06 14:14:22 1: Perfmon: possible freeze starting at 14:14:19, delay is 3.289
2018.01.06 14:14:27 1: Perfmon: possible freeze starting at 14:14:24, delay is 3.281
2018.01.06 14:14:44 1: Perfmon: possible freeze starting at 14:14:42, delay is 2.784
2018.01.06 14:14:48 1: Perfmon: possible freeze starting at 14:14:47, delay is 1.398
2018.01.06 14:15:01 1: Perfmon: possible freeze starting at 14:14:58, delay is 3.352
2018.01.06 14:15:08 1: Perfmon: possible freeze starting at 14:15:05, delay is 3.475
2018.01.06 14:15:22 1: Perfmon: possible freeze starting at 14:15:21, delay is 1.147
2018.01.06 14:15:29 1: Perfmon: possible freeze starting at 14:15:26, delay is 3.437
2018.01.06 14:15:31 1: Perfmon: possible freeze starting at 14:15:30, delay is 1.91
2018.01.06 14:15:40 1: Perfmon: possible freeze starting at 14:15:39, delay is 1.449
2018.01.06 14:15:45 1: Perfmon: possible freeze starting at 14:15:42, delay is 3.445
2018.01.06 14:15:57 1: Perfmon: possible freeze starting at 14:15:55, delay is 2.752
2018.01.06 14:16:17 1: Perfmon: possible freeze starting at 14:16:14, delay is 3.269
2018.01.06 14:16:22 1: Perfmon: possible freeze starting at 14:16:19, delay is 3.329
2018.01.06 14:16:27 1: Perfmon: possible freeze starting at 14:16:24, delay is 3.283
2018.01.06 14:16:45 1: Perfmon: possible freeze starting at 14:16:42, delay is 3.491
2018.01.06 14:16:47 1: Perfmon: possible freeze starting at 14:16:46, delay is 1.011
2018.01.06 14:17:01 1: Perfmon: possible freeze starting at 14:16:58, delay is 3.477
2018.01.06 14:17:08 1: Perfmon: possible freeze starting at 14:17:05, delay is 3.473
2018.01.06 14:17:12 1: Perfmon: possible freeze starting at 14:17:09, delay is 3.385
2018.01.06 14:17:29 1: Perfmon: possible freeze starting at 14:17:26, delay is 3.381
2018.01.06 14:17:45 1: Perfmon: possible freeze starting at 14:17:42, delay is 3.392


addtime sieht so aus:

Code Auswählen Erweitern

active-timers: 95; max-active timers: 108; max-timer-load: 16  min-tmrHandlingTm: 1.4ms; max-tmrHandlingTm: 12418.8ms; totAvgDly: 541.8ms
min-timersortTm: 1.2ms; max-timersortTm: 26.1ms

name                                     function                               max    count      total  average   maxDly   avgDly TS Max call     param Max call
tmr-statistics_PeriodChange              HASH(0x490a3b0)                      11179        3   30538.56 10179.52   986.28   461.71 06.01. 11:00:06 HASH(stat_temperature_humidity)
vbus                                     VBUSLAN_Read                          8689    84293 2793371.11    33.14     0.00     0.00 06.01. 10:24:01 HASH(vbus)
HMLAN1                                   HMLAN_Read                            6333     2748  722517.01   262.92     0.00     0.00 06.01. 10:29:21 HASH(HMLAN1)
doif_KaminStatus                         DOIF_Notify                           5194    18886 1559100.23    82.55     0.00     0.00 06.01. 10:23:58 HASH(doif_KaminStatus); HASH(VBUSDEV_7321)
StatusKamin                              dummy_Set                             4442     3122 1329635.15   425.89     0.00     0.00 06.01. 10:23:57 HASH(StatusKamin); StatusKamin; aus
HMLAN2                                   HMLAN_Read                            3686     2591  292693.85   112.97     0.00     0.00 06.01. 10:27:32 HASH(HMLAN2)
doif_Kamin_Holz_nachlegen                DOIF_Notify                           3233    18886 1769599.65    93.70     0.00     0.00 06.01. 10:23:57 HASH(doif_Kamin_Holz_nachlegen); HASH(StatusKamin)
HMLAN2                                   HMLAN_Ready                           3006      698    4066.78     5.83     0.00     0.00 06.01. 11:35:39 HASH(HMLAN2)
HMLAN3                                   HMLAN_Read                            2536     2166  154090.13    71.14     0.00     0.00 06.01. 10:27:35 HASH(HMLAN3)
Holz_nachlegen                           dummy_Set                             2492     6244 1315590.88   210.70     0.00     0.00 06.01. 10:23:56 HASH(Holz_nachlegen); Holz_nachlegen; nein
harmony                                  harmony_Read                          2446      296    3092.40    10.45     0.00     0.00 06.01. 10:20:15 HASH(harmony)
myJeeLink                                JeeLink_Read                          1814     8173  419005.18    51.27     0.00     0.00 06.01. 10:27:29 HASH(myJeeLink)
HMLAN4                                   HMLAN_Read                            1749     2518  181932.33    72.25     0.00     0.00 06.01. 12:20:18 HASH(HMLAN4)
CUL_0                                    CUL_Read                              1709      731  163172.22   223.22     0.00     0.00 06.01. 12:24:35 HASH(CUL_0)
doif_kaminstatus_gesamt                  DOIF_Notify                           1697    18886  885179.34    46.87     0.00     0.00 06.01. 10:31:11 HASH(doif_kaminstatus_gesamt); HASH(Holz_nachlegen)
tmr-at_Exec                              HASH(0x548c480)                       1553     2113  622739.99   294.72 12659.60   637.58 06.01. 10:31:31 HASH(WattUsageAnDummy)
stat_temperature_humidity                statistics_Notify                     1352    18886   98398.92     5.21     0.00     0.00 06.01. 10:25:29 HASH(stat_temperature_humidity); HASH(eg_wg_Wandthermostat_Climate)
tmr-CUL_HM_ActCheck                      ActionDetector                        1219       18    2920.96   162.28  3363.61  1165.64 06.01. 12:19:25 ActionDetector
tmr-HMLAN_KeepAliveCheck                 keepAliveCk                           1167     1651    1380.95     0.84  4993.52   530.82 06.01. 11:35:31 keepAliveCk:HMLAN2
Viessmann                                VCONTROL_Read                         1164     6375  140752.60    22.08     0.00     0.00 06.01. 10:29:41 HASH(Viessmann)
stat_StatusKamin                         statistics_Notify                     1006    18886  229265.34    12.14     0.00     0.00 06.01. 10:28:43 HASH(stat_StatusKamin); HASH(StatusKamin)
Status_Kamin_gesamt                      dummy_Set                              952     6244  430715.37    68.98     0.00     0.00 06.01. 10:31:10 HASH(Status_Kamin_gesamt); Status_Kamin_gesamt; aus
Fenster_monitoring                       monitoring_Notify                      840    18886 4262341.87   225.69     0.00     0.00 06.01. 10:31:33 HASH(Fenster_monitoring); HASH(HMLAN1)
tmr-statistics_PeriodChange              HASH(0x490f2b8)                        673        3    1325.61   441.87 11485.37  7513.20 06.01. 12:59:55 HASH(stat_Viessmann)
tmr-CUL_HM_respPendTout                  respPend                               635       24    3819.16   159.13  3391.60   644.93 06.01. 13:06:40 respPend:23A83F
ls_licht_eg_wc                           LightScene_Notify                      622    18886    2782.31     0.15     0.00     0.00 06.01. 10:45:07 HASH(ls_licht_eg_wc); HASH(eg_wc_licht)
ls_licht_kg_fo                           LightScene_Notify                      611    18886    2765.97     0.15     0.00     0.00 06.01. 11:52:55 HASH(ls_licht_kg_fo); HASH(kg_fo_licht_ankleide)
ls_licht_kg_fl                           LightScene_Notify                      607    18886    5062.78     0.27     0.00     0.00 06.01. 11:52:41 HASH(ls_licht_kg_fl); HASH(kg_fl_licht_treppenhaus)
ls_licht_eg_ku                           LightScene_Notify                      604    18886    2652.23     0.14     0.00     0.00 06.01. 10:52:32 HASH(ls_licht_eg_ku); HASH(eg_ku_kuechentisch)
stat_Viessmann                           statistics_Notify                      591    18886   75451.66     4.00     0.00     0.00 06.01. 10:29:41 HASH(stat_Viessmann); HASH(Viessmann)
tmr-Spotify_poll                         HASH(0x4b1c4e8)                        556       35    2102.93    60.08  3793.84   780.96 06.01. 11:37:22 HASH(Spotify_Gunther)
Geburtstage                              CALVIEW_Notify                         458    18886    3808.80     0.20     0.00     0.00 06.01. 13:04:46 HASH(Geburtstage); HASH(GeburtstagsKalender)
myAbfall                                 ABFALL_Notify                          380    18886    9293.50     0.49     0.00     0.00 06.01. 10:49:16 HASH(myAbfall); HASH(Abfall)
tmr-statistics_PeriodChange              HASH(0x4cc2638)                        369        3     978.13   326.04 11183.87  3737.46 06.01. 11:59:55 HASH(stat_StatusKamin)
DEVICES_HMLAN2_RSSI_RG                   readingsGroup_Notify                   361    18886    3710.24     0.20     0.00     0.00 06.01. 10:31:53 HASH(DEVICES_HMLAN2_RSSI_RG); HASH(global)
tmr-Twilight_sunpos                      HASH(0x5973268)                        356        1     356.58   356.58    53.65    53.65 06.01. 12:42:27 HASH(au_blaue_Stunde_sunpos)
rg_Batteriestatus                        readingsGroup_Notify                   355    18886    4491.35     0.24     0.00     0.00 06.01. 10:31:54 HASH(rg_Batteriestatus); HASH(global)
DEVICES_HMLAN1_RSSI_RG                   readingsGroup_Notify                   338    18886    6275.57     0.33     0.00     0.00 06.01. 10:31:52 HASH(DEVICES_HMLAN1_RSSI_RG); HASH(global)
STATISTICS                               statistics_Notify                      338    18886   16266.22     0.86     0.00     0.00 06.01. 11:46:21 HASH(STATISTICS); HASH(Aussentemperatur)
tmr-Twilight_sunpos                      HASH(0x69e5988)                        323        1     323.43   323.43     4.35     4.35 06.01. 11:27:19 HASH(au_blaue_Stunde_sunpos)
tmr-harmony_connect                      HASH(0x4fb6468)                        312        1     312.63   312.63     4.01     4.01 06.01. 10:20:03 HASH(harmony)


Besteht die Möglichkeit Devices vorübergehend zu deaktivieren ohne diese aus der fhem.cfg zu löschen?
Konkret geht es mir darum ein paar Module, die ich im Verdacht habe mal rauszunehmen:
Viessmann, VBUS, Traffic, statistics,...

[Amenophis86]

ja mit dem Attribut disable kannst du es ausschalten, muss aber im Modul eingebaut sein. Alternativ kannst du dir die RAW Defintion anschauen, diese irgendwo speichern und dann kannste es später ohne Probleme wieder neu anlagen mit sämtlichen alten Readings.

[Gunther]

An der Hardware scheint es schonmal nicht zu liegen. Zumindest kommen keine freezes wenn ich die example cfg nutze.

Mein Versuch einige Dinge rauszunehmen war leider nicht erfolgreich.

Werde jetzt mal iterativ Zeilen in die Standaed fhem.cfg dazupacken und beobachten wann die freezes losgehen.

Kann natürlich sein, dass der Pi3 an der Grenze ist wenn der ganze Rotz (12.000 Zeilen) drin ist.

[Gunther]

Zur Sicherheit habe ich heute nochmal meine FHEM PI Version gecheckt.
Ich bin noch auf einem RPI2b unterwegs.
Erklärt das zum Teil die Freezes?

[frank]

was macht eigentlich vbus?
ich vermute, apptime lief 2-3 tage. wieso gibt es dann ca. 85000 aufrufe. ca alle 3 sekunden, oder?

ebenso alle dinge, die mit dem kamin zu tun haben. ca 20000 counts. sehr viele einträge haben exakt die selbe anzahl.

scheint wohl lebenswichtig zu sein. 

[Gunther]

VBUS ist ein Modul das meine Vissmann Solar (Kamin) Steuerung ausliest. Konkret liest Sie einen Resol Datenlogger, der an der Viessmann Steuerung hängt aus.
Bekomme das Ding nicht in Zaum (Events).
Hier ein List:

Code Auswählen Erweitern

Internals:
   CHANGED   
   CODE       7321
   DEF        7321
   IODev      vbus
   LASTInputDev vbus
   MSGCNT     948
   NAME       VBUSDEV_7321
   NR         660
   STATE      Defined
   TYPE       VBUSDEV
   vbus_MSGCNT 948
   vbus_RAWMSG aa100021731000011238d8005e011b01b8221002d400b822b822b822b822b822b822000000000000000000000000c80f000017000000000000000000000000000000000055000000000002010903a1500220
   vbus_TIME  2018-01-07 12:42:47
   READINGS:
     2017-03-06 22:05:19   Pumpe-Kamin     0 %
     2017-03-06 22:05:19   Pumpe-Solar-Panel 0 %
     2017-03-06 22:05:19   Temp-Kamin-Wassertasche 72.4 °C
     2017-03-06 22:05:19   Temp-Puffer-oben 68.7 °C
     2017-03-06 22:05:19   Temp-Puffer-unten 43.2 °C
     2017-03-06 22:05:19   Temp-Solar-Panel 22.9 °C
     2018-01-07 12:42:47   controllerversion 258
     2018-01-07 12:42:47   errormask       0
     2018-01-07 12:42:47   impulse_I01     0
     2018-01-07 12:42:47   impulse_I02     0
     2018-01-07 12:42:47   insolation      0 W/qm
     2018-01-07 12:42:47   relaisusagemask 85
     2018-01-07 12:42:47   sensorbrokemask 4040
     2018-01-07 12:42:47   sensorshortmask 0
     2018-01-07 12:42:47   sensorusagemask 23
     2018-01-07 12:42:47   speed_R01       0 %
     2018-01-07 12:42:47   speed_R02       0 %
     2018-01-07 12:42:47   speed_R03       0 %
     2018-01-07 12:42:47   speed_R04       0 %
     2018-01-07 12:42:47   speed_R05       0 %
     2018-01-07 12:42:47   speed_R06       0 %
     2018-01-07 12:42:47   speed_R07       0 %
     2018-01-07 12:42:47   speed_R08       0 %
     2018-01-07 12:42:47   speed_R09       0 %
     2018-01-07 12:42:47   systemtime      777
     2018-01-07 12:42:47   temperature_T01 22 °C
     2018-01-07 12:42:47   temperature_T02 35 °C
     2018-01-07 12:42:47   temperature_T03 28.5 °C
     2018-01-07 12:42:47   temperature_T05 53 °C
     2018-01-07 12:42:47   temperature_T06 21.5 °C
     2018-01-07 12:42:47   warningmask     0
Attributes:
   IODev      vbus
   event-min-interval .*:120
   event-on-change-reading .*
   model      Vitosolic200
   room       00_KG_Heizungsraum,G_VBUS

Kamin sind meine geistigen Ergüsse der letzten Monate.

Aber auch ohne Kamin

[frank]

in diesem modul kannst du events weiter reduzieren, indem du bei event-on-change eine liste der wirklich benötigten readings angibst anstatt ".*". zusätzlich kann man bei jedem reading auch noch einen treshhold setzen.

funktioniert im modul überhaupt event-on-change? teste im eventmonitor mit hilfe der filterfunktion.

vorrangig solltest du aber den input reduzieren. wird der takt vom datenlogger vorgegeben? pusht er? kannst du ihn nicht drosseln?

was ist mit dem io vbus? kann man hier drosseln? gibt es hier auch events?

eventuell solltest du alles was mit vbus, auch indirekt, zu tun hat, in ein externes fhem auslagern.

[nils_]

sehr viele einträge haben exakt die selbe anzahl.

das ist mir auch aufgefallen.

evtl. mal die notifys prüfen oder eins posten, damit wir uns das angucken können