Is there a verbose "show everything even if it's invalid" mode?

[scoobydrvr]

I installed this software this morning and have been running it for about 6 hours but nothing has been received. rtl_tcp found the device and the output looked like the example on the readme gif. It has also been occasionally saying ll+, now 1 or ll-, now 0 but there hasn't been any other output. rtlamr is running using -msgtype=all but has been quiet since startup.
I'm just looking for a sanity check here - surely my gas, electric, or water meters would have said something by now, right?

[kb1ca]

Not all meters speak the specific protocols supported by rtlamr (eg. the Openway protocol is definitely not compatible and never will be). Examine the information stickers on your specific meters and compare them to the known good models of meters documented here: https://github.com/bemasher/rtlamr#compatibility If your model of meter has previously been reported as compatible but you're not getting data then it's possible your utility has made specific configuration changes to their devices that render them incompatible (newer Neptune meters can be reconfigured to transmit using other protocols, or only on request). Presuming your meter appears to be compatible, you could also try moving your SDR device very close to it for several hours. That would help rule out any potential antenna or interference issues. Finally, the 'll+' and 'll-' messages you see are diagnostic messages coming from the interface to the SDR device that indicate possible issues with the rate incoming data is being processed. If you see them very infrequently they're not an issue. If you see them continuously then you've got bigger issues unrelated to rtlamr that you need to resolve (like needing more CPU power). See https://share.google/aimode/lsUUaOQ3kNAlNvkZq Hope that helps.

…

On Tue, Mar 31, 2026 at 1:05 PM scoobydrvr ***@***.***> wrote: I installed this software this morning and have been running it for about 6 hours but nothing has been received. rtl_tcp found the device and the output looked like the example on the readme gif. It has also been occasionally saying ll+, now 1 or ll-, now 0 but there hasn't been any other output. rtlamr is running using -msgtype=all but has been quiet since startup. I'm just looking for a sanity check here - surely my gas, electric, or water meters would have said *something* by now, right? — Reply to this email directly, view it on GitHub <#334?email_source=notifications&email_token=AC7DKCFZ5QRKUS5GBUVE3NL4TQQKFA5CNFSNUABAM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPHE3TSOBUHE32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7DKCHZ7MB275ZAJMQLZ3T4TQQKFAVCNFSM6AAAAACXIH6SRWVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZG44TQNBZG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[scoobydrvr]

I appreciate the feedback @kb1ca - thank you for taking the time to respond!

I decided to do some digging and careful reading of the messages presented and picked up some clues. First, I think it should be said I'm running this software in an Ubuntu VM, for the sake of convenience. The output of rtl_tcp was showing errors about it's inability to write to registers when starting rtlamr. Further investigation revealed my SDR may be becoming faulty; no surprise there as it's been sitting in the attic for a couple years so I ordered a new one.
Eventually, I found that if I stopped and restarted rtlamr it would eventually not show error messages in rtl_tcp - when that happened, I started receiving messages from meters around me. Progress!
Next, I got things working with the id filters taken from the meters connected to my house sudo rtlamr -msgtype=all -filterid=xxxxxxx,xxxxxxx,xxxxxx and let it cook overnight. I came back this morning to a shiny package from Amazon and an empty output from rtlamr.
After connecting the new SDR and attaching it to the VM, much to my disappointment, I received the same error messages. Decided there's something about running it in a VM that could be the problem, so I dusted off a spare raspberry pi 4, flashed the image, and got the setup installed again.
Now I'm able to get consistent and error-free results in sdr_tcp and I'm waiting to capture messages from my meters again. However, I'm getting a ton of ll+, now _ messages that I need to address. I'll fiddle with that and move the whole setup closer to the meters and see what I get!