Hallo, ich habe seit langem ein Problem mit meinen HM-LGW. Fhem läuft auf einem Raspberry Pi 3B. Außer Fhem läuft auf dem Raspi noch der Unifi-Controller, die Probleme bestanden aber schon vor der Installation.
In meiner anfänglichen Fhem-Installation hatte ich nur einen HM-LGW (im Log HMLANEG), damals kamen aber schon immer sporadisch disconnect und keep-alive Meldungen. War aber immer nur ein kosmetisches Problem im Log, im Betrieb hat es nie gestört. Nach einer Zeit kam ein zweiter HM-LGW (im Log HMLANGarage) hinzu, eine VCCU wurde auch eingerichtet. Ab diesem Zeitpunkt gab es die disconnects nur noch beim neuen HM-LGW, der erste hatte seitdem nie wieder Probleme.
Mittlerweile werden die Meldungen aber immer häufiger, so dass ich mich mal auf Fehlersuche machen musste.
Hier mal ein Auszug von heute. Die Freeze-Meldungen von Perfmon kurz vor der vollen Stunde stammen vom Fully-Modul, passen aber zeitlich nie mit den disconnects zusammen.
2017.12.25 06:56:13 1: Perfmon: possible freeze starting at 06:56:12, delay is 1.976
2017.12.25 07:07:13 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 07:07:13 3: HMLANGarage device closed
2017.12.25 07:07:28 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 07:07:28 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 07:07:28 3: HMLANGarage:keepAlive device opened
2017.12.25 07:07:28 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 07:07:28 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 07:21:55 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 07:21:55 3: HMLANGarage device closed
2017.12.25 07:21:58 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 07:21:58 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 07:21:58 3: HMLANGarage:keepAlive device opened
2017.12.25 07:21:58 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 07:21:58 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 07:47:45 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 07:47:45 3: HMLANGarage device closed
2017.12.25 07:47:47 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 07:47:47 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 07:47:47 3: HMLANGarage:keepAlive device opened
2017.12.25 07:47:47 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 07:47:47 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 07:51:52 3: CUL_HM set SchlafzimmerOG.Heizungsaktor on
2017.12.25 07:56:13 1: Perfmon: possible freeze starting at 07:56:12, delay is 1.975
2017.12.25 08:00:00 3: CUL_HM set BadOG.Thermostat_Climate desired-temp 22.5
2017.12.25 08:00:01 3: CUL_HM set BadOG.Heizungsaktor on
2017.12.25 08:03:45 3: CUL_HM set SchlafzimmerOG.Heizungsaktor off
2017.12.25 08:23:26 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 08:23:26 3: HMLANGarage device closed
2017.12.25 08:23:29 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 08:23:29 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 08:23:29 3: HMLANGarage:keepAlive device opened
2017.12.25 08:23:29 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 08:23:29 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 08:24:48 3: CUL_HM set SchlafzimmerOG.Heizungsaktor on
2017.12.25 08:30:16 3: CUL_HM set Steckdose1 off
2017.12.25 08:43:31 3: CUL_HM set Steckdose2_Sw off
2017.12.25 08:43:31 3: CUL_HM set Steckdose3_Sw off
2017.12.25 08:56:13 1: Perfmon: possible freeze starting at 08:56:12, delay is 1.997
2017.12.25 09:00:00 3: CUL_HM set SchlafzimmerOG.Thermostat_Climate desired-temp 16.0
2017.12.25 09:00:00 3: CUL_HM set SchlafzimmerOG.Heizungsaktor off
2017.12.25 09:02:52 3: CUL_HM set BadOG.Heizungsaktor off
2017.12.25 09:50:28 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 09:50:28 3: HMLANGarage device closed
2017.12.25 09:50:35 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 09:50:35 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 09:50:35 3: HMLANGarage:keepAlive device opened
2017.12.25 09:50:35 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 09:50:35 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 09:56:13 1: Perfmon: possible freeze starting at 09:56:12, delay is 1.82
2017.12.25 10:05:03 3: CUL_HM set Wz.Rollo.Garten on
2017.12.25 10:25:24 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 10:25:24 3: HMLANGarage device closed
2017.12.25 10:26:29 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 10:26:29 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 10:26:29 3: HMLANGarage:keepAlive device opened
2017.12.25 10:26:29 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 10:26:29 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 10:38:15 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 10:38:15 3: HMLANGarage device closed
2017.12.25 10:38:22 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 10:38:22 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 10:38:22 3: HMLANGarage:keepAlive device opened
2017.12.25 10:38:22 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 10:38:22 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 10:41:27 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 10:41:27 3: HMLANGarage device closed
2017.12.25 10:41:28 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 10:41:28 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 10:41:28 3: HMLANGarage:keepAlive device opened
2017.12.25 10:41:28 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 10:41:28 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 10:56:13 1: Perfmon: possible freeze starting at 10:56:12, delay is 1.933
2017.12.25 11:00:27 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 11:00:27 3: HMLANGarage device closed
2017.12.25 11:00:30 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 11:00:30 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 11:00:30 3: HMLANGarage:keepAlive device opened
2017.12.25 11:00:30 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 11:00:30 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 11:30:16 3: CUL_HM set BadOG.Thermostat_Climate desired-temp 20.0
2017.12.25 11:56:13 1: Perfmon: possible freeze starting at 11:56:12, delay is 1.907
2017.12.25 11:58:20 2: ROOMMATE set rr_Sarah absent
2017.12.25 12:01:28 2: ROOMMATE set rr_Andy absent
2017.12.25 12:01:28 3: CUL_HM set Wz.Rollo.Garten off
2017.12.25 12:01:47 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 12:01:47 3: HMLANGarage device closed
2017.12.25 12:02:03 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 12:02:03 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 12:02:03 3: HMLANGarage:keepAlive device opened
2017.12.25 12:02:03 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 12:02:03 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 12:43:35 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 12:43:35 3: HMLANGarage device closed
2017.12.25 12:43:42 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 12:43:42 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 12:43:42 3: HMLANGarage:keepAlive device opened
2017.12.25 12:43:42 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 12:43:42 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 12:47:57 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 12:47:57 3: HMLANGarage device closed
2017.12.25 12:48:04 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 12:48:04 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 12:48:04 3: HMLANGarage:keepAlive device opened
2017.12.25 12:48:04 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 12:48:04 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 12:56:14 1: Perfmon: possible freeze starting at 12:56:13, delay is 1.455
2017.12.25 12:58:21 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 12:58:21 3: HMLANGarage device closed
2017.12.25 12:58:29 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 12:58:29 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 12:58:29 3: HMLANGarage:keepAlive device opened
2017.12.25 12:58:29 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 12:58:29 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 13:56:14 1: Perfmon: possible freeze starting at 13:56:12, delay is 2.093
2017.12.25 14:08:54 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 14:08:54 3: HMLANGarage device closed
2017.12.25 14:09:02 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 14:09:02 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 14:09:02 3: HMLANGarage:keepAlive device opened
2017.12.25 14:09:02 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 14:09:02 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 14:22:17 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 14:22:17 3: HMLANGarage device closed
2017.12.25 14:22:25 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 14:22:25 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 14:22:25 3: HMLANGarage:keepAlive device opened
2017.12.25 14:22:25 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 14:22:25 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 14:31:06 1: Perfmon: possible freeze starting at 14:31:05, delay is 1.817
2017.12.25 14:56:14 1: Perfmon: possible freeze starting at 14:56:12, delay is 2.072
2017.12.25 15:32:29 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 15:32:29 3: HMLANGarage device closed
2017.12.25 15:32:29 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 15:32:29 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 15:32:29 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 15:32:33 3: HMLANGarage:keepAlive device opened
2017.12.25 15:32:33 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
2017.12.25 15:37:26 3: CUL_HM set BadOG.Thermostat_Climate desired-temp 20.0
2017.12.25 15:37:26 3: CUL_HM set SchlafzimmerOG.Thermostat_Climate desired-temp 16.0
2017.12.25 15:37:31 3: CUL_HM set BadOG.Thermostat_Climate desired-temp 18.5
2017.12.25 15:37:31 3: CUL_HM set SchlafzimmerOG.Thermostat_Climate desired-temp 16.0
2017.12.25 15:55:23 3: CUL_HM set Steckdose2_Sw on
2017.12.25 15:55:24 3: CUL_HM set Steckdose3_Sw on
2017.12.25 15:55:29 3: eq3: Read callback: Error: read from http://www.eq-3.de:80 timed out
2017.12.25 15:56:14 1: Perfmon: possible freeze starting at 15:56:13, delay is 1.883
2017.12.25 16:11:17 3: CUL_HM set Steckdose1 on
2017.12.25 16:56:14 1: Perfmon: possible freeze starting at 16:56:12, delay is 2.196
2017.12.25 17:25:15 1: HMUARTLGW HMLANGarage:keepAlive did not respond after all, reopening
2017.12.25 17:25:15 3: HMLANGarage device closed
2017.12.25 17:26:20 3: Opening HMLANGarage:keepAlive device 192.168.178.7:2001
2017.12.25 17:26:20 1: 192.168.178.7:2000 reappeared (HMLANGarage)
2017.12.25 17:26:20 3: HMLANGarage:keepAlive device opened
2017.12.25 17:26:20 3: HMUARTLGW HMLANGarage BidCoS-port opened
2017.12.25 17:26:20 3: HMUARTLGW HMLANGarage:keepAlive KeepAlive-port opened
Nach einer Kontrolle von Apptime habe ich ein paar HTTP-Mod disabled, die disconnects kommen aber trotzdem weiterhin vor.
Danach ein Apptime clear durchgeführt, kurz nach dem ersten erneuten disconnect ein erneutes Apptime:
name function max count total average maxDly TS Max call param Max call
tmr-Calendar_PollChild HASH(0x21a2ec0) 2668 1 2668 2668.00 184 25.12. 17:56:14 HASH(DP_Andy)
DP_Andy_Calview CALVIEW_Notify 1885 424 1885 4.45 0 25.12. 17:56:14 HASH(DP_Andy_Calview); HASH(DP_Andy)
tmr-Calendar_PollChild HASH(0x2219f08) 324 1 324 324.00 2 25.12. 17:56:11 HASH(DP_Sarah)
HMLANEG HMUARTLGW_Read 179 371 10505 28.32 0 25.12. 17:31:17 HASH(HMLANEG)
SchlafzimmerOG.Lueften.nf notify_Exec 155 424 2411 5.69 0 25.12. 17:31:17 HASH(SchlafzimmerOG.Lueften.nf); HASH(SchlafzimmerOG.Thermostat_Weather)
BadOG.Lueften.nf notify_Exec 148 424 2645 6.24 0 25.12. 17:23:50 HASH(BadOG.Lueften.nf); HASH(BadOG.Thermostat_Weather)
HMLANGarage HMUARTLGW_Read 148 365 1528 4.19 0 25.12. 17:46:39 HASH(HMLANGarage)
DP_Sarah_Calview CALVIEW_Notify 101 424 101 0.24 0 25.12. 17:56:11 HASH(DP_Sarah_Calview); HASH(DP_Sarah)
tmr-RESIDENTStk_DurationTimer HASH(0x8d87358) 91 1 91 91.00 4 25.12. 17:35:01 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x9c7ddd0) 75 1 75 75.00 18 25.12. 17:25:00 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x61a1630) 71 1 71 71.00 14 25.12. 18:03:01 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x6938328) 68 1 68 68.00 5 25.12. 17:43:01 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x7e5a2c0) 66 1 66 66.00 2 25.12. 17:51:01 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x5967878) 62 1 62 62.00 4 25.12. 17:39:01 HASH(Bewohner_DurationTimer)
tmr-DOIF_TimerTrigger REF(0x70d7340) 59 1 59 59.00 4 25.12. 18:00:00 REF(0x70d7340)
tmr-BOSEST_checkWebSocketConnection HASH(0x4742820) 55 12908 16123 1.25 2655 25.12. 17:37:45 HASH(BOSE_A81B6A5B16DF)
tmr-BOSEST_checkWebSocketConnection HASH(0x3ce7638) 53 8605 11736 1.36 2656 25.12. 17:42:54 HASH(BOSE_08DF1F149880)
tmr-RESIDENTStk_DurationTimer HASH(0x78d9440) 51 1 51 51.00 0 25.12. 17:40:01 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x83d7c58) 51 1 51 51.00 3 25.12. 17:53:01 HASH(Bewohner_DurationTimer)
tmr-RESIDENTStk_DurationTimer HASH(0x55d5bb0) 50 1 50 50.00 4 25.12. 17:21:00 HASH(Bewohner_DurationTimer)
Hat vielleicht noch irgendwer eine Idee was zu den ständigen disconnects führt? In den meisten Fällen hier im Forum konnte der Verursacher über Apptime gefunden werden, aber so wie ich das sehe müssten die Verzögerungen bei mir ja eigentlich passen...
Hat denn keiner einen Vorschlag? :'(
Vielleicht hilft es jemand anderem bei der Fehlersuche weiter.
Bei mir lag das Problem nicht an Fhem, sondern an der Netzwerkverbindung zum LGW. Da dieser in der Garage hängt und dort kein Netzwerkkabel vorhanden ist habe ich die Verbindung über 2 ältere Devolo Powerlan hergestellt. Diese Verbindung war wohl für den LGW nicht stabil genug, der ebenfalls angeschlossene Unifi-AP hatte keine Probleme.
Diese alten Devolo wurden durch zwei Fritz Powerline 1220E ersetzt und seitdem: Keine disconnects mehr 8)