This release fixes GDO blaQ crashes on ESPHome 2026.10 and updates gdolib to v1.3.0. The gdolib update reports a disconnected Security+ 2.0 opener as unsynced, fixes the Security+ 1.0 wall button getting stuck at Pressed, and makes partial closes stop where they should on jackshaft openers. It is built with ESPHome 2026.10.
GDO blaQ
- No more crashes when the door moves on ESPHome 2026.10. With the web UI open, opening or closing the door could crash and reboot the GDO blaQ ("A stack overflow in task gdo_main_task"). Door, light and sensor updates were being published from gdolib's own task instead of ESPHome's main loop, which ESPHome does not support. ESPHome 2026.10's web server uses more stack to send each update, which turned that into a crash. Updates are now handed to the main loop. gdolib's task now uses about 1.3 KB of its 4 KB stack, down from about 5.5 KB. If you build your own GDO blaQ firmware with ESPHome 2026.10, update to this release. (#150, fixes #148; thanks @shawnz for the report and stack measurements, and @bdraco for the suggested design)
gdolib v1.3.0
- Security+ 2.0: a disconnected opener now shows as unsynced. If the wire to the opener was pulled or the opener lost power, the device kept showing Synced with a stale door state. Now, after 5 minutes with no traffic, the device asks the opener for its status. If there is no reply, it shows Synced: No, marks the door state unknown, and re-syncs on its own once the opener is back. This uses one rolling code per 5 idle minutes. (gdolib#50, fixes gdolib#47)
- Security+ 1.0: the wall button no longer sticks at "Pressed". After any door command, the Wall Button entity stayed at Pressed, even with no wall control connected. The same bug could also leave the cover at Closing after the opener refused to close because the safety beam was blocked. (gdolib#48)
- Security+ 2.0 jackshaft openers: partial closes stop on target. On wall-mount (jackshaft) openers that ignore STOP while closing, a partial close (e.g. "close to 20%" from Home Assistant or Google Home) ran all the way to closed. The door now briefly runs past the target, by about 15% on our test opener, then reverses and stops on it. Other openers behave as before. (gdolib#52)
- Door position tracking is more accurate on every opener. Travel in the moment before the door stops is no longer dropped, and reversing straight from closing to opening is tracked correctly.
gdolib Changelog: konnected-io/gdolib@v1.2.0...v1.3.0
Project versions updated
garage-door-gdov2-q: 1.7.0
Full Changelog: 2026.10.0...2026.10.1