apostolakisl

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.

If you are using an Insteon IO link to control your garage door then it could respond to an "all on" and open the door. The "All on" issue is something I have not heard about for years. Search the old threads in here about it. I don't believe it was ever nailed down as to exactly what causes it and perhaps there is more than one thing. I don't think it is the ISY that is doing it and I doubt replacing it will fix the issue. But I have seen where it will mysteriously start, then just as mysteriously stop happening. I had it happen a couple times many many years ago for unknown reasons and then I haven't had it happen again in over a decade. I did not have any battery devices at the time. I assume you are using the most up to date firmware for your 994i. That unit is no longer supported and the most recent firmware is a few years old. However, that firmware is very stable.

Yes, if you can't find a switch: use the swirly arrows to put ISY into INsteon linking mode then push and hold the set button. If it is already added, it will say so and show you the Insteon address. Then click on "home" in your tree of devices and in the right pane it will show all your devices. Click on "address" to sort by address then you can scroll down to the device and see what it is named and what folder it is in.

What @paulbates said is probably the solution. Have you checked your list of programs to make sure you don't have a wayward program turning them on? Maybe write a program that sends you an alert if any of the switches turns on. Then you can see what time the alert arrived and go back to your program summary page and see if any programs executed at that time. Also, knowing what time it happened can maybe give you a clue if there is a bad link to some other device. Say for example, the light turned on at 3am and at 3am you used the bathroom and turned on a light in the bathroom or something. Also, is the whole scene turning on, or just one of the devices in the scene? If the whole scene is turning on, then you might consider deleting the scene and recreating it as well as deleting the devices and re-adding. Don't forget, when you create a scene and add switches as controllers, you need set the on level/ramp rate for each of the devices in the scene that are controllers. ISY used to have an option to automatically do that for you, but they got rid of it. Supposedly something to do with adding in z-wave and other technologies to scenes which created errors in that process.

This would be nice. My intercom system just got fried and can't be fixed unless I happen across some parts on ebay. I already have CAT5 to all the locations and could install wall mounted tablets using poe. To complete the picture, some sort of intercom system capability would be nice. Maybe a tile in there that lets you video conference between different tablets. I assume a third party tablet to tablet video streaming that you can plug-in as a tile?

I assume you have the elk xep unit and it is connected to your LAN. It has instructions on the config page. Here is my setup. Once you do that, it all shows up on the ISY admin console and you just plug the nodes into programs as you see fit.

If you have a second 994i, you can try to do a factory reset on that and install your backup there.

i think he is saying that restoring from backups isn't working. @HTTRC I take it you only lost your plm and your 994i is still functioning. You should not have had to restore your 994i from a backup if it was still working. But it sounds like you did that and now the 994i is corrupt and won't load any backups?

This worked.

My Polisy and PLM got fried in a lightening strike. I had a backup plm and got an eisy. System worked well prior to the lightening. Restored the eisy from a polisy backup that was just a few days old. Did a replace PLM with the new PLM. Then did a restore devices because it wasn't working right. Now this: 1) Lots of scenes when controlled from eisy do nothing. 2) Lots of scenes no longer have settings for the devices but rather say "default". Not all of them, but in some scenes it is all, other scenes just one device, some scenes none. Below is a scene that is supposed to have levels for all those devices. Links table for devices does show the new PLM address (for the handful I checked) EDIT: I've discovered if I take a scene that is not lost its settings to "default" and go down the list of devices and hit "update" for each device. The scene then works. What gives? EDIT2: Tried restoring two other ISY backups, another one from a few days ago and one from 6 months ago. They all are the same. Most of my scenes have "default" instead of the settings that are supposed to be there for all the devices. And the same restoring a 2 year old backup

But he is also getting an error when trying to restore plm. I assume at some point in all of this, he has done a full reboot, power cycle and all.

You won't need any gauges. It is probably the circuit boards. If it is the compressor, then again, no gauges needed, the compressor just won't run. If your AC unit is really old, it won't have any circuit boards, just a contactor and a thermostat. You can check for voltage at the unit with a multimeter and see if the contactor pulls in when the thermostat calls. If not, you can manually push it in with a non-conducting rod of some sort (like a wood pencil) and see if the compressor starts. if not, you might be toast. Could be capacitors. If it is capacitors, the unit will try to start but fail. They can be replaced easily. If the thermostat is calling, but the contactor doesn't pull in, it could be the thermostat.