apostolakisl

maybe isy had a static ip address set and the new router is in a different subnet. When ISY works, you get a new router, and now ISY doesn't work, logic would say there is nothing wrong with ISY and that it is the router configuration. Put your new router on the same subnet as your old one and probably ISY will show up.

My condolences for buying a neo system. There is no linking that to anything, unless you live in Canada and then you can use their app and only their app. Back to your Elk. Were you using Elk to directly control Insteon devices or were you going through ISY? There is no reason for removal of Elk to have anything to do with Insteon traffic except perhaps if you had the Elk working directly with Insteon. I forget exactly how Elk direct control works to say for sure. Looking at your system, you don't have a whole lot of devices. You might just consider deleting everything and readding. Perhaps you some orphan links that are messing with things from the Elk removal. If you delete the devices one at a time and add them back in, any devices in programs will go right back into those programs. You will have to rebuild your scenes. After you do that, you either need to go into each program and hit any random item then "update" then "save" or the program won't work. I think rebooting ISY will also make the programs work again.

Troubles here. I can only assume it is related to this update, but not sure. I haven't done anything else. Things in my house weren't working. I Logged into admin console to see what was up, it had a pop error "loading nodes: retry". It said "linking" in the bottom left corner. Never seen this before. It kept doing it and doing it. I finally power cycled. Opening iox finder, listed was just a single ISY at https://mylocalip/desc After I did the upgrade yesterday, it listed multiple versions of ISY at different ports. Now just the one. I now had to use my portal user/pass to log in even when selectin "lan". OK, I think that was to be expected. But what is up with it stuck in "loading nodes" and not doing anything. @bmercier EDIT: One good thing seems to have happened now. My java admin console is now staying alive. Prior to this, the admin console would lose connection after just 10 or 15 minutes and I would have to re-login. It has now been up continuously for 19 hours.

@bmercier Is the eisy ui intended to only be a user interface or an administrative interface? As a user interface in my situation would get very limited use, but using it as administrative interface would be golden. Writing programs, creating/editing scenes, working on notifications, network resources, all that stuff. The java admin console is just always hanging up.

Collapse all would be appreciated. Expand all would not be a button I would ever press. Search function is super helpful when you know the name of what you are looking for, but it is not uncommon to not recall the exact name of what you are looking for. Why someone would want them all expanded is lost on me. If that is what you like, save yourself the extra work and don't bother making any folders in the first place.

That worked. Now I just need to figure out how this works. First impression, I clicked to create a tile and got a list of my nodes. Every folder was fully expanded by default. The standard admin console seems to do this too. This kind of defeats the whole idea of putting things in folders. You should have them all default to closed and let the user drill down to what they want. Having all the folders expanded is almost the same as not having folders.

Based on the other posts in here, it appears that "upgrade packages" is not putting the eisy-ui on the system.

As instructed, I did upgrade packages (not developer one). eisy.local in a web browser does not work. Nor does http://xxx.xxx.xxx.xxx. or https://xxx.xxx.xxx.xxx where the x's are the lan ip of ISY. And Iox finder does not find my isy at any address except the usual https://xxx.xxx.xxx.xxx:8443. If I try to manual add to Iox Finder http://xxx.xxx.xxx.xxx and https://xxx.xxx.xxx.xxx it does not find anything. Nor does it find http://eisy.local or https://eisy.local In a web broser https://eisy.local:8443/desc finds my ISY and it gives me a bunch of configuration information that starts off looking like: In summary, eisy is not responding to anything on port 80 and 443, but it responding to 8443 using both lan ip and eisy.local. So eisy just isn't listening on port 80 and 443.

I did a power cycle on eisy and still no UI. Am I supposed to be doing the "developmental packages" here? I just did the standard package upgrade.

yes

either way, the launcher only finds ISY's on the same subnet. But looking at the history of updates, it seems like 5.9.1 is not new in the last 24 hours (or even close to that) and that is what isy admin console says I am on. Unless this has nothing to do with the ISY firmware version but rather something else on the eisy box.

And of course Iox launcher has no problem finding it. definitely on the same network. no problem using local ip address:3000 to launch pg3x

I have a router to router vpn between my home and office. But I can't see how that would mess it up. I am currently local to isy and on the same subnet. no, that doesn't work either but I can still get to pg3x by putting the local ip address:3000

I did the upgrade packages. It says I am on 5.9.1 at this point. I forget what I was on before. This is a new eisy, only had it less than 2 weeks. It says it did an upgrade and it required a reboot (which I did). Now I try to go to http://eisy.local/ and it says "site can't be reached". I tried putting in the local ip address of eisy and it is also a dead end.

It is because the program is terminating when the motion sensor goes back to normal. Those are status conditions, they trigger whenever the status changes regardless of what it changes to. So when "violated" occurs, the program triggers, turns the lights on, and starts the timer. But the sensor will return to "normal" prior to one minute, the program will then stop and start over. But it will now be false, which runs the "else" clause, which is blank. To make this work, you either need to use "control" commands in the if clause since "control" commands only trigger on the precise action. Alternatively, you use two programs, the conditions are in the first program and the actions are in the second program. If elk thing 1 is violated or elk thing 2 is violated Then run then program 2 Pgm2 If (blank) Then turn light on wait 1 minute turn light off.