Settable smartevse_current_max_sum_mains #36
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
…to settable number entity, so the max capacity can be dynamically updated using HA automations.
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.
Changed smartevse_current_max_sum_mains from read-only sensor entity to settable number entity, so the max capacity can be dynamically updated using HA automations.
Considering the current Slovenian power network capacity restrictions, where every household can have 5 different power capacities depending on the season, work-day and hour of the day, it is crucial that home-assistant can dynamically set the network capacity on the SMART Evse. In this PR i have just added the EVSE API call to the existing endpoint and changed the entity in HA to input.
Just as an interesting info:
capacity blocks for households
Price per kW of capacity per block:
