Hallo alle zusammen,
ich habe ein starkes Freeze in meiner FHEM Installation:
2018.06.02 17:46:51.588 1: Perfmon: possible freeze starting at 17:46:50, delay is 1.587
2018.06.02 17:46:54.600 1: Perfmon: possible freeze starting at 17:46:53, delay is 1.599
2018.06.02 17:46:58.951 1: Perfmon: possible freeze starting at 17:46:57, delay is 1.951
2018.06.02 17:47:02.098 1: Perfmon: possible freeze starting at 17:47:00, delay is 2.098
2018.06.02 17:47:08.393 1: Perfmon: possible freeze starting at 17:47:07, delay is 1.393
2018.06.02 17:47:13.554 1: Perfmon: possible freeze starting at 17:47:12, delay is 1.553
Apptime sagt das:
name function max count total average maxDly avgDly TS Max call param Max call
tmr-HUEDevice_GetUpdate HASH(0x3094408) 2186 42 25488.66 606.87 2564.45 886.67 02.06. 17:46:58 HASH(br_switch)
tmr-HUEDevice_GetUpdate HASH(0x2cd4790) 1998 42 27517.75 655.18 2168.54 865.04 02.06. 17:46:25 HASH(Livingroomswitch)
WEB_127.0.0.1_53794 FW_Read 706 9 1426.81 158.53 0.00 0.00 02.06. 17:47:17 HASH(WEB_127.0.0.1_53794)
WEB_127.0.0.1_53708 FW_Read 705 13 803.38 61.80 0.00 0.00 02.06. 17:46:40 HASH(WEB_127.0.0.1_53708)
ZWAVE1 ZWDongle_Read 83 42 1177.66 28.04 0.00 0.00 02.06. 17:47:17 HASH(ZWAVE1)
tmr-HUEBridge_GetUpdate HASH(0x20483b8) 77 1 77.30 77.30 1440.43 1440.43 02.06. 17:46:54 HASH(homeBridge)
wz_XBMC XBMC_Ready 69 160 97.29 0.61 0.00 0.00 02.06. 17:47:02 HASH(wz_XBMC)
tmr-RESIDENTStk_DurationTimer HASH(0x40f3618) 31 1 31.73 31.73 0.76 0.76 02.06. 17:46:59 HASH(gr_Bewohner_DurationTimer)
WEB_127.0.0.1_53726 FW_Read 27 3 31.79 10.60 0.00 0.00 02.06. 17:46:49 HASH(WEB_127.0.0.1_53726)
tmr-RESIDENTStk_DurationTimer HASH(0x41c64e0) 26 1 26.52 26.52 0.85 0.85 02.06. 17:46:59 HASH(rr_Kay_DurationTimer)
myJeeLink JeeLink_Read 24 11 81.17 7.38 0.00 0.00 02.06. 17:46:56 HASH(myJeeLink)
logdb DbLog_Log 22 50 756.26 15.13 0.00 0.00 02.06. 17:47:17 HASH(logdb); HASH(KU_Waschmaschine)
WEB_127.0.0.1_53770 FW_Read 17 2 20.90 10.45 0.00 0.00 02.06. 17:46:49 HASH(WEB_127.0.0.1_53770)
tmr-perfmon_ProcessTimer HASH_unnamed 4 54 13.46 0.25 2149.40 819.41 02.06. 17:47:25 HASH(0xd77008)
WEB_127.0.0.1_53722 FW_Read 3 2 5.54 2.77 0.00 0.00 02.06. 17:46:40 HASH(WEB_127.0.0.1_53722)
WEB_127.0.0.1_53720 FW_Read 3 6 12.86 2.14 0.00 0.00 02.06. 17:46:42 HASH(WEB_127.0.0.1_53720)
WEB_127.0.0.1_53814 FW_Read 3 3 7.51 2.50 0.00 0.00 02.06. 17:46:58 HASH(WEB_127.0.0.1_53814)
WEB_127.0.0.1_53730 FW_Read 3 1 3.03 3.03 0.00 0.00 02.06. 17:46:40 HASH(WEB_127.0.0.1_53730)
WEB_127.0.0.1_53812 FW_Read 2 8 13.16 1.64 0.00 0.00 02.06. 17:46:56 HASH(WEB_127.0.0.1_53812)
plex:serverDiscoveryMcast plex_Read 2 8 15.10 1.89 0.00 0.00 02.06. 17:46:40 HASH(plex:serverDiscoveryMcast)
WEB_127.0.0.1_53820 FW_Read 2 5 8.80 1.76 0.00 0.00 02.06. 17:46:56 HASH(WEB_127.0.0.1_53820)
WEB_127.0.0.1_53900 FW_Read 2 1 2.15 2.15 0.00 0.00 02.06. 17:47:17 HASH(WEB_127.0.0.1_53900)
tmr-DOIF_TimerTrigger REF(0x42eb308) 2 1 2.10 2.10 0.98 0.98 02.06. 17:47:18 REF(0x42eb308)
n_KU_Waschmaschine_start notify_Exec 2 29 52.67 1.82 0.00 0.00 02.06. 17:46:45 HASH(n_KU_Waschmaschine_start); HASH(KU_Waschmaschine)
tmr-DOIF_TimerTrigger REF(0x47799e0) 2 1 2.07 2.07 1388.96 1388.96 02.06. 17:47:08 REF(0x47799e0)
tmr-DOIF_TimerTrigger REF(0x4637a00) 2 1 2.04 2.04 1142.65 1142.65 02.06. 17:47:02 REF(0x4637a00)
tmr-DOIF_TimerTrigger REF(0x47ec6d8) 2 1 2.04 2.04 1583.67 1583.67 02.06. 17:46:51 REF(0x47ec6d8)
tmr-DOIF_TimerTrigger REF(0x48817d8) 2 1 2.04 2.04 56.22 56.22 02.06. 17:47:23 REF(0x48817d8)
tmr-DOIF_TimerTrigger REF(0x44703f0) 2 1 2.03 2.03 1066.45 1066.45 02.06. 17:47:29 REF(0x44703f0)
tmr-DOIF_TimerTrigger REF(0x47df4f8) 2 1 2.03 2.03 1053.65 1053.65 02.06. 17:47:35 REF(0x47df4f8)
tmr-DOIF_TimerTrigger REF(0x47e9cf8) 2 1 2.03 2.03 1699.22 1699.22 02.06. 17:46:39 REF(0x47e9cf8)
tmr-DOIF_TimerTrigger REF(0x47fe680) 2 1 2.02 2.02 1716.82 1716.82 02.06. 17:46:45 REF(0x47fe680)
tmr-DOIF_TimerTrigger REF(0x4605948) 2 1 2.02 2.02 1662.89 1662.89 02.06. 17:46:22 REF(0x4605948)
tmr-DOIF_TimerTrigger REF(0x42eaef8) 2 1 2.02 2.02 596.75 596.75 02.06. 17:47:13 REF(0x42eaef8)
tmr-DOIF_TimerTrigger REF(0x47e3a90) 2 1 2.02 2.02 515.96 515.96 02.06. 17:46:56 REF(0x47e3a90)
tmr-DOIF_TimerTrigger REF(0x487ea48) 2 1 2.02 2.02 1585.84 1585.84 02.06. 17:46:51 REF(0x487ea48)
tmr-DOIF_TimerTrigger REF(0x4406978) 2 1 2.01 2.01 1745.10 1745.10 02.06. 17:46:28 REF(0x4406978)
tmr-DOIF_TimerTrigger REF(0x42ea7f0) 2 1 2.00 2.00 1391.16 1391.16 02.06. 17:47:08 REF(0x42ea7f0)
tmr-DOIF_TimerTrigger REF(0x47ce620) 1 1 2.00 2.00 1665.04 1665.04 02.06. 17:46:22 REF(0x47ce620)
tmr-DOIF_TimerTrigger REF(0x42eab98) 1 1 1.99 1.99 3.21 3.21 02.06. 17:47:18 REF(0x42eab98)
tmr-MQTT::Timer HASH(0x2b26470) 1 1 1.98 1.98 1217.13 1217.13 02.06. 17:46:59 HASH(myBroker)
Die Ursache ist wohl Hue, nur was kann ich dagegen tun?
FHEM läuft auf einen Raspberry Pi 3+ und FHEM ist upgedatet. Der Raspberry Pi und die HUE Bridge sind beide per Lan angeschlossen.
Dank für eure Hilfe.
Beste Grüße
gamelive1207