Hallo!
Hab hier ein Problem das scheinbar auch schon andere Leute hatten. Komme aber mit den Lösungsvorschlägen, die ich bereits gelesen habe, nicht weiter.
Immer mal wieder taucht in meinem Log folgendes auf:
2014.09.16 17:34:10 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.16 17:34:10 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.16 17:34:10 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.16 17:34:10 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.16 17:35:13 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.16 17:35:13 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.16 17:35:13 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.16 17:35:13 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.16 17:35:14 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.16 17:35:14 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.16 18:44:30 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.16 18:44:30 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.16 18:45:32 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.16 18:45:32 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.16 18:45:32 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.16 18:54:40 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.16 18:54:40 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.16 18:55:45 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.16 18:55:45 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.16 18:55:45 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.16 19:54:50 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.16 19:54:50 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.16 19:55:53 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.16 19:55:53 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.16 19:55:53 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.16 21:35:11 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.16 21:35:11 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.16 21:35:11 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.16 21:35:11 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.16 21:36:15 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.16 21:36:15 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.16 21:36:15 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.16 21:36:15 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.16 21:36:16 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.16 21:36:16 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.17 19:27:18 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.17 19:27:18 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.17 19:27:18 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.17 19:27:18 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.17 19:28:22 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.17 19:28:22 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.17 19:28:22 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.17 19:28:22 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.17 19:28:22 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.17 19:28:22 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.18 04:38:42 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.18 04:38:42 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.18 04:38:42 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.18 04:38:42 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.18 04:39:45 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.18 04:39:45 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.18 04:39:45 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.18 04:39:45 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.18 04:39:45 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.18 04:39:45 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.18 04:59:02 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.18 04:59:02 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.18 04:59:02 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.18 04:59:02 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.18 05:00:07 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.18 05:00:07 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.18 05:00:07 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.18 05:00:07 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.18 05:00:07 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.18 05:00:07 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.18 06:09:32 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.18 06:09:32 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.18 06:09:32 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.18 06:09:32 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.18 06:10:37 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.18 06:10:37 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.18 06:10:37 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.18 06:10:37 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.18 06:10:37 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.18 06:10:37 1: HMLAN_Parse: HMLAN1 new condition ok
Wie man sieht kommt der Fehler im Block 1-2 mal am Tag.
Dazu habe ich auch noch folgenden Fehler:
2014.09.16 15:04:01 3: HMLAN2: Unknown code A09998112999999000000::-77:HMLAN2, help me!
2014.09.16 15:04:01 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.16 15:04:01 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.16 15:04:01 3: HMLAN1: Unknown code A09998112999999000000::-78:HMLAN1, help me!
Der taucht aber nur auf wenn ich einen shutdown restart mache oder die config neu einlese.
Eingebaut habe ich die zwei HMLAN's folgendermaßen:
define vccu CUL_HM 123ABC
attr vccu IODev HMLAN1
attr vccu IOList HMLAN1, HMLAN2
attr vccu autoReadReg 4_reqStatus
attr vccu expert 2_full
attr vccu model CCU-FHEM
attr vccu subType virtual
attr vccu webCmd virtual:update
Die einzelnen von HMLAN gesteuerten Aktoren haben folgende attr:
attr Heizung.WZ.B IODev HMLAN2
attr Heizung.WZ.B IOgrp vccu:HMLAN2
Kann mir jemand sagen was die Fehler zu bedeuten haben? Einen Abriss in meinem kleinen Netzwerk?
Internals von den HMLAN's
DEF 192.168.178.200:1000
DeviceName 192.168.178.200:1000
FD 9
HMLAN1_MSGCNT 6375
HMLAN1_TIME 2014-09-19 10:13:09
NAME HMLAN1
NR 24
NTFY_ORDER 50-HMLAN1
PARTIAL
RAWMSG E2483AC,0000,27E52B8B,FF,FFD8,E186102483AC0000000A88E00F0014
RSSI -40
STATE opened
TYPE HMLAN
XmitOpen 1
assignedIDsCnt 2
msgKeepAlive dlyMax:9.645 bufferMin:-4
msgLoadEst 1hour:0% 10min steps: 0/0/0/0/0/0
msgParseDly min:-12 max:9265 last:6 cnt:6313
owner 123ABC
owner_CCU vccu
uptime 007 185:55:45.051
und
DEF 192.168.178.201:1000
DeviceName 192.168.178.201:1000
FD 4
HMLAN2_MSGCNT 6253
HMLAN2_TIME 2014-09-19 10:16:09
HM_CMDNR 14
NAME HMLAN2
NR 26
NTFY_ORDER 50-HMLAN2
PARTIAL
RAWMSG E255717,0000,2338F417,FF,FFC6,4486102557170000000A88E1100018
RSSI -58
STATE opened
TYPE HMLAN
XmitOpen 1
assignedIDsCnt 3
msgKeepAlive dlyMax:9.644 bufferMin:-4
msgLoadEst 1hour:0% 10min steps: 0/0/0/0/0/0
msgParseDly: min:-11 max:9184 last:5 cnt:6182
owner 123ABC
uptime 006 164:09:04.841
Vielen Dank für eure Hilfe!
Hallo, nur mal so eine Frage am Rande, hast du zufällig das WS3600 Modul in Verbindung mit fowsr auf dem Host laufen (Einbinden von USB Wetterstation) ?
Wenn ja, liegt es an fowsr. Das Script legt den Host für fast 1min lahm und dadurch gehen die HMLAN auf disconnect.
Auch: http://forum.fhem.de/index.php/topic,26740.15.html
VG
Frank
Hallo,
nein, das Modul habe ich nicht...
Trotzdem Danke!
apptime und Performance Monitor, sind zwei tools um Hänger zu finden.
sind hier im Forum gefühlte 1000 mal beschrieben.
danke, beides lasse ich die Nacht mal laufen und poste dies dann hier.
Hallo nochmal!
Hatte bereits den ersten disconnect.
Habe Apptime, PerfMon und verbose 5 laufen lassen.
2014.09.19 22:08:51 5: HMLAN/RAW: /E22E073,0000,2A747F37,FF,FFB2,8C861022E0730000000A88DB100018
2014.09.19 22:08:51 5: HMLAN_Parse: HMLAN1 R:E22E073 stat:0000 t:2A747F37 d:FF r:FFB2 m:8C 8610 22E073 000000 0A88DB100018
2014.09.19 22:08:51 5: HMLAN1 dispatch A0F8C861022E0730000000A88DB100018::-78:HMLAN1
2014.09.19 22:08:51 4: CUL_HM Heizung.WZ.B dupe: dont process
2014.09.19 22:08:55 5: HMLAN_Send: HMLAN1 I:K
2014.09.19 22:08:55 5: HMLAN_Send: HMLAN2 I:K
2014.09.19 22:08:55 5: HMLAN/RAW: /HHM-LAN-IF,03C1,JEQ0707684,1E9C46,123ABC,25C59C22,0003
2014.09.19 22:08:55 5: HMLAN_Parse: HMLAN2 V:03C1 sNo:JEQ0707684 d:1E9C46 O:123ABC t:25C59C22 IDcnt:0003
2014.09.19 22:08:55 5: HMLAN/RAW: /HHM-LAN-IF,03C1,IEQ0244964,1740D3,123ABC,2A7490DA,0002
2014.09.19 22:08:55 5: HMLAN_Parse: HMLAN1 V:03C1 sNo:IEQ0244964 d:1740D3 O:123ABC t:2A7490DA IDcnt:0002
2014.09.19 22:09:20 5: HMLAN_Send: HMLAN1 I:K
2014.09.19 22:09:20 5: HMLAN_Send: HMLAN2 I:K
2014.09.19 22:09:20 5: HMLAN/RAW: /HHM-LAN-IF,03C1,IEQ0244964,1740D3,123ABC,2A74F28B,0002
2014.09.19 22:09:20 5: HMLAN_Parse: HMLAN1 V:03C1 sNo:IEQ0244964 d:1740D3 O:123ABC t:2A74F28B IDcnt:0002
2014.09.19 22:09:20 5: HMLAN/RAW: /HHM-LAN-IF,03C1,JEQ0707684,1E9C46,123ABC,25C5FDD3,0003
2014.09.19 22:09:20 5: HMLAN_Parse: HMLAN2 V:03C1 sNo:JEQ0707684 d:1E9C46 O:123ABC t:25C5FDD3 IDcnt:0003
2014.09.19 22:09:44 4: HttpUtils url=http://weather.yahooapis.com/forecastrss?w=12835702&u=c
2014.09.19 22:09:54 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.19 22:09:54 5: Triggering HMLAN2 (1 changes)
2014.09.19 22:09:54 5: Notify loop for HMLAN2 DISCONNECTED
2014.09.19 22:09:54 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.19 22:09:54 5: Triggering HMLAN2 (5 changes)
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN2 DISCONNECTED -> DISCONNECTED
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN2 cond: disconnected -> cond: disconnected
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN2 Xmit-Events: ok:1 disconnected:2 init:1 -> Xmit-Events: ok:.* disconnected:.* init:.*
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN2 prot_disconnected: last -> prot_disconnected: last
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN2 prot_keepAlive: last -> prot_keepAlive: last
2014.09.19 22:09:54 1: 192.168.178.200:1000 disconnected, waiting to reappear (HMLAN1)
2014.09.19 22:09:54 5: Triggering HMLAN1 (1 changes)
2014.09.19 22:09:54 5: Notify loop for HMLAN1 DISCONNECTED
2014.09.19 22:09:54 1: HMLAN_Parse: HMLAN1 new condition disconnected
2014.09.19 22:09:54 5: Triggering HMLAN1 (5 changes)
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN1 DISCONNECTED -> DISCONNECTED
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN1 cond: disconnected -> cond: disconnected
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN1 Xmit-Events: ok:1 disconnected:2 init:1 -> Xmit-Events: ok:.* disconnected:.* init:.*
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN1 prot_disconnected: last -> prot_disconnected: last
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN1 prot_keepAlive: last -> prot_keepAlive: last
2014.09.19 22:09:54 1: Perfmon: possible freeze starting at 22:09:45, delay is 9.161
2014.09.19 22:09:54 4: http://weather.yahooapis.com/forecastrss?w=12835702&u=c: HTTP response code 200
2014.09.19 22:09:54 4: HttpUtils http://weather.yahooapis.com/forecastrss?w=12835702&u=c: Got data, length: 2760
2014.09.19 22:09:54 4: Weather YahooWetter: T: 16 H: 98 W: 3
2014.09.19 22:09:54 5: Triggering YahooWetter (51 changes)
2014.09.19 22:09:54 5: Notify loop for YahooWetter wind_direction: 270
2014.09.19 22:09:54 5: Wetter: not on any display, ignoring notify
2014.09.19 22:09:54 5: Wetter.Aktuell.icon: not on any display, ignoring notify
2014.09.19 22:09:54 5: Wetter.Aktuell.temp: not on any display, ignoring notify
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter wind_direction: 270 -> wind_direction: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter pressure: 1015 -> pressure: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter visibility: 10 -> visibility: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc5_code: 32 -> fc5_code: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter wind_chill: 16 -> wind_chill: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc1_low_c: 15 -> fc1_low_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc3_condition: Schauer -> fc3_condition: Schauer
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc1_day_of_week: Fr -> fc1_day_of_week: Fr
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc4_high_c: 16 -> fc4_high_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc4_code: 30 -> fc4_code: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter temperature: 16 -> temperature: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter code: 26 -> code: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc2_low_c: 14 -> fc2_low_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc2_code: 4 -> fc2_code: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc1_high_c: 25 -> fc1_high_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc2_day_of_week: Sa -> fc2_day_of_week: Sa
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc2_condition: Gewitter -> fc2_condition: Gewitter
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter pressure_trend: 1 -> pressure_trend: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc1_icon: heavyrain -> fc1_icon: heavyrain
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter current_date_time: 19 Sep 2014 8:59 pm CEST -> current_date_time: .* Sep .* .*:.* pm CEST
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter day_of_week: Fr -> day_of_week: Fr
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc4_day_of_week: Mo -> fc4_day_of_week: Mo
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter wind_speed: 3 -> wind_speed: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter pressure_trend_txt: steigend -> pressure_trend_txt: steigend
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc5_day_of_week: Di -> fc5_day_of_week: Di
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc5_low_c: 6 -> fc5_low_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc4_condition: teilweise wolkig -> fc4_condition: teilweise wolkig
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter icon: cloudy -> icon: cloudy
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc3_low_c: 9 -> fc3_low_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc4_low_c: 7 -> fc4_low_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc4_icon: partly_cloudy -> fc4_icon: partly_cloudy
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc1_condition: Gewitterregen -> fc1_condition: Gewitterregen
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter wind_condition: Wind: W 3 km/h -> wind_condition: Wind: W .* km/h
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc3_day_of_week: So -> fc3_day_of_week: So
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter wind: 3 -> wind: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc3_code: 11 -> fc3_code: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter city: Moglingen, Germany -> city: Moglingen, Germany
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc3_high_c: 20 -> fc3_high_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc3_icon: chance_of_rain -> fc3_icon: chance_of_rain
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc5_high_c: 18 -> fc5_high_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc1_code: 45 -> fc1_code: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc5_icon: sunny -> fc5_icon: sunny
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter humidity: 98 -> humidity: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc2_high_c: 24 -> fc2_high_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter temp_f: 61 -> temp_f: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter pressure_trend_sym: + -> pressure_trend_sym: +
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc5_condition: sonnig -> fc5_condition: sonnig
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter temp_c: 16 -> temp_c: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter condition: wolkig -> condition: wolkig
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter fc2_icon: thunderstorm -> fc2_icon: thunderstorm
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter T: 16 H: 98 W: 3 -> T: .* H: .* W: .*
2014.09.19 22:09:54 4: eventTypes: Weather YahooWetter state: T: 16 H: 98 W: 3 -> state: T: .* H: .* W: .*
2014.09.19 22:10:55 1: 192.168.178.201:1000 reappeared (HMLAN2)
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:A123ABC
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:C
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:+255717,00,01,00
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:+25572D,00,01,00
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:+22E073,00,01,00
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:Y01,00,
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:Y02,00,
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:Y03,00,
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 I:T1BAF4A4F,04,00,00000000
2014.09.19 22:10:55 1: HMLAN_Parse: HMLAN2 new condition init
2014.09.19 22:10:55 5: Triggering HMLAN2 (3 changes)
2014.09.19 22:10:55 5: Notify loop for HMLAN2 cond: init
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 cond: init -> cond: init
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 Xmit-Events: ok:1 disconnected:2 init:2 -> Xmit-Events: ok:.* disconnected:.* init:.*
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 prot_init: last -> prot_init: last
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN2 S:S8F89F22E stat: 00 t:00000000 d:01 r:8F89F22E m:99 8112 123ABC 000000
2014.09.19 22:10:55 5: Triggering HMLAN2 (1 changes)
2014.09.19 22:10:55 5: Notify loop for HMLAN2 CONNECTED
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 CONNECTED -> CONNECTED
2014.09.19 22:10:55 1: 192.168.178.200:1000 reappeared (HMLAN1)
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:A123ABC
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:C
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:+2483AC,00,01,00
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:+24DEFC,00,01,FE1F
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:Y01,00,
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:Y02,00,
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:Y03,00,
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 I:T1BAF4A4F,04,00,00000000
2014.09.19 22:10:55 1: HMLAN_Parse: HMLAN1 new condition init
2014.09.19 22:10:55 5: Triggering HMLAN1 (3 changes)
2014.09.19 22:10:55 5: Notify loop for HMLAN1 cond: init
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 cond: init -> cond: init
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 Xmit-Events: ok:1 disconnected:2 init:2 -> Xmit-Events: ok:.* disconnected:.* init:.*
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 prot_init: last -> prot_init: last
2014.09.19 22:10:55 5: HMLAN_Send: HMLAN1 S:S8F89F29F stat: 00 t:00000000 d:01 r:8F89F29F m:99 8112 123ABC 000000
2014.09.19 22:10:55 5: Triggering HMLAN1 (1 changes)
2014.09.19 22:10:55 5: Notify loop for HMLAN1 CONNECTED
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 CONNECTED -> CONNECTED
2014.09.19 22:10:55 5: HMLAN/RAW: /HHM-LAN-IF,03C1,JEQ0707684,1E9C46,123ABC,25C76F21,0003
E25572D,0000,25C680F1,FF,FFC8,BD861025572D0000000A88E2100018
E2483AC,0000,25C7261F,FF,FFB1,FD86102483AC0000000A88E60F0014
E22E073,0000,25C76CF9,FF,FFBB,8D861022E0730000000A88DB100018
I00,00,00,00
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN2 V:03C1 sNo:JEQ0707684 d:1E9C46 O:123ABC t:25C76F21 IDcnt:0003
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN2 R:E25572D stat:0000 t:25C680F1 d:FF r:FFC8 m:BD 8610 25572D 000000 0A88E2100018
2014.09.19 22:10:55 5: HMLAN2 dispatch A0FBD861025572D0000000A88E2100018::-56:HMLAN2
2014.09.19 22:10:55 5: Triggering Heizung.WZ.A (5 changes)
2014.09.19 22:10:55 5: Notify loop for Heizung.WZ.A measured-temp: 22.6
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A measured-temp: 22.6 -> measured-temp: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A batteryLevel: 3.1 -> batteryLevel: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A actuator: 0 -> actuator: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A battery: ok -> battery: ok
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A desired-temp: 17.0 -> desired-temp: .*
2014.09.19 22:10:55 5: Triggering Heizung.WZ.A1 (2 changes)
2014.09.19 22:10:55 5: Notify loop for Heizung.WZ.A1 measured-temp: 22.6
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A1 measured-temp: 22.6 -> measured-temp: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A1 22.6 -> .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.A1 state: 22.6 -> state: .*
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN2 R:E2483AC stat:0000 t:25C7261F d:FF r:FFB1 m:FD 8610 2483AC 000000 0A88E60F0014
2014.09.19 22:10:55 5: HMLAN2 dispatch A0FFD86102483AC0000000A88E60F0014::-79:HMLAN2
2014.09.19 22:10:55 5: Triggering Heizung.DG (5 changes)
2014.09.19 22:10:55 5: Notify loop for Heizung.DG measured-temp: 23.0
2014.09.19 22:10:55 5: Heizung.DG.Bat: not on any display, ignoring notify
2014.09.19 22:10:55 5: Heizung.DG.IST: not on any display, ignoring notify
2014.09.19 22:10:55 5: Heizung.DG.Ventil: not on any display, ignoring notify
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG measured-temp: 23.0 -> measured-temp: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG batteryLevel: 3 -> batteryLevel: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG actuator: 0 -> actuator: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG battery: ok -> battery: ok
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG desired-temp: 17.0 -> desired-temp: .*
2014.09.19 22:10:55 5: Triggering Heizung.DG1 (2 changes)
2014.09.19 22:10:55 5: Notify loop for Heizung.DG1 measured-temp: 23.0
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG1 measured-temp: 23.0 -> measured-temp: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG1 23.0 -> .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.DG1 state: 23.0 -> state: .*
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN2 R:E22E073 stat:0000 t:25C76CF9 d:FF r:FFBB m:8D 8610 22E073 000000 0A88DB100018
2014.09.19 22:10:55 5: HMLAN2 dispatch A0F8D861022E0730000000A88DB100018::-69:HMLAN2
2014.09.19 22:10:55 5: Triggering Heizung.WZ.B (5 changes)
2014.09.19 22:10:55 5: Notify loop for Heizung.WZ.B measured-temp: 21.9
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B measured-temp: 21.9 -> measured-temp: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B batteryLevel: 3.1 -> batteryLevel: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B actuator: 0 -> actuator: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B battery: ok -> battery: ok
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B desired-temp: 17.0 -> desired-temp: .*
2014.09.19 22:10:55 5: Triggering Heizung.WZ.B1 (2 changes)
2014.09.19 22:10:55 5: Notify loop for Heizung.WZ.B1 measured-temp: 21.9
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B1 measured-temp: 21.9 -> measured-temp: .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B1 21.9 -> .*
2014.09.19 22:10:55 4: eventTypes: CUL_HM Heizung.WZ.B1 state: 21.9 -> state: .*
2014.09.19 22:10:55 5: HMLAN/RAW: /HHM-LAN-IF,03C1,IEQ0244964,1740D3,123ABC,2A76644F,0002
E25572D,0000,2A7575AC,FF,FFBF,BD861025572D0000000A88E2100018
E2483AC,0000,2A761ADB,FF,FFD9,FD86102483AC0000000A88E60F0014
E22E073,0000,2A7661B4,FF,FFB0,8D861022E0730000000A88DB100018
E123ABC,0000,2
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN1 V:03C1 sNo:IEQ0244964 d:1740D3 O:123ABC t:2A76644F IDcnt:0002
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN1 R:E25572D stat:0000 t:2A7575AC d:FF r:FFBF m:BD 8610 25572D 000000 0A88E2100018
2014.09.19 22:10:55 5: HMLAN1 dispatch A0FBD861025572D0000000A88E2100018::-65:HMLAN1
2014.09.19 22:10:55 4: CUL_HM Heizung.WZ.A dupe: dont process
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN1 R:E2483AC stat:0000 t:2A761ADB d:FF r:FFD9 m:FD 8610 2483AC 000000 0A88E60F0014
2014.09.19 22:10:55 5: HMLAN1 dispatch A0FFD86102483AC0000000A88E60F0014::-39:HMLAN1
2014.09.19 22:10:55 4: CUL_HM Heizung.DG dupe: dont process
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN1 R:E22E073 stat:0000 t:2A7661B4 d:FF r:FFB0 m:8D 8610 22E073 000000 0A88DB100018
2014.09.19 22:10:55 5: HMLAN1 dispatch A0F8D861022E0730000000A88DB100018::-80:HMLAN1
2014.09.19 22:10:55 4: CUL_HM Heizung.WZ.B dupe: dont process
2014.09.19 22:10:55 5: HMLAN/RAW: /I00,00,00,00
I00,00,00,00
R8F89F22E,0002,00000000,FF,7FFF,998112123ABC000000
E123ABC,0000,25C76FED,FF,FFB0,998112123ABC000000
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN2 R:R8F89F22E stat:0002 t:00000000 d:FF r:7FFF m:99 8112 123ABC 000000
2014.09.19 22:10:55 1: HMLAN_Parse: HMLAN2 new condition ok
2014.09.19 22:10:55 5: Triggering HMLAN2 (3 changes)
2014.09.19 22:10:55 5: Notify loop for HMLAN2 cond: ok
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 cond: ok -> cond: ok
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 Xmit-Events: ok:2 disconnected:2 init:2 -> Xmit-Events: ok:.* disconnected:.* init:.*
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN2 prot_ok: last -> prot_ok: last
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN2 R:E123ABC stat:0000 t:25C76FED d:FF r:FFB0 m:99 8112 123ABC 000000
2014.09.19 22:10:55 5: HMLAN2 dispatch A09998112123ABC000000::-80:HMLAN2
2014.09.19 22:10:55 5: HMLAN/RAW: E123ABC,0000,2/A766436,FF,FFAE,998112123ABC000000
I00,00,00,00
I00,00,00,00
I00,00,00,00
R8F89F29F,0002,00000000,FF,7FFF,998112123ABC000000
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN1 R:E123ABC stat:0000 t:2A766436 d:FF r:FFAE m:99 8112 123ABC 000000
2014.09.19 22:10:55 5: HMLAN1 dispatch A09998112123ABC000000::-82:HMLAN1
2014.09.19 22:10:55 4: CUL_HM vccu dupe: dont process
2014.09.19 22:10:55 5: HMLAN_Parse: HMLAN1 R:R8F89F29F stat:0002 t:00000000 d:FF r:7FFF m:99 8112 123ABC 000000
2014.09.19 22:10:55 1: HMLAN_Parse: HMLAN1 new condition ok
2014.09.19 22:10:55 5: Triggering HMLAN1 (3 changes)
2014.09.19 22:10:55 5: Notify loop for HMLAN1 cond: ok
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 cond: ok -> cond: ok
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 Xmit-Events: ok:2 disconnected:2 init:2 -> Xmit-Events: ok:.* disconnected:.* init:.*
2014.09.19 22:10:55 4: eventTypes: HMLAN HMLAN1 prot_ok: last -> prot_ok: last
sieht so aus als ob mein YahooWetter das Problem ist, oder?
Genauer dieser Teil:
2014.09.19 22:09:20 5: HMLAN/RAW: /HHM-LAN-IF,03C1,IEQ0244964,1740D3,123ABC,2A74F28B,0002
2014.09.19 22:09:20 5: HMLAN_Parse: HMLAN1 V:03C1 sNo:IEQ0244964 d:1740D3 O:123ABC t:2A74F28B IDcnt:0002
2014.09.19 22:09:20 5: HMLAN/RAW: /HHM-LAN-IF,03C1,JEQ0707684,1E9C46,123ABC,25C5FDD3,0003
2014.09.19 22:09:20 5: HMLAN_Parse: HMLAN2 V:03C1 sNo:JEQ0707684 d:1E9C46 O:123ABC t:25C5FDD3 IDcnt:0003
2014.09.19 22:09:44 4: HttpUtils url=http://weather.yahooapis.com/forecastrss?w=12835702&u=c
2014.09.19 22:09:54 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
2014.09.19 22:09:54 5: Triggering HMLAN2 (1 changes)
2014.09.19 22:09:54 5: Notify loop for HMLAN2 DISCONNECTED
2014.09.19 22:09:54 1: HMLAN_Parse: HMLAN2 new condition disconnected
2014.09.19 22:09:54 5: Triggering HMLAN2 (5 changes)
2014.09.19 22:09:54 4: eventTypes: HMLAN HMLAN2 DISCONNECTED -> DISCONNECTED
Apptime:
name function max count total average maxDly
tmr-Weather_GetUpdateTimer HASH(0x11c93f8) 10014 35 51792 1479.77 3 HASH(YahooWetter)
FHEMWEB:192.168.178.20:49192 FW_Read 2938 8 2976 372.00 0 HASH(FHEMWEB:192.168.178.20:49192)
tmr-Calendar_Wakeup HASH(0x138d2a0) 2281 5 11111 2222.20 3 HASH(Kalender)
HMLAN2 HMLAN_Read 350 1418 61519 43.38 0 HASH(HMLAN2)
HMLAN1 HMLAN_Read 328 1416 27225 19.23 0 HASH(HMLAN1)
TRX_0 TRX_Read 237 17 709 41.71 0 HASH(TRX_0)
HMLAN2 HMLAN_Ready 113 68 120 1.76 0 HASH(HMLAN2)
HMLAN1 HMLAN_Ready 112 68 118 1.74 0 HASH(HMLAN1)
eventTypes eventTypes_Notify 67 1339 8764 6.55 0 HASH(eventTypes); HASH(YahooWetter)
tmr-HMLAN_KeepAlive keepAlive:HMLAN1 51 860 2751 3.20 8685 keepAlive:HMLAN1
FileLog_Fenster.DG FileLog_Log 18 1339 2513 1.88 0 HASH(FileLog_Fenster.DG); HASH(YahooWetter)
tmr-HMLAN_KeepAlive keepAlive:HMLAN2 15 860 2672 3.11 8681 keepAlive:HMLAN2
tmr-CUL_HM_ActCheck ActionDetector 14 35 414 11.83 10097 ActionDetector
Wetter readingsGroup_Notify 11 1339 163 0.12 0 HASH(Wetter); HASH(YahooWetter)
tmr-FW_closeOldClients 11 359 611 1.70 5164
BAYERN3_AN notify_Exec 7 1339 1464 1.09 0 HASH(BAYERN3_AN); HASH(YahooWetter)
BAYERN3_OFF notify_Exec 7 1339 1093 0.82 0 HASH(BAYERN3_OFF); HASH(YahooWetter)
EINSLIVE_AN notify_Exec 7 1339 1043 0.78 0 HASH(EINSLIVE_AN); HASH(YahooWetter)
HMLAN1 HMLAN_Notify 7 1339 7 0.01 0 HASH(HMLAN1); HASH(HMLAN1)
Heizung.DG.Bat readingsGroup_Notify 7 1339 434 0.32 0 HASH(Heizung.DG.Bat); HASH(YahooWetter)
OE3_AN notify_Exec 7 1339 1226 0.92 0 HASH(OE3_AN); HASH(YahooWetter)
Danke für eure Hilfe!
2014.09.19 22:09:20 5: HMLAN_Send: HMLAN2 I:K
2014.09.19 22:09:20 5: HMLAN_Parse: HMLAN2 V:03C1 sNo:JEQ0707684 d:1E9C46 O:123ABC t:25C5FDD3 IDcnt:0003
2014.09.19 22:09:44 4: HttpUtils url=http://weather.yahooapis.com/forecastrss?w=12835702&u=c
2014.09.19 22:09:54 1: 192.168.178.201:1000 disconnected, waiting to reappear (HMLAN2)
der keepalive wird gesendet 9:20. der nächste ist um 9:45, spätestens aber um 9:50 fällig. Nun startet dein Wetter-check - für 10 sec gerate um 9:44 - vor dem keep-alive. HMLAN reconnected danach, weil die message nicht kommt.
tmr-Weather_GetUpdateTimer HASH(0x11c93f8) 10014 35 51792 1479.77 3 HASH(YahooWetter)
hier noch einmal die 10 sec.
Du solltest versuchen, solche raumgreifenden Prozeduren zu spawnen, also in einem eigenen Prozess laufen lassen um FHEM nicht zu blockieren.
Alternativ (aber sehr unschön) kannst du beim HMLAN den wdTimer auf 15 stellen. Dann wird alle 15sekunden getriggert - plus die 10sec deiner web-abfrage ist das immer noch kleiner als 30sec. So lange die Abfrage nicht noch länger wird geht das.
Ich würde an Lösung 1 arbeiten - web-abfragen sind nicht echtzeitfähig, die solltest du immer auslagern.
Hallo Martin,
vielen Dank für deine Antwort. Natürlich würde ich gerne Lösung 1 anstreben, habe aber keinerlei Idee wie ich das anstellen soll. Ich habe mir das Yahoo-Wetter aus http://www.fhemwiki.de/wiki/Wetter_Vorhersagen (http://www.fhemwiki.de/wiki/Wetter_Vorhersagen) zusammengebastelt. Habe nichts dran geändert, sehe nur gerade das ich die Daten alle 600 Sekunden abhole und nicht alle 3600 - ich werde das mal ändern und beobachten. Vielleicht war auch das dass Problem.
Wie verlege ich die Wetterabfrage in einen eigenen Prozess?
Vielen Dank,
viele Grüße,
Olli
das mit 3600 sec wird die häufigkeit reduzieren - um den Faktor 6. Beseitigen wird es das Problem nicht.
Generell beisst sich echtzeit mit Internet-Abfragen. Diese haben einfach keine wirklich vorhersehbare Zeit.
Um etwas in einen anderen Prozess, der parallel läuft, auszulagern kann man blockingCall nutzen. das ist aber nicht ganz trivial, man muss die Ergebnisse nach der in den Mutterprozess zurückschreiben. Dazu musst du also verstehen, wie die Abfrage funktioniert, sonst wird es nichts.
Gruß Martin
Hallo Martin,
dann wird es wohl eher Lösung 2. ;)
Vielen Dank für deine Hilfe!
Hallo olli84,
oder du machst es ganz "verrückt" und lagerst deine Wetterabfrage auf einen 2. Raspi o.ä. aus und liest die Daten über FHEM2FHEM auf deine Hauptinstanz ein. Mache ich mit fowsr und der über USB angebundenen Wetterstation so. fowsr hat die dumme Angewohnheit den Host für ca. 1min zu blockieren, damit geht HMLAN gerne auf disconnect, desshalb habe ich zu dieser Lösung gegriffen.
VG
Frank