CM10 Sensor, Boot speed and Charge Peak attributes #52
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
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.
New sensor:
CM10 Sensor State: Offline<->Test Pending<->Active
Update sensor:
Moved optional FCR-D info from Daily to new CM10 sensor (breaking)
Added PeakPower x 4 to Battery SoC sensor
Updated event:
Event also transit fcrd_failed
Other:
Boot speed updated (againg) since recent change in how components are started.
Refactoring needed:
pyCheckwatt code for extracting logbook not used and not correct. Only extracts ACTIVEATED. Temporarily this is now i HA, and working.
Daily Charge Peak / Discharge peak should be removed, but will break "manual" CWR reporting so left to avoid breaking change