apostolakisl

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.

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.

No, you just plug it in. Go to tools, diagnostics, plm info and make sure it sees your plm and has the correct address.

@HTTRC I feel your pain. I have a similar thread going here. Also lost two AC units. One was the control board for the air handler and the other the control board for condensing unit. Fortunately, I just happened to have a spare for the air handler and got it back up right away (I know it is weird to have a spare for that, long story. . ). They don't make those boards anymore (15 years old) but ebay had them for cheap, $50-70. So I bought a new spare for the indoor unit and a replacement plus a spare for the outdoor unit. The outdoor one is in my mailbox right now, hopefully that fixes that unit. Anyway, I also lost a load of other stuff including my PLM and Polisy. Also, my Elk alarm, my intercom system, a handful of Insteon devices, two webcontrol boards, one ethernet switch, my OBi voice modem, a couple security cameras, my doorbell, a handful of landscape lights, the charging brick for my automatic lawnmower, and more. Anyway, regarding your AC units, if I had hired someone, they would have just sold me two brand new units for probably $30k or something, so if you are up to it, you might take my example. REGARDING YOUR PLM You don't restore the PLM from an ISY backup. I'm assuming your ISY is working fine. Plug the new PLM in and under the "file" menu, select "restore plm". Don't do "delete plm"! If you have any battery operated devices you will need to put them in linking mode. Or just run the restore and then later go back and put those devices in linking mode and write to them later. If you have a large setup, they may time out of liking mode before ISY gets to them. The jist is that ISY will write all the links to the new PLM, but it will have to also change the links in all of the devices to point to the new plm. So it takes a while depending on how many devices.

When I built the house we looked at having lightening rods as part of the build. It was very expensive and of course far more extensive than this. I'm sure the professional one would work well. I just wonder if a rod like this DIY one is effective. So hard to know since it is such a rare thing. 16 years and this is the first time. I also am not sure exactly where the strike was. I can't find any physical damage anywhere. It was most definitely a lightening strike as my wife was at home and says there was a flash/bang simultaneous and instantly the whole house went crazy (mostly the alarm system). I have an Elk and I though those things were bullet proof. I even have the Elk surge suppressor on my system.

I agree, writing programs where you have to keep using drop down menus for everything is very inefficient. It is well suited to having just a few programs that are very infrequently modified because of the fact that you can't make mistakes and don't have to remember the language. Not at all well suited to having lots of programs.

Yes, i actually just ordered the same thing (different brand) from Amazon because UD is not exactly speedy at shipping.

Thanks for the info. Looks like need to move positions 3,5, and 6 to 1, 7, and 8. My wires have different colors than the other post. I'll give it a try when I get home from work. EDIT: Still no luck. I am confident I have the wires moved correctly. I'll order the UD one and see if there is an issue with the console cable, but I just don't think there was.

This is the part that concerns me: If the panel was modified by an installation company, it may retain their custom codes even after a factory reset.

i can't even buy a usb plm right now, out of stock. I did check and indeed the Insteon box is checked. I think I will take my plm's to my church and plug it into the 994i there and confirm that ISY recognizes it before I waste a bunch of time. I guess the next step would to buy the rs232 adapter from UD, but I really don't think it is different.

I will probably end up going to ebay for a used 1832. Trouble is you have to make sure that it has the factory programming password or at least one that they know and tell you.

My eisy came today but I can't get it to connect to plm. My old plm got fried in the lightening strike but I have two spares and neither will connect. via SSH, eisy says the serial adapter is connected. The PLM's are old but I am pretty sure both of them work. I did factory resets on both of them and both do the normal factory reset sound. Ideas? I am using a USB to serial adapter that I already owned, I don't think it is any different than the one UD sells. I tried different ports and have rebooted and power cycled eisy as well as the plm multiple times. [admin@eisy ~]$ dmesg | grep -i usb xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0 usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <Intel XHCI root HUB> at usbus0 uhub0 on usbus0 uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus0 CAM ugen0.2: <FTDI USB Serial Converter> at usbus0 ugen0.3: <vendor 0x8087 product 0x0026> at usbus0 uftdi0: <FTDI USB Serial Converter, class 0/0, rev 2.00/6.00, addr 1> on usbus0 ubt0: <vendor 0x8087 product 0x0026, class 224/1, rev 2.01/0.02, addr 2> on usbus0 [admin@eisy ~]$ Eisy says

Eisy comes today. I'll open it up and see if it uses the same msata drives. If so, I'll try putting the polisy one in and see what happens. Unless someone thinks it could somehow harm the eisy. And more fried stuff being found. Of course my plm is dead. But a curious one, I have a whole house sound system with 6 controllers that are hard wired back to the main unit. One of the controllers is dead. The rest of the system is working normally. That one controller is in a j-box containing a 2476d switch that is also dead. The j-box is a split jbox, so the low voltage side is decisively separate from the Insteon swtich side. Other Insteon switches controlling the same light and using the same hot wire are fine. How does this happen? To add the insult, the system I use is no longer made and I can't find any individual controllers on ebay. And my intercom system isn't made anymore and I can't find those on ebay, but I can't even figure out what is the faulty part(s).