Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[gs411]

@mcm1957
Habe den Adapter installiert, funktioniert. Vielen Dank für Deine Arbeit.

[andabraha]

Habe den Adpater auch soeben im Einsatz für 2 MS-A2, schreibe die Werte in eine influxDB. Der nächste Step ist die Visualisierung in grafana.
Ich hatte vorher den generischen MQTT Adapter laufen und mußte mir mittels Script die einzelnen Datenpunkte erstellen.
So finde ich das dann doch "smarter"

@mcm1957
Vielen Dank für den Adapter und die Zeit die dafür schon aufgebracht wurde

[mcm1957]

@andre1980hb

Danke fürs Feedback.
Falls dir Funktionen fehlen, erstell gern ein Issue.

Vorweg allerdinsg:
Derzeit plane ich nicht eine komplette Nullpunktregelung zu implementieren. Ich möchte das zwar nicht ausschließen - prio 1 ist aber aber sicher nicht.

P.S. Stable kommt sobal ich Zeit habe.

[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:

[mcm1957]

@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

[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

[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)

[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,

[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 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.

[andabraha]

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

[mcm1957]

@andabraha

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

[andabraha]

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

[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?

[mcm1957]

@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

[mcm1957]

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

[style24]

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

[mcm1957]

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?

[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 Braun]

@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