13bc943dd5
this changeset refactors the web application's DPL settings view. the DPL settings can be complex, and they shall be presented in a way that allows users to comprehend their meaning. irrelevant settings are now hidden or displayed dynamically based on the influencing settings. * group SoC thresholds into their own card * hide battery SoC thresholds if battery disabled. if the user did not even enable the battery interface, battery SoC values will not be used for DPL decisions. in that case we completely hide the respective settings from the DPL admin view. this reduces the amount of settings for new users and especially users who don't even have a battery in their setup or have no BMS connected. * group voltage thresholds and improve label texts * fix load correction factor unit * fix header (wording) * group solar-passthrough settings in new card * group inverter-related settings * hide solar passthrough settings if VE.Direct is disabled. closes #662. * completely disable form if any requirement is not met * list available inverters by name and type. this makes it much more convenient to select the right inverter, especially since the order of the inverters in the web UI is decoupled from their position in the internal array, which was used to select them previously. care was taken that old configs select the same inverter after an update. when editing the DPL settings, the selects an inverter from the newly created drow-down list, and the respective old inverter is pre-selected. * disable form if no inverter is configured (config alert) * make inverter input selection dynamic. adjust selection to actual amount of channels for selected inverter. skip selection altogether if inverter has only one channel, or if it is solar powered. * web app: wording adjustments * group meta data into new property and exclude from submission. saves memory when evaluating the submitted settings. * hide irrelevant settings if inverter is solar-powered * move restart hour setting to inverter card. translate setting which disabled automatic restart. * simplify "drain strategy" setting into an on/off toggle. care was taken that existing configs work the same after an upgrade. the respective drain strategy is translated into the new setting when reading the config. once the config is written, the new setting is persisted and the old is not part of the config any more. * show more configuration hints, depending on actual configuration * replace inputs by InputElement components where possible |
||
|---|---|---|
| .github | ||
| .vscode | ||
| docs | ||
| include | ||
| lib | ||
| patches/esp32c3 | ||
| pio-scripts | ||
| src | ||
| test | ||
| webapp | ||
| webapp_dist | ||
| .DS_Store | ||
| .editorconfig | ||
| .gitignore | ||
| COPYING | ||
| LICENSE | ||
| partitions_custom_4mb.csv | ||
| partitions_custom_16mb.csv | ||
| platformio_override.ini | ||
| platformio.ini | ||
| README_onBattery.md | ||
| README.md | ||
OpenDTU-onBattery
This is a fork from the Hoymiles project OpenDTU.
What is OpenDTU-onBattery
OpenDTU-onBattery is an extension of the original OpenDTU to support battery chargers, battery management systems (BMS) and power meters on a single esp32. With the help of a dynamic power limiter, the power production can be adjusted to the actual consumption. In this way, it is possible to come as close as possible to the goal of zero feed-in.
History of the project
The original OpenDTU project was started from this discussion (Mikrocontroller.net). It was the goal to replace the original Hoymiles DTU (Telemetry Gateway) with their cloud access. With a lot of reverse engineering the Hoymiles protocol was decrypted and analyzed.
Summer 2022 I bought my Victron MPPT battery charger, and didn't like the idea to set up a separate esp32 to recieve the charger data. I decided to fork OpenDTU and extend it with battery charger support and a dynamic power limitter to my own needs. Hoping someone can make use of it.
Highlights of OpenDTU-onBattery
This project is still under development and adds following features:
Warning
In contrast to the original openDTU, with release 2023.05.23.post1 openDTU-onBattery supports only 5 inverters. Otherwise, there is not enough memory for the liveData view.
- Support Victron's Ve.Direct protocol on the same chip (cable based serial interface!). Additional information about Ve.direct can be downloaded directly from Victron's website.
- Dynamically sets the Hoymiles power limited according to the currently used energy in the household. Needs an HTTP JSON based power meter (e.g. Tasmota), an MQTT based power meter like Shelly 3EM or an SDM power meter.
- Battery support: Read the voltage from Victron MPPT charge controller or from the Hoymiles DC inputs and starts/stops the power producing based on configurable voltage thresholds
- Voltage correction that takes the voltage drop because of the current output load into account (not 100% reliable calculation)
- Can read the current solar panel power from the Victron MPPT and adjust the limiter accordingly to not save energy in the battery (for increased system efficiency). Increases the battery lifespan and reduces energy loses.
- Settings can be configured in the UI
- Pylontech Battery support (via CAN bus interface). Use the SOC for starting/stopping the power output and provide the battery data via MQTT (autodiscovery for home assistant is currently not supported). Pin Mapping is supported (default RX PIN 27, TX PIN 26). Actual no live view support for Pylontech Battery.
- Huawei R4850G2 power supply unit that can act as AC charger. Supports status shown on the web interface and options to set voltage and current limits on the web interface and via MQTT. Connection is done using CAN bus (needs to be separate from Pylontech CAN bus) via SN65HVD230 interface.
Documentation
Full documentation of OpenDTU-onBattery extensions can be found at the project's wiki.
For documentation of openDTU core functionality I refer to the original repo and its documentation.
Please note that openDTU-onBattery may change significantly during its development. Bug reports, comments, feature requests and fixes are most welcome!
To find out what's new or improved have a look at the changelog.
Acknowledgment
A special Thank to Thomas Basler (tbnobody) the author of the original OpenDTU project. You are doing a great job!
Last but not least, I would like to thank all the contributors. With your ideas and enhancements, you have made OpenDTU-onBattery much more than I originally had in mind.