MrBill

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.

Those MUST ALWAYS match (there may not be much difference between 4.8.0 and 4.6.2 so it probably works ok in that case, but the rule should always be followed...Firmware and UI should match version wise). To automatically open the correct UI use the launcher instead of the admin console directly. When you are ready to try V5 again, Use the V5.3.1 admin console located here, to start the upgrade: https://isy.universal-devices.com/994i/5.3.1/admin.jnlp

This is a good thing. Is it a dual band device? is there another dual band device nearby on the other phase? What device is each item in your list? more specifically, what is dual band and what is powerline only?

V4 to V5 is a manual update and requires intervention for some items. Did you read the instructions at all?

Did you make a backup first like the instructions instruct? Or decide you could figure that out later too? https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY 1) Factory Reset 2) load 4.8 3) restore backup

Where did you download java and did you download the full version or just the runtime? Specifically just go to www.java.com and click the download button it will select the correct runtime for the machine you're using, you do not need the SDK version. Some of those error message paths suggest you got something else.

It does take awhile to set up, but it's really pretty nice when it's done, whether by Alexa or any other source you can just set the state variable to any value 0 (off), or 1-100 (brightness level) and the device responds. If you're setting up multiples it's much faster for me to use Copy Folder then edit the names and line of the copy to match the next scene.

you can do it a couple of ways, as lilyoyo points out multiply scenes, one for full brightness and one for 20% or whatever. You can also use a technique that I use for Alexa that I wrote up here: after creating programs like those in the linked post, then the program that you have above could just set the state variable to 20 to control the light.

did you plug the PLM in first, wait 30 seconds or so, then plug the ISY in? the only time the ISY checks for a different PLM is during the boot process. If the ISY was no rebooted it won't work. the first thing After that the next step must be Admin Console > File > Restore Modem (PLM) which may take awhile to complete it's task depending on how many devices you have.

I'm aware, I've been in many of those threads and tracking that bug for a very long time. I was always finding battery writes back on even without rebooting too. I know the focus has been on Z-wave certification but I had about given up on that 2 year old bug ever getting fixed given the disfavor that Insteon/smarthome has fallen into.

The only place I previously used it was a bedroom closet light. The controller was a hidden door sensor. At bedtime scene adjust changed the on level to 8%, in the morning some offset after sunrise it changed back to 100%. The idea being if I opened the closet door in the night while my wife was asleep it wouldn't flood the room with light. Worked great with v4.x... version 5.x has a bug where it tries to write to the battery powered scene controller. I had to switch to doing the same thing via programs, which means that I open my closet door now and can count slowly ONE, TWO, THREE then the light comes on, whereas with the scene adjust method it was literally instant. Same use case idea... scene's controlled by motion detectors. If I had motions I would probably want to use it there, I don't have motion detectors tho for several reasons. Another interesting use case, I helped a guy in another thread awhile back that was setting his office up. He was using a motion detector to turn the office on/off based on presence, but he wanted the scene to remember what he had on. If he turned the overhear light on or off manually, he adjusted the scene for the motion, same for the desk light, if he turned it on/off manually it was a scene adjust. The fan was more complicated and took into account the temperature as well, but the jist being when we walked out of the office it should turn everything off, when he came back it should turn back on just what he has turned on when he left. The drawback to what he's doing is that he's not re-writing the scene just twice a day but many times, eventually he'll have devices fail from overwriting the memory frequently (it'll still take years probably but device life will be shortened). What most people don't understand about Adjust Scene: is that it doesn't change the state of what is on or off after the "Adjust scene" action, it changes how the scene is programmed. If it's also desired to actually effect the current state of the lights the program also needs to send the scene and On or Off. How much traffic creates a traffic jam? Insteon does a much better job than X10 did at avoiding collisions. Insteon is also faster than X10 was but it's still a really slow protocol by modern standards, things happening by Insteon are practically almost measured in full seconds, and can only happen one at a time. In the range 15-30 years ago I solved X10 problems that other people created and/or didn't understand. As a result I'm very conscious of everything that creates power-line traffic, most people aren't tho. I helped someone else from this forum offline, he ended up PMing me then we spent a couple hours on a screen share most of his problems were that he was just writing way too much useless traffic to the powerline, many Else bodies that were constantly getting triggered turning things off that were already off, etc. He also had GREAT BIG HUGE programs changing backlights and on levels based not on not just day/night but actually how bright it was outside, and he was basing it on a luminescence sensor that updated every 30 seconds and doing nothing to de-bounce. It was night when I was talking to him, but had it been a partly cloudy day I could actually see that his programs could literally fire those big programs every 30 seconds.

if this means you're turning the scene on and off, then yes it will have the desired result. If you're using it to "adjust scene" then you may not be doing what you intend. The best thing to do when requesting programming help to to post the actual program by right clicking the name of the program in the program tree and choosing "COpy to Clipboard", you can then paste this into a post. Also tell us what you are trying to accomplish.