search

ratgdo / esphome-ratgdo

ratgdo for ESPHome
GNU General Public License v2.0
358 stars 108 forks source link

Sec 1.0 ghost open/close messages #286

Closed lukescott closed 5 months ago

lukescott commented 5 months ago

I'm having ghost open/close issues with Home Assistant, and HomeKit by extension. I had this issue with MQTT firmware as well, but just figured I'd wait for ESPHome version to be 1.0 compatible. So I made the switch yesterday. Unfortunately the issue persists.

Another issue that presented itself with the MQTT firmware is eventually after a few weeks the door would become unresponsive and require me to power cycle that Ratgdo v2.5 (non-i). I have not had the ESPHome version long enough to know if this will become a problem yet.

I have the Chamberlain 3280 with a control board 41AB050-2 (purple learn button). Another thing to note is I have two of these openers and the same thing happens on both.

I do seem to get some "unknown" statuses as well. Not sure if that is relevant. I've attached logs from Home Assistant for both doors over the last day which includes the ghost messages.

history.csv history (1).csv

I would look at the Ratgdo logs, but I'm getting constant logs like this:

11:41:02 | [D] | [ratgdo:209] | Light state=OFF
11:41:02 | [D] | [ratgdo:215] | Lock state=UNLOCKED
11:41:03 | [D] | [ratgdo:100] | Door state=CLOSED

I'm assuming this is because I'm in emulation mode and I have 78LM dumb panels. Just to be sure it wasn't the panels, I disconnected one of them on one of the doors, but that doesn't seem to make a difference. They both behave the same.

I've thought about getting 889LM so I wouldn't have to do emulation mode, but from what I understand the panel pretty much does what the Ratgdo does, and I've heard multiple instances of 889LM actually opening the door on it's own, which is something I want to avoid.

Is there a way to only print the Light/Lock/Door state logs only if it changed? It takes sometimes several hours for the ghost messages to appear. If the logs only printed when a change occurred I could leave the window open and grab it after it happens. Right now because of the log spam and how long it takes to occur, it's really difficult to capture.

lukescott commented 5 months ago

Closing for now. Maybe first day was a fluke. It’s been stable over the past week.