NEWS
Test Luxtronik2-Controller V0.22.x
-
-
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 InfoErklärung
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
-
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.jsonwhere 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, andnode-gypcompilation 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-controllerdependency to>=7.0.7inio-package.jsonto 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 injsonConfig.json(resolves W5611). - Package News Cleanup: Removed unreleased intermediate tags (
0.17.0,0.16.1) fromcommon.newsinio-package.jsonto 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_targetexecution 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.
- Hybrid Modbus TCP Support: Introduced hybrid Modbus TCP support (
-
Jetzt passt auch wieder die Dokumentation zu dem Stand
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.90crash shield. - Troubleshooting & ARM Compatibility: Added troubleshooting documentation regarding harmless
node-gyp/serialport/usocketcompilation warnings on Raspberry Pi / ARM systems, alongside step-by-step guidance for running the raw TCP diagnostic script (Test_Script.ts).
- Complete Alignment of Documentation (
-
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, andfirmware_changelogto the system info tree to directly expose update states and release notes in ioBroker. - Manual Trigger Button: Added a
check_firmwarebutton 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" }independenciesinio-package.json. T
0.19.2 (2026-10-20)
🔧 Compatibility & Maintenance
- Broader Node.js Compatibility: Adjusted Node.js engine requirement from
>=22down to>=18.0.0inpackage.jsonand added{ "node": ">=18.0.0" }todependenciesinio-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.
-
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!


-
-
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, andfirmware_changelogto the system info tree to directly expose update states and release notes in ioBroker. - Manual Trigger Button: Added a
check_firmwarebutton 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" }independenciesinio-package.json. T
0.19.2 (2026-10-20)
🔧 Compatibility & Maintenance
- Broader Node.js Compatibility: Adjusted Node.js engine requirement from
>=22down to>=18.0.0inpackage.jsonand added{ "node": ">=18.0.0" }todependenciesinio-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.
-
uxtronik2-controller.0.Settings.02_Heating.heating_temperature
ist der Wert anstatt z.B. 5 C jetzt 50 CDu 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.
-
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
10to 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.
- Modbus Factor Correction: Explicitly set the scaling factor for the heating target temperature offset (Luxtronik ID 1 / Holding 23) to
-
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
>= 22inpackage.jsonandio-package.jsonto 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
newssection inio-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.
-
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, andpv_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
setStateAsynccalls in the PV manager with the modern Promise-basedsetStateAPI 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.
-
0.21.1 (2026-10-24)
🐛 Bugfixes & Tweaks
- PV Manager Target & Offset Fixes: Fixed remaining references to the read-only
Wamwassertemperatur_Solldatapoint inactivateBoostanddeactivateBoost(now consistently targetingtemperature_hot_water_target). Resolved a baseline mix-up wherefusspunktwas 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!pvIsBoostActiveguard to prevent forced hot water triggers from overwriting active solar boosts, and included a baseline reset (0 K) forheating_temperatureinsetIdleDefaults. - 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
onReadythat recreated disabled virtual datapoints on startup, and fixedPREFIX_MAPPINGfor weekend timer tables (SaSo) to properly reference the52SatSunconfiguration flags.
- PV Manager Target & Offset Fixes: Fixed remaining references to the read-only
-
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
ModbusManagerto prevent TCP port 502 connection collisions when polling and event-driven writes occur simultaneously. - COP Database Optimization: Added an in-memory object cache (
ensuredObjects) tocopManager, eliminating redundantsetObjectNotExistsAsyncdatabase calls during every polling cycle. - DTA Backup & Firmware Check Improvements: Added a 30-second request timeout (
AbortSignal.timeout) and properdta_historyfile naming on fallback tobackupManager, and expanded the version regex inupdateManagerto supportF1.,WWB, andsmofirmware strings.
- Modbus Queue & Socket Protection: Added a sequential operation queue (mutex) with a 50ms socket release delay in
-
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!
-
0.22.6 (2026-11-06)
🐛 Bugfixes
- Cycle Optimization & Hardware Sync (
main.ts):- Pre-Heating & Heating Limit Type Fix: Fixed strict type comparison bugs (
booleanvs.number) when evaluatingheatingLimitandVD1out(vd1). Previously, boolean state values causedisHeatingAllowedByLimitandvd1to evaluate tofalse, which blocked pre-heating before hot water generation (raisingheating_curve_parallel_offsetto 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 inrunOptimizationScheduleso 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
syncConfigValueto 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.
- Pre-Heating & Heating Limit Type Fix: Fixed strict type comparison bugs (
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
initiateDeactivationwhenpv_finish_cyclewas 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
initPvManagementto clear orphaned boost targets left behind after an adapter update or reboot. - Input Parsing: Added
parseConfigFloatto 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
syncConfigValuefor immediate, queue-safe synchronization via native TCP and Modbus[cite: 25, 26].
- Cycle Completion & Reset Deadlock: Fixed a critical bug in
0.22.3 (2026-11-06)
- Notifications & Alarming:
- Fixed an initialization bug where
lastKnownErrorTimestampandlastKnownOutageTimestampwere 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.
- Fixed an initialization bug where
- ZIP Circulation Control:
- Added a raw parameter fallback (
currentRawParams) when backing uporiginalZipConfigto prevent timer schedules from being overwritten withnullif the corresponding timer states are disabled in the object tree. - Fixed an issue in
stopZipAndDeaerationwhere manually disablingActivate_Zipdid not stop the hardware deaeration program (runDeaerate) by checkingVirtual_ZIP_Statusin addition to the trigger state.
- Added a raw parameter fallback (
- Stability & Helpers:
- Wrapped the automated DTA backup cron job initialization (
initAutoBackup) in atry/catchblock to prevent startup crashes on malformed cron expressions. - Hardened
safeCloseinModbusManagerto 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 andNaN) andgetNumber(supporting numeric strings).
- Wrapped the automated DTA backup cron job initialization (
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
activateBoostanddeactivateBoost(now correctly targetingtemperature_hot_water_target). - Resolved baseline configuration mix-ups between
fusspunktand 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.
- Fixed read-only datapoint errors in
-
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.
- Fixed a bug where hot water timer slots (
-
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
ModbusManagerto 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
updateManagerto supportF1.,WWB, andsmofirmware formats. - Added socket
closeevent listeners and safe number roundings for raw write operations.
- Implemented a strict serial operation queue (mutex) with a 50ms release delay in
-
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.jsonnews 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_Solldatapoint inactivateBoostanddeactivateBoost(now consistently targetingtemperature_hot_water_target). Resolved a baseline mix-up wherefusspunktwas 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!pvIsBoostActiveguard to prevent forced hot water triggers from overwriting active solar boosts, and included a baseline reset (0 K) forheating_temperatureinsetIdleDefaults. - 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
onReadythat recreated disabled virtual datapoints on startup, and fixedPREFIX_MAPPINGfor weekend timer tables (SaSo) to properly reference the52SatSunconfiguration 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
ModbusManagerto prevent TCP port 502 connection collisions when polling and event-driven writes occur simultaneously. - COP Database Optimization: Added an in-memory object cache (
ensuredObjects) tocopManager, eliminating redundantsetObjectNotExistsAsyncdatabase calls during every polling cycle. - DTA Backup & Firmware Check Improvements: Added a 30-second request timeout (
AbortSignal.timeout) and properdta_historyfile naming on fallback tobackupManager, and expanded the version regex inupdateManagerto supportF1.,WWB, andsmofirmware strings.
- Cycle Optimization & Hardware Sync (
-
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden

