@scelfo The double close patch seems strange but actually makes some sense. What we saw with other wall panels was they would send only a toggle command to either open or close the door. More specifically it would send a “door action” command with the data being a value that we believe indicates “toggle”. In the logs we would see “DOOR_ACTION, Nibble = 2” with the value 2 equating to toggle. In other panels you would see the nibble value being 0 or 1, equating to open/close. The door opener seems to switch between different configurations depending on what panel is used last and my suspicion is that for safety it would need a double press of a button before closing the door from a different panel to confirm the action, which it then will change modes and close the door.
In your logs there is an interesting value for the nibble, 5, which is above the max values known so far and indicates to me there is something more going on that we don’t know about. If you could log a few button presses, opening/closing and stopping the door without any actions from home assistant and post those I’d really appreciate it.
@user107 There is no interaction between this device and the wireless devices. They operate independently of the wired devices.
@Ryan_P Just wondering out loud if it would bet better to instead send a toggle command instead of double-close if the opener is expecting a toggle. Maybe that’s what’s putting @scelfo’s wall button into a weird state bc it’s seeing the rogue close command?
or you need a “auto/toggle/not-toggle” setting if the end user knows they’re operating in one of two modes, or the Auto if your trying to guess (like todays logic)
if this is an outlier but a painful one at that, you may want that ability for user to force to one of two modes…
I’ve installed the update and it still exhibits the same behavior; Sending the double command. Before I started logging I had hit the open 3 times. It took a total of ~5 times before it actually opened. Closing worked. The other garage door worked after hitting open twice and closed on the first go. Last night when I got in I tried and I was unable to close this garage door it only played the audio and didn’t close. I’ll email both logs to you @nate
@Ryan_P here’s an new log of commands sent only from my wall controller. It starts with a full open, a full close and then a mix of open/stop/close actions on the primary button with a few presses of the light toggle thrown in. I looked quickly at the logs and they match what I remember doing. 2024-04-18-logs_konnected-9c4440_logs.txt · GitHub
Thank you @scelfo, I’ll see what I can learn from these logs and hopefully come up with something.
@nate I’m actually not very surprised, considering the nature of how this seems to work I’m actually a bit surprised the open issue didn’t come up sooner.
@scelfo@Oral_Allen@user107 We’ve just pushed another update to gdolib that @Ryan_P thinks will fully solve the problem. You should be able to OTA update via ESPHome again and get the update. Please let us know how it goes!
Thanks @nate that appeared to have cleared up the install issue. Initial testing seems to be working well for the one device I’ve installed the update on. Opened on first go. Closed on first go also. I’ll continue to monitor over the next few days and report any changes to this.
Spoke a bit too soon.
Tried again after the initial tests worked and they both failed:
Garage Door 1
[16:20:42][D][cover:076]: ‘Garage Door’ - Setting
[16:20:42][D][cover:084]: Position: 100%
[16:20:42][D][gdo_cover:127]: Open command received
[16:20:42][V][esp-idf:000]: I (1191476) gdolib: TX: [55 01 00 60 36 DB 27 B2 C9 6D B5 00 2E DE ED 7A 79 2D B2]
[16:20:42][V][esp-idf:000]: I (1191479) gdolib: TX: [55 01 00 60 36 DB 27 B2 C9 6D B7 00 2E DE ED 7A 79 6D B2]
Garage Door 2
[16:20:17][D][cover:076]: ‘Garage Door’ - Setting
[16:20:17][D][cover:084]: Position: 100%
[16:20:17][D][gdo_cover:127]: Open command received
[16:20:17][V][esp-idf:000]: I (1781925) gdolib: TX: [55 01 00 5A 2C 96 CF 2C B2 C9 63 A1 0A 44 A4 47 AB E4 97]
I retried about 20 seconds after receiving a new rolling code and they both opened. Do we think there is some relation to the rolling codes? I’ll keep the logs open and see how long these rolling codes are updated.
One garage door does not close. Playes audio but fails to close the garage door:
Update went fine, I’ll report back when I’m home about 1\ how it works for open/close and 2\ whether the “push the bar” message goes away.
My plan is to keep talking about both issues in this one thread to keep things simple until we get to a point where the “sometimes garage door will not move” issue gets fixed but “push the bar” remains a problem. If that happens, we can start a new thread just about “push the bar”.
The new firmware does not fix the close issue. I just opened with the wall control (needed to push the button several times to clear the “push the bar” message).
Then I closed with blaQ and it played the warning chime and did not close the garage.
The wall control was already back on the “push the bar” message and I needed to push the wall control several times to close the garage.
Strange enough I don’t get that pushbar message. I noticed on initial install when I had first received the devices however I haven’t seen it popup again.
@Oral_Allen do your wall controllers look like mine? I posted some pictures above showing a manufacture date in 2014. I’ve read on some forums that there is a hardware revision and that the newer wall controllers seem to work better.
Also, do you have them connected in parallel or are you doing the pass through wiring?
I have the same one as you. I’ll take it off the wall to see the revision. I have mine setup in parallel. I did see the message the first time I installed but haven’t seen it again.
