SHM

Sorry, need help again. I am at my summer home which has 3 security+2 openers, previously setup with the MQTT version of the plugin. I re-flashed each ratgdo to security+2 and v2.5I board. I can access each ratgdo via LAN IP or http://ratgdo25i-xxxxxx.local. I installed the new plugin and used custom parameters (gdodevice0...2) and ratgdo25i-xxxxxx.local;ratgdo25i-xxxxxx. I get the attached error message when I try to discover the ratgdos. Log attached. Each ratgdo shows up on my wifi system correctly; the only issue I see is that when I access each board via ratgdo25i-xxxxxx.local, the name for the board on the page is slightly different, ratgdov2.5i xxxxxx. ratgdo_6-21-2024_71650_AM.zip

Worked for me as well. Thanks

By the way, in your notes for version 4.0.8 under #4, you state..."these commands are only generated if the status change results from and external control signal (i.e., not a command from IoX through the plugin." Does this mean that an IoX program that opens the door when a home geofence is entered will not trigger the door open?

Yes, that works as well,

I can access it by the LAN IP address

I went ahead and used the custom Configuration pathway and the ratgdo is discovered. Interestingly, the plugin nodes show only "door status" and "obstruction", which appear the same in IoX. In UD mobile, Door Status shows up as either 0 or 1 and obstruction is absent. The UD mobile favorite is setup as a "toggle". Not a big deal but if there was a way to change to open or closed, that would be nice. The ratgdo for this door is set up as "dry contact" if that makes a difference. So far, the plugin seems more responsive. ratgdo_6-17-2024_10623_PM.zip

Sorry, here is the log ratgdo_6-17-2024_100744_AM.zip

OK. I downloaded ESP Home version directly , via USB cable, to the ratgdo. It appears on my LAN and opens and closes the door, etc. Then went to plugins store and downloaded 4.0.8, waited 10 minutes and tried to discover. No go. Here is log file. Should I try the custom parameter approach?

I downloded ratgdo_esp8266_v2.1.bin and refreshed the firmware from the ratgdo page. After completing, the page still shows all the MQTT data (server, port, prefix, home assistant). Is this correct?

So worst case, ratgdo would no longer be available to IoX?

Hmmm. Not good. I assume this is the same as your post on ESP firmware?

Just upgraded Polisy to 3.2.27. Initially, I noticed nodes were not working and the plugin was not online in the AC. Tried restarting the plugin, with no change. Then deleted and re-installed plugin but cannot "discover" the ratgdo, even after waiting 10 minutes. Attached log. Any suggestions? ratgdo_6-11-2024_63944_PM.zip

Works perfectly. Thanks so much!

Will install tomorrow and let you know

OK. I understand. Maybe I should just delete any field that is atypical? Thanks.

Here is the response from UDI

Thank you. I restart the AC via the configuration section in IoX. Is that correct?

Here is the IoX log ISY Log.v5.8.3__Mon 2024.04.29 03.25.32 PM.txt.zip

he IoX log was too large.T

Sorry for the delay. I have deleted and re-installed the plugin with IoX restart via AC. I have attached the PG3x logs and IoX logs and screen shots of the AC and UD mobile. Interestingly, UD mobile shows all of the weather data points but the AC does not. Seems to be an IoX display issue. AmbientWeather_4-29-2024_11156_PM.zip

Just added Rachio plugin to my PG3x on polisy, 3.2.20 in hopes of controlling a new rachio smart hose timer. I have an api from rachio and in the configuration page, I have set the host to either the LAN IP of the Polisy or rachio (not at the same time) and made sure there was a firewall rule on my Eero to allow port 3001. Either way, the result in AC just shows "Rachio Bridge" with 1 node server. Any suggestions? Rachio_3-24-2024_51549_PM.zip

Will give all those a try. It is interesting that Goose66 just posted this on the Ratgdo section: Members 2Posted 13 hours ago Something I came across when looking into some firmware issues: It appears that in security+ 1.0 and dry contact modes, after a reboot the ratgdo firmware does not seem to know the door state. You must move the door for the ratgdo to regain the door state. This does not appear to be the case in security+ 2.0 mode because that mode supports "querying" the state from the controller. The potential issue here is that, with the unknown door state, any subsequent open or close command to the ratgdo just reverses the true state of the door. So if you have, e.g., a program that automagically closes your door at night, but the ratgdo was rebooted due to a power failure during the day, that close command when sent to the device may, in fact, open the door. I have logged an issue and hope that the firmware can be updated to set the door state in dry contact mode from the current state of the limit switches upon reboot. In the meantime, keep an eye on it.

Here is a screenshot from today. I did change the favorite type to "toggle" but did not open or close any of the garage doors. As you can see, one of the garage doors (west) is yellow and status unknown, despite not having been opened or closed. When this happens, my program using the Ratgdo plugin typically runs but will not open or shut the door.

Yes, I have been experiencing that quite a bit even in the security + 2.0. Is there a way to query the ratgdo every morning using a program? I do that for my door locks.

I have been using UD Mobile for some time now. Recently replaced MyQ with Ratgdo for garage door opening. I have the garage door in the favorites section and have noticed that the icon color does not correspond to the garage door status (and sometimes, the garage door does not open or close using UD Mobile). I am using the "default" icon type for the door, so the icon shows a left upper corner circle and a padlock picture. Should I be using some other icon type instead of "default"? Not sure what the circle does for this door activity.