HA addon - debug gets data, but nothing to configured sensor, CPU usage to 50%, then errors in logs

[VynDesign]

Hardware:

• system: Raspberry Pi 4B
• radio: RTL-SDR Blog v4

Software:
Home Assistant:

• Core 2024.1.2
• Supervisor 2023.12.0
• OS 11.3

rtlamr2mqtt:

• Add-on 2.3.4

Configuration:

general:
  sleep_for: 300
  verbosity: debug
  listen_only: true
  tickle_rtl_tcp: false
  device_id: single
mqtt:
  ha_autodiscovery: true
  ha_autodiscovery_topic: homeassistant
  base_topic: rtlamr
  tls_enabled: false
  user: {{redacted}}
  password: {{redacted}}
custom_parameters:
  rtltcp: "-s 2048000"
  rtlamr: "-unique=true"
meters:
  - id: 1552{{redacted}}
    protocol: scm+
    name: electricity_meter
    unit_of_measurement: kWh
    format: "######.##"
    icon: mdi:meter-electric-outline
    device_class: energy
    state_class: total_increasing

Problem:
After starting the add-on, the logs seem to indicate proper functionality, with a few items showing up in the rtlamr/debug topic (which I can listen to in the MQTT add-on with success) but nothing is filtering to the appropriate electricity_meter sensor:

[2024-01-10 08:40:21] Using "/data/options.json" config file
[2024-01-10 08:40:21] Fetching default MQTT configuration from http://supervisor/services/mqtt
[2024-01-10 08:40:21] Starting in LISTEN ONLY Mode...
[2024-01-10 08:40:21] Using "/data/options.json" config file
[2024-01-10 08:40:21] Fetching default MQTT configuration from http://supervisor/services/mqtt
[2024-01-10 08:40:21] Configured MQTT sender:
[2024-01-10 08:40:21]  > hostname => core-mosquitto
[2024-01-10 08:40:21]  > port => 1883
[2024-01-10 08:40:21]  > username => addons
[2024-01-10 08:40:21]  > client_id => rtlamr2mqtt
[2024-01-10 08:40:21]  > base_topic => rtlamr
[2024-01-10 08:40:21]  > availability_topic => rtlamr/status
[2024-01-10 08:40:21]  > tls => None
[2024-01-10 08:40:21] Starting rtl_tcp with /usr/bin/rtl_tcp 
[2024-01-10 08:40:23] Starting rtlamr with ['/usr/bin/rtlamr', '-msgtype=all', '-format=json']
[2024-01-10 08:40:23] You should see all utility meters after this line:
[2024-01-10 08:40:23] 08:40:23.102836 decode.go:45: CenterFreq: 912600155
[2024-01-10 08:40:23] 08:40:23.103177 decode.go:46: SampleRate: 2359296
[2024-01-10 08:40:23] 08:40:23.103201 decode.go:47: DataRate: 32768
[2024-01-10 08:40:23] 08:40:23.103214 decode.go:48: ChipLength: 72
[2024-01-10 08:40:23] 08:40:23.103227 decode.go:49: PreambleSymbols: 32
[2024-01-10 08:40:23] 08:40:23.103241 decode.go:50: PreambleLength: 4608
[2024-01-10 08:40:23] 08:40:23.103255 decode.go:51: PacketSymbols: 736
[2024-01-10 08:40:23] 08:40:23.103268 decode.go:52: PacketLength: 105984
[2024-01-10 08:40:23] 08:40:23.103289 decode.go:59: Protocols: r900,scm,scm+,idm
[2024-01-10 08:40:23] 08:40:23.103311 decode.go:60: Preambles: 111110010101001100000,0001011010100011,01010101010101010001011010100011,00000000000000001110010101100100
[2024-01-10 08:40:23] 08:40:23.103411 main.go:124: GainCount: 29

The debug topic receives numerous entries, some that are unrelated to my device:

[2024-01-10 08:40:35] {"Time":"2024-01-10T08:40:35.976000702-05:00","Offset":0,"Length":0,"Type":"SCM","Message":{"ID":4202456,"Type":5,"TamperPhy":0,"TamperEnc":2,"Consumption":5129631,"ChecksumVal":53822}}
[2024-01-10 08:40:35] Sending message to MQTT:
[2024-01-10 08:40:35]  > topic => rtlamr/debug
[2024-01-10 08:40:35]  > payload => {"Time": "2024-01-10T08:40:35.976000702-05:00", "Offset": 0, "Length": 0, "Type": "SCM", "Message": {"ID": 4202456, "Type": 5, "TamperPhy": 0, "TamperEnc": 2, "Consumption": 5129631, "ChecksumVal": 53822}}
[2024-01-10 08:40:35]  > retain => False
[2024-01-10 08:40:54] {"Time":"2024-01-10T08:40:54.437824883-05:00","Offset":0,"Length":0,"Type":"SCM","Message":{"ID":4202456,"Type":5,"TamperPhy":0,"TamperEnc":2,"Consumption":5129632,"ChecksumVal":33459}}
[2024-01-10 08:40:54] Sending message to MQTT:
[2024-01-10 08:40:54]  > topic => rtlamr/debug
[2024-01-10 08:40:54]  > payload => {"Time": "2024-01-10T08:40:54.437824883-05:00", "Offset": 0, "Length": 0, "Type": "SCM", "Message": {"ID": 4202456, "Type": 5, "TamperPhy": 0, "TamperEnc": 2, "Consumption": 5129632, "ChecksumVal": 33459}}
[2024-01-10 08:40:54]  > retain => False

Then I get two payloads that do match the ID of the configured meter:

[2024-01-10 08:41:10] {"Time":"2024-01-10T08:41:10.43875615-05:00","Offset":0,"Length":0,"Type":"IDM","Message":{"Preamble":1431639715,"PacketTypeID":28,"PacketLength":92,"HammingCode":198,"ApplicationVersion":4,"ERTType":7,"ERTSerialNumber":1552{{redacted}},"ConsumptionIntervalCount":133,"ModuleProgrammingState":188,"TamperCounters":"AgEABQkA","AsynchronousCounters":0,"PowerOutageFlags":"AAAABAAA","LastConsumptionCount":78277,"DifferentialConsumptionIntervals":[9,8,9,9,7,11,14,15,10,9,8,8,8,7,10,7,11,7,9,10,11,12,8,24,10,15,14,10,9,8,11,9,11,10,10,9,9,10,8,11,7,9,7,8,7,8,9],"TransmitTimeOffset":1609,"SerialNumberCRC":34595,"PacketCRC":24841}}
[2024-01-10 08:41:10] Sending message to MQTT:
[2024-01-10 08:41:10]  > topic => rtlamr/debug
[2024-01-10 08:41:10]  > payload => {"Time": "2024-01-10T08:41:10.43875615-05:00", "Offset": 0, "Length": 0, "Type": "IDM", "Message": {"Preamble": 1431639715, "PacketTypeID": 28, "PacketLength": 92, "HammingCode": 198, "ApplicationVersion": 4, "ERTType": 7, "ERTSerialNumber": 1552{{redacted}}, "ConsumptionIntervalCount": 133, "ModuleProgrammingState": 188, "TamperCounters": "AgEABQkA", "AsynchronousCounters": 0, "PowerOutageFlags": "AAAABAAA", "LastConsumptionCount": 78277, "DifferentialConsumptionIntervals": [9, 8, 9, 9, 7, 11, 14, 15, 10, 9, 8, 8, 8, 7, 10, 7, 11, 7, 9, 10, 11, 12, 8, 24, 10, 15, 14, 10, 9, 8, 11, 9, 11, 10, 10, 9, 9, 10, 8, 11, 7, 9, 7, 8, 7, 8, 9], "TransmitTimeOffset": 1609, "SerialNumberCRC": 34595, "PacketCRC": 24841}}
[2024-01-10 08:41:10]  > retain => False
[2024-01-10 08:41:10] {"Time":"2024-01-10T08:41:10.976877427-05:00","Offset":0,"Length":0,"Type":"SCM+","Message":{"FrameSync":5795,"ProtocolID":30,"EndpointType":7,"EndpointID":1552{{redacted}},"Consumption":78278,"Tamper":513,"PacketCRC":29259}}
[2024-01-10 08:41:10] Sending message to MQTT:
[2024-01-10 08:41:10]  > topic => rtlamr/debug
[2024-01-10 08:41:10]  > payload => {"Time": "2024-01-10T08:41:10.976877427-05:00", "Offset": 0, "Length": 0, "Type": "SCM+", "Message": {"FrameSync": 5795, "ProtocolID": 30, "EndpointType": 7, "EndpointID": 1552{{redacted}}, "Consumption": 78278, "Tamper": 513, "PacketCRC": 29259}}

But nothing to the configured sensor.

Then, the add-on starts using ~50% CPU, and then I get an error (after which CPU usage stays at ~50% until I stop/restart the addon):

[2024-01-10 08:48:16] 08:48:16.889948 main.go:343: Receiver context cancelled.
[2024-01-10 08:48:16] 08:48:16.890646 main.go:320: read tcp 127.0.0.1:33462->127.0.0.1:1234: i/o timeout
[2024-01-10 08:48:16] io.ReadFull
[2024-01-10 08:48:16] main.(*Receiver).Run.func2
[2024-01-10 08:48:16] 	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
[2024-01-10 08:48:16] runtime.goexit
[2024-01-10 08:48:16] 	/usr/local/go/src/runtime/asm_arm64.s:1197

[VynDesign]

Looks like I didn't understand the use of "listen_only" - I flipped that to 'false' and am now getting data to the configured meter.