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 4 minutes ago4 min by JSP0511