bemasher / rtlamr

An rtl-sdr receiver for Itron ERT compatible smart meters operating in the 900MHz ISM band.
GNU Affero General Public License v3.0
2.18k stars 247 forks source link

IDs never repeat #257

Closed greaterthanstar closed 2 years ago

greaterthanstar commented 2 years ago

Hi, I'm running rtlamr with default options. I have a gas meter about 4 ft away on the other side of a wall. After nearly a week of runtime, none of the meters picked up have the same ID, so it's not possible to track consumption. Am I doing something wrong? Can you help me understand this output? I also tried it with all the decoders enabled but it was the same. I'm in the CA bay area (PGE) if that matters.

Thanks!

{Time:2022-06-22T04:33:52.531 SCM:{ID:52147462 Type: 2 Tamper:{Phy:02 Enc:02} Consumption:16668163 CRC:0xA04B}}
{Time:2022-06-22T09:27:33.699 SCM:{ID:22265716 Type: 0 Tamper:{Phy:01 Enc:01} Consumption:16773384 CRC:0x8A54}}
{Time:2022-06-22T09:27:42.972 SCM:{ID: 7777797 Type: 7 Tamper:{Phy:03 Enc:00} Consumption:16634019 CRC:0x0AF7}}
{Time:2022-06-22T14:56:50.889 SCM:{ID:49414101 Type: 7 Tamper:{Phy:00 Enc:02} Consumption:14193722 CRC:0x0F51}}
{Time:2022-06-22T23:31:20.455 SCM:{ID:48125762 Type: 9 Tamper:{Phy:01 Enc:03} Consumption:12519597 CRC:0xA54F}}
{Time:2022-06-23T09:04:17.115 SCM:{ID: 3567546 Type: 7 Tamper:{Phy:01 Enc:02} Consumption:16681388 CRC:0x05A8}}
{Time:2022-06-24T02:16:45.279 SCM:{ID: 3598421 Type: 5 Tamper:{Phy:01 Enc:02} Consumption:12107780 CRC:0x20DA}}
{Time:2022-06-24T03:48:09.287 SCM:{ID: 1572776 Type: 3 Tamper:{Phy:00 Enc:02} Consumption: 7334457 CRC:0x8C1F}}
{Time:2022-06-25T17:20:45.334 SCM:{ID:14513278 Type:15 Tamper:{Phy:02 Enc:01} Consumption: 1255849 CRC:0xFC91}}
{Time:2022-06-25T21:06:30.306 SCM:{ID:33353484 Type: 4 Tamper:{Phy:00 Enc:00} Consumption:13598235 CRC:0xB841}}
{Time:2022-06-26T12:27:06.140 SCM:{ID:55903470 Type: 0 Tamper:{Phy:03 Enc:00} Consumption: 4991656 CRC:0x9959}}
{Time:2022-06-27T16:18:43.150 SCM:{ID:18939726 Type: 1 Tamper:{Phy:01 Enc:00} Consumption:10252586 CRC:0xA873}}
{Time:2022-06-28T13:47:07.122 SCM:{ID:26566252 Type:14 Tamper:{Phy:03 Enc:02} Consumption: 3180728 CRC:0xF793}}
{Time:2022-06-28T22:49:48.123 SCM:{ID: 9469730 Type: 5 Tamper:{Phy:02 Enc:00} Consumption:10188554 CRC:0xB053}}
{Time:2022-06-29T00:08:22.241 SCM:{ID:46481129 Type:11 Tamper:{Phy:02 Enc:01} Consumption: 4418155 CRC:0xA119}}
{Time:2022-06-29T03:43:25.349 SCM:{ID:23491213 Type: 5 Tamper:{Phy:00 Enc:03} Consumption:14512794 CRC:0xE0C1}}
{Time:2022-06-29T06:17:47.299 SCM:{ID:44103666 Type:14 Tamper:{Phy:03 Enc:03} Consumption:13619327 CRC:0x103F}}
{Time:2022-06-29T21:29:50.707 SCM:{ID:21319418 Type:11 Tamper:{Phy:00 Enc:03} Consumption:11926159 CRC:0xB903}}
bemasher commented 2 years ago

Because the messages are so sparse in time, I'd guess that you have no compatible meters in your area for the message types you were using.

Messages are decoded when they have a valid preamble and CRC. Eventually if you listen to enough noise, you'll find "packets" that satisfy these requirements, even when they are not valid.