Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Adapter: Amtron Wallbox

NEWS

  • wichtiges UPDATE für controller 7.2.2 im stable
    HomoranH
    Homoran
    8
    1
    213

  • Neues YouTube-Video: Visualisierung im Devices-Adapter
    BluefoxB
    Bluefox
    14
    1
    2.5k

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    2.8k

Adapter: Amtron Wallbox

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
28 Beiträge 10 Kommentatoren 3.2k Aufrufe 9 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • H helpme

    @icebear said in Adapter: Amtron Wallbox:

    Hallo, ich hab jetzt auch mal den Adapter installiert und hab eine kurze Frage.

    Was ist mit API-Schlüssel gemeint? Was muß ich da eintragen?

    WB= Amtron xtra C11 mit App

    EDIT: Hat sich erledigt, hatte mich nur verschrieben beim API-Schlüssel, jetzt gehts

    Hallo zusammen, hab gerade auch den Adapter installiert.
    Was ist mit API Schlüssel gemeint? Ist das die PIN1 von der Wallbox?
    Wenn ich diese eingebe, werden mir allerdings keine Daten im Apdater angezeigt.
    Amtron xtra 11

    icebearI Online
    icebearI Online
    icebear
    schrieb am zuletzt editiert von icebear
    #8

    @helpme said in Adapter: Amtron Wallbox:

    Ist das die PIN1 von der Wallbox?

    Ja das ist die PIN

    Name, IP und Typ sind richtig eingetragen?

    1 Antwort Letzte Antwort
    0
    • Rene_HMR Rene_HM

      Es gibt eine neue Version des Adapters auf github.

      Diese Version unterstützt nun die RestAPI und damit auch die XTRA, Premium usw.

      Derzeit werden folgende Daten gelesen:

      • allgemeine Geräte-Informationen
      • Ladedaten
      • Statistik-Daten

      bild2.PNG

      Im nächsten step kommt dann noch das Schreiben der Daten (z.Bsp. max. Ladestrom).

      Achtung Die Auswahl des Gerätetypes in der Geräte-Liste ist nicht schön lesbar. Einfach ein wenig hoch und runtersrcollen:
      bild1.PNG

      J Offline
      J Offline
      jrichl
      schrieb am zuletzt editiert von
      #9

      @rene_hm

      Hallo, ich habe den Adapter jetzt auch einmal installiert, und er funktioniert auf meiner XTRA soweit auch gut. Ich wollte nur nachfragen ob inzwischen auch das Schreiben von Daten - also der Ladestrom implementiert ist? Einen entsprechenden Datenpunkt dazu kann ich nicht finden.

      Bildschirmfoto 2024-07-10 um 11.50.08.png

      Oder ist das ActPwr der entsprechend gesetzt werden muss?

      J 1 Antwort Letzte Antwort
      0
      • G Offline
        G Offline
        goudi
        schrieb am zuletzt editiert von
        #10

        Hy, ich habe die Amtron Professional mit Firmwarestand 5.22.5

        Nach diesem Link habe ich die REST api aktiviert und kann wie auch auslesen.

        https://www.adminlabs.de/mennekes-amtron-wallbox-api-auslesen/

        Aber ich bekomme leider keine Verbindung im IObroker. Wo ist um alles in der Welt die PIN einzustellen?

        Noch ne Frage zur Anwendung:
        Kann ich über IObroker dann irgendwann die Energiesteuerung (Überschussladen) einstellen?
        Kann ich je nach Authorisierung mit unterschiedlichen RFID Chips zwischen "normalem Laden" und "überschussladen" umschalten?
        Sollte das jetzt schon gehen, würde ich mich freuen wenn mir jemand verrät wie...

        icebearI 1 Antwort Letzte Antwort
        0
        • G goudi

          Hy, ich habe die Amtron Professional mit Firmwarestand 5.22.5

          Nach diesem Link habe ich die REST api aktiviert und kann wie auch auslesen.

          https://www.adminlabs.de/mennekes-amtron-wallbox-api-auslesen/

          Aber ich bekomme leider keine Verbindung im IObroker. Wo ist um alles in der Welt die PIN einzustellen?

          Noch ne Frage zur Anwendung:
          Kann ich über IObroker dann irgendwann die Energiesteuerung (Überschussladen) einstellen?
          Kann ich je nach Authorisierung mit unterschiedlichen RFID Chips zwischen "normalem Laden" und "überschussladen" umschalten?
          Sollte das jetzt schon gehen, würde ich mich freuen wenn mir jemand verrät wie...

          icebearI Online
          icebearI Online
          icebear
          schrieb am zuletzt editiert von
          #11

          @goudi said in Adapter: Amtron Wallbox:

          Wo ist um alles in der Welt die PIN einzustellen?

          Hier:

          amtron.png

          G 1 Antwort Letzte Antwort
          0
          • icebearI icebear

            @goudi said in Adapter: Amtron Wallbox:

            Wo ist um alles in der Welt die PIN einzustellen?

            Hier:

            amtron.png

            G Offline
            G Offline
            goudi
            schrieb am zuletzt editiert von
            #12

            @icebear Vielen Dank für den Hinweis,
            im Iobroker ist mir das klar - aber nicht in der BOX - Oberfläche - dort finde ich eine solche Angabe nicht.
            Ich hoffe, mir kann das jemand auf der anderen Seite auch zeigen.

            liebe Grüße

            1 Antwort Letzte Antwort
            0
            • icebearI Online
              icebearI Online
              icebear
              schrieb am zuletzt editiert von
              #13

              @goudi said in Adapter: Amtron Wallbox:

              aber nicht in der BOX - Oberfläche

              Ah, Sorry ich hab grad mal nachgeschaut und gesehen das die Amtron Professional mit einer anderen Oberfläche arbeitet als die Xtra.

              Ich weiß nicht ob der Adapter mit der Professional funktioniert, da mußte den Adapter Entwickler fragen, am besten im Git-Hub.

              Du kannst ja versuchen was passiert wenn du in den Einstellungen auf der Box bei 'Rest-Schnittstelle' einstellen kannst, also vielleicht ohne UUID

              1 Antwort Letzte Antwort
              0
              • Rene_HMR Rene_HM

                Für die Mennekes Amtron Wallbox gibt es nun einen Adapter für ioBroker.

                Features:

                • Lesen von System- und Status-Informationen
                • derzeit wird die REST API unterstützt. Diese bietet nur das Lesen von Daten.
                • getestet auf einer AMTRON Charge Control 11 C2

                Bild1.PNG
                to do:

                • Erweiterung auf andere Typen von Amtron
                • Schreiben von Daten

                Der Adapter kann über github oder NPM installiert werden.

                Für feedback, Anregungen und Testergebnisse wäre ich dankbar...

                L Offline
                L Offline
                Lennerocker
                schrieb am zuletzt editiert von
                #14

                Hallo,

                ich bin seit gestern Besitzer einer Mennekes Amtron 4you 500, die ich auch in iobroker einbinden will. Bei der Suche nach einem passenden Adapter bin ich auf deinen gestoßen. Installation ohne Probleme. Die Instanz ist aktiviert (verbunden mit Host, Lebenszeichen). Danach aber eine Fehlermeldung: exception in read_rest [Error: connect ETIMEDOUT
                Kann es sein, dass der Adapter für meine Box nicht funktioniert oder mache ich da einen grundlegenden Fehler?

                VG Bernard

                @rene_hm said in Adapter: Amtron Wallbox:

                Für die Mennekes Amtron Wallbox gibt es nun einen Adapter für ioBroker.

                Features:

                • Lesen von System- und Status-Informationen
                • derzeit wird die REST API unterstützt. Diese bietet nur das Lesen von Daten.
                • getestet auf einer AMTRON Charge Control 11 C2

                Bild1.PNG
                to do:

                • Erweiterung auf andere Typen von Amtron
                • Schreiben von Daten

                Der Adapter kann über github oder NPM installiert werden.

                Für feedback, Anregungen und Testergebnisse wäre ich dankbar...

                Rene_HMR 1 Antwort Letzte Antwort
                0
                • L Lennerocker

                  Hallo,

                  ich bin seit gestern Besitzer einer Mennekes Amtron 4you 500, die ich auch in iobroker einbinden will. Bei der Suche nach einem passenden Adapter bin ich auf deinen gestoßen. Installation ohne Probleme. Die Instanz ist aktiviert (verbunden mit Host, Lebenszeichen). Danach aber eine Fehlermeldung: exception in read_rest [Error: connect ETIMEDOUT
                  Kann es sein, dass der Adapter für meine Box nicht funktioniert oder mache ich da einen grundlegenden Fehler?

                  VG Bernard

                  @rene_hm said in Adapter: Amtron Wallbox:

                  Für die Mennekes Amtron Wallbox gibt es nun einen Adapter für ioBroker.

                  Features:

                  • Lesen von System- und Status-Informationen
                  • derzeit wird die REST API unterstützt. Diese bietet nur das Lesen von Daten.
                  • getestet auf einer AMTRON Charge Control 11 C2

                  Bild1.PNG
                  to do:

                  • Erweiterung auf andere Typen von Amtron
                  • Schreiben von Daten

                  Der Adapter kann über github oder NPM installiert werden.

                  Für feedback, Anregungen und Testergebnisse wäre ich dankbar...

                  Rene_HMR Offline
                  Rene_HMR Offline
                  Rene_HM
                  Developer
                  schrieb am zuletzt editiert von
                  #15

                  @lennerocker

                  Die Amtron 4you 500 kenne ich noch gar nicht, deshalb gehe ich erst mal davon aus, dass sie noch nicht unterstützt wird. Wir müssen also erst mal herausfinden, wie man mit dem Teil reden muss.

                  Wenn die Box die RestApi unterstützt, du dieses Interface aktiviert hast, könnte sie als Type "ChargeControl"
                  funktionieren.

                  Du kannst aber auch testweise im browser mal diese URL aufrufen (natürlich mit der IP, wie sie bei dir im Netzwerk eingerichtet ist)

                  http:// DEINE_IP /rest/full_state
                  
                  L 1 Antwort Letzte Antwort
                  0
                  • Rene_HMR Rene_HM

                    @lennerocker

                    Die Amtron 4you 500 kenne ich noch gar nicht, deshalb gehe ich erst mal davon aus, dass sie noch nicht unterstützt wird. Wir müssen also erst mal herausfinden, wie man mit dem Teil reden muss.

                    Wenn die Box die RestApi unterstützt, du dieses Interface aktiviert hast, könnte sie als Type "ChargeControl"
                    funktionieren.

                    Du kannst aber auch testweise im browser mal diese URL aufrufen (natürlich mit der IP, wie sie bei dir im Netzwerk eingerichtet ist)

                    http:// DEINE_IP /rest/full_state
                    
                    L Offline
                    L Offline
                    Lennerocker
                    schrieb am zuletzt editiert von
                    #16

                    @rene_hm

                    mit dem Link startet das Webinterface der Box mit der Loginaufforderung. Im Protokollbereich wird für den erfolgreichen Loginversuch die Event-ID REST_API-2 angegeben. Kannst Du damit was anfangen?

                    1 Antwort Letzte Antwort
                    0
                    • J jrichl

                      @rene_hm

                      Hallo, ich habe den Adapter jetzt auch einmal installiert, und er funktioniert auf meiner XTRA soweit auch gut. Ich wollte nur nachfragen ob inzwischen auch das Schreiben von Daten - also der Ladestrom implementiert ist? Einen entsprechenden Datenpunkt dazu kann ich nicht finden.

                      Bildschirmfoto 2024-07-10 um 11.50.08.png

                      Oder ist das ActPwr der entsprechend gesetzt werden muss?

                      J Offline
                      J Offline
                      jokeras
                      schrieb am zuletzt editiert von
                      #17

                      @jrichl

                      Ich habe auch die Xtra 11 C2. Im Folder charge habe ich allerdings nur "null" Daten. Im Folder info sind Daten da. Aber eben nicht die Total Energy, die ich gern auslesen würde.
                      Was hast du im Adapter eingestellt? IP + PIN 1 (App PIN)?
                      0cca2c69-c5cb-4178-9085-3e5ec8dc3109-grafik.png

                      5b1a4456-318f-4568-b3d6-4320016763ec-grafik.png

                      1 Antwort Letzte Antwort
                      0
                      • T Offline
                        T Offline
                        Trapper
                        schrieb am zuletzt editiert von
                        #18

                        Hallo, ich habe eine Amtron Charge Control 11 C2. Ixch habe sie schon drei Jahre und habe sie bisher mit dem Adapter abgefragt. Jetzt musste ich den iobroker neu aufsetzen und habe ein Backup eingespielt. Seitdem fragt der Adapter die Box nicht mehr ab. Eingestellt ist eine Minute als Abfrageintervall. Starte ich den Adapter per Hand neu, werden alle Daten abgerufen. Hat jemand eine Idee dazu? Wie macht der Adapter das wieder automatisch? Danke
                        Klaus

                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • T Trapper

                          Hallo, ich habe eine Amtron Charge Control 11 C2. Ixch habe sie schon drei Jahre und habe sie bisher mit dem Adapter abgefragt. Jetzt musste ich den iobroker neu aufsetzen und habe ein Backup eingespielt. Seitdem fragt der Adapter die Box nicht mehr ab. Eingestellt ist eine Minute als Abfrageintervall. Starte ich den Adapter per Hand neu, werden alle Daten abgerufen. Hat jemand eine Idee dazu? Wie macht der Adapter das wieder automatisch? Danke
                          Klaus

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #19

                          @Trapper sagte:

                          Hat jemand eine Idee dazu?

                          Schau ins Log.

                          Linux-Werkzeugkasten:
                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                          NodeJS Fixer Skript:
                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                          T 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @Trapper sagte:

                            Hat jemand eine Idee dazu?

                            Schau ins Log.

                            T Offline
                            T Offline
                            Trapper
                            schrieb am zuletzt editiert von
                            #20

                            @Thomas-Braun
                            Hi,
                            im Log habe ich diese Zeile gefunden

                            2026-06-08 23:03:54.003 - info: amtronwallbox.0 (75592) on message {"command":"checkCurrentVersion","message":{"test":"aaa","test2":"bbb"},"from":"system.adapter.admin.0","callback":{"message":{"test":"aaa","test2":"bbb"},"id":60,"ack":false,"time":1780952634002},"_id":32509577}
                            

                            und die

                            2026-06-08 22:28:51.512 - info: amtronwallbox.0 (74198) amtronwallbox1: 1 cron job(s) created
                            

                            andere Einträge beschreiben das Neustarten, also terminate usw. bis start
                            Alle diese Einträge immer im Zusammenhang mit den manuellen Neustarts, die ich gerade gemacht hatte. Sonst ist im ganzen Tag kein Amtron Eintrag.
                            Adapter ist gün
                            Gruß
                            Klaus

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • T Trapper

                              @Thomas-Braun
                              Hi,
                              im Log habe ich diese Zeile gefunden

                              2026-06-08 23:03:54.003 - info: amtronwallbox.0 (75592) on message {"command":"checkCurrentVersion","message":{"test":"aaa","test2":"bbb"},"from":"system.adapter.admin.0","callback":{"message":{"test":"aaa","test2":"bbb"},"id":60,"ack":false,"time":1780952634002},"_id":32509577}
                              

                              und die

                              2026-06-08 22:28:51.512 - info: amtronwallbox.0 (74198) amtronwallbox1: 1 cron job(s) created
                              

                              andere Einträge beschreiben das Neustarten, also terminate usw. bis start
                              Alle diese Einträge immer im Zusammenhang mit den manuellen Neustarts, die ich gerade gemacht hatte. Sonst ist im ganzen Tag kein Amtron Eintrag.
                              Adapter ist gün
                              Gruß
                              Klaus

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #21

                              @Trapper sagte:

                              beschreiben das Neustarten, also terminate usw. bis start

                              Zeig mehr Kontext, kürz da nichts weg.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              T 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @Trapper sagte:

                                beschreiben das Neustarten, also terminate usw. bis start

                                Zeig mehr Kontext, kürz da nichts weg.

                                T Offline
                                T Offline
                                Trapper
                                schrieb am zuletzt editiert von Trapper
                                #22

                                @Thomas-Braun

                                2026-06-08 22:46:20.911 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 (force=false, process=true)
                                2026-06-08 22:46:20.913 - info: amtronwallbox.0 (74198) Got terminate signal TERMINATE_YOURSELF
                                2026-06-08 22:46:20.915 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 send kill signal
                                2026-06-08 22:46:20.914 - info: amtronwallbox.0 (74198) terminating
                                2026-06-08 22:46:20.915 - info: amtronwallbox.0 (74198) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2026-06-08 22:46:21.415 - info: amtronwallbox.0 (74198) terminating
                                2026-06-08 22:46:21.545 - info: host.iobroker instance system.adapter.amtronwallbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2026-06-08 22:46:24.883 - info: host.iobroker instance system.adapter.amtronwallbox.0 in version "1.0.0" started with pid 74880
                                2026-06-08 22:46:26.151 - info: amtronwallbox.0 (74880) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.amtronwallbox, node: v22.22.3, js-controller: 7.0.7
                                2026-06-08 22:46:26.215 - info: amtronwallbox.0 (74880) amtronwallbox1: 1 cron job(s) created
                                

                                Das ist so eine Sequenz

                                Muss jetzt schlafen, Frühschicht 🙄
                                Danke erst einmal

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • T Trapper

                                  @Thomas-Braun

                                  2026-06-08 22:46:20.911 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 (force=false, process=true)
                                  2026-06-08 22:46:20.913 - info: amtronwallbox.0 (74198) Got terminate signal TERMINATE_YOURSELF
                                  2026-06-08 22:46:20.915 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 send kill signal
                                  2026-06-08 22:46:20.914 - info: amtronwallbox.0 (74198) terminating
                                  2026-06-08 22:46:20.915 - info: amtronwallbox.0 (74198) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                  2026-06-08 22:46:21.415 - info: amtronwallbox.0 (74198) terminating
                                  2026-06-08 22:46:21.545 - info: host.iobroker instance system.adapter.amtronwallbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                  2026-06-08 22:46:24.883 - info: host.iobroker instance system.adapter.amtronwallbox.0 in version "1.0.0" started with pid 74880
                                  2026-06-08 22:46:26.151 - info: amtronwallbox.0 (74880) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.amtronwallbox, node: v22.22.3, js-controller: 7.0.7
                                  2026-06-08 22:46:26.215 - info: amtronwallbox.0 (74880) amtronwallbox1: 1 cron job(s) created
                                  

                                  Das ist so eine Sequenz

                                  Muss jetzt schlafen, Frühschicht 🙄
                                  Danke erst einmal

                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #23

                                  @Trapper

                                  Das sind doch nur 6 Sekunden. Zeig mal 3-4 Minuten.
                                  Der Adapter scheint aber 'sheduled' zu sein.

                                  Linux-Werkzeugkasten:
                                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                  NodeJS Fixer Skript:
                                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                  T 1 Antwort Letzte Antwort
                                  0
                                  • Thomas BraunT Thomas Braun

                                    @Trapper

                                    Das sind doch nur 6 Sekunden. Zeig mal 3-4 Minuten.
                                    Der Adapter scheint aber 'sheduled' zu sein.

                                    T Offline
                                    T Offline
                                    Trapper
                                    schrieb am zuletzt editiert von Trapper
                                    #24

                                    @Thomas-Braun

                                    2026-06-08 22:46:20.913 - info: amtronwallbox.0 (74198) Got terminate signal TERMINATE_YOURSELF
                                    2026-06-08 22:46:20.915 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 send kill signal
                                    2026-06-08 22:46:20.914 - info: amtronwallbox.0 (74198) terminating
                                    2026-06-08 22:46:20.915 - info: amtronwallbox.0 (74198) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                    2026-06-08 22:46:21.415 - info: amtronwallbox.0 (74198) terminating
                                    2026-06-08 22:46:21.545 - info: host.iobroker instance system.adapter.amtronwallbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                    2026-06-08 22:46:23.916 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:46:23.962 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:46:24.277 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:46:24.438 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:46:24.883 - info: host.iobroker instance system.adapter.amtronwallbox.0 in version "1.0.0" started with pid 74880
                                    2026-06-08 22:46:25.027 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:46:26.151 - info: amtronwallbox.0 (74880) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.amtronwallbox, node: v22.22.3, js-controller: 7.0.7
                                    2026-06-08 22:46:26.215 - info: amtronwallbox.0 (74880) amtronwallbox1: 1 cron job(s) created
                                    2026-06-08 22:46:26.220 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:46:27.506 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:46:30.502 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:46:30.696 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:46:30.707 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:46:30.825 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:46:30.827 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:46:30.853 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:46:30.856 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:46:30.880 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:46:30.884 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:46:30.900 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:46:30.903 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:46:30.987 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:46:31.002 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:46:31.030 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:46:31.035 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:46:59.751 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:04.794 - info: midea.0 (1493) LanClient[151732605798558]: LAN authentication succeeded (tcpKey 32 bytes)
                                    2026-06-08 22:47:15.697 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:47:15.708 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:47:15.731 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:47:15.733 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:15.889 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:47:15.892 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:15.981 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:47:15.985 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:16.038 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:47:16.041 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:16.131 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:47:16.135 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:16.200 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:47:16.202 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:47:24.030 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:47:24.071 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:47:24.353 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:47:24.516 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:47:24.634 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:47:25.149 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:47:30.676 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:47:33.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:47:53.173 - info: amtronwallbox.0 (74880) on message {"command":"checkCurrentVersion","message":{"test":"aaa","test2":"bbb"},"from":"system.adapter.admin.0","callback":{"message":{"test":"aaa","test2":"bbb"},"id":53,"ack":false,"time":1780951673171},"_id":32509570}
                                    2026-06-08 22:48:00.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:48:00.703 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:48:00.882 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:00.883 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:00.985 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:00.988 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:01.053 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:01.056 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:01.074 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:01.080 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:01.146 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:01.151 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:01.173 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:01.178 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:01.721 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:13.537 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 (force=false, process=true)
                                    2026-06-08 22:48:13.541 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 send kill signal
                                    2026-06-08 22:48:13.542 - info: amtronwallbox.0 (74880) Got terminate signal TERMINATE_YOURSELF
                                    2026-06-08 22:48:13.545 - info: amtronwallbox.0 (74880) terminating
                                    2026-06-08 22:48:13.545 - info: amtronwallbox.0 (74880) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                    2026-06-08 22:48:14.045 - info: amtronwallbox.0 (74880) terminating
                                    2026-06-08 22:48:14.167 - info: host.iobroker instance system.adapter.amtronwallbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                    2026-06-08 22:48:17.618 - info: host.iobroker instance system.adapter.amtronwallbox.0 in version "1.0.0" started with pid 74982
                                    2026-06-08 22:48:18.591 - info: amtronwallbox.0 (74982) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.amtronwallbox, node: v22.22.3, js-controller: 7.0.7
                                    2026-06-08 22:48:18.658 - info: amtronwallbox.0 (74982) amtronwallbox1: 1 cron job(s) created
                                    2026-06-08 22:48:23.963 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:48:24.007 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:48:24.309 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:48:24.469 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:48:24.583 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:48:25.105 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:48:33.505 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:48:36.505 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:48:45.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:48:45.709 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:48:45.735 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:45.736 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:45.837 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:45.840 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:45.906 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:45.908 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:45.946 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:45.948 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:46.039 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:46.043 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:48:46.069 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:48:46.075 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:04.231 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:24.280 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:49:24.327 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:49:24.679 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:49:24.854 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:49:24.981 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:49:25.560 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:49:30.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:49:30.712 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:49:30.785 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:49:30.786 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:30.890 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:49:30.895 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:30.921 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:49:30.924 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:30.996 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:49:30.998 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:31.058 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:49:31.062 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:31.081 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:49:31.085 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:49:36.509 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:49:39.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:50:05.826 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:15.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:50:15.703 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:50:15.726 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:50:15.727 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:15.754 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:50:15.758 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:15.798 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:50:15.802 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:15.900 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:50:15.903 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:15.928 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:50:15.931 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:15.952 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:50:15.956 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:50:23.933 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:50:23.977 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:50:24.284 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:50:24.448 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:50:24.569 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:50:25.035 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:50:39.506 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:50:42.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:51:00.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:51:00.706 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:51:00.751 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:00.752 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:00.780 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:00.783 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:00.809 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:00.811 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:00.843 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:00.844 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:00.965 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:00.971 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:00.989 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:00.993 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:07.590 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:24.025 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:51:24.068 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:51:24.385 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:51:24.534 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:51:24.636 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:51:25.131 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:51:42.505 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:51:45.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:51:45.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:51:45.706 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:51:45.773 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:45.774 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:45.860 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:45.864 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:45.958 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:45.961 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:45.994 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:45.996 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:46.100 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:46.105 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:51:46.192 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:51:46.195 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:09.443 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:12.140 - info: midea.0 (1493) LanClient[151732605798558]: LAN authentication succeeded (tcpKey 32 bytes)
                                    2026-06-08 22:52:23.892 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:52:23.939 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:52:24.240 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:52:24.392 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:52:24.506 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:52:24.988 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    2026-06-08 22:52:30.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:52:30.706 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:52:30.737 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:52:30.739 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:30.851 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:52:30.855 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:30.878 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:52:30.884 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:30.898 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:52:30.907 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:30.926 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:52:30.948 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:30.971 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:52:30.978 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:52:45.506 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                    2026-06-08 22:52:48.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                    2026-06-08 22:53:11.819 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:15.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                    2026-06-08 22:53:15.711 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                    2026-06-08 22:53:15.729 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:53:15.730 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:15.763 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:53:15.767 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:15.790 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:53:15.795 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:15.845 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:53:15.847 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:15.934 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:53:15.938 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:15.959 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                    2026-06-08 22:53:15.962 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                    2026-06-08 22:53:23.950 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                    2026-06-08 22:53:23.994 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                    2026-06-08 22:53:24.316 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                    2026-06-08 22:53:24.487 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                    2026-06-08 22:53:24.599 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                    2026-06-08 22:53:25.083 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                    

                                    Ja, da ist ein cron, aber es tut sich nichts

                                    Bin wieder da und voller Erwartung, heute ist nicht ein Eintrag für den Adapter im Log

                                    Rene_HMR 1 Antwort Letzte Antwort
                                    0
                                    • T Trapper

                                      @Thomas-Braun

                                      2026-06-08 22:46:20.913 - info: amtronwallbox.0 (74198) Got terminate signal TERMINATE_YOURSELF
                                      2026-06-08 22:46:20.915 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 send kill signal
                                      2026-06-08 22:46:20.914 - info: amtronwallbox.0 (74198) terminating
                                      2026-06-08 22:46:20.915 - info: amtronwallbox.0 (74198) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                      2026-06-08 22:46:21.415 - info: amtronwallbox.0 (74198) terminating
                                      2026-06-08 22:46:21.545 - info: host.iobroker instance system.adapter.amtronwallbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                      2026-06-08 22:46:23.916 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:46:23.962 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:46:24.277 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:46:24.438 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:46:24.883 - info: host.iobroker instance system.adapter.amtronwallbox.0 in version "1.0.0" started with pid 74880
                                      2026-06-08 22:46:25.027 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:46:26.151 - info: amtronwallbox.0 (74880) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.amtronwallbox, node: v22.22.3, js-controller: 7.0.7
                                      2026-06-08 22:46:26.215 - info: amtronwallbox.0 (74880) amtronwallbox1: 1 cron job(s) created
                                      2026-06-08 22:46:26.220 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:46:27.506 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:46:30.502 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:46:30.696 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:46:30.707 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:46:30.825 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:46:30.827 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:46:30.853 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:46:30.856 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:46:30.880 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:46:30.884 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:46:30.900 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:46:30.903 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:46:30.987 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:46:31.002 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:46:31.030 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:46:31.035 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:46:59.751 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:04.794 - info: midea.0 (1493) LanClient[151732605798558]: LAN authentication succeeded (tcpKey 32 bytes)
                                      2026-06-08 22:47:15.697 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:47:15.708 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:47:15.731 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:47:15.733 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:15.889 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:47:15.892 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:15.981 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:47:15.985 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:16.038 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:47:16.041 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:16.131 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:47:16.135 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:16.200 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:47:16.202 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:47:24.030 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:47:24.071 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:47:24.353 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:47:24.516 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:47:24.634 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:47:25.149 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:47:30.676 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:47:33.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:47:53.173 - info: amtronwallbox.0 (74880) on message {"command":"checkCurrentVersion","message":{"test":"aaa","test2":"bbb"},"from":"system.adapter.admin.0","callback":{"message":{"test":"aaa","test2":"bbb"},"id":53,"ack":false,"time":1780951673171},"_id":32509570}
                                      2026-06-08 22:48:00.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:48:00.703 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:48:00.882 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:00.883 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:00.985 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:00.988 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:01.053 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:01.056 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:01.074 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:01.080 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:01.146 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:01.151 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:01.173 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:01.178 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:01.721 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:13.537 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 (force=false, process=true)
                                      2026-06-08 22:48:13.541 - info: host.iobroker stopInstance system.adapter.amtronwallbox.0 send kill signal
                                      2026-06-08 22:48:13.542 - info: amtronwallbox.0 (74880) Got terminate signal TERMINATE_YOURSELF
                                      2026-06-08 22:48:13.545 - info: amtronwallbox.0 (74880) terminating
                                      2026-06-08 22:48:13.545 - info: amtronwallbox.0 (74880) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                      2026-06-08 22:48:14.045 - info: amtronwallbox.0 (74880) terminating
                                      2026-06-08 22:48:14.167 - info: host.iobroker instance system.adapter.amtronwallbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                      2026-06-08 22:48:17.618 - info: host.iobroker instance system.adapter.amtronwallbox.0 in version "1.0.0" started with pid 74982
                                      2026-06-08 22:48:18.591 - info: amtronwallbox.0 (74982) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.amtronwallbox, node: v22.22.3, js-controller: 7.0.7
                                      2026-06-08 22:48:18.658 - info: amtronwallbox.0 (74982) amtronwallbox1: 1 cron job(s) created
                                      2026-06-08 22:48:23.963 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:48:24.007 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:48:24.309 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:48:24.469 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:48:24.583 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:48:25.105 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:48:33.505 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:48:36.505 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:48:45.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:48:45.709 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:48:45.735 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:45.736 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:45.837 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:45.840 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:45.906 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:45.908 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:45.946 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:45.948 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:46.039 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:46.043 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:48:46.069 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:48:46.075 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:04.231 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:24.280 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:49:24.327 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:49:24.679 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:49:24.854 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:49:24.981 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:49:25.560 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:49:30.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:49:30.712 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:49:30.785 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:49:30.786 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:30.890 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:49:30.895 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:30.921 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:49:30.924 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:30.996 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:49:30.998 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:31.058 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:49:31.062 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:31.081 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:49:31.085 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:49:36.509 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:49:39.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:50:05.826 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:15.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:50:15.703 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:50:15.726 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:50:15.727 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:15.754 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:50:15.758 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:15.798 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:50:15.802 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:15.900 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:50:15.903 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:15.928 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:50:15.931 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:15.952 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:50:15.956 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:50:23.933 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:50:23.977 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:50:24.284 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:50:24.448 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:50:24.569 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:50:25.035 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:50:39.506 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:50:42.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:51:00.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:51:00.706 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:51:00.751 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:00.752 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:00.780 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:00.783 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:00.809 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:00.811 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:00.843 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:00.844 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:00.965 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:00.971 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:00.989 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:00.993 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:07.590 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:24.025 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:51:24.068 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:51:24.385 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:51:24.534 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:51:24.636 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:51:25.131 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:51:42.505 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:51:45.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:51:45.698 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:51:45.706 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:51:45.773 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:45.774 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:45.860 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:45.864 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:45.958 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:45.961 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:45.994 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:45.996 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:46.100 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:46.105 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:51:46.192 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:51:46.195 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:09.443 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:12.140 - info: midea.0 (1493) LanClient[151732605798558]: LAN authentication succeeded (tcpKey 32 bytes)
                                      2026-06-08 22:52:23.892 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:52:23.939 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:52:24.240 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:52:24.392 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:52:24.506 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:52:24.988 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      2026-06-08 22:52:30.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:52:30.706 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:52:30.737 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:52:30.739 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:30.851 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:52:30.855 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:30.878 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:52:30.884 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:30.898 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:52:30.907 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:30.926 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:52:30.948 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:30.971 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:52:30.978 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:52:45.506 - info: modbus.0 (1115) Connected to slave 192.168.178.72
                                      2026-06-08 22:52:48.503 - info: modbus.0 (1115) Disconnected from slave 192.168.178.72
                                      2026-06-08 22:53:11.819 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:15.699 - info: sainlogic.0 (73562) Scheduler pulling for new data
                                      2026-06-08 22:53:15.711 - info: sainlogic.0 (73562) RequestError: getaddrinfo ENOTFOUND undefined
                                      2026-06-08 22:53:15.729 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:53:15.730 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:15.763 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:53:15.767 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:15.790 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:53:15.795 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:15.845 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:53:15.847 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:15.934 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:53:15.938 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:15.959 - info: sainlogic.0 (73562) Scheduler updating IOBroker states
                                      2026-06-08 22:53:15.962 - info: sainlogic.0 (73562) State value to set for "sainlogic.0.info.last_update" has to be type "number" but received type "string"
                                      2026-06-08 22:53:23.950 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc2CircuitType.lastup
                                      2026-06-08 22:53:23.994 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:42 ctlv2.messages.Hc3CircuitType.lastup
                                      2026-06-08 22:53:24.316 - warn: ebus.0 (1402) no update since 08/06/2026, 04:57:13 ctlv2.messages.Z1Name2.lastup
                                      2026-06-08 22:53:24.487 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z2RoomZoneMapping.lastup
                                      2026-06-08 22:53:24.599 - warn: ebus.0 (1402) no update since 08/06/2026, 04:56:44 ctlv2.messages.Z3RoomZoneMapping.lastup
                                      2026-06-08 22:53:25.083 - info: ebus.0 (1402) found ebusd update version OK, vaillant/26.vr_71
                                      

                                      Ja, da ist ein cron, aber es tut sich nichts

                                      Bin wieder da und voller Erwartung, heute ist nicht ein Eintrag für den Adapter im Log

                                      Rene_HMR Offline
                                      Rene_HMR Offline
                                      Rene_HM
                                      Developer
                                      schrieb am zuletzt editiert von
                                      #25

                                      @Trapper ja, der Datenabruf wird über cron gesteuert. Der Adapter ist nicht "scheduled".
                                      Die Frage ist, wie du die 1 Minuten Abfrageintervall konfiguriert hast.
                                      Und: ist dein System aktiv, d.h. hast du den Haken bei aktiv in der Liste gesetzt?
                                      Zeig mal deine Konfiguration.
                                      Hast du evtl. von einer alten Version aktualisiert?

                                      T 1 Antwort Letzte Antwort
                                      0
                                      • Rene_HMR Rene_HM

                                        @Trapper ja, der Datenabruf wird über cron gesteuert. Der Adapter ist nicht "scheduled".
                                        Die Frage ist, wie du die 1 Minuten Abfrageintervall konfiguriert hast.
                                        Und: ist dein System aktiv, d.h. hast du den Haken bei aktiv in der Liste gesetzt?
                                        Zeig mal deine Konfiguration.
                                        Hast du evtl. von einer alten Version aktualisiert?

                                        T Offline
                                        T Offline
                                        Trapper
                                        schrieb am zuletzt editiert von
                                        #26

                                        @Rene_HM
                                        Hi Rene, die eine Minute ist im Adapter unter "Allgemeine Einstellungen" eigestellt. Ja, aktiv, Haken gesetzt. Ich denke nicht, dass die Adapterversionen unterschiedlich sind. Ich halte das immer aktuell.
                                        Habe vorhin eine zweite Instanz angelegt. Die hat, obwohl auch eine Minute eingestellt war, in unterschiedlichen Abständen die Wallbox abgefragt. Habe dann alle Instanzen gelöscht und wieder eine installiert. Problem besteht weiter, Wallbox wird nicht abgefragt. Hier die Adaptereinstellung

                                        Amtron.png

                                        Rene_HMR 1 Antwort Letzte Antwort
                                        0
                                        • T Trapper

                                          @Rene_HM
                                          Hi Rene, die eine Minute ist im Adapter unter "Allgemeine Einstellungen" eigestellt. Ja, aktiv, Haken gesetzt. Ich denke nicht, dass die Adapterversionen unterschiedlich sind. Ich halte das immer aktuell.
                                          Habe vorhin eine zweite Instanz angelegt. Die hat, obwohl auch eine Minute eingestellt war, in unterschiedlichen Abständen die Wallbox abgefragt. Habe dann alle Instanzen gelöscht und wieder eine installiert. Problem besteht weiter, Wallbox wird nicht abgefragt. Hier die Adaptereinstellung

                                          Amtron.png

                                          Rene_HMR Offline
                                          Rene_HMR Offline
                                          Rene_HM
                                          Developer
                                          schrieb am zuletzt editiert von
                                          #27

                                          @Trapper schalte die Adapter-Instanz mal auf debug-log. dann sollten wir auch den cron-string sehen. Vielleicht sehen wir da etwas...

                                          T 1 Antwort Letzte Antwort
                                          0

                                          Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                          Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                          Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                          Registrieren Anmelden
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          529

                                          Online

                                          33.0k

                                          Benutzer

                                          83.2k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2026
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe