Buderus KM200 Kommunikationsmodul

DLindner · 27 Mai 2015, 22:14:13

@Sailor

 PERL WARNING: Argument "2/8" isn't numeric in numeric ne (!=) at ./FHEM/73_km200.pm line 1446.
2015.05.27 21:58:16 3: set heizung /heatingCircuits/hc2/switchPrograms/Eigen2 [{"dayOfWeek":"Mo","setpoint":"day","time":150},{"dayOfWeek":"Mo","setpoint":"night","time":1350},{"dayOfWeek":"Tu","setpoint":"day","time":150},{"dayOfWeek":"Tu","setpoint":"night","time":1350},{"dayOfWeek":"We","setpoint":"day","time":150},{"dayOfWeek":"We","setpoint":"night","time":1350},{"dayOfWeek":"Th","setpoint":"day","time":150},{"dayOfWeek":"Th","setpoint":"night","time":1350},{"dayOfWeek":"Fr","setpoint":"day","time":150},{"dayOfWeek":"Fr","setpoint":"night","time":1350},{"dayOfWeek":"Sa","setpoint":"day","time":150},{"dayOfWeek":"Sa","setpoint":"night","time":1350},{"dayOfWeek":"Su","setpoint":"day","time":150},{"dayOfWeek":"Su","setpoint":"night","time":1350}] : ERROR - The service /heatingCircuits/hc2/switchPrograms/Eigen2 could not changed!

root@raspberrypi:/opt/fhem# km200_Set - Writing value: [{"dayOfWeek":"Mo","setpoint":"day","time":150},{"dayOfWeek":"Mo","setpoint":"night","time":1350},{"dayOfWeek":"Tu","setpoint":"day","time":150},{"dayOfWeek":"Tu","setpoint":"night","time":1350},{"dayOfWeek":"We","setpoint":"day","time":150},{"dayOfWeek":"We","setpoint":"night","time":1350},{"dayOfWeek":"Th","setpoint":"day","time":150},{"dayOfWeek":"Th","setpoint":"night","time":1350},{"dayOfWeek":"Fr","setpoint":"day","time":150},{"dayOfWeek":"Fr","setpoint":"night","time":1350},{"dayOfWeek":"Sa","setpoint":"day","time":150},{"dayOfWeek":"Sa","setpoint":"night","time":1350},{"dayOfWeek":"Su","setpoint":"day","time":150},{"dayOfWeek":"Su","setpoint":"night","time":1350}] to the service                     : /heatingCircuits/hc2/switchPrograms/Eigen2
Obtaining value of                                     : /heatingCircuits/hc2/switchPrograms/Eigen2
Waiting for processing time (READBACKDELAY / [ms])     : 2000
Obtaining value of                                     : /heatingCircuits/hc2/switchPrograms/Eigen2
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Size of ReReadItem : 2/8
Size of JsonItem   : 2/8
Writing /heatingCircuits/hc2/switchPrograms/Eigen2 succesfully

Zitat/system/systemType      NSC_ICOM_GATEWAY
dCommand         0
dValue1            0
dValue2            0
d_climaSelect         1
fullResponse         OK

Das ist leider nicht was helfen könnte.
Der Dialog hat eine Bezeichnung, die Du bei der Initialisierung angegeben hast (z.B. Heizprogramme). Einmal darauf klicken, dann wird Dir die Definition angezeigt. Dann nach unten scrollen, dort werden Dir die Zuordnungen (Probably associated with) angezeigt. Dort einmal auf d_climaSelect klicken und das Programm wechsels zum Dummy-ReadingControl d_climaSelect. Dort werden dann alle Reading angezeigt, die für mich interessant wären.

Sailor · 28 Mai 2015, 09:26:38

Hallo DLindner

Zitat von: DLindner am 27 Mai 2015, 22:14:13

Code Auswählen Erweitern
PERL WARNING: Argument "2/8" isn't numeric in numeric ne (!=) at ./FHEM/73_km200.pm line 1446.

Ersetze mal Testhalber die Zeile 1446

Code Auswählen

if (%$ReReadItem != %$JsonItem)

mit

Code Auswählen

if (%$ReReadItem ne %$JsonItem)

Was passiert jetzt?

Gruss
Sailor

DLindner · 28 Mai 2015, 12:17:24

@Sailor,

ZitatWas passiert jetzt?

Werde ich nachher testen.

Ich habe die ReadingsGroup überarbeitet, sodass Sie ein statisches Fenster mit der max-Anzahl switch-Points aufbaut (Spalten entfallen).
Dies hat auch den Vorteil, dass nicht ständig die cfg überschrieben wird.

Lösche bitte alle Definitionen: Heizprogramme, d_climaSelect, d_climaControl*, ntfy_rg, ntfy_setreading, kopiere die PM-Dateien nach FHEM und initialisiere die Readings neu {InitHzDef("mykm200","Heizprogramme")} (ohne den letzten numerischen Parameter).

Sailor · 28 Mai 2015, 14:58:29

Hallo DLIndner

Zitat von: DLindner am 28 Mai 2015, 12:17:24
Lösche bitte alle Definitionen: Heizprogramme, d_climaSelect, d_climaControl*, ntfy_rg, ntfy_setreading, kopiere die PM-Dateien nach FHEM und initialisiere die Readings neu {InitHzDef("mykm200","Heizprogramme")} (ohne den letzten numerischen Parameter).

Alles geloescht und neu gestartet.

Leider kein Erfolg gehabt... Siehe Anhaenge.
Immer noch nur eine Dopelsdpalte wo eigentlich 2 Doppelspalten fuer hc1 B sein sollten.

Gruss
Sailor

DLindner · 28 Mai 2015, 16:38:51

Hi Sailor,

schau dir mal den Parameter MaxSetPoints an. Sollte eigentlich eine Zahl zw. 1 und 5 sein. Danach werden sie Spalten aufgebaut. Kannst Du mir die Ausgabe von "get km200 /heatingCircuits/switchPrograms/B json" mal posten. Ist wohl ein Problem beim Parsen der Werte für MaxSetPoints.

Habe das Problem gefunden:
Bei mir gibt das System unglaubliche Werte aus:

Zitat/hc2/temperatureLevels"},"maxNbOfSwitchPoints":42,"maxNbOfSwitchPointsPerDay":42,"switchPointTimeRaster":10

Ich habe einfach maxNbOfSwitchPointsPerDay durch 14 (7 Tage, 2 Schaltpunte = 3) geteilt.

Bei Dir steht wahrscheinlich 6 statt 42, dann kome ich auf diese Fließkommazahl.
Wenn du in 99_InitUtils.pm die markierte Zeile änderst, dann müsste es klappen.

Zitatsub getHcParam($$$) {
my ($device, $Hc, $Prog) = @_;
my $Kreis = "heatingCircuits";
if ( left($Hc,2) ne "hc" ) {
$Kreis = "dhwCircuits";
}
my $Reading = "/$Kreis/$Hc/switchPrograms/$Prog json";
my $string = fhem("get $device $Reading false");
my $maxSwPoints="maxNbOfSwitchPoints";
my $maxSwPointPerDay="maxNbOfSwitchPointsPerDay";
my $TimeRaster="switchPointTimeRaster";
my $pos1 = index($string, $maxSwPoints);
my $pos2 = index($string, $maxSwPointPerDay);
my $pos3 = index($string, $TimeRaster);
my @Val1 = split(/,/,substr($string, $pos1));
my @Val2 = split(/,/,substr($string, $pos2));
my @Val3 = split(/,/,substr($string, $pos3));
my $val1=(substr($Val1[0],length($maxSwPoints)+2)/2);
my $val2=(substr($Val2[0],length($maxSwPointPerDay)+2)/14); -> my $val2=(substr($Val2[0],length($maxSwPointPerDay)+2)/2)
my $val3=(substr($Val3[0],length($TimeRaster)+2)*1);
fhem("setreading d_climaSelect MaxSetPoints $val2");
fhem("setreading d_climaSelect TimeRaster $val3");

Nach änderung einmal d_climaSelect löschen und und {InitHzDef("heizung","Heizprogramme")} nochmal ausführen.

Ich habe deine Änderung eingebaut und der Fehler erscheint nicht mehr im Log. Trotzdem habe ich immer noch Probleme beim Schreiben. Werde in den nächsten Tagen mal den Powerline-Adapter rauswerfen und durch ein G-Lan ersetzen.

Sailor · 28 Mai 2015, 19:56:39

Hallo DLindner

Zitat von: DLindner am 28 Mai 2015, 16:38:51
Ich habe deine Änderung eingebaut und der Fehler erscheint nicht mehr im Log. Trotzdem habe ich immer noch Probleme beim Schreiben. Werde in den nächsten Tagen mal den Powerline-Adapter rauswerfen und durch ein G-Lan ersetzen.

Ich verstehe das hinten und vorne nicht.

Wenn keine Fehlermeldung auftaucht, nachdem das SOLL - Programm mit dem nach erfolgtem Schreiben zurueckgelesenen IST - Program hash-Wert fuer hash-Wert verglichen wird, wieso gibt es dann immer noch Fehler obwohl die Fehlerpruefung eine Gleichheit ergeben hat?

Da muss ich mal ne Nacht drueber schlafen...

Gruss
Sailor

DLindner · 28 Mai 2015, 20:48:04

Hallo Sailor,

nicht falsch verstehen. Ich habe zwar noch Probleme beim Schreiben, aber nur sporadisch. Mal geht's, mal nicht. Es kommt auch vor, das ganze Tageswerte verschwinden, sodass für z.B. Samstag weder Start- noch Endezeit vorhanden sind. Vielleicht liegt es ja an meiner Hardware.

Newbee · 29 Mai 2015, 12:05:58

Hallo Sailor,

bekomme seit dem update folgende Einträge im LOG.

Code Auswählen

2015.05.29 08:22:47 1: PERL WARNING: Argument "2005-09-24T03:58:00" isn't numeric in numeric comparison (<=>) at ./FHEM/73_km200.pm line 2435.
2015.05.29 08:25:05 1: PERL WARNING: Argument "2015-05-02T18:50:00" isn't numeric in numeric comparison (<=>) at ./FHEM/73_km200.pm line 2924.

Danke vorab.

Grüsse Newbee

Sailor · 29 Mai 2015, 14:36:51

Hallo DLindner

Zitat von: DLindner am 28 Mai 2015, 16:38:51
Wenn du in 99_InitUtils.pm die markierte Zeile änderst, dann müsste es klappen.
Nach änderung einmal d_climaSelect löschen und und {InitHzDef("heizung","Heizprogramme")} nochmal ausführen.

Na das Modul ist ja 'ne Granate!
Kaum den Befehl von Dir ausgefuehrt, friert der gesamte RasPi reproduzierbar ein.

Darueber hinaus bekomme ich beim Start von fhem folgende Meldungen:

Code Auswählen


2015.05.29 14:25:27 1: reload: Error:Modul 99_InitUtils deactivated:
2015.05.29 14:25:27 1: reload: Error:Modul 99_myUtils deactivated:

Eine Ahnung was das bedeutet?

Gruss
Sailor

DLindner · 29 Mai 2015, 15:56:36

Tut mir leid, es hat dir die Log-Datei zugemüllt, wegen einem kleinen Hochkomma '

Wenn es dir nichts ausmacht, änder die 2 Stellen eben selbst. Einmal im Attr Commands der Definition Heizprogramme (Bild 13) und damit es nicht wieder passiert in der 99_InitUtils (Bild14).

Nochmals Tschuldigung.

Sailor · 29 Mai 2015, 16:06:49

Hallo Newbee

Zitat von: Newbee am 29 Mai 2015, 12:05:58
Hallo Sailor,

bekomme seit dem update folgende Einträge im LOG.

Code Auswählen Erweitern
2015.05.29 08:22:47 1: PERL WARNING: Argument "2005-09-24T03:58:00" isn't numeric in numeric comparison (<=>) at ./FHEM/73_km200.pm line 2435. 2015.05.29 08:25:05 1: PERL WARNING: Argument "2015-05-02T18:50:00" isn't numeric in numeric comparison (<=>) at ./FHEM/73_km200.pm line 2924.

Ich habe Version 0052 eingecheckt. Ich hoffe, dass mit den Bugfixes die Fehler verschwunden sind.

Gruss
Sailor

Jorge3711 · 03 Juni 2015, 09:07:04

Hallo zusammen,

ich habe so etwas meine Probleme mit dem Modul. Ich habe immer wieder folgende Meldungen im fhem.log:

Code Auswählen


2015.06.03 08:23:53 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/dhwMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:23:59 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/hcMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:27:53 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/activeSwitchProgram: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:27:59 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/fastHeatupFactor: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/manualRoomSetpoint: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/operationMode: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/operationMode: empty answer received
2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/pumpModulation: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/pumpModulation: empty answer received
2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/roomtemperature: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/roomtemperature: empty answer received
2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/status: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/status: empty answer received
2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/switchPrograms/A: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/switchPrograms/A: empty answer received
2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/switchPrograms/B: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/switchPrograms/B: empty answer received
2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temperatureLevels/comfort2: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temperatureLevels/comfort2: empty answer received
2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temperatureLevels/eco: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temperatureLevels/eco: empty answer received
2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temperatureRoomSetpoint: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temperatureRoomSetpoint: empty answer received
2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temporaryRoomSetpoint: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temporaryRoomSetpoint: empty answer received
2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /notifications: No proper Communication with Gateway: http://172.28.135.35/notifications: empty answer received
2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/CHpumpModulation: No proper Communication with Gateway: http://172.28.135.35/system/appliance/CHpumpModulation: empty answer received
2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/ChimneySweeper: No proper Communication with Gateway: http://172.28.135.35/system/appliance/ChimneySweeper: empty answer received
2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/actualPower: No proper Communication with Gateway: http://172.28.135.35/system/appliance/actualPower: empty answer received
2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/actualSupplyTemperature: No proper Communication with Gateway: http://172.28.135.35/system/appliance/actualSupplyTemperature: empty answer received
2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/flameCurrent: No proper Communication with Gateway: http://172.28.135.35/system/appliance/flameCurrent: empty answer received
2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/gasAirPressure: No proper Communication with Gateway: http://172.28.135.35/system/appliance/gasAirPressure: empty answer received
2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/nominalBurnerLoad: No proper Communication with Gateway: http://172.28.135.35/system/appliance/nominalBurnerLoad: empty answer received
2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/numberOfStarts: No proper Communication with Gateway: http://172.28.135.35/system/appliance/numberOfStarts: empty answer received
2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/powerSetpoint: No proper Communication with Gateway: http://172.28.135.35/system/appliance/powerSetpoint: empty answer received
2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/systemPressure: No proper Communication with Gateway: http://172.28.135.35/system/appliance/systemPressure: empty answer received
2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/appliance/workingTime/centralHeating: No proper Communication with Gateway: http://172.28.135.35/system/appliance/workingTime/centralHeating: empty answer received
2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/appliance/workingTime/secondBurner: No proper Communication with Gateway: http://172.28.135.35/system/appliance/workingTime/secondBurner: empty answer received
2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/appliance/workingTime/totalSystem: No proper Communication with Gateway: http://172.28.135.35/system/appliance/workingTime/totalSystem: empty answer received
2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/healthStatus: No proper Communication with Gateway: http://172.28.135.35/system/healthStatus: empty answer received
2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/heatSources/hs1/actualModulation: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/actualModulation: empty answer received
2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/heatSources/hs1/actualPower: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/actualPower: empty answer received
2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/energyReservoir: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/energyReservoir: empty answer received
2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/fuel/caloricValue: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/fuel/caloricValue: empty answer received
2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/fuel/density: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/fuel/density: empty answer received
2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/fuelConsmptCorrFactor: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/fuelConsmptCorrFactor: empty answer received
2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/nominalFuelConsumption: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/nominalFuelConsumption: empty answer received
2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/reservoirAlert: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/reservoirAlert: empty answer received
2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm1/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm1/dhwMode: empty answer received
2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm1/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm1/hcMode: empty answer received
2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm1/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm1/startStop: empty answer received
2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm2/dhwMode: empty answer received
2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm2/hcMode: empty answer received
2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm2/startStop: empty answer received
2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm3/dhwMode: empty answer received
2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm3/hcMode: empty answer received
2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm3/startStop: empty answer received
2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm4/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm4/dhwMode: empty answer received
2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm4/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm4/hcMode: empty answer received
2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm4/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm4/startStop: empty answer received
2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm5/dhwMode: empty answer received
2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm5/hcMode: empty answer received
2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm5/startStop: empty answer received
2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/sensors/temperatures/chimney: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/chimney: empty answer received
2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/sensors/temperatures/hotWater_t2: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/hotWater_t2: empty answer received
2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/outdoor_t1: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/outdoor_t1: empty answer received
2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/return: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/return: empty answer received
2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/supply_t1: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/supply_t1: empty answer received
2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/supply_t1_setpoint: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/supply_t1_setpoint: empty answer received
2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/switch: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/switch: empty answer received
2015.06.03 08:29:24 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/activeSwitchProgram: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:29:30 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/fastHeatupFactor: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:31:13 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/dhwMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:35:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/hcMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out
2015.06.03 08:35:16 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/dhwMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out

Die Pollingzeiten wurden nicht über die Attr verändert und entsprechen dem Auslieferungszustand des Moduls. Zum Einsatz kommt Version 0052 des Moduls.

Im weiteren Verlauf kommt es dann irgendwann zu folgenden Einträgen in den Logs:

Code Auswählen


2015.05.24 17:43:36 2: myKM200 : ERROR: Service: /gateway/DateTime: No proper Communication with Gateway: http://172.28.135.35/gateway/DateTime: Can't connect(2) to http://172.28.135.35:80: [b]IO::Socket::INET: Too many open files[/b]
2015.05.24 17:43:36 2: myKM200 : ERROR: Service: /gateway/instAccess: No proper Communication with Gateway: http://172.28.135.35/gateway/instAccess: Can't connect(2) to http://172.28.135.35:80: [b]IO::Socket::INET: Too many open files[/b]
2015.05.24 17:43:36 2: myKM200 : ERROR: Service: /gateway/instWriteAccess: No proper Communication with Gateway: http://172.28.135.35/gateway/instWriteAccess: Can't connect(2) to http://172.28.135.35:80: [b]IO::Socket::INET: Too many open files[/b]

Das Resultat daraus ist dann irgendwann dies hier und in FHEM geht nichts mehr:

Code Auswählen


2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)

Diese Einträge müllen mir extremst das fhem.log zu, da tausendfach in der Sekunde diese Einträge im Log erscheinen.

Außerdem bleibt das Modul oft nach einem Start von Fhem im State Sounding.... hängen und pollt überhaupt nicht mehr. Starte ich FHEM erneut ist dieser Hänger (wenn er denn einer ist) meist weg. Aktuell ist es aber tatsächlich so, dass das Modul immer wieder im State Sounding hängen bleibt, auch nach einem "shutdown restart" in FHEM. Initialisiert das Modul hier nicht richtig? Was bedeutet "Sounding..."?

Edit: Selbst nach einem Reboot des RasPi bleibt es bei "Sounding". Ich werde mal das Gerät stromlos machen (lassen)...

Meine FHEM Installation läuft auf einem RasPi B2 der direkt auf den gleichen Netzwerkswitch (GBit) eingesteckt ist wie das KM200. Das KM200 habe ich daran gehindert ins Internet zu kommen, was das Gerät mit orangem leuchten quittiert. Ausser room sind keine Attr für myKM200 gesetzt.

Jemand eine Idee? Danke!

Grüße Carsten

furban · 03 Juni 2015, 09:17:22

Zitat von: Jorge3711 am 03 Juni 2015, 09:07:04
Hallo zusammen,

ich habe so etwas meine Probleme mit dem Modul. Ich habe immer wieder folgende Meldungen im fhem.log:

Code Auswählen Erweitern
2015.06.03 08:23:53 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/dhwMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:23:59 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/hcMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:27:53 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/activeSwitchProgram: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:27:59 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/fastHeatupFactor: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/manualRoomSetpoint: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/operationMode: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/operationMode: empty answer received 2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/pumpModulation: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/pumpModulation: empty answer received 2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/roomtemperature: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/roomtemperature: empty answer received 2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/status: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/status: empty answer received 2015.06.03 08:28:04 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/switchPrograms/A: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/switchPrograms/A: empty answer received 2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/switchPrograms/B: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/switchPrograms/B: empty answer received 2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temperatureLevels/comfort2: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temperatureLevels/comfort2: empty answer received 2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temperatureLevels/eco: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temperatureLevels/eco: empty answer received 2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temperatureRoomSetpoint: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temperatureRoomSetpoint: empty answer received 2015.06.03 08:28:05 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/temporaryRoomSetpoint: No proper Communication with Gateway: http://172.28.135.35/heatingCircuits/hc1/temporaryRoomSetpoint: empty answer received 2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /notifications: No proper Communication with Gateway: http://172.28.135.35/notifications: empty answer received 2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/CHpumpModulation: No proper Communication with Gateway: http://172.28.135.35/system/appliance/CHpumpModulation: empty answer received 2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/ChimneySweeper: No proper Communication with Gateway: http://172.28.135.35/system/appliance/ChimneySweeper: empty answer received 2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/actualPower: No proper Communication with Gateway: http://172.28.135.35/system/appliance/actualPower: empty answer received 2015.06.03 08:28:06 2: myKM200 : ERROR: Service: /system/appliance/actualSupplyTemperature: No proper Communication with Gateway: http://172.28.135.35/system/appliance/actualSupplyTemperature: empty answer received 2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/flameCurrent: No proper Communication with Gateway: http://172.28.135.35/system/appliance/flameCurrent: empty answer received 2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/gasAirPressure: No proper Communication with Gateway: http://172.28.135.35/system/appliance/gasAirPressure: empty answer received 2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/nominalBurnerLoad: No proper Communication with Gateway: http://172.28.135.35/system/appliance/nominalBurnerLoad: empty answer received 2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/numberOfStarts: No proper Communication with Gateway: http://172.28.135.35/system/appliance/numberOfStarts: empty answer received 2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/powerSetpoint: No proper Communication with Gateway: http://172.28.135.35/system/appliance/powerSetpoint: empty answer received 2015.06.03 08:28:07 2: myKM200 : ERROR: Service: /system/appliance/systemPressure: No proper Communication with Gateway: http://172.28.135.35/system/appliance/systemPressure: empty answer received 2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/appliance/workingTime/centralHeating: No proper Communication with Gateway: http://172.28.135.35/system/appliance/workingTime/centralHeating: empty answer received 2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/appliance/workingTime/secondBurner: No proper Communication with Gateway: http://172.28.135.35/system/appliance/workingTime/secondBurner: empty answer received 2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/appliance/workingTime/totalSystem: No proper Communication with Gateway: http://172.28.135.35/system/appliance/workingTime/totalSystem: empty answer received 2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/healthStatus: No proper Communication with Gateway: http://172.28.135.35/system/healthStatus: empty answer received 2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/heatSources/hs1/actualModulation: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/actualModulation: empty answer received 2015.06.03 08:28:08 2: myKM200 : ERROR: Service: /system/heatSources/hs1/actualPower: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/actualPower: empty answer received 2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/energyReservoir: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/energyReservoir: empty answer received 2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/fuel/caloricValue: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/fuel/caloricValue: empty answer received 2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/fuel/density: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/fuel/density: empty answer received 2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/fuelConsmptCorrFactor: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/fuelConsmptCorrFactor: empty answer received 2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/nominalFuelConsumption: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/nominalFuelConsumption: empty answer received 2015.06.03 08:28:09 2: myKM200 : ERROR: Service: /system/heatSources/hs1/reservoirAlert: No proper Communication with Gateway: http://172.28.135.35/system/heatSources/hs1/reservoirAlert: empty answer received 2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm1/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm1/dhwMode: empty answer received 2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm1/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm1/hcMode: empty answer received 2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm1/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm1/startStop: empty answer received 2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm2/dhwMode: empty answer received 2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm2/hcMode: empty answer received 2015.06.03 08:28:10 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm2/startStop: empty answer received 2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm3/dhwMode: empty answer received 2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm3/hcMode: empty answer received 2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm3/startStop: empty answer received 2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm4/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm4/dhwMode: empty answer received 2015.06.03 08:28:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm4/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm4/hcMode: empty answer received 2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm4/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm4/startStop: empty answer received 2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/dhwMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm5/dhwMode: empty answer received 2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/hcMode: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm5/hcMode: empty answer received 2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/startStop: No proper Communication with Gateway: http://172.28.135.35/system/holidayModes/hm5/startStop: empty answer received 2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/sensors/temperatures/chimney: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/chimney: empty answer received 2015.06.03 08:28:12 2: myKM200 : ERROR: Service: /system/sensors/temperatures/hotWater_t2: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/hotWater_t2: empty answer received 2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/outdoor_t1: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/outdoor_t1: empty answer received 2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/return: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/return: empty answer received 2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/supply_t1: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/supply_t1: empty answer received 2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/supply_t1_setpoint: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/supply_t1_setpoint: empty answer received 2015.06.03 08:28:13 2: myKM200 : ERROR: Service: /system/sensors/temperatures/switch: No proper Communication with Gateway: http://172.28.135.35/system/sensors/temperatures/switch: empty answer received 2015.06.03 08:29:24 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/activeSwitchProgram: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:29:30 2: myKM200 : ERROR: Service: /heatingCircuits/hc1/fastHeatupFactor: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:31:13 2: myKM200 : ERROR: Service: /system/holidayModes/hm5/dhwMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:35:11 2: myKM200 : ERROR: Service: /system/holidayModes/hm2/hcMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out 2015.06.03 08:35:16 2: myKM200 : ERROR: Service: /system/holidayModes/hm3/dhwMode: No proper Communication with Gateway: read from http://172.28.135.35:80 timed out

Die Pollingzeiten wurden nicht über die Attr verändert und entsprechen dem Auslieferungszustand des Moduls. Zum Einsatz kommt Version 0052 des Moduls.

Im weiteren Verlauf kommt es dann irgendwann zu folgenden Einträgen in den Logs:

Code Auswählen Erweitern
2015.05.24 17:43:36 2: myKM200 : ERROR: Service: /gateway/DateTime: No proper Communication with Gateway: http://172.28.135.35/gateway/DateTime: Can't connect(2) to http://172.28.135.35:80: [b]IO::Socket::INET: Too many open files[/b] 2015.05.24 17:43:36 2: myKM200 : ERROR: Service: /gateway/instAccess: No proper Communication with Gateway: http://172.28.135.35/gateway/instAccess: Can't connect(2) to http://172.28.135.35:80: [b]IO::Socket::INET: Too many open files[/b] 2015.05.24 17:43:36 2: myKM200 : ERROR: Service: /gateway/instWriteAccess: No proper Communication with Gateway: http://172.28.135.35/gateway/instWriteAccess: Can't connect(2) to http://172.28.135.35:80: [b]IO::Socket::INET: Too many open files[/b]

Das Resultat daraus ist dann irgendwann dies hier und in FHEM geht nichts mehr:

Code Auswählen Erweitern
2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files) 2015.05.24 18:58:13 1: Accept failed (WEB: Too many open files)

Diese Einträge müllen mir extremst das fhem.log zu, da tausendfach in der Sekunde diese Einträge im Log erscheinen.

Außerdem bleibt das Modul oft nach einem Start von Fhem im State Sounding.... hängen und pollt überhaupt nicht mehr. Starte ich FHEM erneut ist dieser Hänger (wenn er denn einer ist) meist weg. Aktuell ist es aber tatsächlich so, dass das Modul immer wieder im State Sounding hängen bleibt, auch nach einem "shutdown restart" in FHEM. Initialisiert das Modul hier nicht richtig? Was bedeutet "Sounding..."?

Meine FHEM Installation läuft auf einem RasPi B2 der direkt auf den gleichen Netzwerkswitch (GBit) eingesteckt ist wie das KM200. Das KM200 habe ich daran gehindert ins Internet zu kommen, was das Gerät mit orangem leuchten quittiert. Ausser room sind keine Attr für myKM200 gesetzt.

Jemand eine Idee? Danke!

Grüße Carsten

Klingt mal nach einem Grundsätzlichen Kommunikationsproblem mit dem KM200
Ich würde demmal erlauben sich ins Internet zu beinden und mal probieren ob dann wenigstens die App überhaupt funktioniert.
Ansonsten mal testen ob sich das KM200 vom Raspi aus anpingen lässt und ob eine "telnet 172.28.135.35 80" einen Fehler meldet oder einen Verbindung aufbauen kann

Jorge3711 · 03 Juni 2015, 09:31:00

Zitat von: furban am 03 Juni 2015, 09:17:22
Klingt mal nach einem Grundsätzlichen Kommunikationsproblem mit dem KM200
Ich würde demmal erlauben sich ins Internet zu beinden und mal probieren ob dann wenigstens die App überhaupt funktioniert.

Bevor ich das KM200 mit FHEM in Betrieb genommen habe, hatte es Internetzugriff und ich konnte per App darauf zugreifen (und man kann mit der App ja wirklich wenig tun).

Zitat
Ansonsten mal testen ob sich das KM200 vom Raspi aus anpingen lässt und ob eine "telnet 172.28.135.35 80" einen Fehler meldet oder einen Verbindung aufbauen kann

Ping tut, telnet tut:

Code Auswählen


# ping 172.28.135.35 -c10
PING 172.28.135.35 (172.28.135.35) 56(84) bytes of data.
64 bytes from 172.28.135.35: icmp_req=1 ttl=64 time=7.68 ms
64 bytes from 172.28.135.35: icmp_req=2 ttl=64 time=5.68 ms
64 bytes from 172.28.135.35: icmp_req=3 ttl=64 time=3.71 ms
64 bytes from 172.28.135.35: icmp_req=4 ttl=64 time=1.72 ms
64 bytes from 172.28.135.35: icmp_req=5 ttl=64 time=9.76 ms
64 bytes from 172.28.135.35: icmp_req=6 ttl=64 time=7.87 ms
64 bytes from 172.28.135.35: icmp_req=7 ttl=64 time=6.67 ms
64 bytes from 172.28.135.35: icmp_req=8 ttl=64 time=4.76 ms
64 bytes from 172.28.135.35: icmp_req=9 ttl=64 time=2.78 ms
64 bytes from 172.28.135.35: icmp_req=10 ttl=64 time=0.747 ms

--- 172.28.135.35 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9016ms
rtt min/avg/max/mdev = 0.747/5.141/9.766/2.769 ms
# telnet 172.28.135.35 80
Trying 172.28.135.35...
Connected to 172.28.135.35.
Escape character is '^]'.

Habe dem KM200 eben nochmal Internet erlaubt - Zugriff per App möglich.

cyberterminal · 03 Juni 2015, 16:22:21

Zu kurze Afragezyklen können dazu führen, dass sich das KM200 aufhängt, und dann kommt es grnsu zu solchen Fehlermeldungen.

Gruß
Manfred

Buderus KM200 Kommunikationsmodul

cyberterminal