MrBill

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

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.

@dalter2 Here's a post Michel made awhile back that better puts this into perspective:

mms.att.net does have it's bad moments, recently it's been good but every now and then there will be weird 4-12 hour delays. As a result I usually send important messages via more than one service. The other method above using policy is to use the service Pushover. there are two (that I know of) nodeservers for that service, on is "Push" the other is "Notification". You can also use Network Resources to send messages via Pushover. Pushover is basically instantaneous most of the time, when I go out to get the mail my watch taps my wrist with the mailbox notification before the mailbox is even fully open. It's not perfect either tho, I've had very few messages that went missing, normally when I think to look at the ISY error log it's an https timeout on the pushover API (the wiki suggests 2000ms for timeout, IIRC mine are set at 4000ms for the network resource originated messages (which are still most of mine because they pre-date Polisy and I've never moved them). What is Pushover? Basically a service that lets you send push notifications to your phone via an API. The only fee they charge for small individual users is the one-time download of the app. (there is a free trial.)

the cost of a portal subscription isn't listed at @DennisC link... but it's very minimal, basically $1.00/month. $23.00/First Two Years $12.00/Year thereafter

are both devices are in the root folder? Maybe it's just the way i'm reading your wording too but if you're on the new device choosing "replace device" that's backward. You want to choose replace device on the OLD device and select the new device. and as per the question above, both devices must be in the top or root folder and not in any folders you created for grouping.

I have all insteon, no-z-wave... if I had to make the "what to start with" decision over again today I would seriously consider Lutron Caseta and/or Caseta Pro. I actually kind of dislike the look of caseta switches tho, they also have a limit on number of devices that I would need to evaluate. There's also Lutron RadioRA I'd have to think about. I like Insteon a lot but I also am one that believes they don't understand the market they are in, and because of that I worry about longevity. I don't like z-wave for lighting because you can't group things to operate at the same time. Those are my thoughts, but I've not researched other options because I have Insteon for literally everything except the garbage disposal.

I agree this happens... I almost now wish for a bigger file tho, the history available in mine is less than 24 hours meaning that if I want to look anything up I've gotta be on top of the situation. I don't use that log alot but it has come in handy in the last week figuring out why a light was randomly turning on (which is how I happen to know that mine only has 16-20 hours of information available now).

That's nodeserver specific and kind of a user preference too... I don't use that nodeserver, so I'll let @bpwwer give you better guidance since he wrote it. I just had a feeling when I read your post and his response that there was a disconnect about WHICH log was being spoken of....

If this statement is true, you have more programs than the ISY is designed to handle, which is 1024. I don't know what happans when you hit this limit. I do know that when you hit the node limit between non-pro and pro, someone has to guess that's the problem because there isn't a hard discrete error message stating it's time to upgrade.

@jukeman do you mean the nodeserver log, or the admin console log: Tools > Log ? Node servers certainly do blast alot of information into the ISY log, mines currently > 61k rows and covers less than 24 hours. If this is the log file you mean you'd need to slow down updates from the node server to slow the logfile buildup.

Use 10digitnum@mms.att.net instead. It’s not immune from delays either, but is usually better. As an added it benefit your messages arrive from your email address as opposed to the weird numbers .txt uses, also the Max message length is 1024 instead of breaking messages up.

I saw another v2.6 reference the other day... Just replying so I can tag @Brian H to make sure he saw too since he's our resident PLM repair expert.