MrBill

Clear the Java cache, and then follow the instructions in the thread linked below to use The Launcher. The Launcher is the newer method of accessing the admin console that always gets the correct version to match your firmware.

your new panel should come with an installation manual. the manual should have pages with the programming worksheet. Watch out for errata sheets too, I haven't done a Vista in 20 years, and it was a different series so they may have gotten better, but they used to be famous for "this is the updated step 12 on page 30".....

The only deviation I would add to @Bumbershoot, is if the new ISY has a z-wave board you'll need to check the version. I don't know when UDI started shipping them with 500 series boards (and you mentioned it's been in the box for a year). If you find the new unit does still have a 300 series board and you're not using any z-wave you might need to either remove the board from the ISY before going to v5.3.1. (I'd check with support@universal-devices.com). if you are using Z-wave then the furthest you can upgrade the firmware is 5.0.16C. (then you can upgrade the z-wave board at your leisure and then finally move to 5.3.1 after).

1 is faster. It resets the device and clears all the links in the device. The ISY still knows the correct version of what needs to be there. Select the device and then right click it and choose restore device, the ISY sends all the links to the device. under #2 your doing the same basic thing in the end, but with alot more steps. removing the links and deleting from ISY, then factory reset the device which is the actual end game, then putting it all back in.

@agudenit sounds like communication is working in one direction but not both ways. The ISY's signal is reaching the switches and they hear it, but when they answer or acknowledge the transmission in the other direction the ISY can't hear that. I'm not certain what to suggest to resolve it tho.

They are easy to find type "2 pole 30 amp contactor 120 volt coil" into amazon search (be wary of amazon search, it tends to mix in others that don't exactly match, double check your choice for all values including coil voltage). Be aware that some are noisy, some are quieter than others. I prefer to stick with name brands like siemens, Eaton, Square D, etc. You'll also need a proper enclosure, if it's metal be certain to follow proper grounding protocols.

If you've resolved your problem be sure to close the loop in other threads where you have queries hanging, so that no on needs to spend time on a resolved issue. Here is one:

typically the red ! will hang around. when I see one I right click on the device and pick query. The ISY then asks the device for its status. if the ! goes away at that point communication was successful.

If you enabled Run on Start for every program that's typically unneeded. Depending on the program and what it does Run at Start may or may not create undesired behavior. Typically ISY programs run on an event queue basis, "Run at Startup" forces an extra run at startup. If the UI and Firmware versions don't match exactly then that's why programs look wonky. Follow the instructions in the following thread to use The Launcher. It will ensure that you are launching the correct version of the admin console for your firmware version.

Be certain to notice the LEVEL dropdown at the bottom of the window. Changing to Level 3 is what turns on Device Communications.

Have you recently deleted a scene? I believe the looks like those attached to scenes. DOF is the off action. I recently accidentally deleted an insteon device while repurposing it. I meant to remove it from the scene it was in but instead removed it from the ISY. Then I just deleted the scene it was in. Later I found programs with simmilar comments added IN PLACE of the previous scene commands. .

1 - Highlight the row in the Summary tab by clicking the name of the program. 2. Right click and choose "Enable Run at Startup" (with the cursor on "Enable Run at Startup" as shown you must left click to make the action occur) 3. View the Run at Startup column to ensure it now says ON. 4. Done. Alternatively I just noticed (I've never used until now) you can also click the row to hi-light it, then use that dropdown above the table to choose "Enable Run at Startup" then click the Apply button to the enable the attribute. If these steps are not working for you please check the Help > About menu and make certain that your "Firmware version" and "UI version" numbers match exactly.

I just played with one 100 Watt equivalent A19 style that I can see from my laptop it seemed to go completely out at 6 or 7% I didn't go take the shade off tho so that I could actually see the bulb, that's plugged into a lamplinc plug in module. The difference made me wonder of age or hardware revision of Insteon made a difference. When we originally bought the A19's I set up a demo with a 100 watt incandescent side by side. The warm glow did get yellower faster, or more specifically at higher dim level, but with each at 100% neither my wife or I could see much difference. (She used to own a lamp and lighting store and is pickier than I am about color temp) The candelabra style bulbs that I have are really only used in carriage lights outside and come on at 15% from Sunset to Sunrise. They very warm in color, in emergency mode they do shoot up to 100% and my memory is pretty white, I'll have to look at them in that mode again tonight. I'll check what % they extinguish at then too

You'll like the Phillips Warm Glow... they are the best dimming bulb made in my opinion. Warm Glow (or for color Hue) is all I buy now, I do still have some cheap bulbs in the garage and storage room etc. but for the most part I've changed over most to warm glow.

Sorry, yes it's correct. I would have called it out if it wasn't. When I type these programs in the forum I'm doing it off the tips of my fingers and memory (and maybe cut and paste from a program posted above) and not using the admin console so their may be variations in the format, you correctly selected "then path" as opposed to my just labeling it (then) I'm confused where we are with [Run at Startup]. On the Programs | Summary tag we want to see: Except with your Program name "Gutter Heat Initialize", but see how on my example it says "On" in the second column over? this will also add square bracketed [Run at Startup] to the end of the first line when you page the program in the forum, like this: Startup/UptimeCounter - [ID 008D][Parent 0001][Run At Startup] What "Run at Startup" actually accomplishes is forcing this program to Run during the ISY boot process. The Reason we want this little two line program to Run at Startup is this condition scenario: You're away on vacation, A winter storm arrives, the Gutter Heat turns on, melting begins... then the power fails, everything stops. When the power utility turns the power back on the Insteon modules will return in the ON state, but when the ISY boots up it won't initialize the programs correctly because the snow sensor and the temp alarm are likely already calling for melt. So the solution is this two line program, being tagged to Run at Startup.... it will wait 5 minutes, then turn off the Gutter Heat, at the end of the off loop if it needs to be on, it will turn back on but it it no longer needs to be on it will stay off. Edit to add: it doesn't matter if this runs when the heat is off (summer) it just makes sure its off. the real issue is that the OFF program is disabled, so we need to make sure it's running and the best way to do that is just force off state anytime we boot the ISY, so that if the gutter heat is turned on the ON program will have started the off program. So to specifically answer the question "Also am I supposed to run the Enable Run at Startup in right hand context menu after ISY starts up ?" No, you don't have to do anything after the ISY starts up, but we do want the "Run at Startup" program attribute turned on for this program. and to this question: "I forgot to ask whether or not the last program "Gutter Heater Initialize (run at startup)" ) was enabled or disabled ?" Enabled is correct.

Hmmm, I started to say Yes it did, but you must have typed the run at startup in the title. the Actual automatically added tag would have been [Run At Startup] Did you switch to the summary tab? did you see the option? I'm not sure what "did not work" means. Did you select that and nothing happened?

@satwarYou might add one more program, the condition it handles is what happens if the ISY reboots while the heat is on. Gutter Heater Initialize (run at startup) If (nothing) Then Wait 5 minutes Run Program 'Gutter Heater Control OFF (disabled)' (Then) Else (nothing) The 5 minutes give the ISY time to finish booting up and for the Insteon Query on startup to finish. Then force runs the off program. Hint: to enable run at startup, create the program and save it, then Switch to the Programs | Summary tab, click the name of the program there to hi-light it then right click and you will see "Enable Run At Startup" in the context menu.

@smarthome_newbie My bet is on the power supply. There have been quite a few lately it seems. Note that the voltage requirements are very wide, meaning a wide variety power supplies will work. UDI also sells a 12v 1amp replacement in the store.

The safest way is to attach too large a load. It's max is 600 watts, so if you connected it to say 1000w incandescent load it would burn out. Another nice load that would be over sized would be to wire it up to a circuit with a space heater or hair dryer plugged in. I don't recommend it but the nuclear option is just connect the red lead to ground and turn it on (and black and white to hot an neutral as normal). Be a safe distance away and consider eye protection, the pop should be short lived and contained tho. If the breaker doesn't trip don't leave it powered long.

Yes but to upgrade from a version less that 5.0.9 you must use a later admin console to perform upgrade. Then you can go back to using the Launcher. Per the installation instructions for the later v5.x versions: "You must use the 5.0.9 Admin Console or greater to upgrade to this release (5.3.0)." In a different recent post Michel gave the URL to the 5.3.1 console suggesting if it was used it would ask you to upgrade the firmware:

Programs look as expected! If you right click the on program and 'run then' i would expect it to cycle the sensors on then immediately off. I don't have any idea how your sensor works but perhaps crushed ice to test?

Have you tried The Launcher? it acts as a middleman kind of and ensures you are launching the correct version of the admin console. Follow the instructions in the first post of this thread: ALso just to double check, did you install java from www.java.com and press download. That also ensures you get the corrrect version of the Java Runtime, you don't need to the full SDK.

I didn't type much, I cut and pasted more. The keys are to use disable/enable and run program. and as @larryllix points out you can use disable and copy to your advantage in setting up the new programs.

The second program does nothing. The better approach is to use two programs: one for the off condition and one for the on condition. Gutter Heater Control ON If 'Weather - Snow Alarm (I2)' Status is On And 'Weather - Temp Alarm (I1)' Status is Off then Set 'Driveway / Gutter Driveway Power' On 100% Wait 1 minute Set 'Driveway / Gutter Porch Power' On 100% Wait 1 minute Set 'Garage / Gutter Garage Power' On 100% Run Program Gutter Heat Control OFF (if) Gutter Heater Control OFF (disabled) If 'Weather - Snow Alarm (I2)' Status is Off or 'Weather - Temp Alarm (I1)' Status is On then disable program gutter heat control ON Set 'Driveway / Gutter Driveway Power' Off Wait 1 minute Set 'Driveway / Gutter Porch Power' Off Wait 1 minute Dis Set 'Garage / Gutter Garage Power' Off wait 15 minutes Enable program gutter heat control ON Run Program gutter heat control ON (if) (I'm not sure of you need this line or not but it won't hurt) Else wait 15 minutes run Program Gutter Heat Control OFF (if) ----- The on program watches for the conditions required to turn on the equipment. The second program being disabled means that it will only run when we tell it to. So the first program turns the equipment on and runs the off program, if its not time to turn it off yet this program drops to the else loop and waits 15 minutes before ending by running itself again. Once we reach the then body we disable the on program, turn off the equipment, wait 15 minutes and re-enable the on program (which de-bounces) I think that should take care of all conditions. without turning the equipment off many times which occurs often when using Status and else bodies. What this doesn't do is stop excessive Insteon traffic from the EZ-IO, if the sensors are actually causing the problem by turning on/off repetitively. You may need to add a Time delay relay into the circuit between the actual sensor and the EZ-IO. I had that problem with another sensor and used this relay to debounce the circuit. (FYI... it's hard to understand the programming buttons of that relay and the functions, the instruction sheet is not very good and made it a frustrating process, but stick with it once you have it set you never need to touch it again... mines been working since 2016 without being reprogrammed.)

If that's all the code you have in a program, I can't see how it helps de-bounce other programs. When discussing your programs it's always best to post the exact program(s) by right clicking the name in the tree selecting copy to clipboard then pasting it into a post. Too many different possible interpretations of psuedocode.