Open
Conversation
Changelog: Homewizard app setting page with log or debug information for discovery, fetch failures, websocket problems and baseload samples
Changelog: Bugfix: Homewizard.poll (legacy unit)
Changelog: Homewizard Preset addition, Heatlink control improvement, Gasmeter fix (external source)
Changelog: Thermometer trigger and condition cards for no response X hours.
Changelog: Improvement fetchQueue (protect against high cpu warning for devices on 1s polling)
Changelog: fetchQueue method dropped, using fetch directly so debug information can be shown in app settings tabs
Changelog: Watermeter daily usage added, Bugfix: Device Fetch Debug wasn't updating
Changelog: Bugfix: Circular Reference device
Changelog: Bugfix: SDM230(p1mode) - updateCapability missed
Changelog: Another Circular Reference device error fix
Changelog: Removed all retry/timeout code for fetch as it seems to lock up devices
Changelog: Cleanup device drivers with overcomplicated checks that ended up with polling deadlocks
Changelog: SDM230(p1mode) - Extra code handling for TIMEOUT issues
Changelog: SDM630 added per phase kwh meter tracking + daily kwh meter (estimate)
Changelog: More gas fix reset at night time (apiv1 and apiv2)
Changelog: Bugfix: incorrect daily reset during day of gas usage
Changelog: Cleanup first_run_logged key
Changelog: Bugfix: Energylink (watermeter) and Thermometer (battery)
Changelog: Plugin battery fetch connection pool fix, energy-socket pairing fallback + timeout and watermeter fix.
…imeout and energy_socket pairing fixes object object (fallback to product type and serialnumber)
Changelog: Crash hunting added logging
Changelog: http agent adjustment
Changelog: Bug hunting
Changelog: Pairing sockets limited to 4 concurrent additions
Changelog: Only 2 connections allowed at pairing
Changelog: Ignore already paired devices
Changelog: Battery policy improvements, Soc projection, Solar yield learning, Weekend/weekday consumption patterns, consumption awareness, battery cycle costs
Changelog: Bugfix planning grid charging while solar is forecasted later
Changelog: Baseload fix with plugin batteries that zero the overall usage, watts should be seen as baseload
…mp added last update
…ice that was temporarily unreachable (EHOSTUNREACH).
1. Lazy‑loading the ExplainabilityEngine The ExplainabilityEngine is no longer initialized at startup. Its require() and constructor call have been moved to the first invocation of _runPolicyCheck() (typically ~15 minutes after startup). This removes ~1049 lines of bytecode from the startup path and reduces peak heap usage during boot. 2. Lazy‑loading the BatteryChartGenerator The BatteryChartGenerator (which normally returns null via a stub) is now also loaded only when its chart method is actually called. This avoids unnecessary initialization work during startup. 3. Race condition fix in MergedPriceProvider The constructor now correctly waits for _loadCache() via _cacheLoadPromise. As a result, after a crash restart (< 1 hour), cached prices are reliably used instead of refetching Xadi + KwhPrice. This prevents two concurrent API calls and avoids redundant JSON parsing during startup. 4. PV predictions limit reduced from 1000 → 300 Only the last 100 entries are used by getPvAdjustmentMultiplier()
Changelog: Baseload fix with plugin battery and heap memory fix at startup, processes postponed for later use rather all update upon starting app
Changelog: Extra logging baseload detection with batteries
Changelog: Tuned log rules to only night summary
Changelog: Baseload fix for energy_v2 (notification tag added), PV Graph planning adjusted, added green line with actual Watts production vs estimate
Changelog: Baseload fix (oscillation), Changed city looking for weather to long lat method instead
Changelog: Cheap tariff fix when battery is not full but pv cant cover it
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since this year it is possible to get the information of a growat sun system to homewizard app it self. But could it be to get the data in the homewizard app of homey. In homewizard you need a plus account.