paulbates

This happens occasionally with major upgrades. The best bet is to use UDI's responsive support: universal-devices.com/my-tickets/

It looks like 2 things were going on at the same time? Replacing a computer that's used to access iox/admin console Replacing PLM. I'd recommend dealing with one of these at a time, and start with 1 I'm not familiar with copying files as part of moving to a new PC, the necessary files and data are in the ISY9994 Uninstall java Reinstall java Clear java cache Download the latest launcher Review this post for specifics Once you can access iox/admin console on the new PC (1), then we'll move on the PLM (2)

Logs are going to help of the time this happens: The general ISY log Event viewer, set to level 3 Logs of the ecobee plugin, set to debug level log EDIT: Any chance the kitchen 3 way is a scene, and somehow ecobee is in that scene? Review the members of that scene. I know sometimes my "mousing" of iox can drag and drop to the wrong place

There's 2 methods. One is linking mode. The other is to add a new Insteon device from the linking menu. You need the six hex digit Insteon id, formatted like this 12.34.5A. It could be digits or the letter A-F. Its found on sticker on the front of the switch, you'll have to take the faceplate off. When you do this, conversation starts with the ISY and there's nothing to do at the switch end. Typically, it will beep when the ISY contacts it. Try that from the linking menu.

It's a communication issue or a dying switch. Since it's single band, it's more vulnerable to line noise... new plugin transformers, tvs, fans.. could all be contributing to this new problem A new dual-band switch will help, but not necessarily fix the problem without eliminating line noise as the problem; this is more involved to exactly isolate A new switch is $55 +shipping, I'm trying to imagine how much less a repair would be compared to just replacing a high use, older device... repair usually means replace capacitors, but not the physical plastic parts that wear down with use There is a replace function, but it's highly sensitive to replacing with the exact device. It would probably work but there's a chance you'll have to visit scenes and programs if it doesn't. Usually its not that bad to do. If it were me, I'd replace an old, single band highly used device. If comm issues persist, post back and we'll step through it.

For submitting the ticket, do you have ad/content blockers on your browser? Try again in a private window or turn off ad/content blockers for universal-devices.com... or try a different browser

Do you use the blue UD icon that is installed on the desktop with the admin console? If you click that, it will bring up the launcher locally from the java cache. When you click on your ISY, do not pick the cloud option, and it will work locally from java cache. Look at this post for the step to restore the blue UD icon if needed

You shouldn't need internet for the launcher and iox to work. As long as you do not click Cloud in in the launcher, it will stay local Are there specific symptoms for what you are experiencing?

@Techman's factory reset is the next logical step, then a restore device. Possible it will fix it, if not replace it

The PLM shouldn't affect the ISY, but if it was a brown out and it affected the eISY, it may have affected the PLM too. My comment was more about pulling the plug on the eISY versus rebooting as it could be the electronics affected, not the software

Based on your write-up, it seems that it's the eISY. One possibility is if there was a brown out, the hardware of the eISY could have been affected by that. Have you tried unplugging the eISY and the PLM, if you have Insteon. Wait 30 seconds... Plug in the PLM, wait 10 seconds and plug in the eISY?

When java is refreshed, you need to re-download the launcher: https://isy.universal-devices.com/start.jnlp Delete existing links/icons first

Ok. Policy has both, my bad recollection. I wouldn't upgrade if you're not experiencing problems

If you don't have a need to upgrade, not experiencing problems or limitation, I'd stay as you are. Not sure the time and $ involved would serve you vs investing in additional automations. Maybe proactively change your SD card in your ISY. The product history is - ISY 994 - Node server capability added years ago and a separate server was needed - Policy became UDIs official method of hosting node servers - eisy does both functions in one box

Yes, that block of code would be needed including the Repeat 1 time, which simply marks the end of steps in the repeat loop. If your count down scenario is the same for all zones, you could put this repeat -countdown code in a separate program (with no if) and call it from each zone's program. Might take some experiment and testing, but it's plausible.

Yes, you'll need a PLM. You can move your existing PLM over, but if it's a serial PLM you'll need UDI's special serial > usb cable. Sometimes these migrations require you to spend a lot of time re-establishing Insteon. Since your PLM is that old, it comes from a time before they made production changes... maybe get a new PLM now and switch over and get it over with during your upgrade. We can talk about the steps later if you choose to go this way One more thought... Insteon is releasing a new version of the PLM, they say this summer. If it was me, and my system was working ok... I'd wait till later this year and upgrade to a new eisy, new re-engineered PLM... go through the upgrade headaches all at once... and let it sit another 10 year.

Insert @IndyMike's suggested repeat loop steps at this point in your program Then $I.MinuteCount = 2 Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Basement / SC BSMT Entry' Off Obviously tweak the variables of the loop to count down your desired wait time

I have to believe it's via Node-Red. Since no one else answered this, I'd open a ticket with UDI and point to this thread and ask them specifics. Posting back how you successfully got it work here afterwards will help others in the future.

Ok. Where/how are you telling it to turn on? With UD Mobile App? Or using geofencing in the UD mobile app so it tries whenever you get close to home (driving, etc)?

See the Programs, right next to Main.. click that one and it will let you create the program iox is the new name for the software you are seeing, the admin console.

Have you logged into the iox java console, or did you do everything in the UD Mobile app? The programs tab in the iox java console is right next to the network tab, which is where all of your devices are. That's where you'll create that program

This works on 994, Polisy and Eisy

Hi and welcome to the forums! Yes you can. The scene you created is considered a 'virtual circuit'... meaning use it, and it only to control the lights together and not the devices themselves 1- For dusk - dawn automation, you create an iox program that looks like this New Program - [ID 005E][Parent 0001] If From Sunrise To Sunset (same day) Then Set 'Lighting Indoor / Virtual Circuits - No Program / Living Room / Lamps' Off Else Set 'Lighting Indoor / Virtual Circuits - No Program / Living Room / Lamps' On This is how it looks in iox when you do it, substituting your scene for my sample above The Set ... lamps on is my scene for 2 lamps, turn the Scene on and off, not the individual devices. The scene icon looks like this in iox 2- Use the same scene in UD mobile... Turn the Scene on and off, not the individul devices. Hope this answers it

Yeh I forgot to mention that the old iox desktop icon(s) need to be deleted before downloading start.jnlp so it doesn't get confusing. Sounds like you got it working so its all good!

You'll want to down load a new start.jnlp https://isy.universal-devices.com/start.jnlp That should get you in business