ISY Newbie

Factory-resetting these dimmer switches is a real pain. You need fine-toothed tweezers to be able to pull out that set button. Even then, it requires fine motor skills. Really bad design from engineering viewpoint. Is there an easier way?

Yes, there is "options" button at the bottom, but it doesn't reveal a "beep" setting for a dimmer switch. I'll upgrade to v.5 and see if it makes a difference.

Is that from Firmware v.5? My admin console looks nothing like that. Mine is missing the Beep option altogether.

I've linked a Dual Band SwitchLinc Dimmer Switch v.45, and after being linked, it beeps when manually controlled. Before being linked to Isy, that wasn't how it behaved and there was definitely no beep. How do you get rid of the beeping sound?

Thanks. The conditional statement "If" operates differently than I expected. In all the other programming languages that I've known, the entire "then" block is executed regardless of whether the "if" condition remains true throughout the execution. I'll keep that in mind.

I have the program that's supposed to turn on exterior lights when a motion sensor is triggered. But sometimes I'd find the lights stay on for hours long after there has been no motion outside. If Status 'Exterior Sensor' is On Then Set 'Exterior Lights' Fast On Wait 5 minutes Set 'Exterior Lights' Off Else No Action Looking at the log file, the only clue to the problem is that the motion sensor was triggered for a second time within the 5-minute period for the lights to be kept on. Can that second motion trigger somehow have thrown off this program and made the lights stay on for the rest of the night?

So what is the consensus here on the fate of serial PLM? Will they be back once the supply chain constraint is eased? Or is Smart Home pulling the plug due to low demand for the Insteon ecosystem altogether?

Thanks for the suggestion. (Now, this is a question that I would have created another thread to ask.) Is there an easy way to "recycle" lines from a previous program? It's such a chore to individually select a device and weave them into a program. It'd be much easier if you could copy & paste from a previous program, as I'll have to here to create three separate programs to turn them on at a give time of the day.

Got it. But I thought the issues were distinct - one about the "From-Then" schedule and the other about commands not running - although the two issues both arose from the same program. That's why I created separate threads intentionally, for posterity's sake, so people who want to look up a particular issue will land at the right thread. Didn't think they were crossovers. Anyways, I'll keep in mind that it's better to minimize the number of threads in this community.

Thanks. Didn't realize the raw text search was case-sensitive. Yes, it worked with the correct case.

I don't have time for trolling. I posted my program in the other thread and didn't feel the need to duplicate it here. For my purposes, I got what I needed all the way back when Asbril explained about the need for a 2-minute wait between commands. People jumped in and replied even after that, and I tried to be nice by responding to those as well. If you think I'm a troll, just block me. I really do not appreciate your attitude.

NightLights If From Sunset To Surrise (next day) And ( Status 'Exterior / Lights1' is Off Or Status 'Exterior / Lights2' is Off Or Status 'Exterior / Lights3' is Off ) Then Wait 2 minutes Set 'Exterior / Lights 1' 40% Set 'Exterior / Lights 2' 40% Set 'Exterior / Lights 3' 40% Else - No Actions - (To add one, press 'Action') This is the same program that I posted in another thread. Sometimes ISY will forget to turn on Lights 2 and/or Lights 3.

Is scene less prone to the kind of problem discussed here?

NightLights If From Sunset To Surrise (next day) And ( Status 'Exterior / Lights1' is Off Or Status 'Exterior / Lights2' is Off Or Status 'Exterior / Lights3' is Off ) Then Wait 2 minutes Set 'Exterior / Lights 1' 40% Set 'Exterior / Lights 2' 40% Set 'Exterior / Lights 3' 40% Else - No Actions - (To add one, press 'Action') This is the same program that I posted in another thread. Sometimes ISY will forget to turn on Lights 2 and/or Lights 3.

Thanks for your remarks. They were very helpful. A follow-up question: when you said an "event" will have ISY evaluate its programs, does ISY evaluate all its programs, regardless of whether that event might affect a particular program or not? Or does ISY evaluate those programs that refer to the device that just had an event?

NightLights If From Sunset To Surrise (next day) And ( Status 'Exterior / Lights1' is Off Or Status 'Exterior / Lights2' is Off Or Status 'Exterior / Lights3' is Off ) Then Wait 2 minutes Set 'Exterior / Lights 1' 40% Set 'Exterior / Lights 2' 40% Set 'Exterior / Lights 3' 40% Else - No Actions - (To add one, press 'Action') This is what I have. Like I mentioned in another thread, sometimes Lights 2 or 3 won't come on. I'm thinking of adding a "wait 5 seconds" between the Then lines.

I don't know what caused it, but some of my network resources are tangled up. Some programs are calling the wrong network resources. Rather than going through the programs to sort things out, I'd like to go through network resources one by one and see which program calls each. But I can't seem to run the find command on network resources. Putting in the name of the network resource as "raw text" doesn't work either. Is there any other way?

This is driving me nuts. I have lines to turn on multiple lights at night if the conditions are met. But not all of the lights in the "then" section are turned on. It's as if ISY just randomly skips lines in the program. What can be the problem?

I don't have any issue yet. I'm trying to prevent a situation where my PLM dies and I need to wait a few days before its replacement arrives.

Thanks. I'll give it a try and see if it works tonight. Why the 2-minute wait though?

I've read stories about PLM being the weakest link in the Isy system. What's the telltale sign? Is it a good idea to have a back-up PLM ready even before there are troubling signs?

I think you're right. My two questions are different, come to think of it. Now, if I build a If phrase that checks on the status of lights, how often does ISY check them?

I'm confused again. Why do I need to check the status of the device? I want to turn on the lights at sunset whether or not the lights have been already turned on (manually by a user) or not. Likewise, I want to turn off the lights at sunrise whether or not the lights have been already turned off (manually by a user) or not. What does checking the status of the device achieve if my intention is to do something regardless of the status of the device?

That was what I wanted to know. So, although the conditional phrase "from A to B" sounds like ISY will check continuously between A and B, ISY actually checks at A and B, then. I'll revise the program to account for that.

It's along these lines: If From Sunset To Sunrise (next day) Then Set Scene 'External Night Lights' on Else Set Scene 'External Night Lights' off I manually turned off one off the light in the 'External Night Lights' scene, and ISY is not turning it back on.