landolfi Posted June 30, 2022 Posted June 30, 2022 I have searched without success for a help topic concerning admin console timing out after some period of time, seems to be 30-60 minutes. When it does, sometimes it presents the ISY login dialog, and others I have to completely relaunch admin. The result after this happens several times is orphaned instances of admin console with dead buttons in the button bar. Not a showstopper but very annoying. I found an old post with a similar issue that suggested clearing the java cache, but that's greyed out because "Keep temporary files on my computer" is unchecked. Running 5.3.4 firmware and UI, Java 8 Update 333 (64-bit) on Windows 10.
jec6613 Posted June 30, 2022 Posted June 30, 2022 Are you on WiFi? The AC is very sensitive to even a momentary connection drop, I had to disable all of my NIC's power saving to keep it from disconnecting periodically - but since then, well, I launched it 2 days ago and it's still open and connected.
landolfi Posted June 30, 2022 Author Posted June 30, 2022 Thanks for the quick reply. Yes, the laptop running the admin console is on wifi. I'll check sleep settings and also try remote desktop with a wired PC running the console to see if that's the problem.
Solution Geddy Posted June 30, 2022 Solution Posted June 30, 2022 @landolfi admin console isn't intended to be left open 24/7. What's your reason for leaving it open for so long? The main function of admin console is simply to setup the ISY function. Once setup things should just work. And therefore no other user intervention through AC would be required. If you're looking for a different option then I would suggest getting UD Mobile and running on a mobile device. Still not expected to be kept "awake"/active 24/7, but seems to be much better for being left running in the background (at least on my iPhone) and opening and connecting on demand if/as needed. But again, the whole part of automation is not to require user intervention. There have been lots of reports (as I recall...several years ago) of issues similar to what you experience. It's a nature of the beast of Windows+Java. It's not meant to be constantly running. So what you are experiencing is "normal". Just close AC after each need and launch again when needed again.
landolfi Posted July 3, 2022 Author Posted July 3, 2022 Thanks, Geddy. Yes, that makes sense. It also makes sense that most, no basically all of my devices just work fine and I also probably shouldn't be querying them over and over again and wondering why the queries sometimes time out, particularly after I have added a new device. So this is mainly because I have too much time for things to work properly without my intervention.
Geddy Posted July 3, 2022 Posted July 3, 2022 @landolfi There's a daily program that was default that does the query daily. That's probably the best just to have maintain connection. There's no real result to it, but I think some have found a way to write other programs based on it. Look in your Program tree for a "Query All" If you don't have it you can recreate it: 00-Query All - KEEP - If Time is 3:00:10AM Then Set 'ISY' Query Else - No Actions - (To add one, press 'Action') To find the "ISY" for the THEN action use "Your Devices" and look for ISY or what you might have called your ISY. Be sure to look all the way up and down the list as some have said it ended up below the scene devices in their list. It's more or less just to keep devices in sync. 1
landolfi Posted July 4, 2022 Author Posted July 4, 2022 Thanks very much. I had that query a long time ago before I used the ISY much and deleted it because it seemed unnecessary. This explains why it might be useful.
Recommended Posts