Allowing piping for numeric entity states #670
Merged
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.
State values of entities can now be merged together by piping the entity names. Only works with numbers. If the state is not a number, the first will be used. If another property than "state" is used, only the values of the first entity will be used.
E.g. my inverter does not provide a single sensor for the current grid consumption. Instead each phase has its own value. So I made a small modification to your project by allowing piping sensor entities.
Example:
grid:
entity: >-
sensor.foxessrs485_grid_ct_r | sensor.foxessrs485_grid_ct_s |
sensor.foxessrs485_grid_ct_t