Repository navigation
E3DC: aktive Speichersteuerung über RSCP - #4152
Open
seaspotter wants to merge 1 commit into
Open
seaspotter wants to merge 1 commit into
seaspotter wants to merge 1 commit into
Conversation
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
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.
UI: openWB/openwb-ui-settings#1135
Aktive Speichersteuerung für E3DC per RSCP (SET_POWER Mode+Value), zusätzlich zum bestehenden Modbus-Lesepfad. Optionale portal_username/portal_password/rscp_key-Config – ohne sie wird der Speicher weiterhin normal ausgelesen, ist aber nicht steuerbar. Mode/Value-Semantik und RSCP-Tags an echter Hardware verifiziert in #3450
Neu hinzugekommene Abhängigkeiten: pye3dc, py3rijndael, tzlocal, websocket-client.
Achtung Python 3.9: die neueste pye3dc-Version (0.10.0) sowie deren neueste eigene Abhängigkeiten (tzlocal, websocket-client) benötigen Python ≥3.10, was mit openWBs Python 3.9 nicht funktioniert. Deshalb auf die jeweils neuesten noch 3.9-kompatiblen Versionen gepinnt (pye3dc==0.9.3, tzlocal==5.3.1, websocket-client==1.9.0), API ist identisch.
Test an echter E3DC-Hardware war mir nicht möglich