larryllix

You need to pay closer attention to all the lines in the programs. I am totally confused by what you have done. I suggest you copy verbatim until you get it running and then experiment for education purposes.

Just to complicate things here If status of SwitchLinc is On Then turn On light Else turn Off light Functions almost the same as If SwitchLinc is switched On AND SwitchLinc is NOT switched Off <------ when switched off becomes NOT True Then turn on light Else turn off light Except for one small point ..SwitchLinc is Switched ON/Off tells you when a finger is on the switch first depressing it. ..SwitchLinc status tells you level of the dimmer electronics no matter what changes the level. State variables present both a status level and a changes trigger. A SwitchLinc line in a program is only True when being called by the ISY event and always False any other time (the button is not likely pressed, anyway). Status can be true or false anytime. Hopefully my ramblings help somewhat.

That's when lighting power conservation was paramount and there wasn't much more we wanted to control.

@poetaaronFirst get rid of the Else code for each program. When the variable changes to any number less than 30, all program Elses sections will attempt to run simultaneously. Your Insteon system won't like that much traffic. Rather than finding it I will create the countdown timer from mental confusion. If $sLED1.timer > 0 Then Wait 1 minute $sLED1.timer -= 1 Else set lamp Off That's it. Self triggering and self- retriggerring, and simple. ISY is amazing! Oh! BTW! You can right click on your program name in the program tree and select copy to clipboard. Paste into your post.

When using the MS II, the retriggerable possibilities in ISY programs is not possible. When you disable the Off command from the MS II, you lose the retriggerable timer possibilities, from the MS II, also. Now that I am aware the Off cycle in the MS II is NOT doing what I thought it was, I can see some possibilities for a very short timer duration inside the MS II and make it run like the original MSes. More experimentation needed here but sounds more promising now.

Take one for the team. Contact UDI support. They will want to know about this and will help you quickly.

Interesting. I have not seen any other poster reporting this about any MS II. Can you post a screenshot of your option settings?

There are many threads about fixing PLM power supplies in the forums. My guess is the same power supply capacitors are used. @Brian H here is a top notch hardware guy that has driven most of the fixin's on that note and may have ideas or info on the insides of the Hub.

If he is in Canada, the shipping costs will cost him almost half the price of an ISY994i and it will come without bad power supply capacitors. It sounds like Insteon is starting to admit that bad PSU components were used.

It is all about having lights on bright and for extended retriggerable times during the day light hours, and very dim and for very short retriggerable times during the night time hours. This doesn't seem to be possible using the MS II with a direct Insteon Scene, whereas using the old MS it was, using a combination of Insteon scene and ISY programs. For occupancy I mostly use MSes that set a programmable timer. Each room sets the timer at different times. In the TV watching room I use 180 minutes due to little motion at times, while the typically exit room, I use only 20 minutes, assuming the person may exit. Is the house security is turn on the timer is set to 1 minute and times out quickly. From 11:00 PM to 8 AM the timer is stopped from counting down. BTW: To use the '@' notification system you must choose the name from the dropdown menu or it just becomes normal text. @greazer vs. @greazer

Always, always, always, factory reset every device before linking to ISY 994. Build your Scenes between Insteon devices in the ISY admin console. ISY is a fabulous Insteon scene manager and will make it easy to edit or create them. Then programs can turn scenes on and off inside ISY also. Insteon devices that are not factory reset can give you a lot of grief down the road when they magically do things they shouldn't and cannot explain. Welcome to the world of ISY! It will take some time to get the triggered events concept down but you will not regret it later. Make sure you upgrade to ISY V5.++ if you do not have it installed. Upgrading from v4 to v5 can cause some stress at times, with existing programs and scenes.

ewwww. I hope there are plans for that one. The owing Battery Writes cause a lot of delay in my ISY.

@Chris Jahn @Michel Kohanim V5.1.0 I believe the Battery Write option does not carry it's settings through an ISY power cycle. I have not tested this to prove I didn't just slip with my mouse clicks but just noticed immediate Battery Writes enabled again after a power blink yesterday.

@greazer I think I have found the problem! MY laundry room is the only place I have left using a MS II. The other two are moved to places where they do not directly control lights and are only used for occupancy logic in ISY, so this problem has not applied to those units. In my laundry room program I was trying to treat the algorithm like the old MSes and use a retriggerable Wait X minutes in ISY software. I had a dual time out based on time of day so some times were worse. Now suppose the MS II is retriggering with motion in the room but the software timer, not getting any retrigger signals, timed out and turns off the lights. The MS II internal timer has been retriggered and will never send another On until it times off, and is set to send On in a new cycle. This would appear with the effect I was describing. No lights on would ever occur until the MS II see no motion for it's timer duration, and it can send another On. Looks like my synopsis of this was dead wrong and it always seemed to prove out as true in situ. I have now changed my ISY timer to an all-else-fails timer at 15 minutes, longer than should ever be needed in the laundry room, and always (hopefully) exceeding the internal MS II timer. CONCLUSION: Never use an ISY program timer to beat the MS II's internal timer, when using a direct Scene link between the MS II and a light, to turn off the light. I will be testing this new idea (for me) to prove whether this was the case. I have lowered the MS II timer down to 90 seconds, but I may also need to physically lower the MS II to catch motion underneath it more dependably. @greazerThank you for your efforts and your persistence! This was a hard lesson for me.

I think you understood correctly by your comments. Perhaps there were different releases and I got a different one than you. If I set my timeout short the lights turn off quickly with lack of movement (of course) If I set my timeout long (3-5 minutes) and the lights time off, I have to not move for those 3-5 minutes before the lights can be triggered on again. These are my options as set for this room. If you can find something obvious I would appreciate any hints to make these more useful.

That all depends on whether the ELK sends every motion sensed On signal to ISY or just the first change of state. You would need a much longer timer to avoid the lights going off randomly while they play in the room, unless your MS will detect the floor play in every corner of the room.

Nice catch! The force is strong with this one! Modified post to match. I was originally mentally designing to have all four LEDs in each scene and use it that way. Need an ISY "select" construct here. I don't like all scenes being hit on every minute simultaneously though. KPLs are all in one device address. hmmmm....maybe disable 3/4 and call each in a daisychain of progressive value tests? Maybe wait and see if the OP comes back with something.

This was a duplicate post from @poetaaron Report post Posted 3 minutes ago (edited) Here is how I would do it. I would create 8 scenes, each containing only one KPL LED = On Then I would create four programs for each side like this If $sLED1.timer >= 90 Then set ledG.scene On Else set ledG.scene Off If $sLED1.timer >= 60 Then set ledE.scene On Else set ledE.scene Off If $sLED1.timer >= 30 Then set ledC.scene On Else set ledC.scene Off If $sLED1.timer > 0 Then set ledA.scene On Else set ledA.scene Off Set up a program to decrement the timer state variable $sLED1.timer by 1 minute each repeat as in other variable based timer programs. Turn off the LED bulb when 0 is reached. Set up a program to advance the state variable timer $sLED1.timer by 15 minutes each timer button A is pushed> If KPL.A is switched On AND $sLED1.timer <= 90 Then $sLED1.timer += 30 Else $sLED1.timer = 0 Duplicate the whole thing for the other side buttons. When you press the top left button your LED1 timer variable should advance by 30 minutes each press. Your KPL LEDs should advance in a column by one more for each press, and also decrease for every 30 minutes that the state variable timer $sLED1.timer counts down, indicating the time left on the bulbs. One too many presses and the timer should reset back to 0 and LED1 bulb should turn off, and the sequence start over again. Let me know how you make out. This is untested and bugs may be found that should be easily fixed.

@poetaaron created own thread with duplicate post. Response deleted

Yes, and yes. The Off time is what nullifies most of my appkications. As long as motion for the timer setting it will never reset and send a new On. I have one in my laundry room on USB power and it makes no difference. If the light goes out until you stand still for X minutes delay the lights will never come back on. I was using them in high usage places due to the USB power but now have removed them and only use for security alerts where duration are not a factor. I wish Insteon would correct this bad design but it seems it was done to support their dumber system and thwart ISY users. The next product logic change will confirm or deny this hypothesis IMHO. Hopefully UDI will discover some new logically corrections to stop these things from hanging the Insteon comm channel in the near future. I don't query them (MS II) anymore. It can cause a disaster in ISY / Insteon systems and the alternate field information is random garbage at times.

@greazer Nice! You should mention your information is about the MS II. Most of it does not apply to the original Insteon MS. The off time duration is not mentioned. I found that aspect makes the MS II mostly useless for lighting, but great, and seemingly more reliable, for logic applications in ISY.

@TAllenYou didn't include any text or person you were posting to in order to alert them. Type '@' and then their name, select the box below like I did yours at the beginning of this paragraph.

Nice! I do use folder conditions for a few purposes (night security zone enable, security MS zones enable, permanently disabling monitoring programs) but they have a few drawbacks. - they are hard to debug, programs underneath cannot be manually tested while the folder is false - they can stop a program midstream and leave devices turned on or off - they are obscure/hard to see and not something I would look for when debugging algorithms. Once you have a bank of basic device/scene/level handlers in a folder the triggering programs get much simpler without the rest of the code. Some of mine turn on Insteon scenes, along with MagicLight controls via NRs through custom software, sometimes three different colours or more, all from one master scene number inserted into the control variable. Divorcing the two sides of the process across a variable works very well to simplify the thinking. Another nice thing about the isolation via a variable is you can pound the variable as many times as you like but unless the value changes none of the devices get pounded with useless Ons or Offs.

1) You don't. Scenes do not have a status and cannot be determined with any accuracy. If you want to know what the last scene was use a variable as I suggested in a previous post. 2.) I don't know what buttons you are referring to. If they are KPL buttons or other Insteon buttons, they do not have a useful status. Their status is always Off but they generate events that can trigger ISY programs. You variable can remember their last operation. 3.) I am not sure if you can copy a scene but you can create a scene very easily inside the admin console. It's most;y a drag and drop process. I only use a few Insteon scenes but I use dozens of different room lighting scenes, all controlled by one state variable. If you want to remember which lighting scene was on for some temporary usage, save the state variable into another variable and when you are done save that variable back into the state variable. As describe previously, all lighting is controlled by that one state variable. The first thing that usually happens with newbies to ISY is "OMG! it takes so many programs!". That is the nature of the beast. Each program is one basic logic statement unlike linear program languages. Most developed systems use hundreds of programs and hundreds of variables. It is not costly for the system. Best of luck. Keep experimenting.

Not sure I can completely understand the logic there but...you seem to be very logically equipped so..... For my deck lights I have 13 WiFi bulbs controlled by my own NRbridge software, driven by ISY NR commands. I have them divided into three groupings, for scenes that I can control from ISY similar to Insteon Scenes, to avoid the popcorn effects, display three different colours, and animate them in a rotational looking effect when desired. I use a single State Variable to control the scenes, exactly the same way as my Gathering room example above. In another folder, I have a bank of programs that all install a scene source variable with the various colour scenes for the deck ceiling potlights, based on the date. Each day at a neutral time I set the controlling source variable to $cDIM so that my deck night lights program uses a copy of $cDIM to illuminate my deck and porch. On festive occasion dates, at a time just a few minutes later than the usual dim white setting, I override the deck lights source variable to festive themes. eg. Canada Day, Christmas, Easter, Halloween, Independence Day, etc... When the main program (sunset + XXX minutes) until 11:00 PM day of week dependent, I copy the scene source variable into the deck light scene control variable causing whatever colours I want to show up around my home.