@Goose66 I'm contacting you because I'm having difficulty with getting devices to connect to the "ratgdo standard edition Plugin" loaded on the universal devices eISY

Background

My home automation controller is a Universal Devices eISY Home running the following packages/versions.

Package Current Version

• eisy-ui 1.4.9

• IoX 6.1.2_14

• UDX 5.3.0

• PG3x 3.4.28

• iox-matter service 1.3.24

• mosquitto 2.0.18

• mDNSResponder 2881.100.56.0.1

• libwebsockets 4.3.3

I recently (Mid-September) migrated from PG3 Plug-ins to the eISY Plugins (allowing for remote access). I have 5 ratgdo devices. Three devices are v25i and two devices are version 32. Prior to purchasing the Version 32 devices, I was running the V25 devices on the ratgdo free plug-in (MQTT) version with no problems.

When I recently purchased the ratgdo 32 devices, I did the following:

• Flashed ALL the ratgdo devices to latest esphome firmware (2026.9.1 (config hash 0xa0707ebd, built 2026-10-16 19:03:35 +0000))

• I was able visit all devices after the firmware updates

• After updating the firmware, I installed/reinstalled the devices into the openers and confirm the wall controls, remotes, and Homelink all worked

• Next, I was able to access 4 of the 5 devices (the fifth device was not included because of location) using the "unique device identifier" and the ".local" designation as follows:

  • ratgdov2.5i ef8bac.local

  • ratgdov2.5i 87b405.local

  • ratgdo32 055dc8.local

  • ratgdo32 6948cc,local

• I was able to toggle the garage door up/down, control the light, etc. when directly accessing the ratgdo devices over WiFi.

• Next, I deleted the ratgdo free plug-in and purchased and installed the ratgdo standard plug-in in the eISY plug-in environment

• After installing the Plug-in and it was connected, I proceeded to attempt to "Discover" devices. However, I received the following error meaasge "No GDO devices discovered. Make sure your devices have been flashed with the ESPHome firmware, are powered on, and are connected to the network". I attempted discovery several times with the same results.

• Then I followed your instructions to enter "Custom Configuration Parameters" as follows:

  • Configuration Parameters Values

    gdodevice1 ratgdo32-055dc8.local;ratgdo32-055dc8
    gdodevice2 ratgdo32-6948cc.local;ratgdo32-6948cc
    gdodevice3 ratgdov25i-87b405.local;ratgdov25i-87b405
    gdodevice4 ratgdov25i-ef8bac.local;ratgdov25i-ef8bac

• After entering the configuration data, I restarted the Plug-in and waited several minutes before attempting to "Discover" devices.

• When I clicked on "Discover", I received the following error message: There was an error attempting to connect to the device at ratgdov25i-ef8bac.local. Please check the log files and correct the issue before restarting the plugin."

I have attached a log file, in debug mode, for your review and comments.. Please provide any assistance possible.

Edited 5 hours ago5 hr by RMichael
added context

I'm having the same exact issue as I'm trying to setup my ratgdo32 for the first time. The current and only available ratgdo firmware is from Oct 16. There has to be some new compatibility issue.

To the seasoned experts on this forum, any thoughts?

Thanks for the reply! Today I flashed a v2.53i board connected it to the network and was able to visit the device. When I attempted to add it to the Plugin, I got the same results. Device not found.

I have 5 of the ratgdov2.53i devices and all worked just fine prior to the eisy upgrade in October. You may be onto something in you comment above. Goose66 has been quiet.

Another quick note. When I try to reinstall the ratgdo plugin from the ratgdo plugin configuration page, it returns an error "API not found", I was able to reinstall the plugin by going to my licenses and reinstalling from there.

I also just tried reinstalling the ratgdo plugin and received the same error.

Any more updates on this? I was about to take the ratgdo plunge until I saw this... 🙁

Not yet. Does anyone have an older version that used to work?

After no response to post from goose66, I took a different approach. I rolled back the firmware (Releases · ratgdo/esphome-ratgdo · GitHub) to the April 2026 version (Firmware Release 1428, April 25, 2026). Restarted the plugin and then entered the configuration data using this format:

key: gdodevice, value: ; for ratgdo device, e.g., "192.168.1.135;ratgdov25i-618d30"

This solved the problem! All of my ratgdos device are connected to the Plugin and working

There seems to be a compatibility issue between Paul Weilands Ratgdo devices (ratgd032 and ratgdov25i) and the Goose66 Plugin that is unresolved. Hopefully, they are aware of the issue and are working to resolve it.

Edited 3 hours ago3 hr by RMichael