larryllix

My ISY came with one program installed. The 3:00 AM containing Query All. When people delete it they have no Query All. I have added a series of device off clean ups and delayed the query until 4:00 AM. Gotta' love those alarms in the middle of the night.? I mostly set flags and check them in the morning for lower urgency alarms like low batteries.

When a program containing a wait or repeat line, is interrupted by it's own If logic triggers, the program knows i,t and terminating action can be taken in the Else section. This is not possible for a folder condition. When a folder condition becomes false the programs inside are not aware of the change, and cannot take any alternative action. Lights and devices can be left in undesirable states.

LOL. That's not a Then or Else. That is a True and False. No programs are enabled during False times and no programs will be run to clean up the mess of programs stopping abruptly.

You came to the right place! I use this technique to determine Home/Away. Each and every device that can be used injects a value (number of minutes delay) into a variable. Each MS or other device injects a different number of minutes to delay. Typically the closer you get to the exit door, the lower the delay number. The security (built into ISY for me) system injects only a 1 minute delay. Motion.EveBR - [ID 0015][Parent 000B] If 'Evening Bedroom / Motion.EveBR' is switched On Or 'Rec Room / RecRm stat / RecRm stat cribroom' Occupancy is Yes Then $sMS.Motion.room = $cROOM.EVEBR Wait 2 seconds $sHouse.occupied.timer = 120 Else - No Actions - (To add one, press 'Action') A countdown program self-retriggers every 1 minute or whatever clock click you desire. Note my implementation allows people to sleep without timing out and resumes in the morning again. Occupied.countdowner - [ID 0167][Parent 000B][Run At Startup] If $sHouse.occupied.timer > 0 And From 7:00:00AM To 11:00:00PM (same day) Then Wait 1 minute $sHouse.occupied.timer -= 1 Else - No Actions - (To add one, press 'Action') Self retriggering timer. Enabled to run at startup! -If startup occurs ouside wake timeframe, will self start at beginning of timeframe. -If timeframe commences while .timer is 0, first new occupied.timer value will start again. A third program monitors the countdown vairable and does the dirty deed desired. Occupied.flagger - [ID 0168][Parent 000B] If $sHouse.occupied.timer > 0 Then $sHouse.occupied = $cTRUE Else $sHouse.occupied = $cFALSE Power up assumes home unoccupied! Shouldn't be long to correct that. Program cannot be combined into "Occupied countdowner" program as it's timeframe end would zero occupied.timer

Will hand sanitiser work?

Complain about systems, complain about devices, complain about how things work, OMG complain about ISY, but never complain about the person (negative ad hominem) without expecting a created negative response from possibly many more posters.

Like @gviliunas posted, folders do not support Else statements. Programs do support Else statments, and can provide space for programs to clean up when the conditions change. If I didn't need any Wait or Repeats, I would have saved money and just purchased an Insteon Hub. Programs inside a folder being autonomous has yet to be tested. I am not afraid of using Variables. They make programming much easier to troubleshoot and are useful in many places inside ISY while still maintaining some sort of filing order for larger systems.

Perhaps the wrong email is registered with UDI. Even after you delete the email it is quite easy to find it in the trash of any email client software I have used. OTOH: I have suggested previously, we should have a ISY Wiki link at the top of every forum page. There is a huge blank banner space with only a UDI logo at one side.

As long as your Query All program is still intact that may work. I assume your Decora light switch is an Insteon SwitchLinc, and not a Zwave device. I am not sure how the Zwave querying works or if those devices are included. The other point to note is: if you use the native triggering style ISY program system you will get a notice of failure at 3:00 AM, right after the query. You may want to do you own time controlled polling, or create a time delay notification "not in the middle of the night". I hate when that happens.

I have only ever had to create one variable in State type as well as Integer type for my programs. I hate having to do that. However, maybe we should not bicker over this agreement anymore. We don't want to upset anybody. ? ?

I ran into this a few years back. IIRC The KPL LEDs indicate a toggled on/off status whether the buttons are in Toggle mode of not. It isn't related to the actual LED status, only to the button press count divided by two. ISY likely keeps it's own status but query overrides it with Insteon's version. Insteon has never fixed this and China probably won't talk to them any more. The warranty on the design expired years ago, and Insteon likely doesn't know how they work. One more reason UDI started supporting Zwave.

That does make it simpler looking and eliminates the "trick" triggers that most people forget, or are not aware of. That transfers the "sneaky triggers" over to whether State or Integer variable types are used. Further if any trigger is using control/switched, it doesn't matter, but if using status, the type of enable variable becomes paramount. I have always wanted to create a logic table for this, but was never sure whether the forum would take HTML code.

Since you never disclosed what "device A" is/was it is hard to know how it could work.

Actually we would need both so we can poke holes in it and help fix it. Sent using Tapatalk

You are looking at two different light switches. One is a program and the other is a scene profile. They are not related except they are controlling the same device. A scene is a preset inside the device. When ISY or any other Insteon device calls out that scene on command the device just does it Insteon devices can hold about 250 scenes each. Sent using Tapatalk

If the device is Insteon then querying it is unnecessary unless you have bad comms and events are missed. On power up ISYwill query all devices to resynch again. Sent using Tapatalk

Not quite. Read the program more carefully. The posted program has an additional trigger that was mentioned @kclenden addresses this in his final paragraph. @lilyoyo1 did not discuss the program. @lhranchBTW: You have to select the attention getting @ technique from the pulldown search resultant or it doesn't function just typing the name. Look for the reverse video difference.

I believe that condition is only known from the last query ISY did on that device (3:00 AM?) , or from the last ACK response ISY got from sending a commend to the device. A cyclic query may need to be set up, if the device or NS does not send a heartbeat.

Copy and paste your program here and people can take a look at it. ISY time triggers can be complex as they can act as filters to screen blocks of time and also as trigger themselves. Eg: If any trigger AND From 8:00 PM To 4:00 AM (next day) Then runs at 8:00 PM each day and also any trigger between 8:00 PM and 4:00 AM Else runs at 4:00 AM each day and also any trigger between 4:00 AM and 8:00PM each day

Yeah, The twenty minutes likely knocks this program out of the troubleshooting. OP should use the search function in the admin console to find any other reference to these devices.

Perhaps he has defective Zwave KeyPadLincs then.

If your scenes contain button LED controls and your program duplicates what your Insteon Scenes do, you may have caused yourself an ALL ON phenomenon. All the devices inside the KPL are on the same address and this type of signal bombardment, is suspected of causing enough signal collision to cause a bad Insteon code, that other Insteon devices can amplify as an ALL ON or a Scene control command. Take the duplicate actions out of your program, or remove the scenes from the devices and just rely on scenes for the on. If you need the response speed, I would isolate the KPL LEDs into separate scenes, allow the lights scene to work directly, and with a 1-2 delay make the program operate the LEDs only. Actually with any human keypress a 1-2 second delay for feedback, or any lights is not that noticeable. Bedtime Prg - [ID 000D][Parent 0001] If 'BedLR1' is switched On Or 'BedLR2' is switched On Then Wait 2 seconds Set 'BedLED' On Run Program 'Lock Doors' (Then Path) Set 'Front Porch Light Dev' Off ... (removed) Wait 2 minutes Set 'Front Hall Light Dev' Off ... (removed) Wait 10 minutes Set 'BedLED' Off Else - No Actions - (To add one, press 'Action')

We use "Alexa...what time is it?" to establish it has disconnected from WiFi. I have jumped up to a mesh network WiFi router and I think with all the automatic amplitude adjusting they do it makes Alexa boxes switch routers occasionally and gives a lot of dead times, we aren't supposed to notice.

@bmercier A further update: Something at amazon definitely was changed as any of my devices with multiple vocals containing the same words get asked about to reaffirm which device I want, now. eg: For alarm system i use two (or more) different vocals. ie: "alarm" and "alarm system". If I ask.... "Alexa... turn on alarm" Alexa will respond with "You said alarm, right?" This was not happening before this week. Either vocal syntax could be used without further query back. I have many vocal using multiple length options like this and the change has caused me lots of maintenance now. Most of these are due to being new,, and the familiar syntax (by humans) was not established until a few usages.

@bmercier I attempted the repeat discover again and no components from ISY Portal were duplicated this time. I conclude that I must have caught amazon in some transitional stage when I did a discover and it duplicated everything I had. IIRC some devices were duplicated 3-4 times while others were not duplicated at all. My attention was attracted when alexa repeatedly advised there were multiple devices with the same names and wouldn't operate certain devices/programs. All good now. Thanks.