unleashed-firmware VS rtl_433

I got one not too long after the official launch and I've used it a decent amount (granted I am in cybersecurity and have a more real-world use cases then the average person). My favorite use case is the IR remote since phones no longer have IR blasters. It's saved me twice so far in having to buy/find a remote for something.

One thing people don't realize is that the custom firmware [0] that you can run allows you to receive and transmit on a wide range of frequencies under 1Ghz. Lots of things use that range (garage doors, gates, fan remotes, etc.) and are not very secure. I think that this will be a time looked back on where it's possible to interact with those devices without having to buy a custom PCB transmitter or somewhat expensive and complex SDR.

[0] https://github.com/DarkFlippers/unleashed-firmware

Check it out at https://github.com/DarkFlippers/unleashed-firmware/releases/tag/unlshd-043

Take a look at my IR Scope. It’s pretty simple. There’s an IR worker that handles talking to the sensor on a second “thread”. The worker has send/receive functions. https://github.com/DarkFlippers/unleashed-firmware/blob/dev/applications/external/ir_scope/ir_scope.c

Instructions for 3rd party firmware are to download the zip to files, then share with the Flipper app. I do not see the flipper app in the share sheet, or selectable if I click +. I've rebooted. I've also opened the app and force quit several times. I see I'm connected via the app to the device, so I know connectivity works. I just updated to iOS 16.4 and not tried this prior, so perhaps a 16.4 bug?https://github.com/DarkFlippers/unleashed-firmware/blob/dev/documentation/HowToInstall.md

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