ambient2mqtt VS rtl_433

One of the most unexpected and wonderful things about my Ambient Weather station is that within its settings app, you can configure an additional URL for it to send periodic pings to. In my case, I whipped up ambient2mqtt[0] as a way to capture the output of the weather station locally and do what I want with it - in this case, post the data to MQTT and InfluxDB.

A few years after that I also purchased a Purple Air PM2.5 monitor. I was pleasantly surprised that this device exposes a local REST interface for polling the data. Naturally, I wrote purpleair2mqtt[1] to pull the data from that and post to MQTT and InfluxDB.

Together these two applications and pieces of hardware give me a great view of the weather conditions. And like the author of the article, I found that other weather information tended to be off significantly. Doubly true as I live next to a lake in a rural-ish part of New England which is about 500ft higher than the city and airport where our weather data comes from. Over the last couple of years I've been pleased to see that my data has become the defacto source for weather data in my town (I publish it to numerous sources) and that the PM2.5 information gets brought into lots of reports, including the EPA's AirNow system - which is great, because it doesn't look like there's another PM2.5 monitor within 20 miles of me.

[0]: https://github.com/pridkett/ambient2mqtt

And there's a multiformat receiver block too: https://github.com/merbanan/rtl_433

pi@pi4b8:/etc/systemd/system $ cat rtl_433.service # based on https://github.com/merbanan/rtl_433/issues/1651 [Unit] Description=RTL_433 service script StartLimitIntervalSec=5 Documentation=https://github.com/merbanan/rtl_433/README.md After=syslog.target network.target [Service] Type=exec ExecStart=/usr/bin/rtl_433 -C si -F mqtt # Restart script if stopped Restart=always # Wait 30s before restart RestartSec=30s # Tag things in the log # View with: sudo journalctl -f -u rtl_433 -o cat SyslogIdentifier=rtl_433 StandardOutput=syslog StandardError=syslog [Install] WantedBy=multi-user.target

For example, rtl_433 has the spec for an X10 sensor say I know what data I want to put where, is there some tool/site I could enter in what the "specifications" of the signal waveform are and the data I want to send as a byte-string or binary-string and it would create a playable .sub file for me?

For "outdoor distances" I'd probably stick to something LoRa or 433MHz based. YoLink has quite a few options using the LoRa protocol. I use basic 433Mhz based AcuRite sensors paired with an RTL-SDR dongle connected to a machine running RTL_433, and use Home Assistant to trigger automations and alerts.

866-868MHz is SRD/ISM band (in UK/EU). Can be things like energy meters, TPMS, medical devices etc. Try rtl_433 on it.

I'm trying to add a Honeywell doorbell to Home Assistant by using the RTL-433 GitHub project/program. When I run the program the SDR dongle is detected but it doesn't display anything when I press the doorbell (the image shows what I see after running the program and pressing the doorbell). I have also tried Honeywell Activelink (FSK) aka [116], so I have tried both 115 and 116 decode protocols.

rtf_433 IoT & embedded device signal receiving https://github.com/merbanan/rtl_433