apostolakisl

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.

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.