rtl_433 VS ntfy

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

Slightly related, but I've also been working on and off for a few years on my own Type 1 Diabetes management solution (https://github.com/algao1/iv3).

I haven't had time to work on it recently, but it uses ntfy (https://ntfy.sh/) to send alerts and such.

I was thinking of eventually incorporating some kind of automatic remedial solution eventually to help keep my glucose in range, but haven't had any time to look into it yet.

If you go to the settings, there should be a notification category, which then contains another menu "App Notifications" where you can see all the apps that are allowed to receive notifications, but I don't know if this will stop google play services to receive these identifiers.

I use GrapheneOS, so I don't have any google play services running, but for the apps where I need notifications I use https://unifiedpush.org/ (only a few apps implement it) and I host my own https://ntfy.sh server.

Kind of similar, in the early days of COVID, I accidentally discovered that my state's website would have test results available several hours before they sent out the "view your results" email. So I made a script that would check the site every five or ten minutes and then ping me as soon as the result changed to something besides PENDING.

In the course of that I stumbled on https://ntfy.sh/ which solved the notification problem without needing Twitter, and I've used it since then to let me know when long-running scripts complete.

I connect any app that supports https://unifiedpush.org/ to a self hosted https://ntfy.sh instance for fully self hosted push notifications

changedetection.io just donated to the awesome crew over at ntfy.sh

For further monitoring & alerting about critical cpu temperatures (unlikely now) for example, I plan to use notify & something else. Haven't thought about this much yet though.

I've started tossing https://ntfy.sh/ alerts into my Deno apps to get push notifications for things I'm interested in

ntfy.sh

If it was for fun and to learn how, that's fair. But are you aware of https://ntfy.sh?