Frankly I don't know all of the information for the v2 that you have listed for the v1, but I can confirm that model AHRML-DL, FCC ID SM6-HOTRODV2ML will function with the same rtl_433 command. I had to turn the gain up on mine from 20 to 50 (which also caused me to think that it didn't work for this model for months before I decided to revisit it today), but this is likely only due to the distance between my RTL-SDR and the meter.
(It's a bit hard to see, but the meter number is 15514971, and the consumption is 0276460.)
This captured frame is from a bit later in the day, where the consumption has increased to 0276480
{"time" : "2024-07-03 23:49:48", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 104, "data" : "afeb10015514971027648005d0"}], "codes" : ["{104}afeb10015514971027648005d0"]}
The data is a bit different from v1, being 104 bytes long and following a different format
?? ?? ?? ?T TT TT TT TC CC CC CC ?? ??
af eb 10 01 55 14 97 10 27 64 80 05 d0
Interestingly enough, my neighbor's meter sends different frames (Meter ID 15514970)
{"time" : "2024-07-03 23:49:49", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 105, "data" : "afeb10015514970020211004200"}], "codes" : ["{105}afeb10015514970020211004200"]}
Where
?? ?? ?? ?T TT TT TT TC CC CC CC ?? ?? ?
af eb 10 01 55 14 97 00 20 21 10 04 20 0
EDIT: On closer inspection, both meters vary between 104 and 105 bytes regularly, with the difference being an extra 0 at the end
At least these are the typical frames... I've had some irregularities
{"time" : "2024-07-04 00:14:07", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 98, "data" : "afeb100155149700202110040"}], "codes" : ["{98}afeb100155149700202110040"]}
This guy came up while I was typing this and is only 98 bytes, and appears to be:
?? ?? ?? ?T TT TT TT TC CC CC CC ?? ?
af eb 10 01 55 14 97 00 20 21 10 04 0
... though this may just be an irregularity in the SDR's listening. My favorites are these:
{"time" : "2024-07-04 00:17:44", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 1770, "data" : "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab209c304016e026dda9701c217a30ea3b67094384ba5c6e28c875d7fe79e99a1f50a588b3c"}], "codes" : ["{1770}aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab209c304016e026dda9701c217a30ea3b67094384ba5c6e28c875d7fe79e99a1f50a588b3c"]}
...which I'm not going to try and decode. I've seen a handful of frames like this come through and may be a newer hotrod in a neighbor's house, or just an error. Bytes range from 1764 to 1774
I'm happy to give any more information about nearby meters to help with documentation for other models. I can't quite go as in depth as your original teardown, as I'm renting, and these are installed on active meters. Everything short of complete destruction is fair game, however.
Frankly I don't know all of the information for the v2 that you have listed for the v1, but I can confirm that model AHRML-DL, FCC ID SM6-HOTRODV2ML will function with the same rtl_433 command. I had to turn the gain up on mine from 20 to 50 (which also caused me to think that it didn't work for this model for months before I decided to revisit it today), but this is likely only due to the distance between my RTL-SDR and the meter.
This captured frame is from a bit later in the day, where the consumption has increased to 0276480
{"time" : "2024-07-03 23:49:48", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 104, "data" : "afeb10015514971027648005d0"}], "codes" : ["{104}afeb10015514971027648005d0"]}The data is a bit different from v1, being 104 bytes long and following a different format
Interestingly enough, my neighbor's meter sends different frames (Meter ID 15514970)
{"time" : "2024-07-03 23:49:49", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 105, "data" : "afeb10015514970020211004200"}], "codes" : ["{105}afeb10015514970020211004200"]}Where
EDIT: On closer inspection, both meters vary between 104 and 105 bytes regularly, with the difference being an extra 0 at the end
At least these are the typical frames... I've had some irregularities
{"time" : "2024-07-04 00:14:07", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 98, "data" : "afeb100155149700202110040"}], "codes" : ["{98}afeb100155149700202110040"]}This guy came up while I was typing this and is only 98 bytes, and appears to be:... though this may just be an irregularity in the SDR's listening. My favorites are these:
{"time" : "2024-07-04 00:17:44", "model" : "hotrod", "count" : 1, "num_rows" : 1, "rows" : [{"len" : 1770, "data" : "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab209c304016e026dda9701c217a30ea3b67094384ba5c6e28c875d7fe79e99a1f50a588b3c"}], "codes" : ["{1770}aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab209c304016e026dda9701c217a30ea3b67094384ba5c6e28c875d7fe79e99a1f50a588b3c"]}...which I'm not going to try and decode. I've seen a handful of frames like this come through and may be a newer hotrod in a neighbor's house, or just an error. Bytes range from 1764 to 1774I'm happy to give any more information about nearby meters to help with documentation for other models. I can't quite go as in depth as your original teardown, as I'm renting, and these are installed on active meters. Everything short of complete destruction is fair game, however.