Hallo, ich habe festgestellt dass beim einlesen meines LS110 von Youless bei jeder Abfrage ein Fehler im LOG entsteht.
habe mal zur Analyse das Verbose auf 5 gesetzt:
Auszug aus dem Logfile:
2016.11.25 11:08:34 1: JSONMETER EnergieEG: ReadFromUrl.461 Could not open connection to ip 192.168.178.242 port 80
2016.11.25 11:09:34 1: JSONMETER EnergieEG: ReadFromUrl.461 Could not open connection to ip 192.168.178.242 port 80
2016.11.25 11:10:35 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 30431
2016.11.25 11:10:35 1: JSONMETER EnergieEG: UpdateAborted.664 Timeout when connecting to host 192.168.178.242
2016.11.25 11:11:34 1: JSONMETER EnergieEG: ReadFromUrl.461 Could not open connection to ip 192.168.178.242 port 80
2016.11.25 11:12:34 1: JSONMETER EnergieEG: ReadFromUrl.461 Could not open connection to ip 192.168.178.242 port 80
2016.11.25 11:13:25 4: JSONMETER EnergieEG: ReadFromUrl.451 opening socket to host 192.168.178.242 port 80
2016.11.25 11:13:32 4: JSONMETER EnergieEG: ReadFromUrl.468 Get json file from http://192.168.178.242:80/a?f=j
2016.11.25 11:13:35 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 30454
2016.11.25 11:13:35 1: JSONMETER EnergieEG: UpdateAborted.664 Timeout when connecting to host 192.168.178.242
2016.11.25 11:14:25 4: JSONMETER EnergieEG: ReadFromUrl.451 opening socket to host 192.168.178.242 port 80
2016.11.25 11:14:34 1: JSONMETER EnergieEG: ReadFromUrl.461 Could not open connection to ip 192.168.178.242 port 80
2016.11.25 11:15:25 4: JSONMETER EnergieEG: ReadFromUrl.451 opening socket to host 192.168.178.242 port 80
2016.11.25 11:15:34 1: JSONMETER EnergieEG: ReadFromUrl.461 Could not open connection to ip 192.168.178.242 port 80
2016.11.25 11:16:25 4: JSONMETER EnergieEG: ReadFromUrl.451 opening socket to host 192.168.178.242 port 80
Definition:
define EnergieEG JSONMETER LS110 192.168.178.242 60
attr EnergieEG alias Energieverbrauch EG
attr EnergieEG event-min-interval statElectricityConsumed_kWhDay:3600,statElectricityConsumed_kWhDayLast:3600,statElectricityConsumed_kWhHourLast:3600
attr EnergieEG group Energiezaehler_Verbraucher
attr EnergieEG icon measure_power
attr EnergieEG room Stromzähler
attr EnergieEG stateFormat {sprintf("Zählerstand: %.1f kWh , Aktuell: %s Watt",(ReadingsVal($name,"electricityConsumed_kWh",0)), ReadingsVal($name,"electricityPower",0))}
attr EnergieEG userReadings electricityConsumed_kWh:electricityConsumed.* {ReadingsVal("EnergieEG","electricityConsumed",0)*0.001}
das list von EnergieEG:
Internals:
DEF LS110 192.168.178.242 60
HOST 192.168.178.242
INTERVAL 60
NAME EnergieEG
NOTIFYDEV global
NR 509
PORT 80
STATE Zählerstand: 66486.1 kWh , Aktuell: 431 Watt
TYPE JSONMETER
deviceType LS110
urlPath a?f=j
Readings:
2016-11-25 06:58:08 electricityConsumed 66486106
2016-11-25 06:58:08 electricityConsumed_kWh 66486.106
2016-11-25 06:58:08 electricityPower 431
2016-11-25 11:16:57 statElectricityConsumed_kWh Hour: 0.000 Day: 2.106 Month: 377.560 Year: 656.226 (since: 2016-10-10 )
2016-11-25 11:16:57 statElectricityConsumed_kWhDay 2.106
2016-11-24 23:59:55 statElectricityConsumed_kWhDayLast 11.667
2016-11-25 11:16:57 statElectricityConsumed_kWhHour 0.000
2016-11-25 10:59:55 statElectricityConsumed_kWhHourLast 0.000
2016-11-25 10:59:55 statElectricityConsumed_kWhLast Hour: 0.000 Day: 11.667 Month: 278.666 Year: - (since: 2016-10-10 )
2016-11-25 11:16:57 statElectricityConsumed_kWhMonth 377.560
2016-10-31 23:59:56 statElectricityConsumed_kWhMonthLast 278.666
2016-11-25 11:16:57 statElectricityConsumed_kWhYear 656.226
2016-11-25 11:16:57 state Can't connect to ip 192.168.178.242 port 80
Fhem:
jsonInterpreter
modulVersion $Date: 2016-09-29 20:35:21 +0200 (Thu, 29 Sep 2016) $
Helper:
_98_statistics EnergieEGstatkWh
Running_pid:
abortFn JSONMETER_UpdateAborted
arg EnergieEG
bc_pid 1131
finishFn JSONMETER_ParseJsonFile
fn JSONMETER_GetJsonFile
pid 30515
timeout 10
Abortarg:
Attributes:
alias Energieverbrauch EG
event-min-interval statElectricityConsumed_kWhDay:3600,statElectricityConsumed_kWhDayLast:3600,statElectricityConsumed_kWhHourLast:3600
group Energiezaehler_Verbraucher
icon measure_power
room Stromzähler
stateFormat {sprintf("Zählerstand: %.1f kWh , Aktuell: %s Watt",(ReadingsVal($name,"electricityConsumed_kWh",0)), ReadingsVal($name,"electricityPower",0))}
userReadings electricityConsumed_kWh:electricityConsumed.* {ReadingsVal("EnergieEG","electricityConsumed",0)*0.001}
Hat jemand ähnliche Erfahrungen bzw. eine Lösung?[/code]
@Heimweh
Wie hast du den Fehler beseitigt?
Ich habe diesen Fehler bei mir ebenfalls festgestellt.
2017.11.05 19:48:54.918 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 5086
2017.11.05 19:48:54.919 1: JSONMETER EnergieAB: UpdateAborted.664 Timeout when connecting to host 192.168.17.243
2017.11.05 19:48:54.971 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 5087
2017.11.05 19:48:54.973 1: JSONMETER EnergieEG: UpdateAborted.664 Timeout when connecting to host 192.168.17.240
2017.11.05 19:48:54.994 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 5088
2017.11.05 19:48:54.996 1: JSONMETER EnergieOG1: UpdateAborted.664 Timeout when connecting to host 192.168.17.241
2017.11.05 19:48:55.015 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 5089
2017.11.05 19:48:55.016 1: JSONMETER EnergieOG2: UpdateAborted.664 Timeout when connecting to host 192.168.17.242
2017.11.05 19:48:55.036 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 5090
2017.11.05 19:48:55.037 1: JSONMETER EnergiePV: UpdateAborted.664 Timeout when connecting to host 192.168.17.244
2017.11.05 19:48:55.458 1: Timeout for SYSMON_blockingCall reached, terminated process 5085
LIST
Internals:
CFGFN /media/hdd/fhem/mycfg/YouLess/Stromzaehler_rasp01.cfg
CHANGED
DEF LS110 192.168.17.243 60
HOST 192.168.17.243
INTERVAL 60
NAME EnergieAB
NOTIFYDEV global
NR 2932
PORT 80
STATE Aktuell: 90 Watt
TYPE JSONMETER
deviceType LS110
urlPath a?f=j
READINGS:
2017-11-06 12:35:24 electricityConsumed 1886819
2017-11-06 12:35:24 electricityPower 90
2017-11-06 12:35:24 state Connected
fhem:
jsonInterpreter 1 3 electricityConsumed 3 1 cnt|1 3 electricityPower 1 0 pwr
modulVersion $Date: 2016-09-29 20:35:21 +0200 (Thu, 29 Sep 2016) $
helper:
Attributes:
alias Energieverbrauch AB
event-on-change-reading electricityPower
group Energiezaehler_Verbraucher
icon measure_power
room AB-Fitnessraum,AB-Pool,AB-Sauna,_Statistiken
stateFormat {sprintf("Aktuell: %s Watt",ReadingsVal("$name","electricityPower",0))}
userReadings electricityPower
verbose 1
so wie ich das interpretiere kann fhem Deine device (zb 192.168.17.243) nicht erreichen. Das wird wohl was mit Deinem Netzwerk zu tun haben.
Am Netzwerk kann es nicht liegen.
Zum Einem scheinen am Netzwerkswitch für die verwendeten Ports keine Fehlermeldungen auf, und zum Anderen kann ich die LS110 Geräte direkt ohne Probleme erreichen.
Auch am Netzwerkport des betreffenden Raspberry gibt es am Switch keine Fehlermeldungen.
Was auffällt ist das dieser Raspberry sehr träge via Web erreichbar ist. Darum bin ich unter anderem bei der Fehlersuche im LOG auf diese Meldungen gestoßen.
Es gibt zudem auch mit den SSL/HTTPS Verbindungen sehr viel Fehlermeldungen.
2017.11.05 19:50:20.841 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 19:52:08.871 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.182)
2017.11.05 19:52:37.741 1: 192.168.17.186:40868 disconnected, waiting to reappear (nanoCUL868_AB_FR)
2017.11.05 19:52:37.991 1: Perfmon: possible freeze starting at 19:51:23, delay is 74.991
2017.11.05 19:52:42.667 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.184)
2017.11.05 19:53:55.078 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.185)
2017.11.05 19:55:07.817 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 19:55:57.693 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.184)
2017.11.05 19:56:57.606 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.182)
2017.11.05 19:57:37.988 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.131)
2017.11.05 19:57:58.897 1: Perfmon: possible freeze starting at 19:57:28, delay is 30.896
2017.11.05 19:58:07.321 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.185)
2017.11.05 19:58:54.481 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 19:59:23.251 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.184)
2017.11.05 19:59:41.219 1: Perfmon: possible freeze starting at 19:59:07, delay is 34.219
2017.11.05 19:59:42.907 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.131)
2017.11.05 19:59:56.048 1: Perfmon: possible freeze starting at 19:59:42, delay is 14.048
2017.11.05 20:00:11.016 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.182)
2017.11.05 20:00:18.867 1: Perfmon: possible freeze starting at 19:59:57, delay is 21.867
2017.11.05 20:00:41.404 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 20:00:49.983 1: Perfmon: possible freeze starting at 20:00:19, delay is 30.982
2017.11.05 20:01:04.675 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.185)
2017.11.05 20:01:04.778 1: Perfmon: possible freeze starting at 20:00:50, delay is 14.778
2017.11.05 20:01:09.744 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 20:01:37.923 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 20:01:51.590 1: Perfmon: possible freeze starting at 20:01:26, delay is 25.59
2017.11.05 20:01:57.639 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.131)
2017.11.05 20:02:10.738 1: Perfmon: possible freeze starting at 20:01:52, delay is 18.738
2017.11.05 20:02:11.956 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 20:02:12.129 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
2017.11.05 20:02:12.195 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.182)
2017.11.05 20:02:12.269 1: telnet SSL/HTTPS error: SSL connect accept failed because of handshake problems (peer: 192.168.17.186)
All dies kann nur im betreffenden Raspberry direkt mit FHEM was zu tun haben.
träge ist gut :) Hier:
2017.11.05 19:52:37.991 1: Perfmon: possible freeze starting at 19:51:23, delay is 74.991
war Dein fhem für sage und schreibe 75 Sekunden komplett im Stillstand. Keine Chance auf irgendwas zu reagieren.
Schau Dir mal apptime und taste Dich damit ran.
Das apptime Ergebnis lautet:
name function max count total average maxDly TS Max call param Max call
nanoCUL868_OG2 CUL_Read 28862 493 3026198 6138.33 0 07.11. 01:12:08 HASH(nanoCUL868_OG2)
nanoCUL868_WebCam CUL_Read 28842 464 3040494 6552.79 0 07.11. 01:04:05 HASH(nanoCUL868_WebCam)
nanoCUL868_EG CUL_Read 28799 474 3008444 6346.93 0 07.11. 01:05:45 HASH(nanoCUL868_EG)
nanoCUL868_OG1 CUL_Read 24067 459 2977775 6487.53 0 07.11. 01:38:32 HASH(nanoCUL868_OG1)
sduino SIGNALduino_Read 20489 6961 4905542 704.72 0 07.11. 01:02:17 HASH(sduino)
nanoCUL433_OG1 CUL_Read 9953 7741 528907 68.33 0 07.11. 01:02:43 HASH(nanoCUL433_OG1)
nanoCUL433_AB_GAW CUL_Read 9922 4813 405419 84.23 0 07.11. 01:00:35 HASH(nanoCUL433_AB_GAW)
autocreate autocreate_Notify 7881 6542 3054431 466.90 0 06.11. 23:18:28 HASH(autocreate); HASH(global)
nanoCUL433_AB_FR CUL_Read 7436 5877 614723 104.60 0 07.11. 13:56:07 HASH(nanoCUL433_AB_FR)
nanoCUL433_OG2 CUL_Read 6784 3006 729167 242.57 0 06.11. 21:50:08 HASH(nanoCUL433_OG2)
nanoCUL433_EG CUL_Read 5530 2629 290012 110.31 0 07.11. 13:28:13 HASH(nanoCUL433_EG)
WEB FW_Read 3422 23 4746 206.35 0 07.11. 15:47:11 HASH(WEB)
tmr-DOIF_SleepTrigger HASH(0x3aaa020) 3412 1 3412 3412.00 4082 07.11. 06:58:16 HASH(Daylight_EG_ST)
tmr-DOIF_SleepTrigger HASH(0x3aaaae8) 3007 1 3007 3007.00 7455 07.11. 06:58:19 HASH(Daylight_OG1_ST)
Daylight_EG_D dummy_Set 2952 1 2952 2952.00 0 07.11. 06:58:16 HASH(Daylight_EG_D); Daylight_EG_D; on
Daylight_OG1_D dummy_Set 2844 1 2844 2844.00 0 07.11. 06:58:19 HASH(Daylight_OG1_D); Daylight_OG1_D; on
tmr-GPIO4_DeviceUpdateLoop HASH(0x25af588) 2323 1074 1075162 1001.08 66060 07.11. 08:14:06 HASH(OG1_EDV_R_EDVVT)
tmr-GPIO4_DeviceUpdateLoop HASH(0x25ada00) 1900 1074 1070319 996.57 65962 07.11. 04:22:05 HASH(OG1_EDV_R_RT)
F2F_Rasp08 FHEM2FHEM_Read 1512 10 13484 1348.40 0 07.11. 09:09:57 HASH(F2F_Rasp08)
F2F_Rasp04 FHEM2FHEM_Read 1357 413 291924 706.84 0 06.11. 23:25:44 HASH(F2F_Rasp04)
tmr-HMUARTLGW_CheckCmdResp HASH(0x216ab38) 1248 604 37557 62.18 81374 07.11. 14:40:12 HASH(HmUART_OG1)
Nur wie hilft mir dieses Ergebnis weiter?
die Probleme müssen nicht zwangsweise miteinander zu tun haben. Aber irgendwo solltest Du halt anfangen.
Die beiden hier würde ich mir zuerst vornehmen und hoffen das sich damit auch der HM Uart löst
tmr-GPIO4_DeviceUpdateLoop HASH(0x25af588) 2323 1074 1075162 1001.08 66060 07.11. 08:14:06 HASH(OG1_EDV_R_EDVVT)
tmr-GPIO4_DeviceUpdateLoop HASH(0x25ada00) 1900 1074 1070319 996.57 65962 07.11. 04:22:05 HASH(OG1_EDV_R_RT)
kannst Du die zuordnen (modul, device) ? Irgendwas mit GPIO ... (raspi vmtl...)
Das sind zwei 1Wire Raumfühler die aber keinen Fehler haben und Temperaturwerte sauber liefern.