FB_CALLMONITOR trotz disabeld 1 , blockiert Fhem ca 3 Sekunden
Meine FB ist gerade nicht existent, deswegen steht das Modul auf disable
aktuell behelfe ich mir, das ich das Modul lösche.
Internals:
DEF 192.168.2.1
DeviceName 192.168.2.1:1012
NAME Anrufliste
NEXT_OPEN 1477049862.3877
NR 502
NTFY_ORDER 50-Anrufliste
PARTIAL
STATE disconnected
TYPE FB_CALLMONITOR
Readings:
2016-10-21 13:36:42 state disconnected
Helper:
Bm:
Fb_callmonitor_attr:
cnt 1
dmx 0
mAr
max 0
tot 0
Fb_callmonitor_get:
cnt 8
dmx 0
mAr
max 0
tot 0
Fb_callmonitor_notify:
cnt 2632
dmx 0
max 10
tot 10
mAr:
HASH(0x1aa9688)
HASH(0x131f780)
Fb_callmonitor_ready:
cnt 18186
dmx 0
max 3012
tot 440646
mAr:
HASH(0x1aa9688)
Fb_callmonitor_set:
cnt 20
dmx 0
mAr
max 0
tot 0
Attributes:
answMachine-is-missed-call 1
disable 1
room Test
stateFormat state<br>last missed_call
2016.10.21 13:37:45.395 1: Perfmon: possible freeze starting at 13:37:43, delay is 2.395
2016.10.21 13:36:42.395 1: Perfmon: possible freeze starting at 13:36:40, delay is 2.395
2016.10.21 13:35:39.395 1: Perfmon: possible freeze starting at 13:35:37, delay is 2.394
2016.10.21 13:34:36.397 1: Perfmon: possible freeze starting at 13:34:34, delay is 2.397
2016.10.21 13:33:33.395 1: Perfmon: possible freeze starting at 13:33:31, delay is 2.395
2016.10.21 13:32:30.395 1: Perfmon: possible freeze starting at 13:32:28, delay is 2.395
2016.10.21 13:31:27.395 1: Perfmon: possible freeze starting at 13:31:25, delay is 2.394
2016.10.21 13:30:24.395 1: Perfmon: possible freeze starting at 13:30:22, delay is 2.395
2016.10.21 13:29:21.397 1: Perfmon: possible freeze starting at 13:29:19, delay is 2.396
2016.10.21 13:28:18.395 1: Perfmon: possible freeze starting at 13:28:16, delay is 2.395
2016.10.21 13:27:15.395 1: Perfmon: possible freeze starting at 13:27:13, delay is 2.395
2016.10.21 13:26:12.395 1: Perfmon: possible freeze starting at 13:26:10, delay is 2.395
2016.10.21 13:25:09.395 1: Perfmon: possible freeze starting at 13:25:07, delay is 2.394
2016.10.21 13:24:06.395 1: Perfmon: possible freeze starting at 13:24:04, delay is 2.395
2016.10.21 13:23:03.397 1: Perfmon: possible freeze starting at 13:23:01, delay is 2.397
2016.10.21 13:22:00.395 1: Perfmon: possible freeze starting at 13:21:58, delay is 2.395
2016.10.21 13:20:57.395 1: Perfmon: possible freeze starting at 13:20:55, delay is 2.394
2016.10.21 13:19:54.395 1: Perfmon: possible freeze starting at 13:19:52, delay is 2.394
2016.10.21 13:18:51.395 1: Perfmon: possible freeze starting at 13:18:49, delay is 2.395
2016.10.21 13:17:48.395 1: Perfmon: possible freeze starting at 13:17:46, delay is 2.395
......
2016.10.21 11:04:27.099 1: Perfmon: possible freeze starting at 11:04:24, delay is 3.099
2016.10.21 11:03:24.008 1: Perfmon: possible freeze starting at 11:03:21, delay is 3.008
Auch das FRITZBOX Modul lebt noch trotz disable, allerdings blockiert es nicht länger einer Sekunde.
define FritzBox FRITZBOX 192.168.2.1
attr FritzBox allowTR064Command 1
attr FritzBox disable 1
attr FritzBox event-on-change-reading .*
attr FritzBox room Test
PS. Update Fhem heute
Hallo Hary,
ich habe FB_CALLMONITOR soeben auf Non-Blocking Connect umgestellt, so dass der Verbindungsaufbau in diesem Fall keinen Freeze verursacht. Desweiteren wird die Verbindung nun geschlossen, wenn das Device disabled ist.
Gibt es ab morgen.
Gruß
Markus
danke, disable funktioniert jetzt ohne freeze :D