I recently purchased several Ratgdo32 devices for my garage doors. I followed the instructions for loading the esphome firmware and connected the first unit to my wifi network. I am able to access the device using HTTP://ratgdo32-055dc8.10.158.1.206 and I can turn the light on/off or place the opener into learn mode.

I then installed the ratgdo plugin on my eisy (I recently updated from the legacy PG3 to eisy plugins) and attempted the discovery process. The Plugin returns the following message "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 tsame results.

Next, I tried entering a custom parameter Name: "gdodevice-N" Value: "10.158.1.206;ratgdo32-055dc8" and I received the following message"There was an error attempting to connect to the device at 10.158.1.206. Please check the log files and correct the issue before restarting the plugin." The log file returned the following information:

2026-11-02 14:24:15.771 Thread-8 (_discover_handler) udi_interface INFO ratgdons:discover: In Nodeserver.discover()...

2026-11-02 14:24:15.991 Thread-8 (_discover_handler) udi_interface WARNING esphomeapi:queryRatgdoDevice: Network/server error in HTTP GET in queryRatgdoDevice: 404 Client Error: Not Found for url: http://10.158.1.206/text_sensor/firmware_version

2026-11-02 14:24:15.991 Thread-8 (_discover_handler) udi_interface WARNING ratgdons:discover: Error querying ratgdo device ratgdo32-055dc8 at 10.158.1.206

2026-11-02 14:24:15.991 Thread-8 (_discover_handler) udi_interface.custom INFO custom:_save: Sending data notices to Polyglot.

2026-11-02 14:24:16.002 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices

Any help in resolving this issue would be appreciated. Let me know if you need additional information on the install.

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?