rtl_433 | decode radio transmissions from devices on the ISM bands | Navigation library

by merbanan C Version: nightly License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | rtl_433 Summary

rtl_433 is a C library typically used in User Interface, Navigation applications. rtl_433 has no bugs, it has a Strong Copyleft License and it has medium support. However rtl_433 has 2 vulnerabilities. You can download it from GitHub.

rtl_433 (despite the name) is a generic data receiver, mainly for the 433.92 MHz, 868 MHz (SRD), 315 MHz, 345 MHz, and 915 MHz ISM bands. The official source code is in the repository. For more documentation and related projects see the site. It works with RTL-SDR and/or SoapySDR. Actively tested and supported are Realtek RTL2832 based DVB dongles (using RTL-SDR) and LimeSDR (LimeSDR USB and LimeSDR mini engineering samples kindly provided by MyriadRf), PlutoSDR, HackRF One (using SoapySDR drivers), as well as SoapyRemote.

Support

Quality

Security

License

Reuse

Support

rtl_433 has a medium active ecosystem.

It has 5008 star(s) with 1173 fork(s). There are 181 watchers for this library.

There were 1 major release(s) in the last 12 months.

There are 256 open issues and 1013 have been closed. On average issues are closed in 18 days. There are 41 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rtl_433 is nightly

Quality

rtl_433 has 0 bugs and 0 code smells.

Security

rtl_433 has 2 vulnerability issues reported (0 critical, 0 high, 2 medium, 0 low).

rtl_433 code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rtl_433 is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

rtl_433 releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 1743 lines of code, 81 functions and 15 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rtl_433

Get all kandi verified functions for this library.

rtl_433 Key Features

No Key Features are available at this moment for rtl_433.

rtl_433 Examples and Code Snippets

No Code Snippets are available at this moment for rtl_433.

Community Discussions

Trending Discussions on rtl_433

Trouble piping to curl through sed

rtl_433 on raspberry pi: Send data to api via http post

QUESTION

Trouble piping to curl through sed

Asked 2022-Feb-16 at 23:00

I have a program, rtl_433, that outputs lines of JSON - maybe once or twice a minute, while it's running. I need to pipe that data as HTTP POST data to curl.

What complicates matters is that this string needs to be encapsulated in single quotes, which they're not, so I need to add that before shipping it to curl.

Now, here's the thing: This works just fine:

...

ANSWER

Answered 2022-Feb-16 at 08:42

The problem here is that rtl_433 never exits, it just keeps printing lines for every message it receives.

This is a problem because curl is going to wait until it receives an EOF (end of file) marker to know when it has received all payload it needs to send to in the HTTP request, but of course it never gets this. The EOF would be automatically added when rtl_433 exited.

Your best bet is probable to move from a one line script to a proper bash command reads from rtl_433 a line at a time and then runs sed on that line before passing it to curl.

e.g.

Source https://stackoverflow.com/questions/71138400

QUESTION

rtl_433 on raspberry pi: Send data to api via http post

Asked 2021-Jan-30 at 16:13

I'm receiving the weather data from my weather station with a dongle on my raspberry pi, that has internet connection via wifi. Now I want to send this data to a rails api/app to save it there in a database. The rails app runs on another server, so I want to post the data via http. How can I do this. I can't add the curl dependency to the rtl_433 project (https://github.com/merbanan/rtl_433) to send the data directly to my backend. Am I able to run the rtl_433 for example with a python script like:
rlt_433 -F json and take that output to send it to my backend or how can I realize that?

...

ANSWER

Answered 2021-Jan-30 at 16:13

You should be able to execute rtl_433 as a subprocess using the subprocess module. Normally you would just use subprocess.run, but since rtl_433 produces output until it is killed, you will need to use subprocess.Popen and parse the output.

Another option is to pipe the output of rtl_433 to your program and using input() or sys.stdin.readline() to read lines. Like rtl_433 -flags | python3 script.py.

Source https://stackoverflow.com/questions/65917930

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rtl_433

rtl_433 is written in portable C (C99 standard) and known to compile on Linux (also embedded), MacOS, and Windows systems. Older compilers and toolchains are supported as a key-goal. Low resource consumption and very few dependencies allow rtl_433 to run on embedded hardware like (repurposed) routers. Systems with 32-bit i686 and 64-bit x86-64 as well as (embedded) ARM, like the Raspberry Pi and PlutoSDR are well supported. On Debian (sid) or Ubuntu (19.10+), apt-get install rtl-433 for other distros check https://repology.org/project/rtl-433/versions. On FreeBSD, pkg install rtl-433. On MacOS, brew install rtl_433. Docker images with rtl_433 are available on the github page of hertzg.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: