SHM

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.

After upgrade to 3.2.13, MyQ stopped again with 429 error. No luck with overnight shutdown/restart. How sad, it was working so well. Guess I'll try ratgdo, but sounds complicated.

Yes, shut down for 5 hours, then restarted and it works fine. Thanks!

Long time user of MyQ node server and love it, but I have the same issue. Running Polisy 3.2.10 and IoX 5.70 and just updated MyQ server to 3.2.23. Changed password on the MyQ app, then entered new password on node server but still get Client 429 error.

1.1.23 not crashing!! Will report on geofencing tomorrow. Thanks Javi

I put it on the ticket site

I just completed the sysdiagnose but the file is 380 mb. Do you want the "crashes and spins"?

I have lots of files called "events" Here is the latest. JetsamEvent-2023-09-20-070359.ips.zip

Still crashing on 1.1.22

Here is the only error message that occurs after synchronizing with portal

Swipe up

Running UD mobile 1.1.20 on iPhone 13 and it is now crashing every time I close it. Running IoX 5.7.0 and polisy 3.2.6. Any suggestions?

Yes, I too have lost local AC login as well as PG3 login.

My disconnects have all but disappeared. For one polisy, it turns out that the ISP cable going to the house was partially damaged so the incoming internet signal strength was weak, causing the modem/router to disconnect. My other polisy (at a different location) has not had disconnects for a week now and I cannot explain why.

I am getting many of portal disconnect notifications in UD Mobile in 2 separate Polisys. I still have Mobilinc Pro installed. Could that be the problem?

I am still running PG3 on my Polisy. I am a bit in the dark as to the mechanism for changing to PG3x and if it wise to do this.

Tried Enable PG3x: https://polisy.local:8443/rest/pg3x.enable nothing happens after manual reboot

thanks

So how does one upgrade to PG3X?

Can't seem to upgrade my Polisy to 3.1.29. Running IoX 5.6.2. Have only tried upgrade via Admin Console.