Vince, Nice write up. Begin shameless plug… Since I am heavily invested in reading things from MQTT, I just run rtl_433 as a separate service and subscribe to the topic. I did this primarily to get the data in a service and secondarily to get sensors that were not ’mapped’. The service invocation, ‘ExecStart=/usr/local/bin/rtl_433 -M utc -F mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]’ And one topic config looks like this [[topics]] ignore = True [[[message]]] type = individual # Upright freezer (basement) [[[rtl_433/weather-data/devices/Acurite-606TX/77/temperature_C]]] ignore = False unit_system = METRIC name = extraTemp8
It may seem more complicated, but since I was invested in MQTT, it actually simplified it. This was primarily because I could treat rtl_433 as a separate service End plug On Wednesday 6 March 2024 at 16:14:25 UTC-5 vince wrote: > In working with another weewx user to help him gets his SDR station > online, it was clear that lots of people (like me) have some problems > really understanding some of the rtl-433 and sdr documentation that is out > there. > > After working through it end-to-end a few times on both ubuntu and on a > raspberry pi, I wrote up the whole setup as a howto with examples mainly > for future-me but I thought it might be of general interest. At worst a > google search should find it for future folks trying to battle SDR into > submission :-) > > The howto and a small github repo with a patched/enhanced fork of the SDR > driver is at https://github.com/vinceskahan/sdr-howto if you have > interest. Start with the toplevel readme file then read the howto.txt file > for how I got it working here. > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e3c6f100-f5b0-422d-a361-58d12d8438ban%40googlegroups.com.
