Goose66

It's in the Production store and called "ratgdo." Since it's all lowercase, it's all the way down at the bottom of the list (somebody doesn't know how to sort database entries). It was added just this afternoon, so you may need to refresh your Plugin Store list.

Adding a topic to discuss experiences with the ratgdo device. My experience: Took 5 1/2 weeks from ordering (Nov. 6) for my ratgdo device to arrive. Initial flashing and connection to my Wifi using Chrome browser, Windows 11, and a USB->micro USB cable was very easy. Configured it for my test MQTT broker and played with it using MQTT explorer to put it through its paces. However, the built-in configuration website is somewhat brittle. If you enter something wrong, or if you forget your password, you are stuck reflashing it to regain access. Of course, this time, if you are like me, it will be done with a laptop from the top of a ladder, so not quite as easy to do subsequent changes. The passwords for OTA and Wifi connection are hidden, with no "show" or "reveal" functionality, so it's easy to mess them up and "brick" the device (especially one handed from the top of the ladder). In addition, each time you flash it, it picks up a new Device Name, so watch for that. Mine is hooked up to a Genie Screw Drive Pro (CM7600IC) so it is in "dry contact" mode. My GDO unit doesn't have exposed terminals for the door position sensors, but I was able to use tap splices on the cables from the door sensors to hookup the sensors to the ratgdo terminals and door status works perfectly. I only get door open, close, and stop functionality from the ratgdo, but my keypad has separate light and lock controls and those continue to work even with the keypad connected through the ratgdo. The obstruction sensors were too high of a voltage (12.95v) so I couldn't hook them up. The status changes and commands are instantaneous - no cloud service or polling latency here. So the ratgdo plugin is already more capable than the MyQ node server was. There is no delay with beeping alarm when closing the door, which I thought I would like but is actually a bit unnerving when closing the door remotely. Also, I haven't thought through all the security implications here, and with holidays coming up I am unsure of whether I want it online while I'm not here. However, the lockout button on my keypad seems to lockout the ratgdo as well, so maybe just manually locking the doors when we leave will have it covered. I am ordering ratgdo devices for my other doors now and taking down the MyQ Smart Garage system and I guess chucking it in the garbage. I hope to work with the developer to add light and lock control to my Genie GDOs from the ratgdo, as well as improve the discovery process so that the plugin is better at creating the requisite nodes based on your installation.

Well, it looks like you rushed your version out while mine was still at the chemists... 😁 Anyway, better late than never I always say. As promised, I have released a plugin for the ratgdo device. It is free to all users to make up for all of you that paid for MyQ and didn't get much use out of it. See details and discussions here: https://forum.universal-devices.com/forum/436-ratgdo/

I have published a new plugin for PG3 and PG3x that allows IoX to connect to ratgdo devices to access and control the functions of Liftmaster and Chamberlain garage door openers (GDOs) as well as basic support for other brands which use dry contacts to control the door. Detailed installation instructions, release notes, and version history can be found here: https://github.com/Goose66/NSDocs/blob/main/ratgdo-pg3.md. This is a pre-lease version in that it has not yet been tested with a Liftmaster/Chamberlain GDO. Let me know how it works for you and I will try to get another release out soon with any fixes.

Oops:

See discussion of restoring event generation in this thread: (bad link removed)

Is it possible that something else is trying to connect to this EnvisaLink? Many times in the past the node server has exhibited the “connection reset by peer” error because another node server, version of PG2, NodeLink, or something else was attempting to connect to the EnvisaLink. The EnvisaLink can only have one UDP socket connection at a time.

The ratgdo plugin uses the Home Assistant discovery mechanism built into the ratgdo firmware to discover the devices and add the appropriate nodes to IoX/Admin Console. You do have to configure the MQTT settings on your ratgdo device(s) however, to get them connected to the MQTT broker on your Polisy/eISY and make them usable by the plugin. The details will be covered in the Instructions and Release Notes for the plugin.

Sorry, no this is not going to het it into the Admin Console - just a way to test that you have ratgdo installed correctly and MQTT configured. To hook into IoX you have (from what I can see) three options: 1. use MQTT plugin and define a node for the ratgdo in the yaml file. I can’t help with that because I’ve never used the MQTT plugin. 2. Wait for the ratgdo specific plugin. Should be done in a week. 3. Get it talking to Home Assistant and then have IoX connect to it through Home Assistant - also another thing that I don’t know how to do.

If you just want to verify install and configuration of the ratgdo outside of the MQTT plugin, configure the ratgdo to talk to the MQTT broker on your Polisy/eISY, and then install and run MQTT explorer (http://mqtt-explorer.com) and connect it to the MQTT broker on your Polisy/eISY as well. MQTT will show you all published messages on all topics from all clients connected to the broker, including the ratgdo (assuming it’s configured correctly).

I received mine on Wednesday (Dec. 13) this week. Ordered on Nov. 6. Came via USPS. No shipping notification. No tracking number. I sent an email last week to the guy and he just said shipping as fast as he can and referred me to the shipping status page at https://paulwieland.github.io/ratgdo/09_faq.html. Flashing with firmware and configuration very easy. Working with my MQTT broker on Polisy. Bug I have Genie GDOs so I am having to do dry contact install paralleled with my limit switches so install a bit trickier. I have lined up somebody with Chamberlain GDOs to do initial testing of ratgdo plugin this weekend but he hasn’t gotten his devices yet. Ordered them same day I did. Hoping he gets them today.

Uh… yeah. Oops.

If your are using the public MQTT broker on Polisy/eISY, it is the local IP address or hostname of your Polisy/eISY and port 1884. i believe the MQTT Plugin has to be configured for the same broker settings, but I don’t use it. The ratgdo plugin will default to the Polisy/eISY public broker but you can set an external broker if you wish (just like Tasmota plugin).

Mine was "NO" as well. Did the Reconfigure, and after about a half an hour or so (the Polisy rebooted), it switched to "YES" and now I am getting events from Ring. It's been a while since this has worked, so the change must have taken place a while back. I wasn't fully understanding the significance of this setting and wasn't aware of the requirement for the Ring node server. But I did look and see that it is in the UD Developer documentation here: https://developer.isy.io/docs/API/pg/Webhooks Looks like not until PG3x, however, which doesn't make a lot of sense. But oh well, it works now so all good. Thanks for the tip!

All that said, my Ring node server is not working - not generating events. It has been messed up for some time. Hopefully you will have better results.

The node “Front Door” should generate a DON command on button press. It shows up in programs as “Ding” command. It is supposed to be able to drop into scenes as a controller.

It’s already there and running in the Polisy. It will be a matter of configuring the connection to it on the ratgdo. Like the Tasmota plugin, I would expect there will be instructions on how to configure ratgdo to work with the plugin.

Looks like both ratgdo and tailwind have push mechanisms for status changes (no polling).

Yes, ratgdo hardwired to GDO, ratgdo connected to Wi-fi, and ratgdo communicating with MQTT broker on Polisy/eISY. I don’t think that the MQTT plugin (node server) supports garage door openers, so we would need a custom plugin to support ratgdo. You could also probably use network resource. I would convert MyQ code. Too bad Tailwind doesn’t do MQTT or we could roll both into one node server.

I get that too. Something in whatever version IoX I have. Hopefully will stop in some future release.

For the node server (plugin) to control the brightness, the Bond bridge has to report a SetBrightness command for the light. This depends on the remote template used to control your fan. Just simple “bright up” and “dim down” commands don’t work for lights without discrete brightness setting, because Bond only supports a start fade and stop fade approach for those lights which doesn’t implement easily or work well with, e.g., Insteon->IoX->plugin->Bond communication.

Same on the Tailwind website: it mentions a local API but there are no details on what it is or how one accesses it.

When I was required to have OpenJDK on my PC, I started the finder like this: java -jar .\downloads\isyfinder-2.0.jar Put it in a "startiox.bat" file. I didn't have too hard of a time finding a copy of isyfinder-x.jar file on the web, but you may have to put in a support ticket to get @Michel Kohanim or @Chris Jahn to post a copy.

Still haven’t gotten mine.

I see a "failed due to bad credentials" in your log four or five times over the course of the day. But it always succeeds a minute later on the next longpoll. I actually got one of these today myself. Based on the timing (the few in your log are exactly one hour apart) it appears to me that the oAuth token is expiring before automatically refreshed, so the pyschlage library just refreshes it on the next call. I will put it in the To-do for the node server to remove the warning message from the PG3 dashboard, but since the node server remains functional (it's just a warning), you can just ignore these errors for now.