Conversation
Neu kann auch für Acthor und andere der Zu meldende Überschuss im Manuellen Modus übergeben werden. Alle möglichen MQTT Topics sind im mqtt modul besschrieben: Generisches MQTT modul Wenn Einschaltbedingung erreicht (Beispiel hier mit Device 2) openWB/LegacySmartHome/Devices/2/ReqRelay = 1 openWB/LegacySmartHome/Devices/2/Ueberschuss = in Watt Wenn Ausschaltbedingung erreicht openWB/LegacySmartHome/Devices/2/ReqRelay = 0 openWB/LegacySmartHome/Devices/2/Ueberschuss = in Watt ReqRelay gibt den Status vom Gerät aus Sicht openWb an (1 = eingeschaltet, 0 = ausgeschaltet) Bei der periodischen Abfrage wird die aktuelle Leistung openWB/set/LegacySmartHome/Devices/2/Aktpower = in Watt erwartet openWB/set/LegacySmartHome/Devices/2/Tempa = Temperatur in C mit max 2 Nachkommastellen openWB/set/LegacySmartHome/Devices/2/Tempb = Temperatur in C mit max 2 Nachkommastellen openWB/set/LegacySmartHome/Devices/2/Tempc = Temperatur in C mit max 2 Nachkommastellen und der aktuelle Zähler in Wattstunden wird hier erwartet openWB/set/LegacySmartHome/Devices/2/Powerc wenn kein Zähler übergeben oder 0 übergeben wird, wird der Zähler selber gerechnet openWB/set/LegacySmartHome/Devices/2/Ueberschuss = in Watt alle Geräte (nicht nur MQTT) können bezüglich manuell / automatisch von extern gesteuert werden. openWB/set/LegacySmartHome/config/set/Devices/2/mode Mode steuert das Gerät (1 = manueller Modus, 0 = automatischer Modus) openWB/set/LegacySmartHome/config/set/Devices/2/device_manual_control device_manual_control steuert das Ferät im manuellen Modus (1 = ein, 0 = aus) openWB/set/LegacySmartHome/config/set/Devices/2/manueb = vorgebener Überschuss in Watt ohne Nachkommastellen Dieser Wert wird wenn das Gerät auf Manueller Modus und ein geschaltet ist, als Überschuss an das jeweilige Gerät übergeben. (nur relevant für Acthor, Elwa, IDM, Lambda die mit überschuss gesteuert werden)
* thread handler: don't start multiple thread instances * logging * review: log message only if the thread was really started
* DC charging * fix test * fix max current * fix rebase * DC charging * draft * draft * fixes * naming * update config * fix test * fix test * undo * fix update config * fix * remove old code
* DC charging * fix test * fix max current * fix rebase * DC charging * draft * draft * fixes * naming * update config * fix test * fix test * undo * fix update config * fix * remove old code * fix configuration.json
* fix consider less charging * fix test
Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.9.4 to 3.10.2. - [Release notes](https://github.com/aio-libs/aiohttp/releases) - [Changelog](https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst) - [Commits](aio-libs/aiohttp@v3.9.4...v3.10.2) --- updated-dependencies: - dependency-name: aiohttp dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* rename Sdm630 to Sdm630_72 * naming soc for vehicle * feed in limit in message * unneeded log message removed
* error timestamp for pro, external, satelllit and smartwb * fix rebase * fix pytest
settings build
usage of ip instead ifconfig in setup_network.sh
remove deprecated ifconfig calls
* fix surplus charging for pv charging - submode instant charging * amend
* rename * handle not installed python packages * improve message
* add growatt * Apply suggestions from code review --------- Co-authored-by: LKuemmel <76958050+LKuemmel@users.noreply.github.com>
* info messages for pv charging * tests
* improve deviating evse current * fix deviating evse current only if set current changed
Colors web theme: Fixes, new energy meter
Colors theme (display): Fix pricechart widget, update dependencies
* fix duo * fix file * boot config enterprise * boot config for enterprise * improve boot config txt * fix boot config * init pin 22 * reboot immediately * fix configuration.json
* The older Kostal Piko inverter provides the total amount of Energy without decimal places. This results in corrupted daily graphs were the PV power is always zero. Only when the counter is increased by 1 KWh we can see a high peak in the daily graph. The Problem is discussed here: https://forum.openwb.de/viewtopic.php?t=8851 The Problem did not occur in Version 1.9 of OpenWB and has been seen since the new Module was introduced for V2 The modifications changes the module in a way that the total energy is calculated by the SimCount module and not be taken anymore from the inverter itself. My tests have shown that the daily graph is looking smooth now. * Review * Review --------- Co-authored-by: LKuemmel <76958050+LKuemmel@users.noreply.github.com>
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
12 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.
No description provided.