ratgdo / esphome-ratgdo

ratgdo for ESPHome
GNU General Public License v2.0
308 stars 75 forks source link

Garage Door - RATGDO - Security 1.0 - No Stop Cover Or Percentage Open + Logs Flooding #224

Open Steven4x4 opened 3 months ago

Steven4x4 commented 3 months ago

I originally posted this in the wrong github area. Hopefully this is the right one.

The problem

I'm new to ESP Home. RATGDO is my first ESP Home device. I'm not entirely sure what ESP Platform the v2.53i is.

When I go to the ESP Home Devices Webpage Directly... With the RATDGO v2.53i board with the Security 1.0 firmware it is flooding the logs every other second with: 14:46:32 | [D] | [ratgdo:210] | Lock state=UNLOCKED 14:46:33 | [D] | [ratgdo:204] | Light state=OFF 14:46:33 | [D] | [ratgdo:210] | Lock state=UNLOCKED 14:46:35 | [D] | [ratgdo:204] | Light state=OFF 14:46:35 | [D] | [ratgdo:210] | Lock state=UNLOCKED 14:46:36 | [D] | [ratgdo:204] | Light state=OFF Video - https://www.youtube.com/watch?v=F8vxAVPcjjo In the video Security 1.0 on the left, security 2.0 on the right.

For reference on the Security 2.0 firmware, it only does this every 5 minutes. (Which is about what I would expect.

Secondly, inside of home assistant, on the integrations > esp home > garage door device. When you try to use the feature where you can open to a specific percentage. It does no work on the 1.0 firmware, but does work on the 2.0 firmware. I reach out to RATDGO directly, and he directed me to post here. Additional, Open Cover works, but Stop Cover does not.

Which version of ESPHome has the issue?

2023.12.9

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

2024.1.6

What platform are you using?

ESP32

Board

RATGDO v2.53i

Component causing the issue

No response

Example YAML snippet

ESP HOME YAML:
substitutions:
  name: ratgdov25i-ca08b2
  friendly_name: Garage Door 1
packages:
  ratgdo.esphome: github://ratgdo/esphome-ratgdo/v25iboard_secplusv1.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: <REDACTED>

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

Anything in the logs that might be useful for us?

No response

Additional information

No response

rlowens commented 3 months ago

What model of garage door opener do you have? What color Learn button?

As far as I know, they are only ever Security+ 2.0 or 1.0 on the wire, never both. So I wouldn't expect the Security+ 1.0 and 2.0 firmwares to both work at all.

Also, the percent open/close is done by timing how long a full open/full close takes and then stopping after a shorter amount of time, so only works after you have successfully run an open/close to calibrate it. Also wouldn't work if the stop command isn't working.

Also confirm how you have the ratgdo wired. And does it show the correct status of the obstruction sensors when you block them/unblock them?

PaulWieland commented 3 months ago

With the RATDGO v2.53i board with the Security 1.0 firmware it is flooding the logs every other second with: 14:46:32 | [D] | [ratgdo:210] | Lock state=UNLOCKED 14:46:33 | [D] | [ratgdo:204] | Light state=OFF 14:46:33 | [D] | [ratgdo:210] | Lock state=UNLOCKED 14:46:35 | [D] | [ratgdo:204] | Light state=OFF 14:46:35 | [D] | [ratgdo:210] | Lock state=UNLOCKED 14:46:36 | [D] | [ratgdo:204] | Light state=OFF

This is how Security + 1.0 works. Every 250 ms or so a query is sent and the status is reported back.

Steven4x4 commented 3 months ago

What model of garage door opener do you have? What color Learn button?

As far as I know, they are only ever Security+ 2.0 or 1.0 on the wire, never both. So I wouldn't expect the Security+ 1.0 and 2.0 firmwares to both work at all.

Also, the percent open/close is done by timing how long a full open/full close takes and then stopping after a shorter amount of time, so only works after you have successfully run an open/close to calibrate it. Also wouldn't work if the stop command isn't working.

Also confirm how you have the ratgdo wired. And does it show the correct status of the obstruction sensors when you block them/unblock them?

Thank you for the response. I originally loaded the Security 1.0 firmware. I did notice when I added it to HA that it quickly did an OTA update. 

The device opens and closes, but the "Stop Cover" function does not work.It did calibrate itself; however, I did notice the calibration times were pretty far off what they should be. They should be around 10-11 and it calibrated around 18–19. Even when using those times and setting my own, the percentage function was not working. I'm assuming that is due to the "Stop Cover" not working.

I have it wired using the three colored wires, color-to-color.  LiftMaster 3800 PLD - Purple Learn Button.

I just tested the obstruction sensors. The correct status is updating when I test them on the device page.

I have a second device on my other security 2.0 opener using the firmware for the 2.0 devices. Wired Color-To-Color and everything works as expected.

This is how Security + 1.0 works. Every 250 ms or so a query is sent and the status is reported back.

Oh Ok. Thank you. I don't see the logs unless I connect directly to the device. I just wasn't sure if it was cause for concern of it overheating based on the constant data flow and querying.

kmycek commented 1 month ago

So my "stop" works just fine, but I am still not able to set the door at any percentage with Security 1.0+

its-pronounced-fee commented 1 month ago

My doors never read as closed, they're always open even when they're closed. In my HA the UP arrow is grayed out leaving only the stop square and down arrow. While closed, either of the available buttons will open my garage. Going directly into the client (via ip) and hitting stop yields "the door is not moving", hitting the down arrow yields position: 0%, up arrow yields position: 100% but pushing any of those three buttons will not activate the door. toggle door however, does work. Obviously my percentage doesn't work either but the priority for me is that ratgdo can read opened and closed.

Light controls work in both HA and direct.

ratgdo v.25i (black PCB) Running ESPhome Security 1.0 FW: 2024.3.0 Mar 25 2024, 04:18:21 Both openers are Chamberlain 041DB002-2 circa 2011 - Purple Button I wired my double as per the suggestion in the diagram but for my single, i just put the three leads into 1, 2, and 4 for shits and giggles to see if there's a difference, there is none and they both seem to work exactly the same and exhibit the same problem of door state: OPEN all the time.

I created an automation that notifies my phone when the either one opens but i get notified both when the door open and when it's closed.

someone mentioned that their closed state didn't start working until after a few manual opens and closes, i've done plenty of that.

I timed my opens and closes and manually moved the slider to see if that helps but it didn't fix it, what it did do was let me switch out the grayed out arrows. After inputting those two variable (via slider directly in the client) I can use HA to slide the door percentage up and down but it only goes fully up or fully down which will then gray out the opposite arrow, still reads as OPEN though.

••••••••••••••••••••••••••••••••••••••••••••••••••••••

OK, so as I was writing this, I was messing with the HA slider to see if I could get the doors to open 50% and in doing so, I also was sliding the controls up and down from 0 to 100, watching my camera, then going the other way. Then later I'd check the HA slider and if the door was closed but the slider says 100% open, I'd use the toggle button in the client (via ip) to make it match the 100% open state; then I'd go back into HA and use only the slider to bring it down to 0% and close the garage and I finally achieved a closed state. I don't know wtf is going on here but as of right now, it seems to be working as intended?! WTF?

I'm gonna not mess with it and hope that it just stays fixed lol, gonna post this anyways in case someone finds it useful.

••••••••••••••••••••••••••••••••••••••••••••••••••••••

OK, well, i'm back again, the double that I wired according to the diagram has retained the position: closed while the one where I just jammed in the three leads will achieve closed but after a few minutes it changes to open (even though the door is closed). I tried my little slider+toggle method again and got closed but then after a few minutes it went back to open. I guess I'll have to climb up there and wire it properly to see if that fixes things.

••••••••••••••••••••••••••••••••••••••••••••••••••••••

welp, that didn't last long - so the other garage is now suddenly reading as open too - so it's not the wiring, the double just took longer to suddenly change to open state, now they're both reading open even though both (the single and the double) are clearly closed. back to the drawing board.

this is driving me insane, i already ditched the myQ - really hoping there's a way to fix this.

slappula commented 1 month ago

@its-pronounced-fee Not sure if this will help, but I had similar issues with one of my two garages after an ESPHome update through Home Assistant. I ended up pulling the Rat module down and flashing the firmware again (starting from scratch). Since then, it has worked perfectly. I did have an issue with the other garage (not showing the right status in HA) that was resolved by hitting the Learn button on the garage opener and then hitting the Sync button on the Rat firmware page.

its-pronounced-fee commented 1 month ago

as it turns out it was my wall-switch. i was fortunate enough to qualify for a replacement through Chamberlain and got a free replacement - the new wall-switch works perfectly. I've called CS and they're sending me a 2nd one, it was the frigg'n wall-switch all a long.