Skip to content
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

When CLOSE command is sent Door remains OPEN but reports CLOSED state briefly | Security+ 1.0 | ESPHome | 2.5i Board on 2024.10.3 Firmware #361

Open
tmason818 opened this issue Jan 23, 2025 · 7 comments

Comments

@tmason818
Copy link

tmason818 commented Jan 23, 2025

Using wall mount opener RJ020 Security+ 1.0 device.

I've been trying to catch this bug since November because I have not found a way to reproduce it. Every so often sending a CLOSE command will not close the Garage Door but RATGDO briefly reports it as being in the CLOSED status.

I'm never able to catch this in the RATGDO logs as they scroll away too quickly so the best I can do is show how it is logged in Home Assistant:

Image

At 5:27:01 AM I opened the garage door from the wall panel, got into my car and pulled it out of the garage.
At 5:27:41 AM I sent the CLOSE command via Home Assistant but it isn't logged; I visually confirmed the door doesn't physically close but at 5:27:56 AM the RATGDO reported the Door was in the CLOSED state; there was no log for a transitive CLOSING state.
Then, only 1 second later, at 5:27:57 AM the RATGDO reported the Door is now in the fully OPEN state- also without any logs of a transitive OPENING state.

For reference my Garage Door takes 13 seconds to Open or Close as can be seen after the another CLOSE command at 5:33:10 AM. The obstruction sensors were clear at all times.

I have had similar issues with the OPEN command but haven't been able to catch it in the logs.

EDIT: Forgot to mention that the Wall Switch is always responsive and will always CLOSE or OPEN.

@xmlguy74
Copy link

xmlguy74 commented Feb 8, 2025

I'm seeing the exact same behavior.

@panzerwaffen
Copy link

panzerwaffen commented Mar 26, 2025

Just adding to the list same problem.

@tmason818
Copy link
Author

tmason818 commented Mar 26, 2025

Just adding to the list same problem.

What's strange is I don't recall this being an issue when using the firmware that sends commands via MQTT. But I believe that firmware is being deprecated with ESPhome being the replacement?

@PaulWieland
Copy link
Contributor

Are you using wall panel emulation mode? If not, what wall panel do you have? How often does the error occur?

@panzerwaffen
Copy link

Are you using wall panel emulation mode? If not, what wall panel do you have? How often does the error occur?

889LM purchased directly from Chamberlain (I add this I purchased two 889LM's from Amazon that were fakes after my 888LM's died), issue was not observed on a competitor device's (but they had enough other issues they are in my IOT graveyard).

Generally my leaving close door automation works.

Arrival close door automation quit working last year, but it is like the command from HA is ignored because I don't get the double notification. I have tried switching from call service to just cover down. No change.

Now my open door automation has been flaky lately.

All automation's in HA show they are working.

Everything else works correctly.

Updated firmware via USB in mid February.

Thank you

@tmason818
Copy link
Author

tmason818 commented Mar 26, 2025

Are you using wall panel emulation mode? If not, what wall panel do you have?

I am using the wall panel that came with my RJO20 which is listed in the manual as:

Door Control (myQ® Control Panel) Model 041A7928-3

It has Chamberlin and myQ branding but looks very similar to the 889LM?

How often does the error occur?

Seems like maybe once a week on average for me? Also seems like it goes through phases where it does it a bunch and then phases where responds every time.

@tmason818
Copy link
Author

Is there a better way to get logs directly from the RATGDO device? The logs scroll so fast its nearly impossible to catch this issue in the logs. This pic is just 3 seconds of logging. Its very noisy.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants