Got my new EISY a few weeks ago.  Everything transferred OK, but I noticed in UD mobile that the ratgdo door state for the plugin has a label of either "0" or "1" instead on"closed" or "open."  B Mercier thought it might be a plugin issue.

I have been using the ratgdo plugin flawlessly, on a Liftmaster 5.0, Security 2.0 commercial door opener, using the ESPHome firmware for "dry contact."  In an effort to fix the UDM issue, I did an OTA firmware upgrade to the ratgdo, again using 2.53/security 2.o/dry contact firmware.  Now, there is no response to the open/close command on the ratgdo, (when triggered from the device on chrome, UDM or the AC).  Attached is screenshot of the ratgdo device information.  The IP of the ratgdo is 10.0.0.21 and the EISY is 10.0.170

The original issue just sounds like the “profile” for the plugin didn’t get successfully loaded. You could have loaded the profile from the PG3 dashboard and restarted the Admin Console to see if that straightened it out.

However, now it sounds like the plugin setup is corrupt once you updated your ratgdo. I would suggest factory reset ratgdo, delete plugin, and then follow all the instructions again to install and discover.

Sounds like a plan.  By factory reset, do you mean erase and re-install the ratgdo firmware?

The erase is not as important as going through the setup steps to get the initial settings right so the Discovery process will work. See here and here.

That worked!  Garage door now responds as before but in UDM, the plugin display shows a number for Open, opening, closed, closing instead of the word.  Any thoughts?

Don’t know what to tell you. Obviously the plugin hasn’t changed in 14 months, including the “profile” files, and it seems to have been working before.

I would think something has changed in UD Mobile and the way it interprets profiles from a recent update, and that is likely the problem. If there is some new format for plugin profile files that UD Mobile has changed to, I am not aware of it.

Please open a ticket with UD to investigate, reminding them that the last code changes to the plugin was 14 months ago.

5 hours ago, SHM said:

That worked!  Garage door now responds as before but in UDM, the plugin display shows a number for Open, opening, closed, closing instead of the word.  Any thoughts?

Typically, this can be corrected by rebooting ISY/Polisy/eisy.

On 7/31/2025 at 5:48 PM, Goose66 said:

Don’t know what to tell you. Obviously the plugin hasn’t changed in 14 months, including the “profile” files, and it seems to have been working before.

I would think something has changed in UD Mobile and the way it interprets profiles from a recent update, and that is likely the problem. If there is some new format for plugin profile files that UD Mobile has changed to, I am not aware of it.

Please open a ticket with UD to investigate, reminding them that the last code changes to the plugin was 14 months ago.

Mine has also stopped working.  Except I didn't change anything like SHM.  The AC seems to correctly read the state of the garage door and the light.  However, open and close commands no longer do anything.  Not entirely sure when this started but sometime in the last month.

Ratgdo32 is a POS. Now I know why there is no refunds. Dude is selling trash! Never worked right out of the box.

I imagine “dude” is making zero money on the device given the cost of the boards, shipping, support, hosting the website, etc. Like the community members developing plugins, it’s probably much more a passion project than a money-making opportunity.

There are certainly challenges working with the security protocols on the MyQ GDOs and I know it can get “out of sync” with rolling codes and all. My RatGDOs working in dry contact mode have been rock solid.

4 hours ago, oke10710 said:

Ratgdo32 is a POS. Now I know why there is no refunds. Dude is selling trash! Never worked right out of the box.

the device does require a slightly more techie user than say what attracts the “plug-n-play” crowd.

I have 4 ratgdo’s. I’ll admit in the beginning it was a tough go. The first I tried to install never worked correctly in security 2.0, but the root cause wasn’t the ratgdo, it turned out to be yet ANOTHER defective LM889. However I probably spent a few weeks worth of leftover time trying to figure it out. Finally I had the thought let’s go install one on a newer operator I have, that worked well first try! Next I moved to the barn, it actually turned out that I had mis-remembered the color of the learn button there and had to set that one up security 1.0, but it too worked first try. Next I moved to the last remaining door, that too installed perfectly first try. This brought us to an interesting point in time because I still couldn’t leave the first connected and its operator was exactly the same model and vintage. Went back to reading closed GitHub issues using ChatGPT as a search engine (what an amazing use of ChatGPT too!) It suddenly occurred to me… the wall control—it’s what’s driving the 24/7 conversation between the operator and itself, ratgdo “sorta” just eavesdrops. So as a test I swapped the identical LM889 keypad. Yup, the problem moved. {see yet another liftmaster/chamberlain rant below}. Ordered a new one from Amazon, arrived, installed. All 4 doors have been fully functional since.

my issue with the ratgdo guy is the he essentially provides zero support and his documentation in my opinion lacks substance and is poorly organized.

on the topic of another LiftMaster/Chamberlain rant. They have or had a couple recall/Replacement programs for LM888/LM889 … but get this! You are limited to ONE per address forever. I replaced an original LM888 when it went bad for free from LiftMaster support. Then I upgraded 3 to LM889 when I wanted to use MyQ back in 2016. All of those have been replaced once because they failed, and now one has been a second time for the ratgdo issue above.

So @oke10710 don’t just come here to air your dirty laundry. If you want to figure out what wrong create a new thread and ask for help, but don’t just tell us “it doesn’t work out of box” like you have here. Tell us exactly which firmware you picked and why you made that choice. Then post your log or a snip from your log that shows the issue. Somebody might help figure your issue out.

I’ve asked the moderator to close this thread, your rant is off topic in this thread. If you need help solving your issue make a new thread.