ratgdo VS pymyq

How does this compare to a ratgdo? https://paulwieland.github.io/ratgdo/

But if you don't want all the wires for a MyQ replacement, I would look at the Ratgdo. It is also cheaper. If you have the skills, you can even solder it to the Opener's board along with powering it and have it hidden inside the opener.

https://paulwieland.github.io/ratgdo/ - With the ESPHome firmware you can control this from a web interface and not need a hub or anything.

ratgdo [https://paulwieland.github.io/ratgdo/] already exists and works great.

For the current roadblock, it appears it was due to cloudflare bot protection [https://community.home-assistant.io/t/the-current-state-of-m...]

Re: MyQ, check out ratgdo [1]. It's a lovely little hardware project that wires into Chamberlain/Liftmaster controllers and provides a local WiFi-only interface. It integrates perfectly with HA. It's a shame Chamberlain discontinued their homekit bridge, because it shouldn't be necessary to use a cloud integration to trigger a garage door.

[1]: https://paulwieland.github.io/ratgdo

Maybe my security background is shining through here. I guess we used to have "slashdotting" but that doesn't generalize well :)

I did do some napkin math to quantify how much that bad traffic may have been: HA estimates between 6857-25576 intallations of the MyQ integration. Let's say 16k clients. HA makes it really easy to detect and "add" the integration (which counts as an installation even if it's not configured), so, that's definitely not all clients hitting the API. Let's say it's 50%, so 8k actually using it. Most users just notice myQ is broken. Let's say some fraction retry, which would look the same as an extra user from a volume perspective. Call it an even 10k users (including repeat users).

The most recent change is after they broke everything past the OAuth dance. Let's say the OAuth request is 1kB. The retry code retries up to 5 times with exponential backoff. Let's say 5 requests over 10 min.

(5 requests / 10 minutes) * 1 request/user * 10k users = 5k requests/minute, or 83 per second, amounting to 83kB/s inbound.

There's no reason to assume those requests would synchronize, but I'm sure there's something (let's say every single myQ user updated at the same time).

If what they're saying is true, sounds like actually malicious botnet wielders can ransom the living daylights out of them. Given 1Tbs DDoS attacks they'd only need 6E-7 of the full bore ion cannon! ;-)

[1]: https://github.com/arraylabs/pymyq/blob/master/pymyq/request...