stillwater

@mflieger Just wondering whether the eisy needed a reboot to work properly after the installation of the new IoX. I routinely do this. I haven't seen clear guidance from UDI on when a reboot is needed.

For @bmarsh ---- @EricBarish told you where in the section you quoted Access the menu by clicking on the three bars at the top left of eisy-ui. Settings is the second option from the bottom. Display is the third tab (the rightmost one at the top of the screen). Presumably you want to chose Light (bottom radio button) or System Default (top radio button).

In my case I had (still have) a micro open/close (or on/off) that twice within a month opened in the middle of the night at the time of the query all. Initially I saved the state of the device before the query all and then reset it after to deal with the problem. The device was not mentioned in any other program that was active at the time. Since I have no problems with devices getting out of sync, I then disabled query all. This was around 2016, I think. No problems since. Additional thought: I can't remember but it's possible a failing PLM was part of the problem.

My understanding is that the original purpose of query all was to true up the state of ISY internal tables with the state of insteon (maybe also X10) devices. With the advent of dual band (RF as well as powerline) communications and users becoming more sophisticated about improving comms this became less necessary. The flurry of signals from the query all program can introduce its own errors, with devices turning on for no evident reason. While UDI apparently eliminated it in clean installs with v 5, it survived through upgrades (install from back up) in many user setups.

Now works properly on my eisy -- IoX 1.4.6 (staging repository)

This has been reported previously. In my case, opening the AC demonstrated that the routine was running and the eisy was receiving links from the PLM; the results just weren't being displayed, as if the display routine prematurely aborted. There may have been some questioning from the UDI team whether this was local or remote (through my.isy.io). In my case it was local.

I have a nonstandard (decade old) node server and I got the same message after an upgrade. either just reaccessing the same page or rebooting eisy (I don't remember which) made the error go away. I didn't regard it as bizarre.

That being said (about where to find update version notes), there are no new notes for UDX 5.1.0

next to each new package on the system upgrade page there is a question mark in a circle. Click on that to see brief notes on what is new in the package. I agree that the scroll bar needs to be put back. In the meantime using the browser settings to decrease the magnification (zoom out) allows display of all packages at once.

maybe try to look at the event viewer or IoX logs? all the actions are tagged with a time. This should be generated by IoX not eisy-ui. -- at least that is what I assume. Logs are found in eisy-ui as a tab under the system menu. Event Viewer is a tab on the log page.

yes sorry eisy.local:3000 etc. 3000 was the port for PG3 when eisy (or polisy?) was first introduced so I am guessing there is something in the PC or Chrome cache that was doing this even though eisy was connecting and inviting login. eisy was accessible using the ip address. Some combination of clearing the chrome cache and setting up an alias in the Hosts file fixed the problem (I googled to find out how). I suspect that this was always an issue with my PC rather than with eisy.

@Javi I am using local connection -- on same LAN. login using eisy.local. It seems to run the query but almost before the query would have time to show any data the box says no records found.

rebooting eisy did not fix mine either.

THis is odd but by no means an urgent issue. Two machines both using wired ethernet on same LAN, both using Chrome browser. Mac works fine with eisy.local and numerical ip address. On PC eisy.local login fails --gets to password screen then redirects to eisy.clocal:3000 and eisy refuses to connect (according to chrome). Can log in on PC using ip address but on the system upgrade screen only three packages are listed-- eisy-ui, IoX, and UDX. This is with staging repo-- 1.4.3_1, 6.1.2_10, 5.0.0_7, PG3x 3.4.26, and mosquitto 2.0.18 . Rebooting eisy and restarting Chrome did not affect this behavior. CORRECTION -- The part about the PC only displaying 3 packages is only partially correct. If I zoom out using the Chrome scren % tool, both the pc and the mac show seven packages. I had thought earlier there was a mechanism for scrolling but there isn't currently, or at least not that I can find. So the only difference between the PC and the MAC is that the PC can't access via eisy.local. the page needs a scroll bar for the packages or a format that shows all at once. the eisy.local access problem seems likely to be solved by clearing a cache in chrome or by creating an equivalence in c:\Windowas\System32\drivers\etc\Hosts -- but it's not really something that needs fixing.

I just checked my eisy... with eisy-ui show PLM links reports "no records found" -- But it also says system busy and event viewer shows eisy receiving something like 870 lines, presumably from the PLM. In fact if I open the admin console it shows the PLM links table scrolling on the screen in response to the eisy-ui initiated process. Clearly something is amiss with eisy-ui display. Otherwise system is behaving normally. This is with eisy-ui 1.4.3_1 and IoX 6.1.2_10.