Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • 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. Tester
  4. Test Adapter hoymiles-ms v0.2.x

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.6k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    848

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Test Adapter hoymiles-ms v0.2.x

Geplant Angeheftet Gesperrt Verschoben Tester
hoymiles-ms mcm1957
74 Beiträge 9 Kommentatoren 2.4k Aufrufe 8 Watching
  • Ä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.
  • andabrahaA andabraha

    Ich habe heute meinen 3. Speicher (mit der Hoymiles Beta Firmware) in Betrieb genommen.
    Seit dem Zeitpunkt mag der Adapter im iobroker nicht mehr so recht mitspielen (kann Zufall sein, paßt nur zeitlich zusammen).

    Der Fehler im Log lautet:
    SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49) at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36) at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)

    ich habe noch nicht viel recherchiert... mach ich aber noch :stuck_out_tongue_winking_eye:

    mcm1957M Online
    mcm1957M Online
    mcm1957
    schrieb am zuletzt editiert von mcm1957
    #15

    @andre1980hb said in Test Adapter hoymiles-ms v0.2.x:

    Unexpected end of JSON input at JSON.parse

    DANKE für die Vorabinfo.

    Die Fehlermeldung "Unexpected end of JSON input at JSON.parse" deutet ein wenig drauf hin, dass da was empfangen wird was nicht so ganz richtig ist. Kann aber nicht sagen wo das passiert.

    Wenn möglich schalt mal auf Loglevel DEBUG und schau ob da mehr Infos kommen. Wichtig wär zu sehen was da Hoymiles schickt. Kann dort aber auch den Log verbessern. Komm aber wahrscheinlich erst am WE dazu.

    Wenn möglich keg bitte ein Issue mit dem Log beim Adapetr an damit das siucher nicht untergeht.

    EDIT: Hab mir issue erstellt https://github.com/mcm4iob/ioBroker.hoymiles-ms/issues/68

    Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
    Support Repositoryverwaltung.

    Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

    LESEN - gute Forenbeitrage

    1 Antwort Letzte Antwort
    0
    • andabrahaA andabraha

      Ich habe heute meinen 3. Speicher (mit der Hoymiles Beta Firmware) in Betrieb genommen.
      Seit dem Zeitpunkt mag der Adapter im iobroker nicht mehr so recht mitspielen (kann Zufall sein, paßt nur zeitlich zusammen).

      Der Fehler im Log lautet:
      SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49) at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36) at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)

      ich habe noch nicht viel recherchiert... mach ich aber noch :stuck_out_tongue_winking_eye:

      mcm1957M Online
      mcm1957M Online
      mcm1957
      schrieb am zuletzt editiert von
      #16

      @andre1980hb

      Hab grad noch macl in den Code geschaut. Ein SILLY Log sollte zeigen was da als Event mit welcher Payload daher kommt:

      this.#log.silly([hoymilesMqtt] process message ${event.topic}: ${event.payload.toString()});

      Im Kern muss ich den Crash natürlich abfangen. Wär nur sinnvoll auch zu wissen ob da verstümmelte Daten kommen - aus welchem Grund auch immer - oder sich was am mqtt Inhalt geändert hat das eigentlich verarbeitet werden sollte.

      Wenn möglich erstell bitte ein silly log. Und wenns zu lang ist dann bitte entweder als attachment oder die [hoymilesMqtt] process message unmittelbar vor dem Crash posten.

      DANKE

      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
      Support Repositoryverwaltung.

      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

      LESEN - gute Forenbeitrage

      andabrahaA 1 Antwort Letzte Antwort
      0
      • mcm1957M mcm1957

        @andre1980hb

        Hab grad noch macl in den Code geschaut. Ein SILLY Log sollte zeigen was da als Event mit welcher Payload daher kommt:

        this.#log.silly([hoymilesMqtt] process message ${event.topic}: ${event.payload.toString()});

        Im Kern muss ich den Crash natürlich abfangen. Wär nur sinnvoll auch zu wissen ob da verstümmelte Daten kommen - aus welchem Grund auch immer - oder sich was am mqtt Inhalt geändert hat das eigentlich verarbeitet werden sollte.

        Wenn möglich erstell bitte ein silly log. Und wenns zu lang ist dann bitte entweder als attachment oder die [hoymilesMqtt] process message unmittelbar vor dem Crash posten.

        DANKE

        andabrahaA Offline
        andabrahaA Offline
        andabraha
        schrieb am zuletzt editiert von
        #17

        @mcm1957

        Mach ich gern, setze mich da nachher mal ran.

        Ich vermute (aus der Hüfte geschossen) , dass sich mit der Firmware für 3x MSA2 was am output geändert hat.
        Die Firmware die derzeit genutzt werden kann, ist noch im beta status, daher muss man gucken wie viel Aufwand da reingesteckt wird.
        Wenn ich das richtig verfolgt habe, soll es im Dezember zu einem offiziellen release kommen. (ohne Gewähr)

        mcm1957M 1 Antwort Letzte Antwort
        0
        • andabrahaA andabraha

          @mcm1957

          Mach ich gern, setze mich da nachher mal ran.

          Ich vermute (aus der Hüfte geschossen) , dass sich mit der Firmware für 3x MSA2 was am output geändert hat.
          Die Firmware die derzeit genutzt werden kann, ist noch im beta status, daher muss man gucken wie viel Aufwand da reingesteckt wird.
          Wenn ich das richtig verfolgt habe, soll es im Dezember zu einem offiziellen release kommen. (ohne Gewähr)

          mcm1957M Online
          mcm1957M Online
          mcm1957
          schrieb am zuletzt editiert von mcm1957
          #18

          @andabraha
          Ja kann sein, dass da was dazu gekommen ist. Im Hoymiles Forum gibts aber guten Support.
          Kann aber auch sein, dass im Adapter was nicht i.O. ist. Mir ist aufgefallen, dass von Zeit zu Zeit fiktive Geräte angelegt werden deren Seriennummern offensichtlich 'abgeschnitten' sind, d.h. sie beginnen wie die Seriennummer meines Akkus sind aber kürzer.

          Keine Ahnung ob der Akku zeitweise Schrott sendet (wenn z.B. das WLAN hustet) oder ob im Code was faul ist und irgendwelche Bufferings nicht beachtet werden. Kann also auch sowas sein,

          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
          Support Repositoryverwaltung.

          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

          LESEN - gute Forenbeitrage

          andabrahaA 1 Antwort Letzte Antwort
          0
          • mcm1957M mcm1957

            @andabraha
            Ja kann sein, dass da was dazu gekommen ist. Im Hoymiles Forum gibts aber guten Support.
            Kann aber auch sein, dass im Adapter was nicht i.O. ist. Mir ist aufgefallen, dass von Zeit zu Zeit fiktive Geräte angelegt werden deren Seriennummern offensichtlich 'abgeschnitten' sind, d.h. sie beginnen wie die Seriennummer meines Akkus sind aber kürzer.

            Keine Ahnung ob der Akku zeitweise Schrott sendet (wenn z.B. das WLAN hustet) oder ob im Code was faul ist und irgendwelche Bufferings nicht beachtet werden. Kann also auch sowas sein,

            andabrahaA Offline
            andabrahaA Offline
            andabraha
            schrieb am zuletzt editiert von andabraha
            #19

            @mcm1957
            ich habe die Objekte im Adapter alle gelöscht (ja da waren auch welche mit kurzen Namen wie "MSA" oder "MSA2800" dabei)
            Damit war der Adapter jungfräulich und er wurde gestartet.
            Dann habe ich in der App die MQTT Konfig angepaßt und das log bis zum "crash" auf silly mitlaufen lassen:

            2025-10-30 21:20:24.789 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client ping
            2025-10-30 21:20:36.337 - debug: hoymiles-ms.0 (4653) [MQTT-Server] client connection from 192.168.1.35
            2025-10-30 21:20:36.338 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client connected with id MSA2800-Serialnumber-1 connected from 192.168.1.35
            2025-10-30 21:20:36.338 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client reconnected from 192.168.1.35, dropping old connection to 192.168.1.35
            2025-10-30 21:20:36.338 - info: hoymiles-ms.0 (4653) [hoymilesMQTT] client MSA2800-Serialnumber-1 connected from 192.168.1.35
            2025-10-30 21:20:36.412 - debug: hoymiles-ms.0 (4653) [MQTT-Server] client connection from 192.168.1.37
            2025-10-30 21:20:36.413 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) client connected with id MSA2800-Serialnumber-3 connected from 192.168.1.37
            2025-10-30 21:20:36.414 - info: hoymiles-ms.0 (4653) [hoymilesMQTT] client MSA2800-Serialnumber-3 connected from 192.168.1.37
            2025-10-30 21:20:36.515 - debug: hoymiles-ms.0 (4653) [MQTT-Server] client connection from 192.168.1.36
            2025-10-30 21:20:36.516 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) client connected with id MSA2800-Serialnumber-2 connected from 192.168.1.36
            2025-10-30 21:20:36.516 - info: hoymiles-ms.0 (4653) [hoymilesMQTT] client MSA2800-Serialnumber-2 connected from 192.168.1.36
            2025-10-30 21:20:44.792 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client ping
            2025-10-30 21:20:46.332 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/switch/MSA-2800-Serialnumber-1/config": {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/attributes","unique_id":"MSA-2800-Serialnumber-1","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
            2025-10-30 21:20:46.332 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/switch/MSA-2800-Serialnumber-1/config: {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/attributes","unique_id":"MSA-2800-Serialnumber-1","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
            2025-10-30 21:20:46.333 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-1 is initializing states
            2025-10-30 21:20:46.350 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.manufacturer" in progress
            2025-10-30 21:20:46.353 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.model" in progress
            2025-10-30 21:20:46.355 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.name" in progress
            2025-10-30 21:20:46.356 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.info.online" in progress
            2025-10-30 21:20:46.359 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.info.ip" in progress
            2025-10-30 21:20:46.360 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.info.timestamp" in progress
            2025-10-30 21:20:46.362 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-1 completed
            2025-10-30 21:20:46.365 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-1 is online
            2025-10-30 21:20:46.367 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.identifiers from homeassistant/switch/MSA-2800-Serialnumber-1/config using value ["2800-Serialnumber-1"]
            2025-10-30 21:20:46.367 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.identifiers" in progress
            2025-10-30 21:20:46.411 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.manufacturer from homeassistant/switch/MSA-2800-Serialnumber-1/config using value Hoymiles
            2025-10-30 21:20:46.413 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.model from homeassistant/switch/MSA-2800-Serialnumber-1/config using value MS-A2
            2025-10-30 21:20:46.414 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.name from homeassistant/switch/MSA-2800-Serialnumber-1/config using value MSA-2800-Serialnumber-1
            2025-10-30 21:20:46.416 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/switch/MSA-2800-Serialnumber-3/config": {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/attributes","unique_id":"MSA-2800-Serialnumber-3","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
            2025-10-30 21:20:46.416 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/switch/MSA-2800-Serialnumber-3/config: {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/attributes","unique_id":"MSA-2800-Serialnumber-3","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
            2025-10-30 21:20:46.416 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-3 is initializing states
            2025-10-30 21:20:46.432 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.manufacturer" in progress
            2025-10-30 21:20:46.432 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.sw_version from homeassistant/switch/MSA-2800-Serialnumber-1/config using value 01.05.11
            2025-10-30 21:20:46.432 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.sw_version" in progress
            2025-10-30 21:20:46.435 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.model" in progress
            2025-10-30 21:20:46.456 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-1/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","system_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/system/state"}}
            2025-10-30 21:20:46.456 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-1/attributes: {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","system_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/system/state"}}
            2025-10-30 21:20:46.457 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.name" in progress
            2025-10-30 21:20:46.498 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.info.ip from homeassistant/switch/MSA-2800-Serialnumber-1/config using value 192.168.1.35
            2025-10-30 21:20:46.518 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-3/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state"}}
            2025-10-30 21:20:46.518 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-3/attributes: {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state"}}
            2025-10-30 21:20:46.518 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-3 in progress...
            2025-10-30 21:20:46.521 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/switch/MSA-2800-Serialnumber-2/config": {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/attributes","unique_id":"MSA-2800-Serialnumber-2","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
            2025-10-30 21:20:46.521 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/switch/MSA-2800-Serialnumber-2/config: {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/attributes","unique_id":"MSA-2800-Serialnumber-2","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
            2025-10-30 21:20:46.521 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-2 is initializing states
            2025-10-30 21:20:46.522 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.info.online" in progress
            2025-10-30 21:20:46.524 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.info.ip" in progress
            2025-10-30 21:20:46.526 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.info.timestamp" in progress
            2025-10-30 21:20:46.529 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-3 completed
            2025-10-30 21:20:46.552 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/number/MSA-2800-Serialnumber-1/power_ctrl/config":
            2025-10-30 21:20:46.552 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/number/MSA-2800-Serialnumber-1/power_ctrl/config:
            2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) unhandled promise rejection: Unexpected end of JSON input
            2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) SyntaxError: Unexpected end of JSON input
            at JSON.parse ()
            at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
            at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
            at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
            at async Connection. (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
            2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) Unexpected end of JSON input
            2025-10-30 21:20:46.556 - info: hoymiles-ms.0 (4653) terminating
            2025-10-30 21:20:46.556 - warn: hoymiles-ms.0 (4653) Terminated (UNCAUGHT_EXCEPTION): Without reason
            2025-10-30 21:20:46.557 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-3 is online
            2025-10-30 21:20:46.600 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.identifiers from homeassistant/switch/MSA-2800-Serialnumber-3/config using value ["2800-Serialnumber-3"]
            2025-10-30 21:20:46.600 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.identifiers" in progress
            2025-10-30 21:20:46.609 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/number/MSA-2800-Serialnumber-3/power_ctrl/config":
            2025-10-30 21:20:46.610 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/number/MSA-2800-Serialnumber-3/power_ctrl/config:
            2025-10-30 21:20:46.612 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.manufacturer from homeassistant/switch/MSA-2800-Serialnumber-3/config using value Hoymiles
            2025-10-30 21:20:46.612 - error: hoymiles-ms.0 (4653) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            2025-10-30 21:20:46.613 - error: hoymiles-ms.0 (4653) unhandled promise rejection: Unexpected end of JSON input
            2025-10-30 21:20:46.613 - error: hoymiles-ms.0 (4653) SyntaxError: Unexpected end of JSON input
            at JSON.parse ()
            at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
            at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
            at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
            at async Connection. (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
            2025-10-30 21:20:46.613 - error: hoymiles-ms.0 (4653) Unexpected end of JSON input
            2025-10-30 21:20:46.625 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-2/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state"}}
            2025-10-30 21:20:46.625 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-2/attributes: {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state"}}
            2025-10-30 21:20:46.625 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 in progress...
            2025-10-30 21:20:46.625 - warn: hoymiles-ms.0 (4653) delay called, but adapter is shutting down
            2025-10-30 21:20:46.655 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.manufacturer" in progress
            2025-10-30 21:20:46.656 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.model from homeassistant/switch/MSA-2800-Serialnumber-3/config using value MS-A2
            2025-10-30 21:20:46.661 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-1/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.661 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-1/soc/config: {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.662 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.model" in progress
            2025-10-30 21:20:46.703 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.name from homeassistant/switch/MSA-2800-Serialnumber-3/config using value MSA-2800-Serialnumber-3
            2025-10-30 21:20:46.711 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-3/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.712 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-3/soc/config: {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.713 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.name" in progress
            2025-10-30 21:20:46.727 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/number/MSA-2800-Serialnumber-2/power_ctrl/config":
            2025-10-30 21:20:46.728 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/number/MSA-2800-Serialnumber-2/power_ctrl/config:
            2025-10-30 21:20:46.728 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 in progress...
            2025-10-30 21:20:46.728 - warn: hoymiles-ms.0 (4653) delay called, but adapter is shutting down
            2025-10-30 21:20:46.728 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.sw_version from homeassistant/switch/MSA-2800-Serialnumber-3/config using value 01.05.11
            2025-10-30 21:20:46.728 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.sw_version" in progress
            2025-10-30 21:20:46.732 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.info.online" in progress
            2025-10-30 21:20:46.752 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-1/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.752 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-1/bat_p/config: {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.754 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.info.ip" in progress
            2025-10-30 21:20:46.796 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.info.ip from homeassistant/switch/MSA-2800-Serialnumber-3/config using value 192.168.1.37
            2025-10-30 21:20:46.814 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-3/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.814 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-3/bat_p/config: {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.816 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.info.timestamp" in progress
            2025-10-30 21:20:46.833 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-2/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.833 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-2/soc/config: {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.833 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 in progress...
            2025-10-30 21:20:46.833 - warn: hoymiles-ms.0 (4653) delay called, but adapter is shutting down
            2025-10-30 21:20:46.852 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/select/MSA-2800-Serialnumber-1/ems_mode/config":
            2025-10-30 21:20:46.852 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/select/MSA-2800-Serialnumber-1/ems_mode/config:
            2025-10-30 21:20:46.896 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 completed
            2025-10-30 21:20:46.898 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-2 is online
            2025-10-30 21:20:46.899 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.identifiers from homeassistant/switch/MSA-2800-Serialnumber-2/config using value ["2800-Serialnumber-2"]
            2025-10-30 21:20:46.899 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.identifiers" in progress
            2025-10-30 21:20:46.903 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.manufacturer from homeassistant/switch/MSA-2800-Serialnumber-2/config using value Hoymiles
            2025-10-30 21:20:46.904 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.model from homeassistant/switch/MSA-2800-Serialnumber-2/config using value MS-A2
            2025-10-30 21:20:46.906 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.name from homeassistant/switch/MSA-2800-Serialnumber-2/config using value MSA-2800-Serialnumber-2
            2025-10-30 21:20:46.908 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.sw_version from homeassistant/switch/MSA-2800-Serialnumber-2/config using value 01.05.11
            2025-10-30 21:20:46.908 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.sw_version" in progress
            2025-10-30 21:20:46.911 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.info.ip from homeassistant/switch/MSA-2800-Serialnumber-2/config using value 192.168.1.36
            2025-10-30 21:20:46.917 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/select/MSA-2800-Serialnumber-3/ems_mode/config":
            2025-10-30 21:20:46.917 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/select/MSA-2800-Serialnumber-3/ems_mode/config:
            2025-10-30 21:20:46.925 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-2/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:46.925 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-2/bat_p/config: {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
            2025-10-30 21:20:47.028 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/select/MSA-2800-Serialnumber-2/ems_mode/config":
            2025-10-30 21:20:47.028 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/select/MSA-2800-Serialnumber-2/ems_mode/config:
            2025-10-30 21:20:47.056 - info: hoymiles-ms.0 (4653) terminating
            2025-10-30 21:20:47.075 - error: host.iobroker instance system.adapter.hoymiles-ms.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
            2025-10-30 21:20:47.075 - info: host.iobroker Restart adapter system.adapter.hoymiles-ms.0 because enabled
            2025-10-30 21:21:14.969 - info: host.iobroker "system.adapter.hoymiles-ms.0" disabled
            2025-10-30 21:21:17.758 - debug: hoymiles-ms.0 (4871) Redis Objects: Use Redis connection: 0.0.0.0:9001
            2025-10-30 21:21:17.767 - debug: hoymiles-ms.0 (4871) Objects client ready ... initialize now
            2025-10-30 21:21:17.767 - debug: hoymiles-ms.0 (4871) Objects create System PubSub Client
            2025-10-30 21:21:17.768 - debug: hoymiles-ms.0 (4871) Objects create User PubSub Client
            2025-10-30 21:21:17.776 - debug: hoymiles-ms.0 (4871) Objects client initialize lua scripts
            2025-10-30 21:21:17.778 - debug: hoymiles-ms.0 (4871) Objects connected to redis: 0.0.0.0:9001
            2025-10-30 21:21:17.779 - silly: hoymiles-ms.0 (4871) redis psubscribe cfg.o.system.user.*
            2025-10-30 21:21:17.783 - silly: hoymiles-ms.0 (4871) redis psubscribe cfg.o.enum.*
            2025-10-30 21:21:17.784 - silly: hoymiles-ms.0 (4871) objectDB connected
            2025-10-30 21:21:17.785 - debug: hoymiles-ms.0 (4871) Redis States: Use Redis connection: 0.0.0.0:9000
            2025-10-30 21:21:17.788 - debug: hoymiles-ms.0 (4871) States create System PubSub Client
            2025-10-30 21:21:17.788 - debug: hoymiles-ms.0 (4871) States create User PubSub Client
            2025-10-30 21:21:17.833 - debug: hoymiles-ms.0 (4871) States connected to redis: 0.0.0.0:9000
            2025-10-30 21:21:17.833 - silly: hoymiles-ms.0 (4871) statesDB connected
            2025-10-30 21:21:17.839 - error: hoymiles-ms.0 (4871) adapter disabled
            2025-10-30 21:21:17.881 - warn: hoymiles-ms.0 (4871) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
            2025-10-30 21:21:18.401 - error: host.iobroker instance system.adapter.hoymiles-ms.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
            2025-10-30 21:21:18.401 - info: host.iobroker Do not restart adapter system.adapter.hoymiles-ms.0 because disabled or deleted
            

            Ich hoffe das ist nicht zu viel output für den Beitrag hier

            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • andabrahaA andabraha

              @mcm1957
              ich habe die Objekte im Adapter alle gelöscht (ja da waren auch welche mit kurzen Namen wie "MSA" oder "MSA2800" dabei)
              Damit war der Adapter jungfräulich und er wurde gestartet.
              Dann habe ich in der App die MQTT Konfig angepaßt und das log bis zum "crash" auf silly mitlaufen lassen:

              2025-10-30 21:20:24.789 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client ping
              2025-10-30 21:20:36.337 - debug: hoymiles-ms.0 (4653) [MQTT-Server] client connection from 192.168.1.35
              2025-10-30 21:20:36.338 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client connected with id MSA2800-Serialnumber-1 connected from 192.168.1.35
              2025-10-30 21:20:36.338 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client reconnected from 192.168.1.35, dropping old connection to 192.168.1.35
              2025-10-30 21:20:36.338 - info: hoymiles-ms.0 (4653) [hoymilesMQTT] client MSA2800-Serialnumber-1 connected from 192.168.1.35
              2025-10-30 21:20:36.412 - debug: hoymiles-ms.0 (4653) [MQTT-Server] client connection from 192.168.1.37
              2025-10-30 21:20:36.413 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) client connected with id MSA2800-Serialnumber-3 connected from 192.168.1.37
              2025-10-30 21:20:36.414 - info: hoymiles-ms.0 (4653) [hoymilesMQTT] client MSA2800-Serialnumber-3 connected from 192.168.1.37
              2025-10-30 21:20:36.515 - debug: hoymiles-ms.0 (4653) [MQTT-Server] client connection from 192.168.1.36
              2025-10-30 21:20:36.516 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) client connected with id MSA2800-Serialnumber-2 connected from 192.168.1.36
              2025-10-30 21:20:36.516 - info: hoymiles-ms.0 (4653) [hoymilesMQTT] client MSA2800-Serialnumber-2 connected from 192.168.1.36
              2025-10-30 21:20:44.792 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) client ping
              2025-10-30 21:20:46.332 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/switch/MSA-2800-Serialnumber-1/config": {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/attributes","unique_id":"MSA-2800-Serialnumber-1","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
              2025-10-30 21:20:46.332 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/switch/MSA-2800-Serialnumber-1/config: {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/attributes","unique_id":"MSA-2800-Serialnumber-1","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
              2025-10-30 21:20:46.333 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-1 is initializing states
              2025-10-30 21:20:46.350 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.manufacturer" in progress
              2025-10-30 21:20:46.353 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.model" in progress
              2025-10-30 21:20:46.355 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.name" in progress
              2025-10-30 21:20:46.356 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.info.online" in progress
              2025-10-30 21:20:46.359 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.info.ip" in progress
              2025-10-30 21:20:46.360 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.info.timestamp" in progress
              2025-10-30 21:20:46.362 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-1 completed
              2025-10-30 21:20:46.365 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-1 is online
              2025-10-30 21:20:46.367 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.identifiers from homeassistant/switch/MSA-2800-Serialnumber-1/config using value ["2800-Serialnumber-1"]
              2025-10-30 21:20:46.367 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.identifiers" in progress
              2025-10-30 21:20:46.411 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.manufacturer from homeassistant/switch/MSA-2800-Serialnumber-1/config using value Hoymiles
              2025-10-30 21:20:46.413 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.model from homeassistant/switch/MSA-2800-Serialnumber-1/config using value MS-A2
              2025-10-30 21:20:46.414 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.name from homeassistant/switch/MSA-2800-Serialnumber-1/config using value MSA-2800-Serialnumber-1
              2025-10-30 21:20:46.416 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/switch/MSA-2800-Serialnumber-3/config": {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/attributes","unique_id":"MSA-2800-Serialnumber-3","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
              2025-10-30 21:20:46.416 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/switch/MSA-2800-Serialnumber-3/config: {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/attributes","unique_id":"MSA-2800-Serialnumber-3","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
              2025-10-30 21:20:46.416 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-3 is initializing states
              2025-10-30 21:20:46.432 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.manufacturer" in progress
              2025-10-30 21:20:46.432 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.device.sw_version from homeassistant/switch/MSA-2800-Serialnumber-1/config using value 01.05.11
              2025-10-30 21:20:46.432 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-1.device.sw_version" in progress
              2025-10-30 21:20:46.435 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.model" in progress
              2025-10-30 21:20:46.456 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-1/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","system_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/system/state"}}
              2025-10-30 21:20:46.456 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-1/attributes: {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/device/state","system_state":"homeassistant/sensor/MSA-2800-Serialnumber-1/system/state"}}
              2025-10-30 21:20:46.457 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.name" in progress
              2025-10-30 21:20:46.498 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-1.info.ip from homeassistant/switch/MSA-2800-Serialnumber-1/config using value 192.168.1.35
              2025-10-30 21:20:46.518 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-3/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state"}}
              2025-10-30 21:20:46.518 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-3/attributes: {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-3/device/state"}}
              2025-10-30 21:20:46.518 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-3 in progress...
              2025-10-30 21:20:46.521 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/switch/MSA-2800-Serialnumber-2/config": {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/attributes","unique_id":"MSA-2800-Serialnumber-2","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
              2025-10-30 21:20:46.521 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/switch/MSA-2800-Serialnumber-2/config: {"state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/attributes","unique_id":"MSA-2800-Serialnumber-2","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.05.11"}}
              2025-10-30 21:20:46.521 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-2 is initializing states
              2025-10-30 21:20:46.522 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.info.online" in progress
              2025-10-30 21:20:46.524 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.info.ip" in progress
              2025-10-30 21:20:46.526 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.info.timestamp" in progress
              2025-10-30 21:20:46.529 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-3 completed
              2025-10-30 21:20:46.552 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/number/MSA-2800-Serialnumber-1/power_ctrl/config":
              2025-10-30 21:20:46.552 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/number/MSA-2800-Serialnumber-1/power_ctrl/config:
              2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) unhandled promise rejection: Unexpected end of JSON input
              2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) SyntaxError: Unexpected end of JSON input
              at JSON.parse ()
              at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
              at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
              at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
              at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
              at async Connection. (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
              2025-10-30 21:20:46.555 - error: hoymiles-ms.0 (4653) Unexpected end of JSON input
              2025-10-30 21:20:46.556 - info: hoymiles-ms.0 (4653) terminating
              2025-10-30 21:20:46.556 - warn: hoymiles-ms.0 (4653) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2025-10-30 21:20:46.557 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-3 is online
              2025-10-30 21:20:46.600 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.identifiers from homeassistant/switch/MSA-2800-Serialnumber-3/config using value ["2800-Serialnumber-3"]
              2025-10-30 21:20:46.600 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.identifiers" in progress
              2025-10-30 21:20:46.609 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/number/MSA-2800-Serialnumber-3/power_ctrl/config":
              2025-10-30 21:20:46.610 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/number/MSA-2800-Serialnumber-3/power_ctrl/config:
              2025-10-30 21:20:46.612 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.manufacturer from homeassistant/switch/MSA-2800-Serialnumber-3/config using value Hoymiles
              2025-10-30 21:20:46.612 - error: hoymiles-ms.0 (4653) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              2025-10-30 21:20:46.613 - error: hoymiles-ms.0 (4653) unhandled promise rejection: Unexpected end of JSON input
              2025-10-30 21:20:46.613 - error: hoymiles-ms.0 (4653) SyntaxError: Unexpected end of JSON input
              at JSON.parse ()
              at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
              at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
              at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
              at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
              at async Connection. (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
              2025-10-30 21:20:46.613 - error: hoymiles-ms.0 (4653) Unexpected end of JSON input
              2025-10-30 21:20:46.625 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-2/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state"}}
              2025-10-30 21:20:46.625 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-2/attributes: {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","device_state":"homeassistant/sensor/MSA-2800-Serialnumber-2/device/state"}}
              2025-10-30 21:20:46.625 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 in progress...
              2025-10-30 21:20:46.625 - warn: hoymiles-ms.0 (4653) delay called, but adapter is shutting down
              2025-10-30 21:20:46.655 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.manufacturer" in progress
              2025-10-30 21:20:46.656 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.model from homeassistant/switch/MSA-2800-Serialnumber-3/config using value MS-A2
              2025-10-30 21:20:46.661 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-1/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.661 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-1/soc/config: {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.662 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.model" in progress
              2025-10-30 21:20:46.703 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.name from homeassistant/switch/MSA-2800-Serialnumber-3/config using value MSA-2800-Serialnumber-3
              2025-10-30 21:20:46.711 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-3/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.712 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-3/soc/config: {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.713 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.name" in progress
              2025-10-30 21:20:46.727 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/number/MSA-2800-Serialnumber-2/power_ctrl/config":
              2025-10-30 21:20:46.728 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/number/MSA-2800-Serialnumber-2/power_ctrl/config:
              2025-10-30 21:20:46.728 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 in progress...
              2025-10-30 21:20:46.728 - warn: hoymiles-ms.0 (4653) delay called, but adapter is shutting down
              2025-10-30 21:20:46.728 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.device.sw_version from homeassistant/switch/MSA-2800-Serialnumber-3/config using value 01.05.11
              2025-10-30 21:20:46.728 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-3.device.sw_version" in progress
              2025-10-30 21:20:46.732 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.info.online" in progress
              2025-10-30 21:20:46.752 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-1/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.752 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-1/bat_p/config: {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-1/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-1"],"name":"MSA-2800-Serialnumber-1","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.754 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.info.ip" in progress
              2025-10-30 21:20:46.796 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-3.info.ip from homeassistant/switch/MSA-2800-Serialnumber-3/config using value 192.168.1.37
              2025-10-30 21:20:46.814 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-3/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.814 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-3/bat_p/config: {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-3/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-3"],"name":"MSA-2800-Serialnumber-3","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.816 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.info.timestamp" in progress
              2025-10-30 21:20:46.833 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-2/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.833 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-2/soc/config: {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.833 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 in progress...
              2025-10-30 21:20:46.833 - warn: hoymiles-ms.0 (4653) delay called, but adapter is shutting down
              2025-10-30 21:20:46.852 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-1) received message from client on topic "homeassistant/select/MSA-2800-Serialnumber-1/ems_mode/config":
              2025-10-30 21:20:46.852 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/select/MSA-2800-Serialnumber-1/ems_mode/config:
              2025-10-30 21:20:46.896 - debug: hoymiles-ms.0 (4653) initialization of states for device MSA-2800-Serialnumber-2 completed
              2025-10-30 21:20:46.898 - info: hoymiles-ms.0 (4653) Device MSA-2800-Serialnumber-2 is online
              2025-10-30 21:20:46.899 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.identifiers from homeassistant/switch/MSA-2800-Serialnumber-2/config using value ["2800-Serialnumber-2"]
              2025-10-30 21:20:46.899 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.identifiers" in progress
              2025-10-30 21:20:46.903 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.manufacturer from homeassistant/switch/MSA-2800-Serialnumber-2/config using value Hoymiles
              2025-10-30 21:20:46.904 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.model from homeassistant/switch/MSA-2800-Serialnumber-2/config using value MS-A2
              2025-10-30 21:20:46.906 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.name from homeassistant/switch/MSA-2800-Serialnumber-2/config using value MSA-2800-Serialnumber-2
              2025-10-30 21:20:46.908 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.device.sw_version from homeassistant/switch/MSA-2800-Serialnumber-2/config using value 01.05.11
              2025-10-30 21:20:46.908 - debug: hoymiles-ms.0 (4653) creation of state "MSA-2800-Serialnumber-2.device.sw_version" in progress
              2025-10-30 21:20:46.911 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] updateing state MSA-2800-Serialnumber-2.info.ip from homeassistant/switch/MSA-2800-Serialnumber-2/config using value 192.168.1.36
              2025-10-30 21:20:46.917 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-3) received message from client on topic "homeassistant/select/MSA-2800-Serialnumber-3/ems_mode/config":
              2025-10-30 21:20:46.917 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/select/MSA-2800-Serialnumber-3/ems_mode/config:
              2025-10-30 21:20:46.925 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/sensor/MSA-2800-Serialnumber-2/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:46.925 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/sensor/MSA-2800-Serialnumber-2/bat_p/config: {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800-Serialnumber-2/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800-Serialnumber-2"],"name":"MSA-2800-Serialnumber-2","manufacturer":"Hoymiles","model":"MS-A2"}}
              2025-10-30 21:20:47.028 - debug: hoymiles-ms.0 (4653) [MQTT-Server] (MSA2800-Serialnumber-2) received message from client on topic "homeassistant/select/MSA-2800-Serialnumber-2/ems_mode/config":
              2025-10-30 21:20:47.028 - silly: hoymiles-ms.0 (4653) [hoymilesMqtt] process message homeassistant/select/MSA-2800-Serialnumber-2/ems_mode/config:
              2025-10-30 21:20:47.056 - info: hoymiles-ms.0 (4653) terminating
              2025-10-30 21:20:47.075 - error: host.iobroker instance system.adapter.hoymiles-ms.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
              2025-10-30 21:20:47.075 - info: host.iobroker Restart adapter system.adapter.hoymiles-ms.0 because enabled
              2025-10-30 21:21:14.969 - info: host.iobroker "system.adapter.hoymiles-ms.0" disabled
              2025-10-30 21:21:17.758 - debug: hoymiles-ms.0 (4871) Redis Objects: Use Redis connection: 0.0.0.0:9001
              2025-10-30 21:21:17.767 - debug: hoymiles-ms.0 (4871) Objects client ready ... initialize now
              2025-10-30 21:21:17.767 - debug: hoymiles-ms.0 (4871) Objects create System PubSub Client
              2025-10-30 21:21:17.768 - debug: hoymiles-ms.0 (4871) Objects create User PubSub Client
              2025-10-30 21:21:17.776 - debug: hoymiles-ms.0 (4871) Objects client initialize lua scripts
              2025-10-30 21:21:17.778 - debug: hoymiles-ms.0 (4871) Objects connected to redis: 0.0.0.0:9001
              2025-10-30 21:21:17.779 - silly: hoymiles-ms.0 (4871) redis psubscribe cfg.o.system.user.*
              2025-10-30 21:21:17.783 - silly: hoymiles-ms.0 (4871) redis psubscribe cfg.o.enum.*
              2025-10-30 21:21:17.784 - silly: hoymiles-ms.0 (4871) objectDB connected
              2025-10-30 21:21:17.785 - debug: hoymiles-ms.0 (4871) Redis States: Use Redis connection: 0.0.0.0:9000
              2025-10-30 21:21:17.788 - debug: hoymiles-ms.0 (4871) States create System PubSub Client
              2025-10-30 21:21:17.788 - debug: hoymiles-ms.0 (4871) States create User PubSub Client
              2025-10-30 21:21:17.833 - debug: hoymiles-ms.0 (4871) States connected to redis: 0.0.0.0:9000
              2025-10-30 21:21:17.833 - silly: hoymiles-ms.0 (4871) statesDB connected
              2025-10-30 21:21:17.839 - error: hoymiles-ms.0 (4871) adapter disabled
              2025-10-30 21:21:17.881 - warn: hoymiles-ms.0 (4871) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
              2025-10-30 21:21:18.401 - error: host.iobroker instance system.adapter.hoymiles-ms.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
              2025-10-30 21:21:18.401 - info: host.iobroker Do not restart adapter system.adapter.hoymiles-ms.0 because disabled or deleted
              

              Ich hoffe das ist nicht zu viel output für den Beitrag hier

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

              @andabraha sagte in Test Adapter hoymiles-ms v0.2.x:

              Ich hoffe das ist nicht zu viel output für den Beitrag hier

              Wenn du es in CodeTags </> packen würdest dann nicht.

              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

              andabrahaA 1 Antwort Letzte Antwort
              1
              • Thomas BraunT Thomas Braun

                @andabraha sagte in Test Adapter hoymiles-ms v0.2.x:

                Ich hoffe das ist nicht zu viel output für den Beitrag hier

                Wenn du es in CodeTags </> packen würdest dann nicht.

                andabrahaA Offline
                andabrahaA Offline
                andabraha
                schrieb am zuletzt editiert von
                #21

                @thomas-braun
                danke für den Hinweis, habs geändert

                mcm1957M 1 Antwort Letzte Antwort
                0
                • andabrahaA andabraha

                  @thomas-braun
                  danke für den Hinweis, habs geändert

                  mcm1957M Online
                  mcm1957M Online
                  mcm1957
                  schrieb am zuletzt editiert von
                  #22

                  @andabraha

                  Danke
                  kanns mir wahracheinlich erst morgen abends od Sa ansehen. Sorry

                  Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                  Support Repositoryverwaltung.

                  Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                  LESEN - gute Forenbeitrage

                  andabrahaA mcm1957M 2 Antworten Letzte Antwort
                  0
                  • mcm1957M mcm1957

                    @andabraha

                    Danke
                    kanns mir wahracheinlich erst morgen abends od Sa ansehen. Sorry

                    andabrahaA Offline
                    andabrahaA Offline
                    andabraha
                    schrieb am zuletzt editiert von
                    #23

                    @mcm1957
                    kein Stress, lass mich wissen ob ich noch was nachstellen kann

                    mcm1957M 1 Antwort Letzte Antwort
                    0
                    • mcm1957M mcm1957

                      Release 0.2.0 sollte ab morgen im LATEST Repository verfügbar sein.

                      Changelog siehe Repository.

                      Im Wesentlichen wurde geändert:

                      • überarbeitetes Handling der States
                        • states werden beim Neustart zurückgesetzt um veraltete Daten zu vermeiden
                        • es werden nur mehr jene States angelegt, die der Hoymiles auch meldet. Allerdings werden keine States aktiv gelöscht um zu verhindern, dass gesetzte Konfigurationsdaten (z.B. History) verloren gehen. Sollte also z.B. ein Master zum Slave werden, dann bitte ggF states manuell löschen
                      • Support zu Leistungseinstellung wurde implementiert

                      Um die Leistungseinstellungen zu steuern muss

                      • der State 'ems_mode.command' mit dem Wert 'mqtt_ctrl' beschrieben werden (Defaultl und automatic mode is 'general'
                      • die gewünschte Abgabeleistung (positiv) oder Ladeleistung (negativ) im State 'power_ctrl.set' eingetragen werden.

                      Hinweis: um den notwendigen zyklischen Refresh der Abgabeleistung kümmert sich der Adapter. Solange sich die Abgabeleistung nicht ändern soll, braucht der State daher nicht neu / regelmäßig beschrieben werden.

                      Da ich nur einen Akku besitze suche ich Tester die Erfahrungen mit mehr als einem Gerät beisteuern können. (Ich gehe davon aus, dass mir niemand einen zweiten A2 spendieren will damit ich selbst testen kann :-) ) DANKE an potenzielle Freiwillige.

                      Übrigends:
                      Ob der mqtt controlmode aktiv ist sieht man auch in der App.

                      M Offline
                      M Offline
                      Matze2
                      schrieb am zuletzt editiert von
                      #24

                      @mcm1957

                      Ich habe den Adapter erst heute entdeckt und installiert.
                      Vorher habe ich mit Hilfe des "mqtt" Adapters einzelne Felder selbst parsen müssen. Auch dass die Variablen gut beschrieben sind, erleichtert die Auswahl der relevanten Variablen, obwohl ich hier erst am Anfang stehe.
                      Also schon mal an dieser Stelle vielen Dank für Deine Mühe!

                      Eine Frage habe ich zur Implementierung. Es schaut für mich so aus, als ob für jedes einzelne Objekt die jeweilige JSON-Payload immer wieder neu geparst wird. Mir scheint das nicht optimal.

                      Ist das mit Absicht so implementiert oder gibt es Planungen, die Payload für alle Felder nur einmal zu parsen?

                      mcm1957M 1 Antwort Letzte Antwort
                      0
                      • M Matze2

                        @mcm1957

                        Ich habe den Adapter erst heute entdeckt und installiert.
                        Vorher habe ich mit Hilfe des "mqtt" Adapters einzelne Felder selbst parsen müssen. Auch dass die Variablen gut beschrieben sind, erleichtert die Auswahl der relevanten Variablen, obwohl ich hier erst am Anfang stehe.
                        Also schon mal an dieser Stelle vielen Dank für Deine Mühe!

                        Eine Frage habe ich zur Implementierung. Es schaut für mich so aus, als ob für jedes einzelne Objekt die jeweilige JSON-Payload immer wieder neu geparst wird. Mir scheint das nicht optimal.

                        Ist das mit Absicht so implementiert oder gibt es Planungen, die Payload für alle Felder nur einmal zu parsen?

                        mcm1957M Online
                        mcm1957M Online
                        mcm1957
                        schrieb am zuletzt editiert von mcm1957
                        #25

                        @matze2 said in Test Adapter hoymiles-ms v0.2.x:

                        Es schaut für mich so aus, als ob für jedes einzelne Objekt die jeweilige JSON-Payload immer wieder neu geparst wird. Mir scheint das nicht optimal.

                        Das ist richtig. Das Verfahren wurde von einem anderen Adapter übernommen, da so die Konfiguration neuer States vom eigentlichen Code weitgehend getrennt ist.

                        Ist das mit Absicht so implementiert oder gibt es Planungen, die Payload für alle Felder nur einmal zu parsen?

                        Diene Anmerkung des redundanten Oaresnes ist pronzipiell richtig. Ich notier das mal als zukünftige Verbesserung, DANKE für das Feedback.

                        Ref: https://github.com/mcm4iob/ioBroker.hoymiles-ms/issues/75

                        Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                        Support Repositoryverwaltung.

                        Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                        LESEN - gute Forenbeitrage

                        1 Antwort Letzte Antwort
                        0
                        • mcm1957M mcm1957

                          @andabraha

                          Danke
                          kanns mir wahracheinlich erst morgen abends od Sa ansehen. Sorry

                          mcm1957M Online
                          mcm1957M Online
                          mcm1957
                          schrieb am zuletzt editiert von mcm1957
                          #26

                          @mcm1957 said in Test Adapter hoymiles-ms v0.2.x:

                          @andabraha

                          Danke
                          kanns mir wahracheinlich erst morgen abends od Sa ansehen. Sorry

                          Sorry - gestern null Kapazität. Und so wies heute aussieht eher auch nicht (Familie / Enkel sind da). Ich schau aber dass ich asap ne Alpha bau wo das abgefangen wird.

                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                          Support Repositoryverwaltung.

                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                          LESEN - gute Forenbeitrage

                          1 Antwort Letzte Antwort
                          1
                          • style24S Offline
                            style24S Offline
                            style24
                            schrieb am zuletzt editiert von
                            #27

                            Kann es sein, dass der Adapter seit dem heutigen Update der Firmware des MS-A2 nicht mehr startet?

                            1 Antwort Letzte Antwort
                            0
                            • mcm1957M Online
                              mcm1957M Online
                              mcm1957
                              schrieb am zuletzt editiert von
                              #28

                              Da ich meine MS A2 noch nicht aktualisisert habe kann ich das nicht beantworten.
                              Aber du solltest ja selbst sehen ob dein Adapter startet oder nicht :-).
                              MQTT hat ein paar Erweiterungen bekommen. Ob auch was inkompatibel geändert wurde hab ich noch nicht analysiert.

                              Ich geh mal davon aus, dass er bei dir nicht startet sonst würdest du nicht fragen. Kannst du ein wenig mehr Infos liefern? Z.B. einen Log mit der Fehlermeldung?

                              Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                              Support Repositoryverwaltung.

                              Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                              LESEN - gute Forenbeitrage

                              1 Antwort Letzte Antwort
                              0
                              • style24S Offline
                                style24S Offline
                                style24
                                schrieb am zuletzt editiert von
                                #29

                                Hi mcm1957,
                                ioBroker ist immer noch ne Aufgabe für mich. Ich schau mal was ich liefern kann und vielleicht hilft das :-)

                                
                                hoymiles-ms.0
                                2026-01-08 20:29:30.707	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v20.19.6, js-controller: 7.0.7
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:57.227	info	terminating
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:57.204	warn	setInterval called, but adapter is shutting down
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:57.203	info	[hoymilesMqtt] starting refresh timer
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:57.178	info	[hoymilesMqtt] device MSA-28002437xxxx subscribing to topic homeassistant/number/MSA-28002437xxxx/power_ctrl/set
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.724	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.722	info	terminating
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.716	error	Unexpected end of JSON input
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.715	error	SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49) at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36) at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.713	error	unhandled promise rejection: Unexpected end of JSON input
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.713	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.588	info	Device MSA-28002437xxxx is online
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.431	info	Device MSA-28002437xxxx is initializing states
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:56.365	info	[hoymilesMQTT] client MSA228002437xxxx connected from 192.168.0.142
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:42.628	info	[main] MQTT-Server started
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:42.627	info	MQTT server is running on 192.168.0.5:1883
                                
                                hoymiles-ms.0
                                2026-01-08 20:28:42.023	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v20.19.6, js-controller: 7.0.7
                                
                                Thomas BraunT 1 Antwort Letzte Antwort
                                1
                                • style24S style24

                                  Hi mcm1957,
                                  ioBroker ist immer noch ne Aufgabe für mich. Ich schau mal was ich liefern kann und vielleicht hilft das :-)

                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:29:30.707	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v20.19.6, js-controller: 7.0.7
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:57.227	info	terminating
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:57.204	warn	setInterval called, but adapter is shutting down
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:57.203	info	[hoymilesMqtt] starting refresh timer
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:57.178	info	[hoymilesMqtt] device MSA-28002437xxxx subscribing to topic homeassistant/number/MSA-28002437xxxx/power_ctrl/set
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.724	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.722	info	terminating
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.716	error	Unexpected end of JSON input
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.715	error	SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49) at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36) at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.713	error	unhandled promise rejection: Unexpected end of JSON input
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.713	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.588	info	Device MSA-28002437xxxx is online
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.431	info	Device MSA-28002437xxxx is initializing states
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:56.365	info	[hoymilesMQTT] client MSA228002437xxxx connected from 192.168.0.142
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:42.628	info	[main] MQTT-Server started
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:42.627	info	MQTT server is running on 192.168.0.5:1883
                                  
                                  hoymiles-ms.0
                                  2026-01-08 20:28:42.023	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v20.19.6, js-controller: 7.0.7
                                  
                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #30

                                  @style24 sagte in Test Adapter hoymiles-ms v0.2.x:

                                  ioBroker ist immer noch ne Aufgabe für mich.

                                  Dann haste noch eine weitere Aufgabe: Bring das ganze Spiel auf die aktuell vorgesehene nodejs-Version:
                                  Per

                                  iob nodejs-update
                                  

                                  Und das Logfile am besten immer aus dem Dateisystem verwenden, das ist besser formatiert.
                                  Per

                                  iob logs
                                  

                                  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

                                  1 Antwort Letzte Antwort
                                  0
                                  • style24S Offline
                                    style24S Offline
                                    style24
                                    schrieb am zuletzt editiert von style24
                                    #31

                                    So, nodejs ist geupdatet
                                    Vielen Dank übrigens für den Adapter fand den richtig gut - für Anfänger und so :-)

                                    code_text2026-01-08 20:55:48.904  - info: host.homebridge instance system.adapter.hoymiles-ms.0 in version "0.2.0" started with pid 17480
                                    2026-01-08 20:55:51.226  - info: hoymiles-ms.0 (17480) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v22.21.0, js-controller: 7.0.7
                                    2026-01-08 20:55:51.798  - info: hoymiles-ms.0 (17480) MQTT server is running on 192.168.0.5:1883
                                    2026-01-08 20:55:51.799  - info: hoymiles-ms.0 (17480) [main] MQTT-Server started
                                    2026-01-08 20:55:54.036  - info: host.homebridge instance system.adapter.dwd.0 in version "2.8.5" started with pid 17502
                                    2026-01-08 20:55:54.868  - info: hoymiles-ms.0 (17480) [hoymilesMQTT] client MSA228002437xxxx connected from 192.168.0.142
                                    2026-01-08 20:55:54.937  - info: hoymiles-ms.0 (17480) Device MSA-28002437xxxx is initializing states
                                    2026-01-08 20:55:55.279  - info: hoymiles-ms.0 (17480) Device MSA-28002437xxxx is online
                                    2026-01-08 20:55:55.289  - error: hoymiles-ms.0 (17480) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                    2026-01-08 20:55:55.290  - error: hoymiles-ms.0 (17480) unhandled promise rejection: Unexpected end of JSON input
                                    2026-01-08 20:55:55.293  - error: hoymiles-ms.0 (17480) SyntaxError: Unexpected end of JSON input
                                        at JSON.parse (<anonymous>)
                                        at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
                                        at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
                                        at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
                                        at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
                                        at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
                                    2026-01-08 20:55:55.295  - error: hoymiles-ms.0 (17480) Unexpected end of JSON input
                                    2026-01-08 20:55:55.301  - info: hoymiles-ms.0 (17480) terminating
                                    2026-01-08 20:55:55.302  - warn: hoymiles-ms.0 (17480) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                    2026-01-08 20:55:55.763  - info: hoymiles-ms.0 (17480) [hoymilesMqtt] device MSA-28002437xxxx subscribing to topic homeassistant/number/MSA-28002437xxxx/power_ctrl/set
                                    2026-01-08 20:55:55.809  - info: hoymiles-ms.0 (17480) terminating
                                    2026-01-08 20:55:55.843  - warn: hoymiles-ms.0 (17480) redis get hoymiles-ms.0.MSA-28002437xxxx.power_ctrl.set, error - Connection is closed.
                                    2026-01-08 20:55:55.849  - info: hoymiles-ms.0 (17480) [hoymilesMqtt] starting refresh timer
                                    2026-01-08 20:55:55.854  - warn: hoymiles-ms.0 (17480) setInterval called, but adapter is shutting down
                                    2026-01-08 20:55:56.055  - error: host.homebridge instance system.adapter.hoymiles-ms.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    2026-01-08 20:55:56.059  - info: host.homebridge Restart adapter system.adapter.hoymiles-ms.0 because enabled
                                    2026-01-08 20:55:57.339  - info: dwd.0 (17502) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v22.21.0, js-controller: 7.0.7
                                    2026-01-08 20:55:58.165  - info: dwd.0 (17502) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                    2026-01-08 20:55:58.706  - info: host.homebridge instance system.adapter.dwd.0 having pid 17502 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                    2026-01-08 20:56:26.899  - info: host.homebridge instance system.adapter.hoymiles-ms.0 in version "0.2.0" started with pid 17617
                                    2026-01-08 20:56:29.482  - info: hoymiles-ms.0 (17617) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v22.21.0, js-controller: 7.0.7
                                    2026-01-08 20:56:30.113  - info: hoymiles-ms.0 (17617) MQTT server is running on 192.168.0.5:1883
                                    2026-01-08 20:56:30.114  - info: hoymiles-ms.0 (17617) [main] MQTT-Server started
                                    2026-01-08 20:56:31.020  - info: hoymiles-ms.0 (17617) [hoymilesMQTT] client MSA228002437xxxx connected from 192.168.0.142
                                    2026-01-08 20:56:31.128  - info: hoymiles-ms.0 (17617) Device MSA-28002437xxxx is initializing states
                                    2026-01-08 20:56:31.284  - info: hoymiles-ms.0 (17617) Device MSA-28002437xxxx is online
                                    2026-01-08 20:56:31.397  - error: hoymiles-ms.0 (17617) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                    2026-01-08 20:56:31.398  - error: hoymiles-ms.0 (17617) unhandled promise rejection: Unexpected end of JSON input
                                    2026-01-08 20:56:31.400  - error: hoymiles-ms.0 (17617) SyntaxError: Unexpected end of JSON input
                                        at JSON.parse (<anonymous>)
                                        at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
                                        at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
                                        at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
                                        at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
                                        at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
                                    2026-01-08 20:56:31.402  - error: hoymiles-ms.0 (17617) Unexpected end of JSON input
                                    2026-01-08 20:56:31.407  - info: hoymiles-ms.0 (17617) terminating
                                    2026-01-08 20:56:31.408  - warn: hoymiles-ms.0 (17617) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                    2026-01-08 20:56:31.809  - info: hoymiles-ms.0 (17617) [hoymilesMqtt] device MSA-28002437xxxx subscribing to topic homeassistant/number/MSA-28002437xxxx/power_ctrl/set
                                    2026-01-08 20:56:31.833  - info: hoymiles-ms.0 (17617) [hoymilesMqtt] starting refresh timer
                                    2026-01-08 20:56:31.834  - warn: hoymiles-ms.0 (17617) setInterval called, but adapter is shutting down
                                    2026-01-08 20:56:31.910  - info: hoymiles-ms.0 (17617) terminating
                                    2026-01-08 20:56:32.024  - error: host.homebridge instance system.adapter.hoymiles-ms.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    2026-01-08 20:56:32.024  - info: host.homebridge Restart adapter system.adapter.hoymiles-ms.0 because enabled
                                    
                                    1 Antwort Letzte Antwort
                                    0
                                    • mcm1957M Online
                                      mcm1957M Online
                                      mcm1957
                                      schrieb am zuletzt editiert von mcm1957
                                      #32

                                      Hmm ...
                                      An der stelle parst er eigentlich nur die Daten die der Akku schickt. Ein Unexpected end of Json ist da eher unerwartet - außer da kommen fehlerhafte Daten an.
                                      (Sollte der Adapter aber auch abfangen ...)
                                      Kannst du bitte mal den Loglevel der Instanz auf DEBUG setzen und das Log posten? Loglevel einstellen geht wenn du expert Mode aktiv hast. Würd gern sehen was da tasächlich gesendet wird.

                                      Übrigends: in obigem Beispiel ist noch deine client ID drinnen (beim 'connected from ') - maskier die ev.
                                      Hab das auch registriert dass das de Adapter gleich macht

                                      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                      Support Repositoryverwaltung.

                                      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                      LESEN - gute Forenbeitrage

                                      1 Antwort Letzte Antwort
                                      0
                                      • style24S Offline
                                        style24S Offline
                                        style24
                                        schrieb am zuletzt editiert von
                                        #33

                                        hier bitte, hoffe das passt so

                                        026-01-08 21:38:36.312  - info: host.homebridge Restart adapter system.adapter.hoymiles-ms.0 because enabled
                                        2026-01-08 21:38:59.679  - info: host.homebridge instance system.adapter.hoymiles-ms.0 in version "0.2.0" started with pid 21434
                                        2026-01-08 21:39:01.582  - debug: hoymiles-ms.0 (21434) Redis Objects: Use Redis connection: 127.0.0.1:9001
                                        2026-01-08 21:39:01.655  - debug: hoymiles-ms.0 (21434) Objects client ready ... initialize now
                                        2026-01-08 21:39:01.659  - debug: hoymiles-ms.0 (21434) Objects create System PubSub Client
                                        2026-01-08 21:39:01.660  - debug: hoymiles-ms.0 (21434) Objects create User PubSub Client
                                        2026-01-08 21:39:01.751  - debug: hoymiles-ms.0 (21434) Objects client initialize lua scripts
                                        2026-01-08 21:39:01.759  - debug: hoymiles-ms.0 (21434) Objects connected to redis: 127.0.0.1:9001
                                        2026-01-08 21:39:01.818  - debug: hoymiles-ms.0 (21434) Redis States: Use Redis connection: 127.0.0.1:9000
                                        2026-01-08 21:39:01.843  - debug: hoymiles-ms.0 (21434) States create System PubSub Client
                                        2026-01-08 21:39:01.845  - debug: hoymiles-ms.0 (21434) States create User PubSub Client
                                        2026-01-08 21:39:01.929  - debug: hoymiles-ms.0 (21434) States connected to redis: 127.0.0.1:9000
                                        2026-01-08 21:39:02.131  - info: hoymiles-ms.0 (21434) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.hoymiles-ms, node: v22.21.0, js-controller: 7.0.7
                                        2026-01-08 21:39:02.207  - debug: hoymiles-ms.0 (21434) reset of states in progress...
                                        2026-01-08 21:39:02.260  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.info.online
                                        2026-01-08 21:39:02.267  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.info.ip
                                        2026-01-08 21:39:02.274  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.power_ctrl.min
                                        2026-01-08 21:39:02.281  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.power_ctrl.max
                                        2026-01-08 21:39:02.287  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.sw_version
                                        2026-01-08 21:39:02.294  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.power_ctrl.step
                                        2026-01-08 21:39:02.302  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.power_ctrl.set
                                        2026-01-08 21:39:02.309  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.ems_mode.command
                                        2026-01-08 21:39:02.317  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.bat_p
                                        2026-01-08 21:39:02.326  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.bat_sts
                                        2026-01-08 21:39:02.336  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.grid_on_p
                                        2026-01-08 21:39:02.343  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.grid_off_p
                                        2026-01-08 21:39:02.350  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.soc
                                        2026-01-08 21:39:02.358  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_bat_p
                                        2026-01-08 21:39:02.367  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_grid_p
                                        2026-01-08 21:39:02.378  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_load_p
                                        2026-01-08 21:39:02.386  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_plug_p
                                        2026-01-08 21:39:02.396  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_pv_p
                                        2026-01-08 21:39:02.404  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_soc
                                        2026-01-08 21:39:02.411  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.realtime.sys_sp_p
                                        2026-01-08 21:39:02.418  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.bat_p
                                        2026-01-08 21:39:02.424  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.bat_i
                                        2026-01-08 21:39:02.430  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.chg_e
                                        2026-01-08 21:39:02.437  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.bat_p
                                        2026-01-08 21:39:02.445  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.dchg_e
                                        2026-01-08 21:39:02.453  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.bat_temp
                                        2026-01-08 21:39:02.461  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.grid_p
                                        2026-01-08 21:39:02.470  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.bat_v
                                        2026-01-08 21:39:02.482  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.ems_mode
                                        2026-01-08 21:39:02.512  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.bat_sts
                                        2026-01-08 21:39:02.521  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.plug_in_e
                                        2026-01-08 21:39:02.527  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.ein
                                        2026-01-08 21:39:02.534  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.plug_out_e
                                        2026-01-08 21:39:02.543  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.eout
                                        2026-01-08 21:39:02.549  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.pv_e
                                        2026-01-08 21:39:02.556  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.etin
                                        2026-01-08 21:39:02.569  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.pv_p
                                        2026-01-08 21:39:02.575  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.etout
                                        2026-01-08 21:39:02.582  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.soc
                                        2026-01-08 21:39:02.589  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.i
                                        2026-01-08 21:39:02.595  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.system.sp_p
                                        2026-01-08 21:39:02.602  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.f
                                        2026-01-08 21:39:02.608  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.p
                                        2026-01-08 21:39:02.614  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.q
                                        2026-01-08 21:39:02.620  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_off.v
                                        2026-01-08 21:39:02.627  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.ein
                                        2026-01-08 21:39:02.633  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.eout
                                        2026-01-08 21:39:02.640  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.etin
                                        2026-01-08 21:39:02.646  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.etout
                                        2026-01-08 21:39:02.652  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.i
                                        2026-01-08 21:39:02.659  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.f
                                        2026-01-08 21:39:02.665  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.p
                                        2026-01-08 21:39:02.671  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.q
                                        2026-01-08 21:39:02.677  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.grid_on.v
                                        2026-01-08 21:39:02.684  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.ein
                                        2026-01-08 21:39:02.690  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.eout
                                        2026-01-08 21:39:02.696  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.etin
                                        2026-01-08 21:39:02.703  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.etout
                                        2026-01-08 21:39:02.709  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.i
                                        2026-01-08 21:39:02.716  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.p
                                        2026-01-08 21:39:02.722  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.q
                                        2026-01-08 21:39:02.744  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.inv.v
                                        2026-01-08 21:39:02.753  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.rssi
                                        2026-01-08 21:39:02.760  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-2800243xxxxxx.device.soc
                                        2026-01-08 21:39:02.767  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-.info.online
                                        2026-01-08 21:39:02.774  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-.info.ip
                                        2026-01-08 21:39:02.781  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MS.info.online
                                        2026-01-08 21:39:02.804  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MS.info.ip
                                        2026-01-08 21:39:02.810  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.M.info.online
                                        2026-01-08 21:39:02.817  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.M.info.ip
                                        2026-01-08 21:39:02.823  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-28.info.online
                                        2026-01-08 21:39:02.830  - debug: hoymiles-ms.0 (21434) resetting id hoymiles-ms.0.MSA-28.info.ip
                                        2026-01-08 21:39:02.836  - debug: hoymiles-ms.0 (21434) [hoymilesMqtt] initializing
                                        2026-01-08 21:39:02.837  - debug: hoymiles-ms.0 (21434) [MQTT-Server] init server at 192.168.0.5:1883
                                        2026-01-08 21:39:02.853  - info: hoymiles-ms.0 (21434) MQTT server is running on 192.168.0.5:1883
                                        2026-01-08 21:39:02.853  - info: hoymiles-ms.0 (21434) [main] MQTT-Server started
                                        2026-01-08 21:39:16.253  - debug: hoymiles-ms.0 (21434) [MQTT-Server] client connection from  192.168.0.142
                                        2026-01-08 21:39:16.284  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) client connected with id MSA22800243xxxxxx connected from 192.168.0.142
                                        2026-01-08 21:39:16.350  - info: hoymiles-ms.0 (21434) [hoymilesMQTT] client MSA22800243xxxxxx connected from 192.168.0.142
                                        2026-01-08 21:39:16.387  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) client ping
                                        2026-01-08 21:39:16.443  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/switch/MSA-2800243xxxxxx/config": {"state_topic":"homeassistant/sensor/MSA-2800243xxxxxx/device/state","json_attributes_topic":"homeassistant/sensor/MSA-2800243xxxxxx/attributes","unique_id":"MSA-2800243xxxxxx","device":{"identifiers":["2800243xxxxxx"],"name":"MSA-2800243xxxxxx","manufacturer":"Hoymiles","model":"MS-A2","sw_version":"01.06.03"}}
                                        2026-01-08 21:39:16.447  - info: hoymiles-ms.0 (21434) Device MSA-2800243xxxxxx is initializing states
                                        2026-01-08 21:39:16.538  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/sensor/MSA-2800243xxxxxx/attributes": {"supported_topics":{"quick_state":"homeassistant/sensor/MSA-2800243xxxxxx/quick/state","device_state":"homeassistant/sensor/MSA-2800243xxxxxx/device/state","system_state":"homeassistant/sensor/MSA-2800243xxxxxx/system/state","ems_mode":"homeassistant/select/MSA-2800243xxxxxx/ems_mode/command","power_ctrl":"homeassistant/number/MSA-2800243xxxxxx/power_ctrl/set","tou_day_plan":"homeassistant/sensor/MSA-2800243xxxxxx/tou_day_plan/set","tou_week_plan":"homeassistant/sensor/MSA-2800243xxxxxx/tou_week_plan/set","tou_get":"homeassistant/sensor/MSA-2800243xxxxxx/tou_plan/get"}}
                                        2026-01-08 21:39:16.542  - debug: hoymiles-ms.0 (21434) initialization of states for device MSA-2800243xxxxxx in progress...
                                        2026-01-08 21:39:16.574  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.device.manufacturer" in progress
                                        2026-01-08 21:39:16.591  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.device.model" in progress
                                        2026-01-08 21:39:16.620  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.device.name" in progress
                                        2026-01-08 21:39:16.632  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.info.online" in progress
                                        2026-01-08 21:39:16.640  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/number/MSA-2800243xxxxxx/power_ctrl/config": 
                                        2026-01-08 21:39:16.641  - debug: hoymiles-ms.0 (21434) initialization of states for device MSA-2800243xxxxxx in progress...
                                        2026-01-08 21:39:16.647  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.info.ip" in progress
                                        2026-01-08 21:39:16.657  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.info.timestamp" in progress
                                        2026-01-08 21:39:16.673  - debug: hoymiles-ms.0 (21434) initialization of states for device MSA-2800243xxxxxx completed
                                        2026-01-08 21:39:16.697  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/number/MSA-2800243xxxxxx/power_ctrl/config": {"name":null,"command_topic":"homeassistant/number/MSA-2800243xxxxxx/power_ctrl/set","device_class":"power","unit_of_measurement":"W","min":-1000,"max":1257,"step":0.100000000000000,"unique_id":"MSA-2800243xxxxxx","device":{"identifiers":["2800243xxxxxx"],"name":"MSA-2800243xxxxxx","manufacturer":"Hoymiles","model":"MS-A2"}}
                                        2026-01-08 21:39:16.712  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.power_ctrl.min" in progress
                                        2026-01-08 21:39:16.730  - info: hoymiles-ms.0 (21434) Device MSA-2800243xxxxxx is online
                                        2026-01-08 21:39:16.741  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.power_ctrl.max" in progress
                                        2026-01-08 21:39:16.757  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.device.identifiers" in progress
                                        2026-01-08 21:39:16.774  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.power_ctrl.step" in progress
                                        2026-01-08 21:39:16.803  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/sensor/MSA-2800243xxxxxx/soc/config": {"name":"soc","state_topic":"homeassistant/sensor/MSA-2800243xxxxxx/quick/state","value_template":"{{ value_json.soc }}","device_class":"battery","unit_of_measurement":"%","device":{"identifiers":["2800243xxxxxx"],"name":"MSA-2800243xxxxxx","manufacturer":"Hoymiles","model":"MS-A2"}}
                                        2026-01-08 21:39:16.892  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/sensor/MSA-2800243xxxxxx/bat_p/config": {"name":"bat_power","state_topic":"homeassistant/sensor/MSA-2800243xxxxxx/quick/state","value_template":"{{ value_json.bat_p }}","device_class":"power","unit_of_measurement":"W","device":{"identifiers":["2800243xxxxxx"],"name":"MSA-2800243xxxxxx","manufacturer":"Hoymiles","model":"MS-A2"}}
                                        2026-01-08 21:39:16.899  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.device.sw_version" in progress
                                        2026-01-08 21:39:16.954  - error: hoymiles-ms.0 (21434) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                        2026-01-08 21:39:16.955  - error: hoymiles-ms.0 (21434) unhandled promise rejection: Unexpected end of JSON input
                                        2026-01-08 21:39:16.956  - error: hoymiles-ms.0 (21434) SyntaxError: Unexpected end of JSON input
                                            at JSON.parse (<anonymous>)
                                            at mqtt_publish_funct (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/states.js:750:49)
                                            at HoymilesMqtt.onMqttMessage (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/hoymilesMqtt.js:50:25)
                                            at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
                                            at async HoymilesMsAdapter.mqttEventCallback (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/main.js:71:36)
                                            at async Connection.<anonymous> (/opt/iobroker/node_modules/iobroker.hoymiles-ms/build/lib/mqttServer.js:60:13)
                                        2026-01-08 21:39:16.956  - error: hoymiles-ms.0 (21434) Unexpected end of JSON input
                                        2026-01-08 21:39:16.962  - info: hoymiles-ms.0 (21434) terminating
                                        2026-01-08 21:39:16.964  - warn: hoymiles-ms.0 (21434) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                        2026-01-08 21:39:16.997  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/select/MSA-2800243xxxxxx/ems_mode/config": 
                                        2026-01-08 21:39:17.042  - info: host.homebridge instance system.adapter.openweathermap.0 in version "1.1.2" started with pid 21476
                                        2026-01-08 21:39:17.055  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/select/MSA-2800243xxxxxx/ems_mode/config": {"command_topic":"homeassistant/select/MSA-2800243xxxxxx/ems_mode/command","options":["general","mqtt_ctrl","tou_plan"],"unique_id":"MSA-2800243xxxxxx","device":{"identifiers":["2800243xxxxxx"],"name":"MSA-2800243xxxxxx","manufacturer":"Hoymiles","model":"MS-A2"}}
                                        2026-01-08 21:39:17.097  - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) client subscribed to "homeassistant/number/MSA-2800243xxxxxx/power_ctrl/set"
                                        2026-01-08 21:39:17.100  - debug: hoymiles-ms.0 (21434) [hoymilesMqtt] process subscription homeassistant/number/MSA-2800243xxxxxx/power_ctrl/set
                                        2026-01-08 21:39:17.162  - info: hoymiles-ms.0 (21434) [hoymilesMqtt] device MSA-2800243xxxxxx subscribing to topic homeassistant/number/MSA-2800243xxxxxx/power_ctrl/set
                                        2026-01-08 21:39:17.163  - debug: hoymiles-ms.0 (21434) creation of state "MSA-2800243xxxxxx.power_ctrl.set" in progress
                                        2026-01-08 21:39:17.233  - info: hoymiles-ms.0 (21434) [hoymilesMqtt] starting refresh timer
                                        2026-01-08 21:39:17.233  - warn: hoymiles-ms.0 (21434) setInterval called, but adapter is shutting down
                                        2026-01-08 21:39:17.465  - info: hoymiles-ms.0 (21434) terminating
                                        2026-01-08 21:39:17.632  - error: host.homebridge instance system.adapter.hoymiles-ms.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                        2026-01-08 21:39:17.633  - info: host.homebridge Restart adapter system.adapter.hoymiles-ms.0 because enabled
                                        2026-01-08 21:39:17.634  - warn: host.homebridge Do not restart adapter system.adapter.hoymiles-ms.0 because restart loop detected
                                        
                                        1 Antwort Letzte Antwort
                                        0
                                        • mcm1957M Online
                                          mcm1957M Online
                                          mcm1957
                                          schrieb am zuletzt editiert von
                                          #34

                                          Jep - sieht nach nem Bug bei Hoymiles aus.
                                          Da kommt ne leere Message an ...

                                          2026-01-08 21:39:16.640 - debug: hoymiles-ms.0 (21434) [MQTT-Server] (MSA22800243xxxxxx) received message from client on topic "homeassistant/number/MSA-2800243xxxxxx/power_ctrl/config":

                                          Hab das mal an Hoymiles weitergeleitet.
                                          Ich kann und werd das auch im Adapter abfangen und zeitnahe eine alpha Testversion erstellen. Bitte gib mir ein zwei Tage,

                                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                          Support Repositoryverwaltung.

                                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                          LESEN - gute Forenbeitrage

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          633

                                          Online

                                          32.6k

                                          Benutzer

                                          82.1k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          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