Besides the door operation ratgdo gives access to the light, motion sensor, obstruction sensor and can lock out remotes. It's easy to physically install and potentially a few $ cheaper than relay/sensor method. But there's a squeeze to get the juice.
You'll have to modify the build files for Hubitat limitations. And then figure out drivers.
Right on, I know that ratgdo can give access to add'l bells-&-whistles if your opener has said goodies, and that's pretty darn cool.
Just seems like there've been a couple folks here so far that don't seem much interested in jumping thru the MQTT/ESP hoops necessary, so I'm simply curious if those additional capabilities are worth that much to them?
Again, I'm genuinely not trying to stir any pot here (I got no dog in this hunt!), I'm just curious.
I love this. I'm able to lock out the remotes when we're sleeping now for a little more peace of mind.
Yeah, that's a nice one, no doubt!
I'm currently having analysis paralysis when it comes to my garage door opener. I had an old one with a go-control that died from a lightning strike and I've been without a GDO for a couple months. I've looked and I can't seem to find anything I can confirm doesn't have security 2.0. I already have hubitat, a lutron hub, and broadcom hub, an old macbook running homebridge, and a ring lighting hub. I really don't want to add another hub or something like a raspberry pi just to get my GDO connected...
Like others here, the idea of the ratgdo sounds appealing (I've always wished I could control the light on the GDO) but don't want another bridge type piece of software to have to think about.
I'm hoping at some point some firmware or other solution for the ratgdo is developed that direct allows local control via HE.
At this point I'm thinking about just doing something like the garadget dry contact adapter, or going with a genie GDO with their OEM dry contact adapter.
Konnected just announced a new product that is based on ratgo and can control the light and knows status of the beam sensors. A bit pricey and estimated ship date in March:
Curious how you have the door open/close button setup in HE? I have the ratgdo setup in HA and added to HE with the home assistant bridge. All the HE entities/buttons work except for the open close. HE sees it as an unknown binary sensor. I tried a few options, but none seemed to work.
Part of the setup in Hubitat Package Manager when installing the HA Bridge is choosing the generic drivers that will be available. You want to make sure that you selected the Generic Garage Door driver. It should look like this when it's working correctly...
Go into HPM and View your existing Apps and Drivers. It SHOULD list a bunch and include one for the garage door..
If you don't see that, you may have to re-install or update the app to make sure those drivers are available for you.
Do an HPM Repair. Changes were made to HADB that need a Repair.
I am using the ESPHome driver for ratGDO, itās available in HPM (though not the latest version) and works directly with the ratGDO device locally. Look for ESPHome and install it along with the ratGDO driver
I tested that out just now and it works well though it's a bit confusing since it's just a driver and not an app. You have to go and add a virtual device under Devices, then choose the ESPRatgo driver, then put in the IP Address of the device in the parameters of the virtual device, then Save. Once you save, you can control the garage door natively. Pretty slick!
Yeah, there really is no reason for an app, though one could be easily addedā¦ Should I?! Not sure how itād be delivered, since the driver is part of the ESPHome library.
Really, the only thing the app should do (if it needs to exist at all) is allow a user to create a given ESP32 device, ask it what the IP of the device is and what they want to name it, then just create the device for the user with the IP already configured. That way the device is already ready to go without having to add a virtual device and configure it (which is unintuitive for novice users).
Agree it is confusing but there are many inbuilt integrations that require the same steps of creating a virtual device first: Denon and Onkyo AVRs, Twilio SMS, Pushover, etc. So nothing unique with this driver and I would say an app is unnecessary overhead.
i recently worked on the HOMEKIT version of RATGDO, i added sec+1.0 to it
still sitting as a PR (for some reason) but I gotten very familiar with the code.
i improved the issues with SEC1.0 and have another idea that will make it perfect
(but it required some hardware improvements)
there is webserver on the esp8266(which now serves the config), could use that to directly control GDO
i dont know the HE platform well enough to make a driver really quick...
could do it via simple HTTP Gets
http://ipaddress?GDO=open
I just need to work with someone on the Hubitat side
You are aware that there is a Hubitat driver that directly interfaces with ESPHome on the RatGDO, arenāt you?
Only thing to note is that you need to turn off ESPHome encryption because the driver does not currently support ESPHome Encryption. Otherwise, works fine.
yes. i am, and i think at one point i had the ESPHome fw on it
and had some issues with SEC1.0
i have learned so much since then, i prob revisit
Then you might want to add the same SEC+1.0 changes in a PR for the Hubitat ESPHome driver so that can work with ESPHome security.
Recently setup a hubitat and was able to get the ratgdo to work following the well written instructions via MQTT. Is there a method to add a control to the hubitat dashboard to control the ratgdo? I've played with a few of the control types (button, switches, garage (control), etc.) - but haven't found a solution. The button is the closest - I played with the JSON command field and thought that I might be able to control it if I used the command-open or Open() function, but have not been successful yet. Any pointers would be apprecaited.
Download the Hubitat app
