SunSpec: Channel values synchronized #2609
Merged
Conversation
This file contains 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
|
|
|
|
sfeilmeier
approved these changes
Apr 29, 2024
fanass-dev
pushed a commit
to fanass-dev/openems
that referenced
this pull request
May 6, 2024
* onUpdate() replaced by onSetNextValue() in mapFirstPointToChannel() * Fix prepare-commit script
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.
A small fix in the mapping between SunSpec channel values and OpenEMS channel values: Previously, this was done by an
onUpdate()-listener, meaning that the OpenEMS channel was one cycle behind the SunSpec channel. This is fixed here by using anonSetNextValue()-listener instead.