NEWS
New Adapter for rtl_433 incoming data
-
Thanks for developing this adapter and contributing to the ioBroker community.
I am widely using 433 sensors. To integrate into ioBroker I am curently using RFLink which uses cheap RXB6 receivers and an arduino Mega 2560 to decode the received messages. An ioBroker adapter manages the messages into the objects folders, the pairing etc.
As far as I understood, your adapter does similar things:- transceiver is a common USB SDR-stick such as Realtek RTL2832 based units
- as a decoder serves the rtl_433 SW (which also is available for Windows). This is where the "magic happens" and novel units have to be implemented
- your adapter glues the rtl_433 project to ioBroker, supplying a HMI for pairing and organized the object folders.
Did I get this correctly?
@klassisch
yes this is how the adapter works.
It recognizes a large number of devices and also works simultaneously in the frequency range of approx. 433-868Mhz. The only disadvantage as far as I know you can only receive data.
Sending is not possible. -
@klassisch
yes this is how the adapter works.
It recognizes a large number of devices and also works simultaneously in the frequency range of approx. 433-868Mhz. The only disadvantage as far as I know you can only receive data.
Sending is not possible.@vogtländer sagte in New Adapter for rtl_433 incoming data:
Sending is not possible.
For me that would be no limitation. Althoug RFLink also supports transmitting, I neither use it nor need it. Most of the 433MHz units do not have a backward channel and are 2nd choice for actuators. For actuators I prefer Homematic, Shelly, Zigbee.
As far as I am informed, the RTL2832 has an on chip integrated USB interface. This could be a disadvantage for my mode of operation. I modified the arduino Mega for usage over Ethernet. This makes me independent of the location of my ioBroker computer.
-
@phillipssc
Hello, I've now found time to deal with the problem.
I updated the rtl_433 installation (not adapter). After that I got better logs and could
customize the command line like this:
rtl_433 -F json -f 868000000 -s 1024000 -f 433920000 -s 250000 -H 300 and it runs.
I think there is the problem in the adapter that the command line is not created correctly.
Still, the adapter is awesome!@vogtländer - It looks like it had to do with unit conversion. It would have been interesting to see what that said - but I will cover it in the next round none the less.
-
Thanks for developing this adapter and contributing to the ioBroker community.
I am widely using 433 sensors. To integrate into ioBroker I am curently using RFLink which uses cheap RXB6 receivers and an arduino Mega 2560 to decode the received messages. An ioBroker adapter manages the messages into the objects folders, the pairing etc.
As far as I understood, your adapter does similar things:- transceiver is a common USB SDR-stick such as Realtek RTL2832 based units
- as a decoder serves the rtl_433 SW (which also is available for Windows). This is where the "magic happens" and novel units have to be implemented
- your adapter glues the rtl_433 project to ioBroker, supplying a HMI for pairing and organized the object folders.
Did I get this correctly?
@klassisch said in New Adapter for rtl_433 incoming data:
apter glues the rtl_433
Yes, that's precisely it, and as mentioned incoming messages only
-
@vogtländer sagte in New Adapter for rtl_433 incoming data:
Sending is not possible.
For me that would be no limitation. Althoug RFLink also supports transmitting, I neither use it nor need it. Most of the 433MHz units do not have a backward channel and are 2nd choice for actuators. For actuators I prefer Homematic, Shelly, Zigbee.
As far as I am informed, the RTL2832 has an on chip integrated USB interface. This could be a disadvantage for my mode of operation. I modified the arduino Mega for usage over Ethernet. This makes me independent of the location of my ioBroker computer.
@klassisch "This makes me independent of the location of my ioBroker computer." You can use this as such in this adapter too. Rtl_433 runs on top of Rtl-sdr. You can run rtl_sdr on a Raspberry Pi with the dongle in tcp_ip mode. Feed the params into rtl_433 (which my adapter supports) and it will connect to the remote computer for the data. Better instructions are in my README
-
@klassisch "This makes me independent of the location of my ioBroker computer." You can use this as such in this adapter too. Rtl_433 runs on top of Rtl-sdr. You can run rtl_sdr on a Raspberry Pi with the dongle in tcp_ip mode. Feed the params into rtl_433 (which my adapter supports) and it will connect to the remote computer for the data. Better instructions are in my README
@phillipssc because ioBroker supports multihost operation, this is always an (additional) option. You can also run your adapter on a raspi (or similar) as an ioBroker slave.
-
@klassisch "This makes me independent of the location of my ioBroker computer." You can use this as such in this adapter too. Rtl_433 runs on top of Rtl-sdr. You can run rtl_sdr on a Raspberry Pi with the dongle in tcp_ip mode. Feed the params into rtl_433 (which my adapter supports) and it will connect to the remote computer for the data. Better instructions are in my README
@phillipssc Could You please explain the settings for tcp_ip mode. I'am not able to get it working. I get these messages:
rtl_433.0 2021-09-28 17:52:52.688 debug rtl_433 ret: -2:null rtl_433.0 2021-09-28 17:52:52.687 info Go to https://github.com/merbanan/rtl_433 to for installation instructions rtl_433.0 2021-09-28 17:52:52.686 error rtl_433 is not found on the system. Please check the installation of rtl_433 rtl_433.0 2021-09-28 17:52:52.682 info spawning: rtl_tcp=192.168.69.140 rtl_433.0 2021-09-28 17:52:52.626 debug Checking for dead devices... rtl_433.0 2021-09-28 17:52:22.625 debug Checking for dead devices... rtl_433.0 2021-09-28 17:51:52.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:51:22.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:51:12.681 debug killing rtl_433 rtl_433.0 2021-09-28 17:51:12.680 error rtl_433 disconnected, reconnecting in 100s ... rtl_433.0 2021-09-28 17:51:12.680 debug rtl_433 ret: -2:null rtl_433.0 2021-09-28 17:51:12.678 info Go to https://github.com/merbanan/rtl_433 to for installation instructions rtl_433.0 2021-09-28 17:51:12.677 error rtl_433 is not found on the system. Please check the installation of rtl_433 rtl_433.0 2021-09-28 17:51:12.673 info spawning: rtl_tcp=192.168.69.140 rtl_433.0 2021-09-28 17:50:52.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:50:34.582 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.dwd.0.connected rtl_433.0 2021-09-28 17:50:22.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:49:52.672 debug killing rtl_433 rtl_433.0 2021-09-28 17:49:52.672 error rtl_433 disconnected, reconnecting in 80s ... rtl_433.0 2021-09-28 17:49:52.671 debug rtl_433 ret: -2:null rtl_433.0 2021-09-28 17:49:52.669 info Go to https://github.com/merbanan/rtl_433 to for installation instructions rtl_433.0 2021-09-28 17:49:52.669 error rtl_433 is not found on the system. Please check the installation of rtl_433 rtl_433.0 2021-09-28 17:49:52.663 info spawning: rtl_tcp=192.168.69.140 rtl_433.0 2021-09-28 17:49:52.623 debug Checking for dead devices... rtl_433.0 2021-09-28 17:49:22.623 debug Checking for dead devices... -
@phillipssc Could You please explain the settings for tcp_ip mode. I'am not able to get it working. I get these messages:
rtl_433.0 2021-09-28 17:52:52.688 debug rtl_433 ret: -2:null rtl_433.0 2021-09-28 17:52:52.687 info Go to https://github.com/merbanan/rtl_433 to for installation instructions rtl_433.0 2021-09-28 17:52:52.686 error rtl_433 is not found on the system. Please check the installation of rtl_433 rtl_433.0 2021-09-28 17:52:52.682 info spawning: rtl_tcp=192.168.69.140 rtl_433.0 2021-09-28 17:52:52.626 debug Checking for dead devices... rtl_433.0 2021-09-28 17:52:22.625 debug Checking for dead devices... rtl_433.0 2021-09-28 17:51:52.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:51:22.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:51:12.681 debug killing rtl_433 rtl_433.0 2021-09-28 17:51:12.680 error rtl_433 disconnected, reconnecting in 100s ... rtl_433.0 2021-09-28 17:51:12.680 debug rtl_433 ret: -2:null rtl_433.0 2021-09-28 17:51:12.678 info Go to https://github.com/merbanan/rtl_433 to for installation instructions rtl_433.0 2021-09-28 17:51:12.677 error rtl_433 is not found on the system. Please check the installation of rtl_433 rtl_433.0 2021-09-28 17:51:12.673 info spawning: rtl_tcp=192.168.69.140 rtl_433.0 2021-09-28 17:50:52.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:50:34.582 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.dwd.0.connected rtl_433.0 2021-09-28 17:50:22.624 debug Checking for dead devices... rtl_433.0 2021-09-28 17:49:52.672 debug killing rtl_433 rtl_433.0 2021-09-28 17:49:52.672 error rtl_433 disconnected, reconnecting in 80s ... rtl_433.0 2021-09-28 17:49:52.671 debug rtl_433 ret: -2:null rtl_433.0 2021-09-28 17:49:52.669 info Go to https://github.com/merbanan/rtl_433 to for installation instructions rtl_433.0 2021-09-28 17:49:52.669 error rtl_433 is not found on the system. Please check the installation of rtl_433 rtl_433.0 2021-09-28 17:49:52.663 info spawning: rtl_tcp=192.168.69.140 rtl_433.0 2021-09-28 17:49:52.623 debug Checking for dead devices... rtl_433.0 2021-09-28 17:49:22.623 debug Checking for dead devices...@radi - Sorry I didn't see this sooner.
If you want to use TCP/IP to read an adapter. The remote host with the RTL-SDR dongle must be running rtl_sdr (rtl_tcp is included with the dist). Then on that host you would run the command:
rtl_tcp -a hostname -I <ip address>
On your ioBroker server you will need to run rtl_433 (which also requires rtl_sdr) and configure the instance with the ip address. You can take ioBroker out of the picture for testing and run the command:
rtl_433 -F json -d rtl_tcp://<ip address>:1234
In each case the <ip address> would be the address of the host with the RTL-SDR dongle - presumably 192.168.69.140
From the looks of the log provided rtl_433 is not installed on the ioBroker host yet
-
Hello @phillipssc,
I've installed your adapter yesterday and it works very well.
But I've got a problem when I restart the adapter in iobroker.The spawned subprocess ob rtl_433 won't be killed and on the next restart it' not possible to start a new instance of rtl_433 because the usb device is blocked by the older process.
Any advice?
-
Hello @phillipssc,
I've installed your adapter yesterday and it works very well.
But I've got a problem when I restart the adapter in iobroker.The spawned subprocess ob rtl_433 won't be killed and on the next restart it' not possible to start a new instance of rtl_433 because the usb device is blocked by the older process.
Any advice?
@w00dst0ck @phillipssc I have the same problem, is there a chance to solve the problem?
-
@w00dst0ck @phillipssc I have the same problem, is there a chance to solve the problem?
@elmar-faber as you can see, my question is unanswered.
-
@radi - Sorry I didn't see this sooner.
If you want to use TCP/IP to read an adapter. The remote host with the RTL-SDR dongle must be running rtl_sdr (rtl_tcp is included with the dist). Then on that host you would run the command:
rtl_tcp -a hostname -I <ip address>
On your ioBroker server you will need to run rtl_433 (which also requires rtl_sdr) and configure the instance with the ip address. You can take ioBroker out of the picture for testing and run the command:
rtl_433 -F json -d rtl_tcp://<ip address>:1234
In each case the <ip address> would be the address of the host with the RTL-SDR dongle - presumably 192.168.69.140
From the looks of the log provided rtl_433 is not installed on the ioBroker host yet
-
help can't get it to work in iobroker (TCP/IP)
what command on the RTL-SDR host
and which one in the iobroker adapter ??
Please be more specific command with example IP
@wolfi Sorry I missed this. I'm not sure what the test you did makes sense. What happens if you run
rtl_433 -F json -d rtl_tcp://192.168.178.153:1234? -
@wolfi Sorry I missed this. I'm not sure what the test you did makes sense. What happens if you run
rtl_433 -F json -d rtl_tcp://192.168.178.153:1234?@phillipssc
Could You please explain, what is going wrong here and how to fix it?rtl_433.0 2023-11-02 12:40:55.617 error Error: Parameter "parentChannel" needs to be of type "string" but type "undefined" has been passed rtl_433.0 2023-11-02 12:40:55.617 debug Creating State rain_mm on TFA-Drop-538256 rtl_433.0 2023-11-02 12:40:55.617 error Error: Parameter "parentChannel" needs to be of type "string" but type "undefined" has been passed rtl_433.0 2023-11-02 12:40:55.616 debug Creating State battery_ok on TFA-Drop-538256 rtl_433.0 2023-11-02 12:40:55.615 debug rtl_433:{"time":"2023-11-02 12:40:55","protocol":147,"model":"TFA-Drop","id":538256,"battery_ok":1,"rain_mm":2.794,"mic":"CHECKSUM","mod":"ASK","freq":433.902,"rssi":-4.738,"snr":15.883,"noise":-20.621} rtl_433.0 2023-11-02 12:40:28.695 debug rtl_433.0.TFA-Drop-538256: okThere is another Sensor for wind running well. The rainsensor has got new batterys and has changed the number to TFA-Drop-538256.
-
@phillipssc
Could You please explain, what is going wrong here and how to fix it?rtl_433.0 2023-11-02 12:40:55.617 error Error: Parameter "parentChannel" needs to be of type "string" but type "undefined" has been passed rtl_433.0 2023-11-02 12:40:55.617 debug Creating State rain_mm on TFA-Drop-538256 rtl_433.0 2023-11-02 12:40:55.617 error Error: Parameter "parentChannel" needs to be of type "string" but type "undefined" has been passed rtl_433.0 2023-11-02 12:40:55.616 debug Creating State battery_ok on TFA-Drop-538256 rtl_433.0 2023-11-02 12:40:55.615 debug rtl_433:{"time":"2023-11-02 12:40:55","protocol":147,"model":"TFA-Drop","id":538256,"battery_ok":1,"rain_mm":2.794,"mic":"CHECKSUM","mod":"ASK","freq":433.902,"rssi":-4.738,"snr":15.883,"noise":-20.621} rtl_433.0 2023-11-02 12:40:28.695 debug rtl_433.0.TFA-Drop-538256: okThere is another Sensor for wind running well. The rainsensor has got new batterys and has changed the number to TFA-Drop-538256.
-
Hello everyone.
You can check out this adapter, if you wish, at: https://github.com/phillipssc/ioBroker.rtl_433
I am relatively new to ioBroker having just started with it 7 months ago. I previously was running OpenHAB but liked the pure JavaScript approach to ioBroker.
When I saw how the Sonoff adapter was done I was interested if I could do something similar for rtl_433 data. For anyone wondering, rtl_433 builds off of rtl-sdr and uses largely former USB TV Tuner hardware to receive signals in the Rf spectrum (incoming data only). Often this will be at 433 MHz but it is not limited to that frequency. I use this to monitor temperature senders commonly used for weather stations and I have a large number of contact sensors as well. I have been running this adapter for about 6 months now, it is stable.
I created the adapter using the instructions on the site. Starting at: "npx @iobroker/create-adapter iobroker.rtl_433". I have run the utility through the adapter checker at: https://adapter-check.iobroker.in/ the only two errors I currently get are:
[E300] Not found on travis. Please setup travis
1
[W400] Cannot find "rtl_433" in latest repository
1Travis is set up - however it does not pass due to the lack of an RTL-SDR USB stick nor the rtl_433 software in their environment.
The command that fails, "npm run test:integration" passes locally on my worstation. Messages in the log alert the user that the environment needs to be set up and points them to the rtl_433 site https://github.com/merbanan/rtl_433 for installation instructions.I do not believe that my adapter will be in the latest repository until it is accepted by ioBroker at large.
I am trying to get this published using the instructions at https://www.iobroker.net/#en/documentation/dev/adapterpublish.md and this post seems to be the first step :)
Thanks, feel free to let me know what you think,
SeanHi @phillipssc, I have an ioBroker installation on Ubuntu and your Adaper works.
However, I had to set the protocols manually in the command line:
There are none in the overview:
Any ideas? What is wrong?
Support us
468
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge