Monatsrückblick Oktober 2026 ist online!

[Kanzler1959]

Ok ... zur Installation: das Problem war zwischen den Ohren --> war schon lange her, das ich die Beta Sachen genutzt habe (waren also nicht zugelasen).
Habe es umgestellt ... log mit einem error (als Tipp - funktioniert aber):

$ iobroker add luxtronik2-controller auto --host myIOBroker --debug
NPM version: 10.9.8
Installing iobroker.luxtronik2-controller@0.18.2... (System call)
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated gauge@2.7.4: This package is no longer supported.
> usocket@0.3.0 install
> node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2gyp info using node@22.23.2 | linux | arm64
(node:309458) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.(Use `node --trace-deprecation ...` to show where the warning was created)
gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
gyp ERR! UNCAUGHT EXCEPTION gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#<Object>'gyp ERR! stack at createConfigFile (/opt/iobroker/node_modules/usocket/node_modules/node-gyp/lib/configure.js:117:21)gyp ERR! stack at /opt/iobroker/node_modules/usocket/node_modules/node-gyp/lib/configure.js:84:9gyp ERR! stack at FSReqCallback.oncomplete (node:fs:186:23)gyp ERR! System Linux 6.12.96+rpt-rpi-v8gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/usocket/node_modules/.bin/node-gyp" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/usocketgyp ERR! node -v v22.23.2gyp ERR! node-gyp -v v7.1.2gyp ERR! Node-gyp failed to build your package.gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.
added 2 packages in 12s
226 packages are looking for funding run `npm fund` for details
host.myIOBroker install adapter luxtronik2-controller
upload [21] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/de.json i18n/de.json application/json
upload [20] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/en.json i18n/en.json application/json
upload [19] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/es.json i18n/es.json application/json
upload [18] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/fr.json i18n/fr.json application/json
upload [17] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/it.json i18n/it.json application/json
upload [16] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/nl.json i18n/nl.json application/json
upload [15] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/pl.json i18n/pl.json application/json
upload [14] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/pt.json i18n/pt.json application/json
upload [13] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/ru.json i18n/ru.json application/json
upload [12] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/uk.json i18n/uk.json application/json
upload [11] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/i18n/zh-cn.json i18n/zh-cn.json application/json
upload [10] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/HUP_Optimierung.svg img/HUP_Optimierung.svg image/svg+xml
upload [9] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/HUP_Optimierung_de.svg img/HUP_Optimierung_de.svg image/svg+xml
upload [8] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/HUP_Optimierung_en.svg img/HUP_Optimierung_en.svg image/svg+xml
upload [7] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/Objekte.png img/Objekte.png image/png
upload [6] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/Objekte_DE.png img/Objekte_DE.png image/png
upload [5] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/Objekte_EN.png img/Objekte_EN.png image/png
upload [4] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/Takt_Optimierung.svg img/Takt_Optimierung.svg image/svg+xml
upload [3] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/img/Takt_Optimierung_de.svg img/Takt_Optimierung_de.svg image/svg+xml
upload [1] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/jsonConfig.json jsonConfig.json application/json
upload [0] luxtronik2-controller.admin /opt/iobroker/node_modules/iobroker.luxtronik2-controller/admin/luxtronik2-controller.png luxtronik2-controller.png image/png
host.myIOBroker object system.adapter.luxtronik2-controller created/updated
Updating objects from io-package.json for adapter "luxtronik2-controller" with version "0.18.2"
host.myIOBroker create instance luxtronik2-controller
host.myIOBroker object system.adapter.luxtronik2-controller.0.alive created
host.myIOBroker object system.adapter.luxtronik2-controller.0.connected created
host.myIOBroker object system.adapter.luxtronik2-controller.0.compactMode created
host.myIOBroker object system.adapter.luxtronik2-controller.0.cpu created
host.myIOBroker object system.adapter.luxtronik2-controller.0.cputime created
host.myIOBroker object system.adapter.luxtronik2-controller.0.memHeapUsed created
host.myIOBroker object system.adapter.luxtronik2-controller.0.memHeapTotal created
host.myIOBroker object system.adapter.luxtronik2-controller.0.memRss created
host.myIOBroker object system.adapter.luxtronik2-controller.0.inputCount created
host.myIOBroker object system.adapter.luxtronik2-controller.0.outputCount created
host.myIOBroker object system.adapter.luxtronik2-controller.0.eventLoopLag created
host.myIOBroker object system.adapter.luxtronik2-controller.0.sigKill created
host.myIOBroker object system.adapter.luxtronik2-controller.0.logLevel created
host.myIOBroker object system.adapter.luxtronik2-controller.0.objectsWarnLimit created
host.myIOBroker object luxtronik2-controller.0.info created
host.myIOBroker object luxtronik2-controller.0.backups created
host.myIOBroker object luxtronik2-controller.0.info.connection created
host.myIOBroker Set default value of luxtronik2-controller.0.info.connection: false
host.myIOBroker object system.adapter.luxtronik2-controller.0 created
Process exited with code 0

Noch ein Tip: Ich habe zwei Telegram Instanzen (bots) ... einer mit wenig Zeugs für die Familie und einer mit 'allerlei' für mich ;-). Es wird aber 'kein Tele....' angezeigt:

Aber die Instanzen sind dann schon da:

Ja - die neue Pumpe (nach wie vor eine Solepumpe) ist jetzt geschmeidiger (was ich so sagen kann bei drei Tagen (Dauer)lauf. Bis jetzt ist Sie tatsächlich durchgelaufen (75h). Die Nibe Fighter vorher war ein EIN/AUS Kompressor. Hat - vielleicht interessiert es jemanden - gute 20 Jahre gehalten. Dann war der Durchfluss nur noch 150l/h. Der Installateur hat mal reingeschaut (konnte man erst nach dem Abbau): Die Heizungsseite des Wärmetauschers war 'dicht'. Warum - keine Ide (evtl. das 'normale' Wasser in der Fussbodenheizung in Verbindung mit etwas sorglosem Umgang mit dem Druck in der Heizung. Ich habe teilweise Monate / Jahre nicht nach der Heizung geschaut - lief ja. Der Kompressor und der Rest liefen bis zum Ende einwandfrei. Wir haben uns dann gegen eine Reparatur entschieden, da das Ding dazu sowieso raus musste aus der Ecke - und wir jetzt (bis wir dann wirklich alt sind) erst mal Ruhe haben (und Förderung gibt es ja auch (noch)).

Man sieht - ich kann auch in lang ;-)

Jetzt muss ich mir noch ein bischen VIS basteln. Hab nix zum c/p gefunden

[TbsJah]

Der Adapter aura bietet auch sehr gute Visualisierungsmöglichkeiten.
Hat bei mir VIS abgelöst

[TbsJah]

@Kanzler1959 sagte:

log mit einem error (als Tipp - funktioniert aber):

Die Meldung betrifft ausschließlich Raspberry Pi / ARM-Nutzer.
Ich habe die Readme angepasst - Danke für die Info

Erklärung

Spoiler

Das Paket modbus-serial, das du für die Luxtronik-Kommunikation brauchst, unterstützt nicht nur Modbus TCP (über das Netzwerk), sondern auch Modbus RTU (über echte, physische serielle Kabel). Dafür versucht es, Hardware-Pakete für serielle Schnittstellen und systemnahe Sockets (wie serialport und tief im Baum versteckt dann eben auch usocket) herunterzuladen.
Weil diese ganze Kette aber durch das Wort optional eingeleitet wird, passiert beim Anwender auf dem Raspberry Pi genau das Richtige:
NPM versucht, diese systemnahen Pakete zu kompilieren. Der Compiler crasht (die roten Fehler im Log). NPM sagt sich: "Egal, der Entwickler von modbus-serial hat gesagt, das Zeug ist nur optional!", ignoriert den Fehler komplett und installiert deinen Adapter einfach erfolgreich zu Ende. Da du für die Luxtronik ohnehin nur Modbus TCP (Netzwerk) nutzt, funktioniert das auch ohne die fehlenden Pakete tadellos.

@Kanzler1959 sagte:

Es wird aber 'kein Tele....' angezeigt:

Da hast du völlig recht, das ist ein klassischer Logik-Fehler in der Oberfläche!
Ist jetzt aktualisiert in der 0.19.0

Spoiler

[TbsJah]

0.19.0 (2026-10-19)

🚀 Features & UX Improvements

• Hybrid Modbus TCP Support: Introduced hybrid Modbus TCP support (modbus-serial) to write volatile parameters (e.g., target temperatures, heating curves, and coils/switches) directly into the Luxtronik RAM without causing EEPROM/flash memory wear, while continuing to read full telemetry via native port 8889/8214.
• Smart ZIP Configuration: Completely redesigned the Circulation Pump (ZIP) tab in the Admin UI. Introduced a dynamic dropdown (zip_control_mode) to intuitively switch between Internal Controller, External Actor (e.g., Shelly), and Modbus TCP (Coil 7), automatically hiding irrelevant settings to prevent misconfigurations.
• ZIP Countdown Timer: Added a new virtual datapoint (Information.03_Outputs.Virtual_ZIP_Remaining_Time) that displays the remaining runtime of the active circulation pump cycle in seconds.
• Seamless Migration: Implemented an automatic background migration routine to seamlessly upgrade existing user configurations to the new ZIP control logic without data loss.

🐛 Bugfixes

• Telegram Notifications UI: Fixed a logic issue in jsonConfig.json where the Telegram warning message was incorrectly displayed even when instances were installed and available, and fixed the broken icon on the test button.

📝 Documentation

• ARM Installation Notes: Added a troubleshooting note to the README clarifying that usocket, serialport, and node-gyp compilation errors on Raspberry Pi / ARM systems originate from optional serial dependencies and can be safely ignored.

0.18.2 (2026-10-17)

🔧 Maintenance & Repository Compliance

• Core Dependency Update: Raised minimum required js-controller dependency to >=7.0.7 in io-package.json to ensure compatibility with modern ioBroker environments (resolves E1057).
• Full i18n Localization for Admin UI: Added complete multi-language label sets (ru, pt, nl, fr, it, es, pl, uk, zh-cn) for COP power and thermal source selection dropdowns in jsonConfig.json (resolves W5611).
• Package News Cleanup: Removed unreleased intermediate tags (0.17.0, 0.16.1) from common.news in io-package.json to align strictly with published NPM releases (resolves W2004).
• CI/CD Security Compliance: Updated GitHub auto-merge workflows for Dependabot to adhere to GitHub's updated pull_request_target execution policies (PR #90 / Issue #89).
• Code Modernization: Migrated built-in Node.js module imports to use the explicit node: protocol prefix (e.g. node:fs, node:path).

0.18.1 (2026-10-13)

🐛 Bugfixes

• COP Database Persistence: Fixed a critical bug in the object manager's cleanup routine (cleanupStates). The internal database folder (hidden.cop_buckets) was missing from the exclusion list and got aggressively deleted upon every adapter restart, resulting in wiped COP histories and (null) values. The hidden states are now strictly protected against the cleanup process, ensuring long-term persistence for energy calculations.

[TbsJah]

Jetzt passt auch wieder die Dokumentation zu dem Stand

Info Deutsch
Info English

0.19.1 (2026-10-20)

📝 Documentation & Guide Overhaul

• Complete Alignment of Documentation (README.md & documentation/readme_de.md & documentation/readme_en.md):
  • Restructured and synchronized both German and English documentation to accurately match all 11 configuration tabs of the Admin UI in sequential order:
  • Hardware Protection Architecture: Added an explicit section explaining Read-Before-Write protection (writePumpSafe), daily and total flash cycle counters, and the vendor firmware .90 crash shield.
  • Troubleshooting & ARM Compatibility: Added troubleshooting documentation regarding harmless node-gyp / serialport / usocket compilation warnings on Raspberry Pi / ARM systems, alongside step-by-step guidance for running the raw TCP diagnostic script (Test_Script.ts).

[TbsJah]

0.20.0 (2026-10-22)

🚀 Features & Enhancements

• Automatic Firmware Update Check: Added a background service to automatically check the official AIT download portal for new heat pump firmware updates.
• Update Notifications: Added a new configuration tab to set a custom cron schedule and enable optional Telegram notifications when a new firmware version is released.
• New Update Datapoints: Added firmware_available, firmware_update_available, and firmware_changelog to the system info tree to directly expose update states and release notes in ioBroker.
• Manual Trigger Button: Added a check_firmware button to manually initiate the update check process at any time.

0.19.6 (2026-10-22)

🚀 Features & Enhancements

• Defrost Request Datapoint: Added Information.03_Outputs.DefrostRequest2 (Defrost request) to monitor the active defrosting request of the heat pump directly from the RAM telemetry (Index 235).

• Defrost Request Datapoint: Added Information.03_Outputs.DefrostRequest (Defrost request) to monitor the active defrosting request of the heat pump directly from the RAM telemetry (Index 234).

0.19.4 (2026-10-20)

🔧 Compatibility & Maintenance

• Hybrid Modbus Value Persistence: Prevented native 3003 telemetry polling (EEPROM) from overwriting volatile parameters actively managed via Modbus TCP (RAM) in the ioBroker object tree.

0.19.3 (2026-10-20)

🔧 Compatibility & Maintenance

• Broader Node.js Compatibility: Adjusted Node.js removed { "node": ">=18.0.0" } in dependencies in io-package.json. T

0.19.2 (2026-10-20)

🔧 Compatibility & Maintenance

• Broader Node.js Compatibility: Adjusted Node.js engine requirement from >=22 down to >=18.0.0 in package.json and added { "node": ">=18.0.0" } to dependencies in io-package.json. This enables full compatibility with widely used Long-Term Support (LTS) releases (Node.js 18 and 20) while preventing installation on deprecated runtimes.
• Hybrid Modbus Value Persistence: Prevented native 3003 telemetry polling (EEPROM) from overwriting volatile parameters actively managed via Modbus TCP (RAM) in the ioBroker object tree.

[TbsJah]

Neu: Automatische Firmware-Update-Prüfung!

Ab sofort informiert euch der Adapter vollautomatisch, wenn ein neues Firmware-Update für eure Wärmepumpe bereitsteht.

Die neue Funktion bringt folgende Einstellmöglichkeiten mit:

• ListenpunktFlexibler Timer: Der Abfragezeitraum lässt sich in den Einstellungen ganz individuell per Cron-Job definieren.

• ListenpunktBenachrichtigungswege: Ihr könnt frei wählen, wie ihr informiert werden möchtet – per Telegram-Nachricht und/oder direkt über das ioBroker Notification Center (die kleine Glocke oben rechts).

• ListenpunktInklusive Changelog: Die Release Notes der neuen Version werden direkt lesbar in der Benachrichtigung mitgeliefert.

Viel Spaß beim Testen und Feedback ist wie immer willkommen!

[Homer.J.]

@TbsJah sagte:

0.20.0 (2026-10-22)

nach dem Update ist mir ein Bug aufgefallen.
luxtronik2-controller.0.Settings.02_Heating.heating_temperature
ist der Wert anstatt z.B. 5 C jetzt 50 C

Grüße

[TbsJah]

@Homer.J. sagte:

uxtronik2-controller.0.Settings.02_Heating.heating_temperature
ist der Wert anstatt z.B. 5 C jetzt 50 C

Du hast völlig recht, da war tatsächlich ein Fehler beim Skalierungsfaktor! Das Problem ist in der neuen Version 0.20.1 behoben. Zur Sicherheit empfehle ich dir, den betroffenen Datenpunkt vor dem Start der neuen Version einmal händisch im ioBroker zu löschen, auch wenn der Wert sich normalerweise automatisch korrigieren sollte.

[TbsJah]

0.20.1 (2026-10-22)

🐛 Bugfixes & Tweaks

• Modbus Factor Correction: Explicitly set the scaling factor for the heating target temperature offset (Luxtronik ID 1 / Holding 23) to 10 to correctly handle and display Modbus TCP values in tenths of a degree (e.g., 5.0 °C instead of 50).
• Configuration UI: Clarified the English and German labels for heating parameters (such as base point and parallel offset) in the adapter settings to prevent mapping confusion.

[TbsJah]

0.20.4 (2026-10-24)

🔧 Maintenance & Compatibility

• Repository Checker Fixes: Addressed multiple warnings from the ioBroker repository checker.
• Node.js Requirement: Updated minimum Node.js requirement to >= 22 in package.json and io-package.json to meet current adapter standards.
• UI Layout: Added missing responsive size attributes (xs, sm, md, lg, xl) to elements in the new updates configuration tab.
• Translations: Added missing i18n translations for all supported languages in the configuration dropdown menus (COP sources and ZIP control mode).
• Metadata: Removed non-existent version entries from the news section in io-package.json.

✨ Features & Enhancements

• Notification Center: Introduced a dedicated notification category (lwpSystem) for firmware updates and system info to cleanly separate them from critical heat pump errors in the ioBroker UI.

[TbsJah]

0.21.0 (2026-10-24)

🚀 New Features

• PV Surplus Management (PV-Ready): Introduced a fully integrated, automated PV surplus control system.
• PV Hysteresis Control: Added a dedicated stop threshold (pv_threshold_stop) to the PV surplus manager. This prevents the heat pump from cancelling its own boost cycle by consuming the solar surplus (feedback loop). The system now supports independent start and stop boundaries (Schmitt trigger logic).
• Dynamic Setpoint Boost: Automatically raises hot water and heating setpoints (wear-free via Modbus RAM) based on your current grid feed-in.
• Smart Timers: Includes customizable start and stop delay timers to prevent compressor short-cycling during variable cloud cover.
• Cycle Protection: Added a "finish cycle" safety feature. If the solar surplus drops, the adapter intelligently waits for an active heating or hot water cycle to finish before reverting the setpoints, protecting the compressor hardware.
• PV Telemetry: Added three new virtual datapoints under Information.17_PV_Surplus (pv_boost_active, pv_boost_active_since, and pv_boost_last_activation) to make the current surplus control status transparently available for external ioBroker visualizations.
• Battery Prioritization (PV): Added an optional feature to include your home battery's charging power into the PV surplus calculation. This allows you to treat the heat pump as the primary thermal battery, intercepting the solar power to heat up the house or hot water before it flows into your chemical battery.

🐛 Bugfixes & Tweaks

• Cycle Optimization vs. PV Logic: Fixed an edge-case bug where a temporary high target temperature from the cycle optimization module leaked into the PV surplus manager if the heat pump skipped the standby/idle state. The adapter now explicitly resets cross-cycle targets and forces the PV manager to reference the secure baseline configuration limits.
• Modbus Stability: Fixed a critical race condition in the Modbus manager. Concurrent read and write operations no longer share a single global client, preventing connection collisions and adapter crashes during hybrid mode operations.
• API Modernization: Replaced deprecated setStateAsync calls in the PV manager with the modern Promise-based setState API to comply with the latest ioBroker adapter guidelines and resolve TypeScript warnings.
• Unit Conversion: The PV feed-in datapoint now natively supports kilowatts (kW) via a new toggle in the configuration UI, automatically converting it to Watts internally.
• Admin UI Polish: Replaced HTML-based information blocks in the configuration UI with native ioBroker JSON components to bypass React XSS-filtering issues and ensure clean rendering.

[TbsJah]

0.21.1 (2026-10-24)

🐛 Bugfixes & Tweaks

• PV Manager Target & Offset Fixes: Fixed remaining references to the read-only Wamwassertemperatur_Soll datapoint in activateBoost and deactivateBoost (now consistently targeting temperature_hot_water_target). Resolved a baseline mix-up where fusspunkt was mistakenly applied to the parallel offset (heating_temperature), and fixed the heating saturation check (isHzFull) to compare actual return temperature against target return + hysteresis without prematurely revoking active boosts.
• Cycle Optimization & Heating Limit: Replaced the language-dependent 'Heating limit' string check during idle with a reliable numerical evaluation of the heating limit parameters. Added a !pvIsBoostActive guard to prevent forced hot water triggers from overwriting active solar boosts, and included a baseline reset (0 K) for heating_temperature in setIdleDefaults.
• ZIP Controller Timer Fix: Fixed a bug in zipManager (internal controller mode) where hot water timer slots (WW_MoSo_...) were backed up and overwritten instead of the circulation pump timer slots (Zirkulation_MoSo_...), and improved time string restoration.
• COP Calculation Accuracy: Fixed a UTC timezone offset in the daily rollover check so COP snapshots occur accurately at local midnight (00:00). Included defrosting cycles (WP_BZ_akt = 4) in the heating COP bucket and added clamping against negative deltas if external energy meters are reset.
• Object Management & Virtual States: Removed a redundant loop in onReady that recreated disabled virtual datapoints on startup, and fixed PREFIX_MAPPING for weekend timer tables (SaSo) to properly reference the 52SatSun configuration flags.

[TbsJah]

0.22.0 (2026-10-24)

🐛 Performance & Tweaks

• Modbus Queue & Socket Protection: Added a sequential operation queue (mutex) with a 50ms socket release delay in ModbusManager to prevent TCP port 502 connection collisions when polling and event-driven writes occur simultaneously.
• COP Database Optimization: Added an in-memory object cache (ensuredObjects) to copManager, eliminating redundant setObjectNotExistsAsync database calls during every polling cycle.
• DTA Backup & Firmware Check Improvements: Added a 30-second request timeout (AbortSignal.timeout) and proper dta_history file naming on fallback to backupManager, and expanded the version regex in updateManager to support F1., WWB, and smo firmware strings.

[TbsJah]

Hallo zusammen,

nach den umfangreichen Updates der letzten Zeit (PV-Steuerung, Hybrid-Modus, Takt-Optimierung) ist erst einmal ein Feature-Freeze: Es sind aktuell keine neuen Features geplant.

Mein Fokus liegt jetzt zu 100 % auf Fehlerbereinigung und Stabilität, um den Adapter zeitnah ins offizielle Stable-Repository von ioBroker zu bringen.

Testet den aktuellen Stand gerne ausgiebig! Anmerkungen, Anregungen oder auch einfach kurze "Läuft fehlerfrei"-Rückmeldungen sind jederzeit herzlich willkommen.

Jedes Feedback hilft uns enorm auf dem Weg zum Stable-Release.

Danke für euren fantastischen Support und das fleißige Testen!

[TbsJah]

0.22.6 (2026-11-06)

🐛 Bugfixes

• Cycle Optimization & Hardware Sync (main.ts):
  • Pre-Heating & Heating Limit Type Fix: Fixed strict type comparison bugs (boolean vs. number) when evaluating heatingLimit and VD1out (vd1). Previously, boolean state values caused isHeatingAllowedByLimit and vd1 to evaluate to false, which blocked pre-heating before hot water generation (raising heating_curve_parallel_offset to 35 °C), prevented the 10-minute base point reset, and skipped HUP voltage optimization.
  • Raw Data Fallbacks (rawValues / rawParams): Added direct fallbacks to raw heat pump telemetry and parameter arrays in runOptimizationSchedule so cycle optimization, HUP control, and heating limit checks remain fully functional even if individual datapoints (thresholdHeatingLimit, Mitteltemperatur, heatingLimit, VD1out, etc.) are disabled in the ioBroker object tree.
  • Hardware Out-of-Sync Verification: Enhanced syncConfigValue to verify target values against the live hardware parameter cache (currentRawParams), ensuring parameters are reliably written to the controller even if the local ioBroker state is disabled or out of sync with the heat pump.

0.22.5 (2026-11-06)

🔧 Maintenance & Compatibility

• Repository Compliance: Added missing multi-language translations (i18n) for all configuration dropdown menus (e.g. COP sources, PV modes) to meet strict ioBroker stable repository requirements.

0.22.4 (2026-11-06)

🐛 Bugfixes & Tweaks

• PV Surplus Management (pvManager.ts):
  • Cycle Completion & Reset Deadlock: Fixed a critical bug in initiateDeactivation when pv_finish_cycle was enabled: the inactive operating mode (e.g., hot water while heating is running) is now immediately reset to baseline[cite: 26, 28, 29]. This prevents infinite cycle loops where cycle optimization erroneously triggered forced 60 °C hot water runs at the end of a heating cycle[cite: 25, 28].
  • Target Reset vs. PV Max: Corrected cycle completion behavior so active compressor runs finish at normal baseline setpoints instead of continuing to heat to elevated PV boost targets with grid/battery power[cite: 26, 28, 29]. Added a dynamic timer to enforce the 10-minute minimum compressor run time before final reset[cite: 26].
  • Hysteresis Deadband & Timer Protection: Prevented the deactivation timer (pvStopTimer) from being aborted by minor meter/battery balancing fluctuations in the deadband between the stop threshold and start threshold[cite: 26, 27, 29].
  • Startup Recovery: Added baseline recovery during initPvManagement to clear orphaned boost targets left behind after an adapter update or reboot.
  • Input Parsing: Added parseConfigFloat to safely parse decimal values formatted with commas (e.g., "1,5") in the admin configuration[cite: 26, 29].
  • Direct Hardware Sync: Switched state updates to syncConfigValue for immediate, queue-safe synchronization via native TCP and Modbus[cite: 25, 26].

0.22.3 (2026-11-06)

• Notifications & Alarming:
  • Fixed an initialization bug where lastKnownErrorTimestamp and lastKnownOutageTimestamp were not set on adapter startup if the history remained unchanged, which previously caused the first genuine error or outage after a restart to be silently ignored.
  • Decoupled the 60-minute flow warning cooldown (lastFlowNotificationTime) from critical heat pump malfunctions so genuine fault alarms are never suppressed by preceding flow warnings.
  • Added language-independent outage code detection (codes 0, 1, 11, 18) alongside text-based fallbacks.
• ZIP Circulation Control:
  • Added a raw parameter fallback (currentRawParams) when backing up originalZipConfig to prevent timer schedules from being overwritten with null if the corresponding timer states are disabled in the object tree.
  • Fixed an issue in stopZipAndDeaeration where manually disabling Activate_Zip did not stop the hardware deaeration program (runDeaerate) by checking Virtual_ZIP_Status in addition to the trigger state.
• Stability & Helpers:
  • Wrapped the automated DTA backup cron job initialization (initAutoBackup) in a try/catch block to prevent startup crashes on malformed cron expressions.
  • Hardened safeClose in ModbusManager to cleanly terminate sockets even if a connection timeout occurs before the socket is marked as open.
  • Improved input validation in formatTimerSecondsToTime (guarding against negative values and NaN) and getNumber (supporting numeric strings).

0.22.2 (2026-11-06)

🐛 Bugfixes & Tweaks

• Cycle Optimization & PV Integration: Fixed an issue where the cycle optimization was blocked during an active PV boost. The adapter now correctly forces seamless transitions between heating and hot water (without compressor shutdown and anti-cycle delays) even when solar surplus is available. A new handshake mechanism ensures that PV target temperatures are immediately and safely restored after the cycle optimization resets the baseline idle defaults.

• PV Surplus Management & Compressor Optimization:

  • Fixed read-only datapoint errors in activateBoost and deactivateBoost (now correctly targeting temperature_hot_water_target).
  • Resolved baseline configuration mix-ups between fusspunkt and the heating parallel offset (heating_temperature).
  • Fixed the heating saturation check (isHzFull) to prevent premature boost revocation.
  • Implemented a seamless "PV-Boost Handshake" allowing cycle optimization to force hot water transitions even during active solar surplus without triggering anti-cycle compressor delays.

• ZIP Circulation & Timer Logic:

  • Fixed a bug where hot water timer slots (WW_MoSo_...) were mistakenly backed up and overwritten instead of circulation pump slots (Zirkulation_MoSo_...).
  • Improved time string conversions and state restoration robustness.

• COP Calculation & Virtual States:

  • Fixed a UTC timezone offset in daily rollovers so COP snapshots trigger precisely at local midnight.
  • Included defrosting cycles (WP_BZ_akt = 4) into the heating COP calculations and added clamping protection against negative energy deltas.
  • Added an in-memory object cache (ensuredObjects) to drastically reduce redundant database write calls.
  • Added a raw value fallback for total energy and thermal energy calculations if individual states are disabled in the object tree.

• Modbus & Raw Communication Stability:

  • Implemented a strict serial operation queue (mutex) with a 50ms release delay in ModbusManager to prevent TCP port 502 connection collisions.
  • Added a 30-second request timeout (AbortSignal.timeout) to DTA backups and corrected file naming for fallback paths (dta_history).
  • Expanded firmware version regex in updateManager to support F1., WWB, and smo firmware formats.
  • Added socket close event listeners and safe number roundings for raw write operations.

• Repository Compliance & Maintenance:

  • Added complete multi-language translations (i18n) for all configuration dropdown menus to meet strict ioBroker stable repository requirements.

  • Cleaned up unpublished ghost versions from the io-package.json news section.

  • Standardized the README changelog header format (## Changelog).

  • Repository Compliance: Added missing multi-language translations (i18n) for all configuration dropdown menus (e.g. COP sources, PV modes) to meet strict ioBroker stable repository requirements.

0.22.1 (2026-11-06)

🐛 Bugfixes & Tweaks

• PV Manager Target & Offset Fixes: Fixed remaining references to the read-only Wamwassertemperatur_Soll datapoint in activateBoost and deactivateBoost (now consistently targeting temperature_hot_water_target). Resolved a baseline mix-up where fusspunkt was mistakenly applied to the parallel offset (heating_temperature), and fixed the heating saturation check (isHzFull) to compare actual return temperature against target return + hysteresis without prematurely revoking active boosts.
• Cycle Optimization & Heating Limit: Replaced the language-dependent 'Heating limit' string check during idle with a reliable numerical evaluation of the heating limit parameters. Added a !pvIsBoostActive guard to prevent forced hot water triggers from overwriting active solar boosts, and included a baseline reset (0 K) for heating_temperature in setIdleDefaults.
• ZIP Controller Timer Fix: Fixed a bug in zipManager (internal controller mode) where hot water timer slots (WW_MoSo_...) were backed up and overwritten instead of the circulation pump timer slots (Zirkulation_MoSo_...), and improved time string restoration.
• COP Calculation Accuracy: Fixed a UTC timezone offset in the daily rollover check so COP snapshots occur accurately at local midnight (00:00). Included defrosting cycles (WP_BZ_akt = 4) in the heating COP bucket and added clamping against negative deltas if external energy meters are reset.
• Object Management & Virtual States: Removed a redundant loop in onReady that recreated disabled virtual datapoints on startup, and fixed PREFIX_MAPPING for weekend timer tables (SaSo) to properly reference the 52SatSun configuration flags.

0.22.0 (2026-11-06)

🐛 Performance & Tweaks

• Modbus Queue & Socket Protection: Added a sequential operation queue (mutex) with a 50ms socket release delay in ModbusManager to prevent TCP port 502 connection collisions when polling and event-driven writes occur simultaneously.
• COP Database Optimization: Added an in-memory object cache (ensuredObjects) to copManager, eliminating redundant setObjectNotExistsAsync database calls during every polling cycle.
• DTA Backup & Firmware Check Improvements: Added a 30-second request timeout (AbortSignal.timeout) and proper dta_history file naming on fallback to backupManager, and expanded the version regex in updateManager to support F1., WWB, and smo firmware strings.

[TbsJah]

Tolles Projekt von @obermolch
Link

Interessant wenn kein LAN Kabel zur Verfügung steht