Derived sensors #3
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
nhoening
requested changes
Sep 20, 2021
|
So the derived sensors - are they really z-info sensors? It seems to me they are derived from Z-Info sensors, but really not a representation of any z-info raw data. |
|
I made a ticket to refactor further. |
It's probably not even necessary to make the distinction once we move to a single config setting. Perhaps the unified config setting could be renamed again to |
nhoening
approved these changes
Sep 20, 2021
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 currently undocumented feature to set up (using a new plugin config setting) additional FlexMeasures sensors whose data is derived from other sensors (that are directly mapped to a Z-info sensor).