This is brilliant! Thank you! I'll give it a shot. On Wed, Nov 16, 2022 at 1:15 PM bell...@gmail.com <bellri...@gmail.com> wrote:
> I use ''rtl_433 -F mqtt://localhost:1883' and it publishes directly to the > following topics: > rtl_433/<hostname>/devices[/type][/model][/subtype][/channel][/id] > rtl_433/<hostname>/events > rtl_433/<hostname>/states > I then subscribe to > 'rtl_433/<hostname>/devices[/type][/model][/subtype][/channel][/id]' as > 'type = individual'. > > If you want/need to continue piping to mosquitto_pub, look at > https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-additional-options#msg_id_field. > Then you can use the 'ignore' option with the appended 'id'. > > rich > > On Wednesday, 16 November 2022 at 12:48:36 UTC-5 bryan...@gmail.com wrote: > >> I'm currently running Weewx 4.9.1 and using WeeWX-MQTTSubscribe to >> capture data from 2 separate RTL SDR's. One of the RTL-SDR devices is >> listening on 433.92 and is picking up weather data from a couple nearby >> weather stations. One of the weather stations I'm listening to has a bad >> wind sensor, so I do not want the wind data from that station, the other >> station has good wind data so I do want that data. These two stations are >> from the same manufacturer and fall under the same device decoding protocol >> ( [40] Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning, >> 899 Rain, 3N1, Atlas). >> >> The other RTL-SDR is listening on 915.00 in order to pick up pressure >> data from another sensor. >> >> When using >> `rtl_433 -F json -M utc -R 40 | mosquitto_pub -t weather/radio -h >> localhost -l` >> >> I receive all packets from both stations and pass that to the >> WeeWX-MQTTSubscribe driver where I have set up the various fields and map >> them to weewx. For example, the wind data: >> >> [[topics]] >> unit_system = US >> [[[weather/radio]]] >> >> ... snip ... >> [[[[*wind_avg_km_h*]]]] >> name = windSpeed >> >> [[[[*wind_dir_deg*]]]] >> name = windDir >> >> ... snip ... >> >> since both stations emit, for example, 'wind_avg_km_h', I don't have a >> way to filter out one of them (the bad one) so I end up getting some >> garbage data in the mix with good data. >> >> My question is this: since these two stations are the same 'device >> decoding protocol' (40) is there a way to differentiate between the json >> data coming from the one vs the other? The both have different [[[[id]]]] >> fields, the one I want has an ID of 3522 and the one I don't want wind data >> from is ID 2849. >> >> Essentially I want to keep data from both devices but exclude just the >> wind data from one of them. >> >> Thanks much for any help you all can provide. >> >> Bryan >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/yzk4qXDa87o/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > weewx-user+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/ef1bfb7c-0204-425d-84bf-b6b13a56bb57n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/ef1bfb7c-0204-425d-84bf-b6b13a56bb57n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPXDAYZh26%2BH80uPf_oMvo-EpBAYT6MWj2V-pkQ5brdGN5N7EA%40mail.gmail.com.
