Replies: 7 comments
-
Hey mate, is there enough pins at all for? dry_contact_open_pin: D5
dry_contact_close_pin: D6
dry_contact_light_pin: D3 I noticed there's no USB on this device, do you flash it with a CH340G USB to TTL Serial Wire Adapter? |
Beta Was this translation helpful? Give feedback.
-
I flashed it with a random aliexpress TTL adapter i had lying around. There probably would be enough pins, i just was having trouble with my transistors so i kept disabling things until i realised where the problem was |
Beta Was this translation helpful? Give feedback.
-
Thanks for this. So without the dry contacts you're just using it as a sensor with any control functions, correct? |
Beta Was this translation helpful? Give feedback.
-
My garage door has a seperate pin for security+, so my wall button still goes directly to the garage and I can then use security+ to control the garage door from home assistant |
Beta Was this translation helpful? Give feedback.
-
Got it. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Something changed in the ratgdo main branch, I had to pin the external source to a commit from around the time of this post - like this:
Otherwise ESPHome failed to build the image. |
Beta Was this translation helpful? Give feedback.
-
Made a unit with this board yesterday and would like to add some notes: I used the following pin config: uart_tx_pin: GPIO14 # "red wire" TX
uart_rx_pin: GPIO35 # "red wire" RX
input_obst_pin: GPIO36 # Obstruction input
status_door_pin: GPIO5
status_obstruction_pin: GPIO4
dry_contact_open_pin: GPIO20 # Dummy, not used.
dry_contact_close_pin: GPIO19 # Dummy, not used.
dry_contact_light_pin: GPIO21 # Dummy, not used. The dummy dry contact pins are a terrible hack (I just chose pins that seem unused). I have concerns that they may be floating and trigger unexpectedly. I am waiting for ratgdo/esphome-ratgdo#264 to be fixed. I had an issue where the gdo would open every time the ratgdo rebooted, which I traced to the dummy GPIO pin I was using always showing a button press. I papered over it by trying other pins until I found one that returned an appropriate status, but it's far from a permanent solution. I ended up needing to add a 10k pullup on GPIO35 to make sensor status update properly. I suppose an internal pullup should have been used, but I haven't dug into why that isn't working on this board. Probably some aspect of that specific GPIO pin. Without the pullup, I could successfully toggle the door open and closed, but that's pretty much it. Paul, if you're reading this, consider making a wired version. I'm not sure what your stance is on this 3rd-party reverse engineering project (there seems to be no discussion of it on the official repos), but if there were a wired option from you I probably would have bought it. I dislike wifi for critical applications, such as gaining entry to my home. If WiFi drops, I might have no way to get in (only if I forget my keys, but misfortune tends to happen in clumps, doesn't it?). |
Beta Was this translation helpful? Give feedback.
-
Figured i would note that these do work - i had an easily accessible ethernet port near my GDO and was having issues with wifi dropouts, the only thing to note is that there really aren't many pins on these, so i ended up disabling all the dry contact stuff.
I ended up using these pins - others may work although this board is a bit weird with its strapping pins
You do end up needing to put your own YAML together anyways since you need to get rid of the improv serial stuff and swap wifi out for ethernet. I ended up with the following config:
Beta Was this translation helpful? Give feedback.
All reactions