I won't bother you with all the process.
I have the task of extracting the serial number of medical alarm triggers (the label is worn off) basically, like the "I've fallen and I can't get up" meme.
My hardware is "Nooelec NESDR Nano 2+"
I started knowing 0 (I don't know too much now either
Turns out not all the serial number is on the radio signal, but enough to make a search on a database to get the full one or almost.
The trigger is MyAmie. Here is the command y use "rtl_433-rtlsdr.exe -f 869.202M -s 250k -v -A".
The result are 3 bursts of 51200 characters each after some shenanigans I get a partial serial number. Now, my problem is the TX4 model, I have tested variations and values for rtl_433 for two days (different bandwidths, frequencies...) and I can't get a reliable read, sometimes I capture 30k or 20k characters from some triggers, but mostly 2 or none characters is the norm.
With the "MyAmie" model, thanks to the spectrum analyzer, it was clear there was 3 equal bursts.
The TX4 shows 2 short and two long "messages" on 2 frequencies (868 and 869). I am fully lost, I have no idea how to get a proper capture for this trigger.
Why I need "code" instead of the raw signal? I feed that hexadecimal string to python and get a serial number.
At an extreme I suppose python can capture the raw signal and process it, but rtl_433 should be able to do the capture, but getting the "data" with rtl_433 is the easiest way.
Hoping for some help.
Thank you very much.