rtl_433 VS frigate

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

Am in to selfhosting and homeserver, finally got to try Frigate with some aliexpress camera that was not mine. Love it.

However, I have had success using IP Camera app with Frigate. https://play.google.com/store/apps/details?id=com.pas.webcam https://frigate.video/

Frigate https://frigate.video/ and ZoneMinder https://zoneminder.com/ come to mind. Blue Iris https://blueirissoftware.com/ is not open source but is what I prefer to use for my PoE systems ($80/yr)

Logger: custom_components.frigate Source: custom_components/frigate/__init__.py:201 Integration: Frigate (documentation, issues) First occurred: 1:59:34 AM (2 occurrences) Last logged: 1:59:48 AM

Engineering implies working within constraints. Most people in this realm only have to deal with the spouse acceptance factor as a limiter.

Went from openhab -> homeassistant -> Node-RED. Then sprinkle in MySensors, Frigate, and Double-Take, but not on just the entrance, go for the perimeter then defense in depth.

https://www.mysensors.org/

https://frigate.video/

https://github.com/jakowenko/double-take

- https://github.com/blakeblackshear/frigate/discussions/7932#...

I have found my frigate+ model to be much more accurate and crazy good even at night. Will be curious how things change when it snows here more often, since I've not submitted any examples of winter at this house yet.

According to the author of that PR, they're using 10% of 1 NPU core on 3 cameras: https://github.com/blakeblackshear/frigate/pull/8382#issueco...

The bottleneck instead will probably be the video stream decoding speed, especially as the SoC's hardware decoder isn't being used yet.