SHM

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.

I am having the same issue. No problems with internet or power.

I tried all those things but still have no luck. IoX launcher displays the LAN addresses fairly quickly but need to "load" the saved IoX finder to display the WAN addresses. Weird. Only happens at 1 site.

So both locations have virtually identical networks (equipment, speed) and the laptop is used for both. For site 1, the IoX launcher opens the LAN AND WAN options almost immediately. For site 2, I just tried and launcher initially was blank and at the top of the window it displayed "IoX finder not found." After about 30 seconds, the LAN option for site1 appeared. Waited several minutes, then hit refresh and the LAN for site 2 appeared. No WAN options unless I load it from a saved finder file.

The Java memory was at 512 so I increased to 1024 with no effect

I have 2 nearly identical Polisy systems running at separate locations on the same type of network. Running IoX 5.6.0 and PG3 3.1.20. I have noticed that on one system, when opening IoX launcher the finder immediately opens the WAN and LAN options for both sites. When I open IoX launcher on the other system, the finder opens very slowly and often only the LAN address for the second site is displayed. Refresh does not do anything and opening a saved finder file does display the other WAN/LAN addresses, but very slowly and only for that session. I use the same laptop to open IoX launcher and it has the latest Java. Any ideas?

Just lost all communication with Insteon devices. Have tried ISY and Polisy reboot with no luck. Running IoX 5.5.9 and PG3 3.1.20