fix EEP A5-12-00 #144
Open
fix EEP A5-12-00 #144
Conversation
This file contains hidden or 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
|
Hello @GuillaumePod, thank for the fix, I have the same wizzconso meter A5-12-00. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hello, thank you for this project providing rich support for the EnOcean protocol for Home Assistant.
Having a WizzConso meter, I noticed an error in the integration. The EEP A5-12-00 profile offers several counters, but in the current integration, it doesn't differentiate them and all values end up in the same entity.
I have therefore made a correction that generates two entities: the counter and the current value for each of the 16 possible channels.