Releases: davidusb-geek/emhass-add-on
EMHASS add-on v0.11.1
Fix
- Fix parameter saving and duplicate battery bugs
- utils.py add more specific logging information for config
- Fix issue where thermal runtime parameters were not being propagated into optim_conf
What's Changed
Full Changelog: v0.11.0...v0.11.1
EMHASS add-on v0.11.0
This version marks huge improvement works by @GeoDerp aiming to simplfy the intial and normal setup of EMHASS. The workflow for setting the EMHASS configuration regardless of the installation method has now been centralized on the single config.json file. The webserver has now a configuration tab that can be used to to modify and save the config.json file.
The complete discussion of the changes on this thread:
davidusb-geek/emhass#334
Automatic version bot improvements
- Bump h5py from 3.11.0 to 3.12.1
- Bump markupsafe from 2.1.5 to 3.0.2
What's Changed
Full Changelog: v0.10.6...v0.11.0
EMHASS add-on v0.10.6
Fix
- Fixed bug on predicted room temeprature publish, wrong key on DataFrame
Full Changelog: v0.10.5...v0.10.6
EMHASS add-on v0.10.5
Improvement
- Added support for pubishing thermal load data, namely the predicted room temperature
Full Changelog: v0.10.4...v0.10.5
EMHASS add-on v0.10.4
In this release a new thermal modeling for deferrable loads.
Thanks to @werdnum for this contribution!
Improvement
- Added a new thermal modeling, see the new section in the documentation for help to implement this of model for thermal deferrable loads
- Improved documentation
Full Changelog: v0.10.3...v0.10.4
EMHASS add-on v0.10.3
Some minor improvements:
Improvement
- Added improved support for
def_start_penaltyoption - Improved documentation
What's Changed
- Davidusb geek/dev/preparing new version by @davidusb-geek in #97
- en.yaml add description for list_set_deferrable_startup_penalty by @GeoDerp in #98
Full Changelog: v0.10.2...v0.10.3
EMHASS add-on v0.10.2
In this release:
Improvement
- Weather forecast caching and Solcast method fix by @GeoDerp
- Added a new configuration parameter to control wether we compute PV curtailment or not
- Added hybrid inverter to data publish
- It is now possible to pass these battery parameters at runtime:
SOCmin,SOCmax,Pd_maxandPc_max
Fix
- Fixed problem with negative PV forecast values in optimization.py, by @GeoDerp
Full Changelog: v0.10.1...v0.10.2
EMHASS add-on v0.10.1
Fix
- Fixed PV curtailment maximum possible value constraint
- Added PV curtailement to variable to publish to HA
Full Changelog: v0.10.0...v0.10.1
EMHASS add-on v0.10.0
BREAKING CHANGE
- In this new version we have added support for PV curtailment computation. While doing this the nominal PV peak power is needed. The easiest way find this information is by directly using the
inverter_modeldefined in the configuration. As this is needed in the optimization to correctly compute PV curtailment, this parameter need to be properly defined for your installation. Before this chage this parameter was only needed if using the PV forecast methodscrapper, but now it is not optional as it is directly used in the optimization.
Use the dedicated webapp to find the correct model for your inverter, if you cannot find your exact brand/model then just pick an inverter with the same nominal power as yours: https://emhass-pvlib-database.streamlit.app/
Improvement
- Added support for hybrid inverters and PV curtailment computation
- Implemented a new
continual_publishservice that avoid the need of setting a special automation for data publish. Thanks to @GeoDerp - Implement a deferrable load start penalty functionality. Thanks to @werdnum
- This feature also implement a
def_current_statethat can be passed at runtime to let the optimization consider that a deferrable load is currently scheduled or under operation when launching the optimization task
- This feature also implement a
Fix
- Fixed forecast methods to treat delta_forecast higher than 1 day
- Fixed solar.forecast wrong interpolation of nan values
Full Changelog: v0.9.1...v0.10.0
EMHASS add-on v0.9.1
Fix
- Fix patch for issue with paths to modules and inverters database
- Fixed code formatting, or at least trying to keep a unique format
Full Changelog: v0.9.0...v0.9.1