-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ratgdo 2.52i w/ Overhead Door Odyssey 1000 - Obstruction Sensor Works, But Can't Control Lights or Door #294
Comments
Try the dry contact control protocol. |
I am having the same issue. This door opener does not have the required ports available for the dry contact method. |
Works for me with the dry contact control protocol with the red ctrl wire attached to the (4) black (BWC) contact on the opener, the white grnd wire attached to the (3) white (BWC) contact, and the black obst wire attached to the (2) orange (STB) contact. Toggling the door open and closed is the only capable function. Would be interested if there are other wiring configurations that would enable other functionality, i.e. light trigger. |
The only thing I can get to operate this gdo is the button press with dry contact mode and wired up like the previous comment says, the cover stuff doesn't work at all. Button doesn't show in HomeKit properly. Flashed to the HomeKit and nothing works there either. |
The HomeKit firmware does not yet support dry contact control. Limit switches are required in order to have status feedback as well as discrete controls. Without them the only thing that will work is the toggle control. |
Hi folks,
Quick Details:
Hardware: ratgdo 2.52i
Firmware: 2.56 (Current), Also tried 2.57
GDO: Overhead Door Odyssey 1000
GDO Control Protocol: Sec2 and Sec1
Overall my issue seems very similar to #122, but the solution mentioned in that issue (using terminal 0 instead of 1) doesn't really translate to my situation since I have a different model gdo and pin layout.
I can open my garage door via the wall switch fine. Before I swapped the wiring (shown in the picture below), my obstruction sensors didn't light up and I couldn't use the wall switch to open/close.
Now, at some point, I thought that I read somewhere that Overhead door openers were just rebranded chamberlain or liftmaster units, but I can't actually find a source for that anymore so I may have dreamt it up. So it's possible that ratgdo will just not work on my door opener. However, it does seem to be able to get obstruction status fine, as I can see it updating in home assistant properly. Still, perhaps there are slight differences in the control protocol that overhead door has made to make it incompatible or non-standard, I obviously don't know enough about all of this to say. I do suspect there might be slight differences since they obviously want to sell their own "smart panel" to control your opener and make you pay a monthly fee and all of that.
I can say that I had to wire it up slightly differently than I was expecting based on the wiring diagram. Here's a picture of how my gdo was wired up before I installed the ratgdo (top) and after (bottom):
And this is a picture of the wiring on the ratgdo (note: Garage door wires were bigger so I spliced smaller jumpers to make it easier which is why they aren't the big white wires shown in the picture above):
I've attached logs I took while telling the door to do various things, like open and close, turn on / off the light, etc. It seems like it was able to get rolling codes and it thinks it's writing them successfully, but the door doesn't actually do anything. I've tried with both sec2 and sec1 control protocol, which is why the two logs.
The thread mentioned above also mentions resetting your client id in order to get new rolling codes, but I don't see where to do that in the web interface.
I also tried with firmware 2.57 flashed on the ratgdo, but same results.
I've also attached the owners manual for my gdo, just in case there's anything useful in there.
Appreciate any tips anyone might have on things I could try!
esp-web-tools-logs (sec1).txt
esp-web-tools-logs (sec2).txt
Odyssey Destiny Owners Manual.pdf
The text was updated successfully, but these errors were encountered: