Neuer Adapter EMS-ESP für Bosch Heizungen
-
@chaot Freut mich. Noch Fragen zur km200 Strukturumsetzung?
-
@tp1de
Noch ein paar Fehlermeldungen wegen falscher Datenart:ems-esp.0 2021-06-18 23:16:57.259 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwactivated" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:55.634 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwcirc" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:55.418 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwcircmode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:54.818 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwchargetype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:54.484 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwcircpump" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:53.809 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwcomfort" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:53.471 info State value to set for "ems-esp.0.dhwCircuits.dhw1.wwtype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:52.576 info State value to set for "ems-esp.0.heatSources.hs1.maintenance" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:47.096 info State value to set for "ems-esp.0.heatSources.hs1.heatingactivated" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:46.727 info State value to set for "ems-esp.0.heatSources.hs1.ignwork" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:46.428 info State value to set for "ems-esp.0.heatSources.hs1.fanwork" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:46.188 info State value to set for "ems-esp.0.heatSources.hs1.heatingpump" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:45.492 info State value to set for "ems-esp.0.heatSources.hs1.burngas" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:42.452 info State value to set for "ems-esp.0.heatSources.hs1.tapwateractive" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:42.146 info State value to set for "ems-esp.0.heatSources.hs1.heatingactive" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:16:41.263 info start initializing ems states ems-esp.0 2021-06-18 23:16:40.251 info starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v12.22.1, js-controller: 3.3.12 -
@chaot
Die enum Attribute scheinen falsch übermittelt zu werden vom Ems-esp.
was gibt ems-esp/api/boiler/burngas zurück?Bei mir
{
"name": "burngas",
"fullname": "gas",
"value": 0,
"type": "boolean",
"min": 0,
"max": 1,
"enum": [
0,
1
],
"unit": " ",
"writeable": false
} -
@tp1de sagte in Neuer Adapter EMS-ESP für Bosch Heizungen:
/api/boiler/burngas
{ "name": "burngas", "fullname": "gas", "value": "off", "type": "boolean", "min": 0, "max": 1, "enum": [ "off", "on" ], "unit": " ", "writeable": false }Ist übrigens eine Gastherme Marke Sieger
-
@tp1de
Zum Basteln:
Wenn ich die KM200 Struktur weglasse kommen ein paar mehr:ems-esp.0 2021-06-18 23:45:05.132 info recordings:false hour ems-esp.0 2021-06-18 23:45:05.132 info km200:false 90 secs ems-esp.0 2021-06-18 23:45:05.131 info ems :true 15 secs ems-esp.0 2021-06-18 23:45:05.131 info start polling intervals now. ems-esp.0 2021-06-18 23:45:04.950 info end of initializing ems states ems-esp.0 2021-06-18 23:45:03.835 info State value to set for "ems-esp.0.thermostat.hc1.control" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:45:03.541 info State value to set for "ems-esp.0.thermostat.hc1.reducemode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:45:03.224 info State value to set for "ems-esp.0.thermostat.hc1.heatingtype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:45:01.676 info State value to set for "ems-esp.0.thermostat.hc1.holidaymode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:45:01.373 info State value to set for "ems-esp.0.thermostat.hc1.summermode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:59.262 info State value to set for "ems-esp.0.thermostat.hc1.modetype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:58.598 info State value to set for "ems-esp.0.thermostat.hc1.mode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:57.702 info State value to set for "ems-esp.0.thermostat.wwcircmode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:57.408 info State value to set for "ems-esp.0.thermostat.wwmode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:57.144 info State value to set for "ems-esp.0.thermostat.building" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:54.229 info State value to set for "ems-esp.0.boiler.wwheat" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:54.060 info State value to set for "ems-esp.0.boiler.wwactive" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:53.764 info State value to set for "ems-esp.0.boiler.wwtempok" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:53.644 info State value to set for "ems-esp.0.boiler.wwrecharging" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:53.115 info State value to set for "ems-esp.0.boiler.wwcharging" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:52.856 info State value to set for "ems-esp.0.boiler.wwdisinfecting" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:52.444 info State value to set for "ems-esp.0.boiler.wwonetime" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:52.204 info State value to set for "ems-esp.0.boiler.wwactivated" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:50.634 info State value to set for "ems-esp.0.boiler.wwcirc" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:50.363 info State value to set for "ems-esp.0.boiler.wwcircmode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:49.698 info State value to set for "ems-esp.0.boiler.wwchargetype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:49.365 info State value to set for "ems-esp.0.boiler.wwcircpump" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:48.811 info State value to set for "ems-esp.0.boiler.wwcomfort" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:48.470 info State value to set for "ems-esp.0.boiler.wwtype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:50.634 info State value to set for "ems-esp.0.boiler.wwcirc" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:50.363 info State value to set for "ems-esp.0.boiler.wwcircmode" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:49.698 info State value to set for "ems-esp.0.boiler.wwchargetype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:49.365 info State value to set for "ems-esp.0.boiler.wwcircpump" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:48.811 info State value to set for "ems-esp.0.boiler.wwcomfort" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:48.470 info State value to set for "ems-esp.0.boiler.wwtype" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:47.112 info State value to set for "ems-esp.0.boiler.maintenance" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:41.440 info State value to set for "ems-esp.0.boiler.heatingactivated" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:41.175 info State value to set for "ems-esp.0.boiler.ignwork" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:40.871 info State value to set for "ems-esp.0.boiler.fanwork" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:40.518 info State value to set for "ems-esp.0.boiler.heatingpump" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:39.913 info State value to set for "ems-esp.0.boiler.burngas" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:37.131 info State value to set for "ems-esp.0.boiler.tapwateractive" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:36.858 info State value to set for "ems-esp.0.boiler.heatingactive" has to be type "number" but received type "string" ems-esp.0 2021-06-18 23:44:35.988 info start initializing ems states ems-esp.0 2021-06-18 23:44:34.976 info starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v12.22.1, js-controller: 3.3.12 ems-esp.0 2021-06-18 23:44:34.895 info starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v12.22.1, js-controller: 3.3.12 ems-esp.0 -
@chaot Ok ich registriere gerade, das die Einstellungen von MQTT Settings für das Bolean Format auch für API genommen werden. Das ist nicht so gut. Wenn Du das in den MQTT settings auf 0/1 setzt, dann sollte es funktionieren.
-
@tp1de Jau! Treffer!
Klappt einwandfrei - ein weiterer Punkt für die Installationsanleitung
-
@tp1de Was kommt bei ..../api/thermostat/building zurück?
Bei mir:
name "building" fullname "building" value 2 type "enum" min 1 max 3 enum 0 "light" 1 "medium" 2 "heavy" writeable true -
@tp1de sagte in Neuer Adapter EMS-ESP für Bosch Heizungen:
/api/thermostat/building
{ "name": "building", "fullname": "building", "value": 1, "type": "enum", "min": 0, "max": 2, "enum": [ "light", "medium", "heavy" ], "writeable": true } -
@chaot
Danke fürs erste Feedback. Das Boolean Format sollte ich im Adapter abfangen können, um unabhängig von den MQTT Settings zu sein. Die enum Formate des http get Befehls sind leicht unterschiedlich. Ich schaue Morgen mal den Adapter-Code nach. Die einzelnen Werte nehme ich zum initialieren der ioBroker States und die Werte werden dann je Device gelesen. Kannst Du mir zum Abschluss für heute noch schicken, was bei .../api/thermostat zurückkommt? -
@tp1de gerne doch:
{ "id": 76, "errorcode": "(0)", "lastcode": "A0(816) 18.11.2020 22:50", "datetime": "23:58:35 18/06/2021", "intoffset": 0, "minexttemp": -16, "dampedoutdoortemp": 26, "building": 1, "wwmode": 2, "wwcircmode": 2, "hc1": { "seltemp": 22.5, "currtemp": 25, "mode": 1, "modetype": 1, "daytemp": 22.5, "nighttemp": 20, "designtemp": 75, "offsettemp": 0, "holidaytemp": 17, "targetflowtemp": 28, "summertemp": 16, "summermode": 0, "holidaymode": 0, "nofrosttemp": 3, "roominfluence": 3, "minflowtemp": 5, "maxflowtemp": 75, "flowtempoffset": 5, "heatingtype": 1, "reducemode": 2, "control": 2, "program": 0, "pause": 0, "party": 0 } } -
@tp1de Heute kam noch eine Fehlermeldung:
ems-esp.0 2021-06-19 01:06:45.413 warn State value to set for "ems-esp.0.boiler.selburnpow" has value "123" greater than max "100" -
@chaot oh Deine Heizung kann mehr als 100% Modulation .... Was ist Dein Brenner?
-
@tp1de Das ist eine Heizung von Sieger.
Den Modulationswert habe ich ehrlich gesagt nie beachtet, aber der ist irgendwie seltsam. Aktuell steht 100% im Datenpunkt.
Aber selburnpower ist doch ein Setzwert. Der steht auf 100% und sollte doch sich von sich aus nicht verändern. Entweder liest hier der ems-esp Mist aus oder das ist ein anderer Datenpunkt. -
@chaot Die min / max Werte kommen über das API und ich setze diese dann in den States. Deshalb die Warnmeldung.
Kannst auch in dem State den Max-Wert erhöhen, damit keine Warnung kommt. -
@tp1de Wäre eine Möglichkeit.
Ist aber trotzdem strange wo da 123 herkommen sollten.Edit: Aktuell stehen wieder 123% drin.
-
@chaot Es gibt aktuell noch einige "Ungereimtheiten" in der EMS-ESP Firmware.
Das liegt auch daran, dass mehr als 60 unterschiedliche Hardware-Systeme unterstützt werden.Du kannst ja im Github eine Fehlermeldung aufmachen und den JSON-Output aus dem Browser für das Feld als Beispiel hinzufügen.
Ich habe gerade im Github einen Thread geöffnet: https://github.com/emsesp/EMS-ESP32/issues/76.
Der MQTT Parameter für das Boolean Format verändert die Werte für Boolean and Enum von Number zu Text.
Das betrifft scheinbar auch das Setzen der Werte in den http post Kommandos.D.h. der Adapter funktioniert im Moment nur mit dem Boolean Format 1/0 in den MQTT Settings.
Ich versuche das im Adapter anzupassen, ist aber nicht so trivial. Besser wäre es die FW des ems-esp zu verändern. -
@tp1de Werde ich heute Nachmittag machen. Ich will zuerst noch testen ob der Datenpunkt wirklich übereinstimmt.
Wenn ich also an der Regelung den Maximalwert auf 50% setze müsste der Punkt mitgehen. Wenn nicht, liest er irgendwas falsches aus dem Protokoll aus. -
@chaot sagte in Neuer Adapter EMS-ESP für Bosch Heizungen:
wenn ich also an der Regelung den Maximalwert auf 50% setze
Versuch mal den Wert über den Adapter zu setzen: boiler.burnmaxpower.
-
@tp1de Hi, habe jetzt eine 2. Instanz installiert. Die erste läuft, bis auf ein paar Ungereimtheiten, problemlos.
