foreverimagining
commented
5 months ago Yours sounds like it might be doing some extra funny things, so I'm not completely sure I'll be able to help, but I will proffer what knowledge I have.
Firstly, I'm assuming that you are using this schematic since I only see 3 resistors. This one has worked for a number of people, but others have only had luck with this other schematic, which is a little more up to date and based on my original v2.5 RATGDO. That's a good place to start troubleshooting.
Also:
I used 2n7000 MOSFETs (and also tried BS170, same problem)
The 2n7000s have been notoriously finicky, so it's probably better to just stick with BS270s, which have recently been recommended as much more suitable and, therefore, reliable. I pulled up datasheets for the BS170 to compare to the BS270, and the BS170 looks like it has a wider range for the Gate Threshold Voltage. Actually, it appears to have the same range as the 2n7000, so it's probably also not as good of an option as the BS270, though, I am by no means well-educated on the matter.
A few other things I can remark on:
I flashed it via the ESPHome website installer here, using "Security + 2.0; round yellow learn button" (first row, first pic) and "ratgdo v2.5x; v2.5, v2.5i, v2.52i, v2.53i (black PCB)" (second row, first pic) which seemed to work fine. (It is the correct software?)
My GDO should be Security 2+.
This looks like the correct firmware to me since you are using an ESP8266 not an ESP32, and yes, you appear to have a Security+2.0 GDO with a yellow learn button that is not a jackshaft opener. That being said, I don't know if there is a specific difference with the D1 mini PRO that might affect the compatibility somehow. If all else fails, this could be the problem.
I also switched D1 and D4 pins at my ESP8266 (because I read something about possible different PIN mappings)
Previous versions of the RATGDO used D4, which is pulled HIGH at boot, and it did cause some GDOs to open on their own occasionally when the ESP restarted. I have been under the impression that they fully opened, and then, didn't close on their own, so yours seems like it might be doing something different, unless my understanding is incorrect. The firmware for v2.0 should be using D4, but the firmware for v2.5+ should be using D1. That is, unless you change the yaml file in ESPHome to assign different pins, but it's easier to just use the original pins and move the wire on the breadboard if necessary.
I also tried with and without connecting the black OBSTACLE wire but noting changed
Yeah, this probably won't benefit your issues because the obstruction sensors can totally cause their own issue, and you don't seem to be having it. Basically, the close command doesn't work if you don't have the obstruction sensors connected, though toggle still does. It's a weird thing.
(Off-topic: as far as I understood, the green +/- battery terminals should have 30V but I measured 0V. It that correct? I have no backup battery installed but also don't know where to do that. Once this all works, I thought about powering the ESP via these terminals, if possible.)
I don't have a battery backup, so I won't be helpful here, but other people have made RAT-RATGDOs that run off their battery backups, so it should be possible. You can take a look at what other people have done, unless someone who knows a bit more about it wants to chime in.
And one last word of advice: loose connections are the absolute devil. We frequently have people having trouble with breadboards that seem to be unable to work out the problems no matter what they try, and it may ultimately come down to loose connections. There never seem to be problems with the PCBs that use SMD parts, and there don't seem to be many problems involving soldered perfboards, either (besides 2n7000s). If you try everything else and nothing works, you may just have to go all-in and solder something a bit more permanent and give that a go. There can also be loose connections at the GDO terminals, though, if they don't bite down well enough on the wires, so really, there are no guarantees.
youaintnobody
CodeFinder2
Hi,
I tried to build a breadboard circuit (prototype) based on a Wemos D1 mini Pro which looks like this):
I can also try to draw this if needed. I (and also a friend) double-checked the wiring and it should be correct (?). Resistors also measured to be 9,99kOhm. I used 2n7000 MOSFETs (and also tried BS170, same problem).
This is how I wired it to the GDO:
I flashed it via the ESPHome website installer here, using "Security + 2.0; round yellow learn button" (first row, first pic) and "ratgdo v2.5x; v2.5, v2.5i, v2.52i, v2.53i (black PCB)" (second row, first pic) which seemed to work fine. (Is it the correct software?)
My GDO should be Security 2+.
TL;DR: once my ESP is connected, my GDO does strange things (opening/closing) and I don't see any status in ESPhome.
The Problem When I connect it to my GDO and power it up, it immediately starts moving the garage door (GD). However, this just happens for about a second and then the motion is interrupted again. After about another second, it starts moving again. This repeats a few times until the GD finally closes completely and nothing more happens. In ESPhome's web UI, there seem to be no (valid) status reporting for the GD(O) and I am also unable to control the GD, light, etc. After some "back and forth" of the GD, these spurious commands seem to stop. Note that I can control the GD using my normal (original) remote control (before, meanwhile and after these strange open/close commands). To my understanding, this seems to be an issue with the TX/RX circuit part but I do not see any issue.
Not sure if this is a helpful log but anyway:
I can also try to collect a log of the strange open/close attempts after powering it up (please let me know how I should do that ideally).
(Off-topic: as far as I understood, the green +/- battery terminals should have 30V but I measured 0V. It that correct? I have no backup battery installed but also don't know where to do that. Once this all works, I thought about powering the ESP via these terminals, if possible.)
What I already tried I also tried with and without connecting the black OBSTACLE wire but noting changed (but AFAIK, this should't have an effect anyway). For try-and-error, I also switched D1 and D4 pins at my ESP8266 (because I read something about possible different PIN mappings) but that didn't help. In fact, after that, no spurious open/close commands where triggered anymore but also still no status avail (and still no control using ESPhome).
Remarks Generally, my GD is working just fine. I also connected a wired wall switch (as part of my GDO system, using the same red and white terminals) and that worked fine as well.
Any help/hints/advice is highly appreciated. Also, please let me know if you need more logs (and how I should collect them).
Thank you very much! :-)