secplus

Left out is a bit of the saga of ratgdo and that it's not actually open source hardware. There is a separate effort in that space - https://github.com/Kaldek/rat-ratgdo I have no issues with closed hardware and making money. However, the ratgdo maintainer will actively delete any references to other alternatives which I think is poor form and leaves a bad taste. Especially since his product relies so heavily on other open-source such as esphome, as well as the Security+2.0 protocol work that is out there (eg. https://github.com/argilo/secplus )

This sounds like HomeLink and is indeed more complex. My understanding of it is that they partner with lots of companies to support their rolling/fixed codes and remotes so that they can be paired to your garage door. I linked this in a sub comment, but the largest garage door maker in the US is Chamberlain [0] (which owns a ton of other brands) and uses known rolling code algorithms that can be decoded. [1] [0] https://www.chamberlain.com/ [1] https://github.com/argilo/secplus

The largest garage door manufacture in the US uses the Security+ and Security+ 2.0 algorithms that are rolling, but can be fairly trivially decoded to gain the serial number and rolling value of a remote. [0] This is how the flipper zero decodes remotes for playback later. [0] https://github.com/argilo/secplus

While rolling codes can be secure (KeeLoq [0] is a more secure example but has it's own issues), this [1] is an example of some of the weaknesses that can happen if a rolling code algorithm is broken. I have personally been able to capture, decode, encode, and transmit garage door codes using that python script and a HackRF (which can also be done with a flipper and custom firmware). [0] https://en.wikipedia.org/wiki/KeeLoq [1] https://github.com/argilo/secplus

For Chamberlain brands [0] there is some research that shows that their rolling code system (Security+ and Security+ 2.0) is quite easy to decode/decrypt [1]. This feature is supported in the flipper firmware, but is restricted (you can't create a custom remote, only clone is supported) without custom firmware. However, I'm sure you could decode a raw capture file if needed in a pinch. [0] https://chamberlaingroup.com/our-brands [1] https://github.com/argilo/secplus

A gentle reminder that the Security+ and Security+ 2.0 RF protocols have been reverse engineered (https://github.com/argilo/secplus). While they are not the most secure thing in the world, you can build a custom RF transmitter (remote) that is network connected. Having done some research into Chamberlain's products, I don't recommend anyone to use them if they have the choice.