stillwater

Thanks! Luckily I'm not using any plugins. I seem to be stuck at 5.3.0_1. The upgrade page offers 5.2.0_1 but then it doesn't load, presumably because 5.3.0_1 (installed) is greater than 5.2.0_1. Hopefully 5.3.0_1 is just 5.2.0_1 with another name and the next version will be > 5.3.0_1.

On Staging Repo. Yesterday (afternoon? in US MT) Eisy offered an upgrade of UDX. I didn't pay attention to the version numbers. After upgrade, my UDX is at 5.3.0_1 according to the package update page yet the "update" offered is now 5.2.0_1. System seems to be working ok. Maybe there was an upgrade that was briefly available and then withdrawn? Should I be concerned? Will this preclude the next upgrade?

If you can reach your eisy's administrative console (using the old fashioned access via java), all the old ways still work there.

Years ago I remember reading that the process is fickle and will stop short of completion if there is other insteon traffic being processed by the PLM. So that can explain the low link counts. This was represented as something inherent in the process but I suppose a smarter software routine in IoX could do a better job an keeping track and re-starting where it left off. The high link count is not something I've encountered but could be explained by the process repeating and the second run-through being appended to the first. This should be apparent in the table.

@mmb The lat/long was/is correct. Today the sunrise/sunset times are displaying correctly on the eisy.ui configuration page. I don't know if this is because of some invisible software update (as mentioned by someone in the forum) or whether it just took a day for the sunrise/sunset times to display correctly (as mentioned by others).

In the AC under Configuration/System/Clock, I see a check box for "Daylight Saving US-Canada]. If you uncheck this does it solve your problem?

I am in US Salt Lake City time zone on staging repo (1.4.8). Time change was correct. Sunrise/Sunset times are both an hour early. Rebooting eisy did not change display. Not surprisingly, sunrise and sunset are also an hour early in AC.

On the staging repo eisy.ui (1.4.8), when I go to System/Configuration and click on the i at the upper right corner of the sunrise/sunset display graphic, under "Details" there is a box labelled "DST Rule" with a drop down menu that has "off" as one of the options. I haven't tested this.

point taken, though It looks worse in the picture than in person

Here's what it looks like on a MacBook Pro laptop using Chrome with the dark eisy.ui theme. Perfectly legible.

On October 22 you were told that on the Settings page "Display is the third tab (the rightmost one at the top of the screen)." Hard to see how a description could have been clearer than that. But you discovered it in a black area all on your own.

something about your computer seems different from mine and obviously also different from what UDI used when they designed/tested. You should stop to think that UDI wouldn't have delivered a design that looked the way it does on your system. But instead you just assume everyone else has the same experience you do and you "suggest" UDI conform to your experience. I find some readability problems withe the light theme (low contrast with some of the colored messages about update status) but I would never suggest that this was "ridiculous design." Might have been helpful to explain something about your setup. Also might have been gracious to thank those who went out of their way to tell you exactly where to find the Display setting rather than acting like you found it all by yourself. I'll certainly be less likely to help in the future if I remember your handle.

Presumably a particular module version generally makes its way from staging to beta to production repos and so the date corresponds to the date the version was completed rather than when it appeared in a particular repo.

@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.