SHM

On a related issue, my insteon motion sensor detects the presence of a car in my garage and via a program, a state variable is set to 1. When the sensor times out, the variable resets to 0, which is not desired. Do I use a scene or change the motion sensor to "report on" only?

Yes, I did the restarts with no effect. Should I delete the nodes and api and start over?

My plugin shows 3 nodes and node 2 has 11 "drivers" which match the available weather data from my station. These drivers do not show up on the AC. Am I missing something?

I have Ambient Weather plugin linked to my RainwiseNet weather station via AWN api. I have entered just the api in the plugin configuration and it then gives me all of the weather station data (attached). However, on the AC, the plugin only shows 2 nodes, each with the same weather station data (Barometric pressure, atmospheric pressure, temperature). Have tried "adding all nodes" in the plugin menu with no luck. Any ideas on how to get the other data to the AC to use for programming? ambient weather plugin.pdf install.log debug.log

Bullseye! It was an "all lights on" program that I have for emergencies that somehow was enabled to run at startup. Thanks!

Whenever I reboot my IoX (5.8.0 and earlier), many of my insteon lights come on. Preventable?

My MQTT communications problems have gone away for some unknown reason. Good news. I have noticed that if the power goes out to your garage (and ratgdo if you connect it via usb to AC power), then all the nodes default to "unknown." Hitting the open/close button in the node resets the door status, but if you use door status in a program and the condition depends on "open or close" status, then the program won't run. Argues for connecting the ratgdo to the batter backup, if you have it.

Thanks you. Makes sense. When I drove away from the house today, my ISY program that closes the door based on geolocation ran and gave me a push notification that the door was closed but it did not. I was able to close it on UD mobile but sounds like the network is the issue. I have one of the original Polisy devices that has been upgraded along the way to PG3 but maybe its time to upgrade to eISY. I will open a ticket. Maybe Michel can work his magic.

So in the interim, I started over by deleting the ratgdo plugin, then re-installing it and re-discovered the ratgdo devices. I have attached the debug log and MQTT Explorer page that lists the devices (is it expected that under Homeassistant, the devices also appear?). When I use UD Mobile and watch the MQTT Explorer, each device shows the correct change in the open and close command from UD mobile, although there is a 5 second or so delay. For some reason ratgdo-41031 only shows the open/close under a separate level labeled "command". Since I still have my doors connected to MyQ wireless (maybe I should not?), I can watch the doors open and close. When I am on AC, the open/close commands also work, but with a slightly longer delay. At one point, I did receive a TCP error on AC after hitting the open command several times for one door. Not sure how I troubleshoot the network but I am willing to learn. Hope this helps and again, thanks for your Sunday help. ratgdo_1-7-2024_14011_PM.zip

Here are the log and log package ratgdo_1-7-2024_82253_AM.zip ratgdo_1-7-2024_82307_AM.zip

OK. I deleted the MQTT plugin and went to the ratgdo plugin, deleted the nodes then re-discovered. Populates ISY fine, but still no garage door activity (or light) when I try "one" or "close" from the AC. MQTT explorer shows all 3 doors. I did upgrade the ratgdo firmware to 2.57 btw. Interestingly, the UD Mobile app does open and close the doors (albeit slowly). Will see if my door open/close programming still works.

P.S. I should mention that MQTT explorer shows all doors and nodes active under my polisy LAN IP

Hmmm. Seems like I have gone backwards. Updated to polisy 3.2.17, IoX 5.8.0 and ratgdo plugin 3.1.4. I did the node deletions and re-discovered. My 3 garage doors with ratgdo devices installed and configured properly are added and show again on ISY. For each door node, I see "door state", "lockout", "online" and "obstruction." All doors are online and correctly show the open or closed status. However, the "open" and "close" buttons no longer open or close the doors. The ratgdo plugin log doesn't show anything, but the MQTT plugin log shows "waiting on valid configuration." For the latter, I have entered custom parameters of MQTT_host ("localhost"), MQTT_port ("1884"), MQTT_clientID ("RATGDONS") and discoverytopicprefix ("home assistant"). Any suggestions? Doors had been working fine.

firmware is up to 2.56 now

Just finished final configuration. I made a mistake on the first attempt as I renamed the ratgdo device to ratgdo-east door" and it would not show "online" in AC. Changed the name to "ratgdoE" and now in AC I have separate nodes for the door function and light. Both work perfectly and I put the door node in my garage door programs in place of MyQ. By the way, the motion sensor for my liftmaster is at the keypad, so I don't need to have it as a separate node. Many thanks for constructing the plugin so quickly. Will continue to test and would be happy to contribute $ for your effort (MyQ was not your fault).

Not seeing the plugin on the production or non-production store!

Here is my setup so far on Mac OS: 1. Install MQTT plugin on Polisy, no special configuration 2. Open https://paulwieland.github.io/ratgdo/flash.html in Google chrome 3. Download USB serial driver 4. Re-start computer 5. Connect ratgdo to computer 6. re-open (2) 7. set version to 2.54 and hit connect 8. Erase ratgdo/install latest firmware 9. Once (8) is complete, set wireless credentials of your network, then connect to your (ratgdo) device 10. Rename ratgdo (optional), set ratgdo password, set MQTT server (your polisy LAN IP), port 1884, username (your polisy username), password (your Polisy password), topic prefix (ratgdo) 11.Save 12. Open MQTT explorer (MQTT-explorer.com) 13. hit "+" for new connection 14. name connection 15. protocol: MQTT://your polisy LAN IP Port 1884 16. Username and password: use your polisy settings 17. connection should now show the ratgdo device on MQTT Now just need commands to open/close, etc

Just figured it out. There was a problem with ratgdo IP assignment between my wifi and ratgdo. I am now connected to the MQTT server on Polisy, but await instructions on how to add garage door open/close, etc.

My problem is that I cannot save the configuration in ratgdo without a valid MQTT server IP and I have tried the LAN IP of Polisy (with and without :8443) but it does not connect to MQTT on polisy.

Agree with bullet points. I'm a bit lost.

Still cannot finish connection with ratgdo. When I connect to it, it has an assigned name and IP address (10.0.1.205) but my eero wifi app shows the IP as 10.0.1.207. I have also entered the MQTT IP from the assigned eero address (10.0.1.188) and even tried adding either :3000 or :8443 to this. Entered port as 1884 and left server username and password blank. Still cannot finish the final connection and ratgdo log shows no communication with MQTT plugin (I have not entered anything on the plugin configuration page). Any ideas?

If you look at Paul's GitHub site there is a section on orders and you can see where the device is according to order date

What MQTT IP and port settings did you use when you programmed the ratgdo? do you use the LAN IP of the polisy? Did you enter anything in the configuration of the MQTT plugin?

I received my Ratgdo and flashed the firmware and then opened the ESP window where you enter the device name, OTA password and SSID. It shows the LAN IP assignment. It also asks for the MQTT server IP, port, username, password and topic prefix. Where do I go from here? I have the MQTT plugin on my Polisy, but don't quite understand broker/client, etc. Incidentally, MacOS did not seem to work configuring the ratgdo so I used windows.

I sent for the ratdgo device but the setup seems daunting. I have 4 lift masters (3 8550W and 1 commercial Logic 5.0 so will try to set rated up on 1 to see how it works. Trying to figure out the wiring and MQTT but it is not intuitive. Count me in on testing.