New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter based on tamper flags or type #288
Comments
The specifications for my meter (https://www.smartmetereducationnetwork.com/uploads/how-to-tell-if-I-have-a-ami-dte-smart-advanced-meter/Itron%20Centron%20Meter%20Technical%20Guide1482163-201106090057150.pdf) only mention |
This request is a bit of a workaround, so I'm happy to discuss alternative approaches.
My energy meter reports via SCM, and most readings appear correct. Occasionally, I see messages that indicate unrealistic consumption spikes, where it suggests that I consumed over 1,000,000 kWh since the last report.
With debug logging enabled, I noticed that these spikes correlate to SCM messages from the same meter, but with a different
Type
, and with bothTamperPhy
andTamperEnc
flags set.The sample messages are unaltered from the logs, except for the message
ID
, which I've redacted. This ID is the same in both of the real messages.Ordinary message (Type: 4, no tamper) @ 21:09:12
Sample "spike" message (Type: 6, tamper) @ 21:09:54
Another ordinary message (Type: 4, no tamper) @ 21:09:54
Consumption resets to expected level following the erroneous spike.
Has anyone come across this before? These false consumption spikes are problematic for me downstream, so I'd like a way to filter them out before publishing them into MQTT (via https://github.com/allangood/rtlamr2mqtt).
The text was updated successfully, but these errors were encountered: