podsync VS rtl_433

this is not something you would host and share with everyone, as transcoding is not cheap to host, it only makes sense for personal use only, also stuff like podsync has existed for a long time, which is basically the same thing missing the transcoding.

Completely unrelated to Tailscale, another option is Cloudflare Tunnel. It will also traverse CGNAT and expose your Plex server to the public internet. The only limitation here is that you must have a subdomain. I have my own paid one, but I don't see why you couldn't use something like https://freedns.afraid.org/ to get a free subdomain. Cloudflare Tunnel is completely free, and it comes with free TLS too. I use it with podsync to watch YouTube using my podcasting app and make the feeds available to my friends as well (which would be more hassle if we used Tailscale).

I'll turn them into podcasts with tools like Listenbox, YouCast, Podsync

Another option is podsync

If you’re technically minded you can spin up your own instance of https://github.com/mxpv/podsync - I ran one on Amazon S3 for a while until I found listenbox - but you could run on your own server too.

If you have the expertise to do so, the best way to consume YouTube is to use PodSync to map channels to RSS feeds consumable by any standard podcast player. No algorithm, no ads, just the content you actually want to see.

I'm looking to setup https://github.com/mxpv/podsync but I've have numerous issues with mapping the config file.

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