Support for the NETIDM message type

[marbletravis]

I would like to contribute and add support for NETIDM.

My thought would be to detect that type, and when its that type create and send two messages, for two two devices {name}_generated and {name}_consumed.

Is this something that you would be willing to merge in?
Have you attempted to support this protocol in the past and had issues?

Thanks
Travis

[allangood]

Hi @marbletravis , this project is just a wrapper around RTLAMR and RTL_TCP. This means I don't do any protocol decoding, this is something that must done by the bemasher/rtlamr project.

[allangood]

Ok, if it is supported by rtlamr, then I can work on it.

If you could send me a few lines of the reading, I can add support for it then.

[marbletravis]

Is this sufficient? Also, I am happy to help, let me know.

[2025-05-30 03:19:28] {"Time":"2025-05-30T03:19:28.187840937Z","Offset":0,"Length":0,"Type":"NetIDM","Message":{"Preamble":1431639715,"ProtocolID":28,"PacketLength":92,"HammingCode":198,"ApplicationVersion":4,"ERTType":7,"ERTSerialNumber":27267720,"ConsumptionIntervalCount":120,"ProgrammingState":188,"LastGeneration":106,"LastConsumption":0,"LastConsumptionNet":2181169632,"DifferentialConsumptionIntervals":[15902,929,13368,1860,136,5899,4424,11284,8897,11817,961,13372,1859,12412,3975,8440,7941,8272,2052,128,4106,256,10260,641,4128,1282,64],"TransmitTimeOffset":1249,"SerialNumberCRC":50566,"PacketCRC":39654}} [2025-05-30 03:19:43] {"Time":"2025-05-30T03:19:43.220546262Z","Offset":0,"Length":0,"Type":"NetIDM","Message":{"Preamble":1431639715,"ProtocolID":28,"PacketLength":92,"HammingCode":198,"ApplicationVersion":4,"ERTType":7,"ERTSerialNumber":22991567,"ConsumptionIntervalCount":34,"ProgrammingState":188,"LastGeneration":143,"LastConsumption":0,"LastConsumptionNet":2273551041,"DifferentialConsumptionIntervals":[6189,1346,10326,2693,4264,3334,12504,7182,432,14364,1154,12376,2821,10420,5514,12632,11285,8897,5149,1058,1090,2116,2184,4489,272,10001,8769],"TransmitTimeOffset":1458,"SerialNumberCRC":5026,"PacketCRC":12338}} [2025-05-30 03:20:26] {"Time":"2025-05-30T03:20:26.381803887Z","Offset":0,"Length":0,"Type":"NetIDM","Message":{"Preamble":1431639715,"ProtocolID":28,"PacketLength":92,"HammingCode":198,"ApplicationVersion":4,"ERTType":7,"ERTSerialNumber":22988047,"ConsumptionIntervalCount":179,"ProgrammingState":188,"LastGeneration":83,"LastConsumption":0,"LastConsumptionNet":37830912,"DifferentialConsumptionIntervals":[11780,96,7176,193,14428,896,8216,773,8592,8196,64,3074,128,2056,256,12320,776,8320,1538,609,8240,704,4140,3077,24,512,8336],"TransmitTimeOffset":2225,"SerialNumberCRC":20490,"PacketCRC":38752}}

[marbletravis]

Hold out, I just realized that consumption and return come across on SCM+, but separate ids. this may not be necessary.

[allangood]

More info on how to use the new release in the #193

[allangood]

Yes, this is very helpful.

[allangood]

As far I could understand, there are 3 meters in this output and what I think it is important is the LastGeneration field.
What I am confused is the LastConsumptionNet and the LastConsumption value. Which one should I use for consumption in this type of meter?

[marbletravis]

LastConsumption is the consumption value.

LastConsumptionNet would be the difference between Generation and Consumption, it wouldn't be bad to have that data come across, but I don't think its needed.

[allangood]

Added LastConsumption message support in #268