Corrections especially welcome
Contact
Field reports are the most valuable thing you can send. The dataset knows what the FCC filed; it does not know what actually decoded.
hello@meterradio.com
No form, no newsletter, no tracking pixel. Email is fine.
What is most useful to send
The single gap in this site is the column no scraper can produce: the FCC database says a device is authorised in 902–928 MHz, but only somebody with a receiver knows whether an open tool actually decoded it. If you have that, it is worth more than anything else you could send.
A useful field report:
| Include | Why |
|---|---|
| The FCC ID from the faceplate | Ties your report to a specific filing rather than a model name. |
| Utility — gas, water or electric | The three behave differently and are tracked separately. |
| Message type that worked | scm / scm+ / idm / r900 / r900bcd |
| Which tool decoded it | rtlamr, rtl_433, something else |
| Rough frequency observed | Confirms or contradicts the filed range. |
| Region | State or country is plenty. Provisioning varies by utility. |
Negative results count. "This FCC ID is listed as in-band and nothing decodes it" is a genuinely useful data point, and harder to come by than a success — nobody writes up the things that did not work.
Please do not send meter IDs, account numbers, addresses, or consumption data. None of it is needed and it is not wanted.
Corrections
If something here is wrong, say so directly — a filing misparsed, a frequency misattributed, a protocol claim that does not survive contact with your receiver. Corrections get made.
What this site cannot help with
Being clear about this saves everyone time:
- Reading a meter you do not own. Not a topic here.
- Bypassing, modifying, unsealing, or interfering with a meter. No.
- Decrypting proprietary AMI mesh traffic. Not covered, not attempted.
- Disputing your utility bill. The broadcast is the utility's own number, so it can be useful evidence — but the dispute is between you and them.