Add support for Apator Metra E-RM 30 water meter #3203
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
carpalex
force-pushed
the
apator-metra-erm30
branch
2 times, most recently
from
9b4c062 to
41fc184
Compare
carpalex
force-pushed
the
apator-metra-erm30
branch
from
41fc184 to
cd6636b
Compare
|
One more style change: |
carpalex
force-pushed
the
apator-metra-erm30
branch
from
cd6636b to
202ccc5
Compare
Done. |
|
hey, did you have any news? thanks |
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.
This provides partial support for decoding the telegrams transmitted by an Apator Metra E-RM 30 radio module for water meters.
The partial support is due to the fact that the payload is encrypted and only a limited set of fields were successfully reverse engineered, yet. The encryption appears to be a (custom) algorithm based on 4x4 S-boxes (see
src/devices/apator_metra_erm30.cfor more details).Even so, the current state of the code provides decryption for the ID, Volume and Date, which should cover most the common use cases.
See also issue #3012.