Yes, you can. For the security 2.0 openers you have to solder two jumper wires to the button. Pretty simple to do. If your remote has other buttons like the light button, you should be able to the same.
I bypassed the Myq cloud many months ago using a modified 883LMW, Zooz Zen17 along with a reed switch. Works great!
@billyjoebob999 When you use zooz zen17, you donât get the audio warning beeps when you trigger close remotely right?
This could be a safety concern if you have children aroundâŚ
Thatâs true with most of the alternative options. Easy enough to throw in a siren to alert if you want, or flash the lights.
I donât see why anyone would prefer this over ratgdo. For a Security+ opener, ratgdo gives a lot more functionality for approximately the same net cost. Discrete open and close, light, native door status without reed switches.
And⌠no soldering required. Not that soldering is a big deal, but for a lot of folks, the tools are just another extra expense and time suck, along with the cost of the extra controller.
I seem to recall Paul mentioning somewhere that the beep alert was the only feature he couldnât access from RatGDO but he couldnât figure out why. The only way to make the thing beep at all from standalone opener, is by hitting the learn button. Somehow the MyQ app is the only way to trigger the alert mode. I guess it would be better anyway to just toss a speaker out into the garage. Whenever homeassistant triggers the garage door to close, toggle the garage lights that you now have access to in HA, and spool up some kind of funny jingle. That would be a win anyway over that annoying beeping for the whole neighborhood to listen to.
Does one ratgdo need to be connected to each door?
@JermaNoiD Not a bad idea. ButâŚwarning lights require that people near the garage door notice the lights going off, if they are looking away, they wonât see this warning.
Audio warning should have a higher success rate, assuming youâre not deaf.
As already stated, it does not but doesnât sound like any solution does. You can add the jumper wires to the light button and create an automation to flash the light before the door closes.
That is correct.
Personally, I never even heard of ratgdo until these threads started popping up about myq issues. My issue is ratgdo seem to be pushed as the ONLY solution when that just isnât true. Iâm sure itâs a great product and iâm sure it will work well for those that go that route.
I did look into ratgdo a bit. Found a video on YouTube where Paul was being interviewed. What I gather from that interview was the ratgdo is emulating the security protocols. Since he had to reverse engineer there is a possibility that Chamberlain could go after him especially if he used some of their code or Chamberlain could modify their firmware to stop ratgdo from working going forward. I also got the impression he doesnât really want to maintain this long term.
If I was looking for a solution today, I would still choose to modify a wall button and use a smart relay. I would just have better piece of mind and no longer would have to worry about the whole cat and mouse game.
At the end of the day everyone should know what all their options are and choose what is best for them.
Iâve been seeing people rig the RatGDO up with just the 3 wires. From my understanding all the features of the door are accessible over those 3 wires. On the schematic there are optional electrical nodes on the adjacent side of the board that provide a momentary switch for the doors and lights with grounds during the obstruction and doors-open events. I donât understand the significance of that side of the board. Is that to emulate a dry-contact scenario? Just seeking some clarity.
Would you please explain how to do this?
The general idea there is to disconnect the garage doors from wifi and just remove the MyQ account completely to prevent any firmware updates. Although I think theyâd require a hardware change if they wanted to cirumvent the ratgdo. Just spitballing here a little bit, but they can update the firmware of the garage door motor if they wanted, but I donât believe they can update the wall button firmware. If they made any drastic changes to the protocol to prevent this, theyâd be risking the wall buttons breaking for people as well. Plus the software is open source although he doesnât want to open source the hardware which is easily reverse engineered anyway. Paul is still planning on homekit, but the firmware is still open source for the community to run with. Ultimately there is no 100% winning solution at the end of the day as everyone has different requirements and preferences for success. For my automations I need to know where to door is at and the direction itâs moving. But I prefer not to have extra wired or wireless sensors if i can forgo it as itâs just another battery to monitor or cable to hide. And my zigbee network isnât the best as I have wireless interference I canât really avoid. Plus I like Paul just for throwing a fk-you wrench directly at Chaimberland.
By no means the only solution, several have been discussed, but nothing else does as much or is as simple to implement.
I think itâs a very real possibility.
BUTâŚ
The board schematics are in the wild and the software is open source. Even if they stop him from selling the devices, the basic solution would live on.
Very difficult to do. It would be difficult to find signaling that would break ratgdo without also breaking all the installed wall consoles.
They could always come out with Security+ 3.0, but I donât see existing units breaking.
@Lash-L I just wanted to thank you for all the work. I am sorry you might just have to call this one done. Unless HA can get on the partner list. Seems they donât want to play ball with us HA folks⌠There is a light the end of the tunnelâŚ
More time to work on the RoboRock integration. 
I ordered a RATGDO yesterdayâŚ
Thanks again.
For those interested in the warning beeps (@actran70, @billyjoebob999), this seems to have been worked out on the ESPHome side of Ratgdo and is in the process of being implemented. TTC Controls by mulcmu ¡ Pull Request #43 ¡ ratgdo/esphome-ratgdo ¡ GitHub Basically, as I understand it, when you simply close the door, the warning is not triggered, but if the door is closed on a delay (Time to Close (TTC)), it will flash and beep until the delay is up. The app would just be triggering that delay as a safety feature. Personally, I always thought it was a bit long, and therefore annoying, so if I can shorten that delay a bit, I will be very happy.
Wow, those are impressive and quite possibly excessive, but I think youâre good.
For my house, we donât have kids around often, and Iâm not that concerned about the door lowering on someone because itâs so easy to stop it even if youâre standing right below it. Just stick out a leg. Leaving any warning would really be a just-in-case sort of thing.
Also, some of the relay switches does have the setting to turn this switch into a âgarage door modeâ where it would release back to off automatically within 1 sec, to simulate a manual button press. This is what I did with Zooz ZEN51. My write up here.
(I understand the write-up is not about MyQ, but the point here is to show that there are indeed dry contact relays out there that can do momentary.)
What are the details of Home Assistant Tailwind support? I couldnât find an integration or custom component searching on Tailwind.
