Connected but not working

[bcdavis75]

I'm at a loss.  It's always been a bit flaky for me, but I cannot get it working at all anymore.  It is correctl reading the door state in the AC, so it is connected properly and getting information through the NS.  There's nothing to my eye that looks odd in the logs (attached).  I've rechecked the wiring to make sure it's secure.  It simply will not open/close the door though.  Any help much appreciated.

ratgdo_8-29-2025_53522_PM.zip

[Goose66]

I’m out of the country for a few weeks. I’ll looK at it when I get back. But you may want to see if you can open and close the door from the built in Web interface in the ESPHome firmware. If not, then it’s your ratgdo’s connection to the opener.

[bcdavis75]

Updates... I took down the unit and went through the process of of reflashing it with the newer version of the node server.  That worked fine.  However, I cannot get it to connect to the new node server (purchased).  Log attached.  They are on the same network.

ratgdo_8-29-2025_62823_PM.zip

[Goose66]

The Plugin is discovering your ratgdo at ratgdov25i-18fe31.local, however when it turns around and queries it for details via HTTP, it can’t connect. Not to be cynical, but the cause of this is likely that UD blew up mDNS and its ability to resolve *.local addresses with a recent update (sorry - this has all been very frustrating for plugin developers). Try adding a ‘gdodevice’ entry to your Custom Configuration Parameters (i.e., value '192.168.0.224;ratgdov25i-18fe31’) and then re-perform discovery. See note # 2 from the Release Notes at goose66.github.io/nsdocs/ratgdo-pg3.html (recreated below).

2. The plugin utilizes mDNS service disovery to discover the ratgdo devices on the LAN. If a GDO device cannot respond to broadcasts, e.g., is on a different LAN segment or network, then you can add a Custom Configuration Parameter for each such device before performing the Discovery process to force the plugin to connect to the devices. Add a Custom Configuration Parameter with a key of "gdodevice" and a value of "<host>;<devicename>" for the ratgdo device, e.g., "ratgdov25i-fc64f3.local;ratgdov25i-fc64f3" or "192.168.1.135;ratgdov25i-618d30". Additional Custom Configuration Parameters can be specified for additional devicecs with key values of "gdodevice" with an index, e.g., "gdodevice0", "gdodevice1", etc. NOTE: the "devicename" is utilized to generate the node address and a specific value should be consistently used for each device, e.g., the name of the device with periods removed and space replaced with dash, in order to prevent subsequent Discovery processes from generating duplicate nodes with different addresses.

[bcdavis75]

Worked!  Thanks.