wmcneil Posted March 3, 2022 Posted March 3, 2022 I have migrated from my 994 5.3.4 to IoP version 5.4.0 Everything is working as expected, except after an IoP reboot, a system busy window is popping up, and taking on the order of 10 minutes to complete. This is happening three times in a row, for a total of about 30 minutes of System Busy popups being present. This 30 minutes of time is happening even if I make no changes whatsoever to IoP, and only do a reboot. I have 4 zwave devices, 14 insteon devices, and 3 PG2 node servers (unchanged from 994 to IoP, except of course for pointing PG2 at IoP instead of 994). All of the devices and node servers seem to be behaving properly. Many of my programs are colored yellow, because the Elk nodeserver does yet support Elk thermostats. so I can't fix those programs yet.
brians Posted March 4, 2022 Posted March 4, 2022 I have experienced similar issue with previous version of IoP back when I first got it. For me, it was the query all program is doing this on startup. What I did was uncheck Query at Restart in Configuration, System. I then make my own custom query program that only does devices I want and this seems to be much quicker... I set this program to Run at Startup. It took a while to add all my devices but once is done I just have to maintain it. If you do not Query and know state of devices then some programs, scenes etc. may not work correctly, or not at all. I am interested in knowing what exactly the built-in Query does and why it hangs up like this.
wmcneil Posted March 4, 2022 Author Posted March 4, 2022 1 minute ago, brians said: I have experienced similar issue with previous version of IoP back when I first got it. For me, it was the query all program is doing this on startup. What I did was uncheck Query at Restart in Configuration, System. I then make my own custom query program that only does devices I want and this seems to be much quicker... I set this program to Run at Startup. It took a while to add all my devices but once is done I just have to maintain it. If you do not Query and know state of devices then some programs, scenes etc. may not work correctly, or not at all. I am interested in knowing what exactly the built-in Query does and why it hangs up like this. I did have "Query at restart" checked. After unchecking it, the issue goes away. I am also surprised, given the higher performance hardware of Polisy, that the query operations are taking that long.
gzahar Posted March 4, 2022 Posted March 4, 2022 2 hours ago, wmcneil said: I did have "Query at restart" checked. After unchecking it, the issue goes away. I am also surprised, given the higher performance hardware of Polisy, that the query operations are taking that long. The bottleneck is the Insteon and/or Zwave traffic, not a function of the Polisy hardware.
brians Posted March 4, 2022 Posted March 4, 2022 47 minutes ago, gzahar said: The bottleneck is the Insteon and/or Zwave traffic, not a function of the Polisy hardware. Yes, I think that I found before I disabled and made my own custom Query program that it would hang up on certain Z-Wave devices. In particular ISY seems to spend a long time with my Zooz ZEN25 double plug and I think it is sending power consumption updates frequently causing network traffic. I also think it is the ISY Maybe there could be an option on each device/node to exclude from query all, but my workaround seems ok. However, I do let the regular built-in query run at 3am and have not experienced any errors so it does work, and I believe there is more overhead with GUI when watching it from the Administrative console open.
Recommended Posts