Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Neuer Adapter EMS-ESP für Bosch Heizungen

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    Neuer Adapter EMS-ESP für Bosch Heizungen

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      manrum1 @tp1de last edited by

      @tp1de said in Neuer Adapter EMS-ESP für Bosch Heizungen:

      https://github.com/tp1de/ioBroker.ems-esp

      Hi, hab installiert und läuft auf Anhieb. Recordings lasse ich auf influxdb.0 laufen. Bin gespannt auf die Auswertung.
      Was soll ich testen?
      VG

      T 1 Reply Last reply Reply Quote 0
      • T
        tp1de @manrum1 last edited by tp1de

        @manrum1 sagte in Neuer Adapter EMS-ESP für Bosch Heizungen:

        Recordings lasse ich auf influxdb.0 laufen. Bin gespannt auf die Auswertung.
        Was soll ich testen?

        Freut mich, dass alles läuft. Schreib mal wie lange ein Lese-Durchlauf bei Dir läuft. Steht unter statistics.km200-read.
        Bei mir ca. 18-22 Sekunden für 120 Werte ohne Recordings.

        Ich habe den Adapter schon ca. 2 Monate in Betrieb. Mal mit mySQL und mal mit InfluxDB.
        Seit dem js-controller 3.3.x hatte ich aber Probleme mit den Recordings, wenn ich diese mit storeState im Array wegschreibe. Mein InfluxDB Adapter hatte sich regelmäßig nach 1-2 Tagen Laufzeit aufgehängt, wahrscheinlich wegen dem schnellen Schreiben der Recording-States im Array.

        Schreibe nun im Loop einzeln mit 20mSek Verzögerung. Gib mal nach 1-2 Tagen Feedback, ob alles stabil bleibt, oder ob es Stabiltätsprobleme mit den Recordings/InfluxDB gibt. Ich benutze aktuell mySQL.

        So sieht meine Recordings-Auswertung aus:
        5ee2431a-57b2-4788-9f3f-c37c384b6fa0-grafik.png

        M 2 Replies Last reply Reply Quote 0
        • M
          manrum1 @tp1de last edited by

          @tp1de Bei mir steht 30,987. Die Heizung steht aber nicht in meinem lokalen Netz, sondern in meinem Ferienhaus.

          T 1 Reply Last reply Reply Quote 0
          • T
            tp1de @manrum1 last edited by

            @manrum1
            30 Sekunden ist ok bei 90 Sekunden Polling. Ist noch kein Parameter.

            M 1 Reply Last reply Reply Quote 0
            • Chaot
              Chaot @tp1de last edited by

              @tp1de Auf den Adapter warte ich schon lange.

              Installation lief bisher ohne Probleme, aber beim Einrichten taucht gleich dir Frage auf woher ich den Token bekomme.
              Kannst du mir das weiterhelfen?

              T 1 Reply Last reply Reply Quote 0
              • T
                tp1de @Chaot last edited by

                @chaot
                Der Adapter verwendet Api V3 welche nur mit ESP32 funktioniert. Wenn Du noch den noch nicht hast, dann musst Du den kaufen. Alibaba 3 bis 4 Euro ... bei Amazon 8 Euro. Und dann die ESP32 dev Firmware einmal manuell flashen. In den Settings kannst Du dann einstellen ob der Token für writes verwendet wird. Probier erst einmal ohne.
                Unter security settings siehst Du dann den Token per user .... Schlüsselsymbol

                Chaot metaxa 2 Replies Last reply Reply Quote 0
                • Chaot
                  Chaot @tp1de last edited by

                  @tp1de Ok, wer lesen kann..... Steht ja auch oben. Danke. Dann eben den lange überfälligen Wechsel auf den ESP32 sofort durchziehen.

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    tp1de @Chaot last edited by tp1de

                    @chaot Nimm dann auch die aktuellste dev Version. Stand heute ist das v3.1.1b6. Ich habe den AZDelivery ESP32 D1 Mini genommen. Der braucht aber auf jedem Fall USB Power für einen stabilen Betrieb. Bei BBQKees nachlesen .....

                    Chaot 1 Reply Last reply Reply Quote 0
                    • Chaot
                      Chaot @tp1de last edited by

                      @tp1de Ich habe einen D1 ESP32 im Einsatz der scheinbar gut funktioniert.
                      Was mir aktuell nicht weiterhilft ist die KM200 Geschichte.
                      Ich habe bisher den alten Adapter über MQTT ausgelesen und dort hauptsächlich die Betriebsparameter gezogen. Jetzt kommen die scheinbar nich rein, oder ich finde die nicht.
                      Dazu habe ich noch eine Fehlermeldung:

                      ems-esp.0
2021-06-18 22:57:43.685	info	recordings:false hour
ems-esp.0
2021-06-18 22:57:43.685	info	km200:false 90 secs
ems-esp.0
2021-06-18 22:57:43.684	info	ems :true 15 secs
ems-esp.0
2021-06-18 22:57:43.684	info	start polling intervals now.
ems-esp.0
2021-06-18 22:57:43.664	info	end of initializing ems states
ems-esp.0
2021-06-18 22:57:43.664	warn	ems read system error - wrong ip address?
ems-esp.0
2021-06-18 22:57:43.604	info	start initializing ems states
ems-esp.0
2021-06-18 22:57:42.637	info	starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v12.22.1, js-controller: 3.3.12
                      T 1 Reply Last reply Reply Quote 0
                      • T
                        tp1de @Chaot last edited by

                        @chaot Welche Firmware Version. Findet die IP nicht oder API ist nicht V3.

                        Chaot 2 Replies Last reply Reply Quote 0
                        • Chaot
                          Chaot @tp1de last edited by

                          @tp1de ah, ich habe die 3.1.0 erwischt...

                          T 1 Reply Last reply Reply Quote 0
                          • Chaot
                            Chaot @tp1de last edited by

                            @tp1de Genial - läuft scheinbar.

                            Sollte vielleicht erwähnt werden das der mit der 3.1.0 nicht funktioniert.

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              tp1de @Chaot last edited by

                              @chaot gib zuerst mal ems-esp/api/system im Browser ein um zu überprüfen das V3 api funktioniert.

                              1 Reply Last reply Reply Quote 0
                              • T
                                tp1de @Chaot last edited by tp1de

                                @chaot sagte in Neuer Adapter EMS-ESP für Bosch Heizungen:

                                Sollte vielleicht erwähnt werden das der mit der 3.1.0 nicht funktioniert.

                                Ändere ich Morgen ... Gib mal ein Feedback, ob soweit alles funktioniert.
                                ich hatte 3.1.0 nie installiert ...

                                Chaot 2 Replies Last reply Reply Quote 0
                                • Chaot
                                  Chaot @tp1de last edited by

                                  @tp1de Der Befehl funktioniert bei mir nicht. Ich muss das über die feste IP Adresse aufrufen. Dann klappt das allerdings. Der Adapter macht das auch klaglos über die feste IP.

                                  Antwort:

                                  {
  "System": {
    "version": "3.1.1b6",
    "uptime": "000+00:09:26.654",
    "freemem": 180
  },
  "Status": {
    "bus": "connected",
    "bus protocol": "Buderus",
    "#telegrams received": 551,
    "#read requests sent": 161,
    "#write requests sent": 0,
    "#incomplete telegrams": 0,
    "#tx fails": 0,
    "rx line quality": 100,
    "tx line quality": 100,
    "#dallas sensors": 0,
    "#dallas reads": 0,
    "#dallas fails": 0
  },
  "Devices": [
    {
      "type": "Boiler",
      "name": "BK13/BK15/Smartline/GB1x2 (DeviceID:0x08, ProductID:64, Version:03.06)",
      "handlers": "0x10 0x11 0x14 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A 0xD1 0xE3 0xE4 0xE5 0xE6 0xE9 0xEA"
    },
    {
      "type": "Thermostat",
      "name": "ES73 (DeviceID:0x10, ProductID:76, Version:02.08)",
      "handlers": "0xA3 0x06 0xA2 0x12 0x3E 0x3D 0x3F 0x48 0x47 0x49 0x52 0x51 0x53 0x5C 0x5B 0x5D 0xA5 0x37"
    },
    {
      "type": "Controller",
      "name": "BC10/RFM20 (DeviceID:0x09, ProductID:68, Version:02.03)",
      "handlers": ""
    }
  ]
}
                                  T 1 Reply Last reply Reply Quote 0
                                  • T
                                    tp1de @Chaot last edited by

                                    @chaot Freut mich. Noch Fragen zur km200 Strukturumsetzung?

                                    1 Reply Last reply Reply Quote 0
                                    • Chaot
                                      Chaot @tp1de last edited by

                                      @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
                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        tp1de @Chaot last edited by

                                        @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
                                        }

                                        Chaot 2 Replies Last reply Reply Quote 0
                                        • Chaot
                                          Chaot @tp1de last edited by Chaot

                                          @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

                                          T 1 Reply Last reply Reply Quote 0
                                          • Chaot
                                            Chaot @tp1de last edited by

                                            @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
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            817
                                            Online

                                            30.4k
                                            Users

                                            76.7k
                                            Topics

                                            1.2m
                                            Posts

                                            api bosch buderus ems-esp heizungssteuerung junkers km200 netfit
                                            55
                                            682
                                            70111
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo