Iām currently testing the software, in a non-permanent fashion, in a screen session, with the following command: sudo rtl_433 -F json -G | mosquitto_pub -t outdoor/rtl_433 -l -h 192.168.x.x
Ran out of time to see if sudo was absolutely necessary, it may not be. The user running the command, may just need to be in the dialout group, not sure yet, will investigate tonight.
Sure is! Works great as well.
I plan on embedding the RTL-SDR with the Raspberry Pi Zero, into some kind of 3D-printed, all-in-one case; Iāll design it once I get the software all figured outā¦ So itās basically a remotely managed, 433 -> MQTT bridgeā¦ Should be fun!
So I got my device and installed as per your instructions. However when I run sudo rtl_433 -F json -G | mosquitto_pub -t outdoor/rtl_433 -l -h 192.168.0.8
Connection Refused: not authorised.
Do you have authentication enabled on your MQTT broker?
Might need to add -u -P to the command for username & password, respectively.
So:
Right it was the username and password needed. However it runs well but when I transmit a rf signal from my remote it doesnāt pick it up (the transmitted code) which is very surprising. Do you experience that?or am I doing something wrong?
Youāll probably have to do a little troubleshooting to figure this out. Try running:
rtl_433 -G
It wonāt pipe to MQTT, but it will try and decode all known signals.
If that doesnāt work, check to see if your device is in the āsupported device protocolsā table, on the github page.
If that still doesnāt work, you might have to work on adding your device, to the supported devices. See the āSupporting Additional Devices and Test Dataā section on the github page.
OK so my DVB-T dongle arrived from chinaā¦ complete with crappy aerial and remote control
Turns out its a FC0012 tuner model.
Iāve connected it to my x86 ESXi server and passed the USB through to an Ubuntu 16.04 VM (this one happens to be also running docker + hass.io).
I needed to blacklist the DVB kernel modules to get rtl_433 working.
But I have problemsā¦
Firstly I cannot receive and decode the signals from a known supported device (protocol [44] āCurrentCost Current Sensorā).
When running rtl_433 -a I can see a periodic packet every 6 seconds, which is what I expect from the current costā¦ but its not decoded when running with rtl_433 -R 44 - I just see nothing.
Secondly whenever rtl_433 quits it seems to leave the USB device in a non-functioning state, and I need to pull and re-insert the dongle. If I donāt do this then next time I run rtl_433 it exits as soon as it calls out to rtl_sdr - i.e. pretty much immediately. Weirdly this seems to be related to the version of rtl_433/rtl_sdr being run - when I ran an out of date version of rtl_433 from docker (https://hub.docker.com/r/sysrun/rtl_433/) it didnāt have the same issuesā¦
I also tried with very latest versions with a new docker image I forked from here: https://hub.docker.com/r/hijinx/rtl433test/
The latest version has support for more devices, but exhibits this āonly works on 1st executionā issueā¦
(BTW I also compiled and ran rtl_433 directly on the ubuntu vm with same result)
Is it my cheap and crappy dongle? Should I try with a device from reputable (and more expensive) brand?
Or do I need to fiddle about with any of the tuner parameters? (and if so, how to I find out what?)
My problem is more with the rtl dongle I thinkā¦ itās weird that it works great with an old version of rtlsdr and rtl433, but if I use latest rtlsdr and compile rtl433 from source itās working only 1st time I run them never again until I pull and reinsert the dongle.
Note that this image hardcodes the tuner offset ppm (rtl_433 -p switch) to the offset for my tuner.
If you need to change this you can fork my repo and change the rtl2mqtt.sh script to update the ppm value or remove the -p switch and get docker hub to build you a custom image.
Ultimately I hope that the problems I have with rtl_433 crashing with new version are due to my cheap and crappy tuner rather than the software. I have another tuner on order to check this. If that one works well Iāll update the rtl_433 docker to be a hass.io addonā¦
If I have 3 sensors for my 2gigs alarm system that are on 433mhz, do I have to synchronize them with the usb key ? How does it know that itās a door sensor or a movement sensor ?
