Replies: 2 comments
-
|
Note: this is about the flex decoder https://github.com/merbanan/rtl_433/blob/master/conf/qx-30x.conf Flex decoder are added at runtime and have no defined protocol number. There is no audio, right? Tranceiver, but data only? Something like a baby-monitor would jam the channel. Try to monitor the band with a SDR UI, if it supports |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
It sends audio data only when you accept a call. https://a.aliexpress.com/_EJcio20 I'll check with rtl_tcp in the SDR UI and tell you what I see. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've set -R 0 and I'm doing a -X to specify it since QX-30X is the only interesting device for me to send to Mqtt.
I don't know does QX-30X have a protocol number?
I've got 2 inkbird temp sensors (protocol 194)
I can't imagine them being the noise.
So the only other thing that's same frequency around is this 2 way door bell.
So I opened it up and took a look inside.
And it's a bit of trickery there. But I managed to find this little guy.
And searching for the first washed out letters I got this:
https://www.silabs.com/documents/public/data-sheets/Si4438.pdf
The door bell does more than audio over 433, also triggers a separate 433 MHz relay. By the looks of it, it's actively pinging the other side perhaps with some battery information, unclear, because rtl_433 -A is very messy with chunked bits of random data of varying sizes.
The non QX-30X packets send both 24 bit and 25 bit at random, and frequently.
Beta Was this translation helpful? Give feedback.
All reactions