Standard 4.0.8 (licensed) finds nothing on a ratgdo32 disco running ESPHome 2026.1.5 (ratgdo.v32disco_secplus2).

eisy, IoX 6.1.2_10, PG3x 3.4.26. Board at 192.168.30.5, same subnet as the eisy; its web page loads fine.

On Discover, the debug log shows the mDNS reply (name ratgdo32disco-2c32dc, 192.168.30.5, port 6053), then "No devices returned from discovery." No nodes are created.

I also added the custom parameter from the release notes, gdodevice = 192.168.30.5;ratgdo32disco-2c32dc, and restarted the plugin. The log never mentions it.

Does 4.0.8 support the v32disco board or ESPHome 2026.x? Log attached.

Same symptom as some users in the closed "New Release v4.0.8 - ESPHome version" thread, but the gdodevice parameter doesn't fix it on this board.

debug.log

@Goose66 Tagging you since this is your plugin. More info on the ratgdo32 disco issue above: the board's own event stream works fine. http://192.168.30.5/events returns normal state events for Door, Light, Motion, Obstruction, plus the disco-only entities (vehicle detected/arriving/leaving, distance, voltage). Full output attached.

The ping event reports title "ratgdo32disco 2c32dc". The mDNS name is ratgdo32disco-2c32dc. Every working example I've seen in the old v4.0.8 thread is a ratgdov25 board.

Does the plugin filter discovered devices by name, such as a ratgdov25 prefix, or only handle certain entity sets? That would explain why it hears the mDNS reply and then returns no devices without ever connecting.

events.txt

Edited October 17Oct 17 by JSP0511

@Goose66 6 Update with a debug-level log. The gdodevice parameter is saved (192.168.30.5;ratgdo32disco-2c32dc, screenshot attached) and the plugin was restarted. I also added a hosts entry so the eisy resolves ratgdo32disco-2c32dc.local. Before that, ping by name said "Name does not resolve", while ping by IP always worked.

Discover still receives the full mDNS record (name, address, host, port 6053, ESPHome 2026.1.5), waits about 11 seconds, then logs "No devices returned from discovery." There is no connection attempt or error line in between, and the log never mentions gdodevice. Is the plugin filtering this board out, or is something in eisy-ui 6.1.x stopping the connection?

debug.log

Update: solved on my end. The gdodevice parameter had three stray leading spaces in both key and value (visible in the debug log as {' gdodevice': ' 192.168.30.5;...'}), so the plugin ignored it. Retyped without the spaces and Discover created the nodes: Garage Door Opener, Light, Motion, Door. So 4.0.8 does work with a ratgdo32 disco on ESPHome 2026.1.5 via the manual gdodevice setting. Thanks for looking.