larryllix

Overlapping timers could be a problem for simple schemes to implement this in ISY.

If you think of it this is actually asking ISY to accept a passed parameter. This may come in years but I doubt soon. Even if Alexa could accept concurrent commands like Alexa Wait and then turn off bedroom light. whereas the ISY Wait could be a 10 minute program delay to set a flag Then the bedroom light off program could be activated when the timer was complete. I am guessing this could be done now. This would take a bank of variable and routine triggered on those variables. I use that technique now. When Alexa is asked to do each task it could set a "forthcoming" bank of variables based on the task. After the installed wait the "forthcoming" bank of variable would be copied into the trigger bank of variable and the task would run after a delay. "Alexa ask izzy to wait" sets a short timer program "Alexa ask izzy to wait longer" sets a longer timer program "Alexa ask izzy to turn bedroom lights off" set the "forthcoming" bank variable. Of course this would take multiple repeated programs involved in time delays. Commands may become possible like. "Alexa, ask izzzy to delay unit 8 PM" etc.... using the same technique.

Here is a set of programs that I use to alert me of my dryer items. The first program gets alerted by the dryer running after 10 minutes to avoid somebody just looking in the dryer door or tossing in another piece of clothing while running. Included is a notification that the dryer is running too long. This can be caused by the dryer door being open and detecting the light in the drum being on. Cold air is leaked into the house while the door remains open or the timer could be stuck on the dryer. That part would probably not apply to your washing machine and those lines can be removed. Dryer Running - [ID 009C][Parent 0066] If 'Mudroom / Dryer' is switched On And 'Mudroom / Dryer' is not switched Off Then Wait 10 minutes Enable Program 'Dryer Finished.Alert' Wait 1 hour and 20 minutes Send Notification to 'Text Jackie' content 'Dryer Still Running' Wait 3 seconds Send Notification to 'Text Larry' content 'Dryer Still Running' Wait 3 seconds Send Notification to 'eMail Jackie' content 'Dryer Still Running' Wait 3 seconds Send Notification to 'eMail Larry' content 'Dryer Still Running' Else - No Actions - (To add one, press 'Action') Negative condition in "If" aborts "Dryer Didn't Stop" notifications. The second program gets enabled by the first program, and goes through a sequence. It rings my back doorbell 8 minutes later, it rings my doorbell and a chime in the basement. 10 minutes later, it sends notifications out to cell phones. This sequence is cancelled, at any stage, by opening the dryer door or entering the laundry room to witness the dryer stopped. Dryer Finished.Alert - [ID 0096][Parent 0066][Not Enabled] If 'Mudroom / Dryer' is switched Off And 'Mudroom / Dryer' is not switched On And 'Mudroom / Motion.MudRm' is not switched On Then Run Program 'Dryer Running' (Else Path) Wait 15 seconds Set 'Foyer / Doorbell.Back' On Wait 3 seconds Set 'Foyer / Doorbell.Back' Off Wait 8 minutes Set 'Foyer / Doorbell.Back' On Wait 1 second Set 'Rec Room / Chime' On Wait 3 seconds Set 'Foyer / Doorbell.Back' Off Wait 1 second Set 'Rec Room / Chime' Off Wait 10 minutes Send Notification to 'Text Jackie' content 'Dryer Finished' Run Program 'Dryer Finished.Alert' (Else Path) Else Wait 2 seconds Set 'Foyer / Doorbell.Back' Off Set 'Rec Room / Chime' Off Wait 2 seconds Disable Program 'Dryer Finished.Alert' 'Dryer Running' enables and disables this program. Motion in room or dryer opening cancels notifications.

Oh yeah, I got one of those the other day with an install URL on it that redirected me to the real install software. LOL I think I have only ever watched 1-2 DVD movies in my life since VHS/Beta/8mm died but I still watch about a dozen per week at the theatre, downloaded and Internet and sat. streaming.

DVD? You are having a flashback! I haven't rented or played one of those since I put my VHS machine away. hmmmm... well, rented one...ever?

It has to set to deliver On commands when opened for the OP complaint to be true. An Off signal would trigger the else clause and cancel the then case and the OP complaint wouldn't exist. Also, the door closed can never be detected and the logic never work if Off is never sent. Since the OP now claims, it does work, but didn't previously AND now invalidates the lack of Off arguments above, he must have intermittent comms from his Door sensor to ISY.

Wikipedia was wonderful and working when we were without wondering if Washington was word washing.

As an afterthought v5 can assign variables the value of a thermostat mode and restore them after by assigning the mode the variable value. This could be used to memorise the stat mode, regardless of what mode is currently set, and restore it after the open door policy enforcement.

oooops...Not gonna' be that easy. If Status 'Doors and Windows / Door-Sliding' is On and Status "Air Conditioner' is Mode Cool <----the Mode was set = Off when the door opened. Then Set 'Air Conditioner' Mode - Off Else Set 'Air Conditioner' Mode - Cool The plot thickens with variables. It gets a little thicker, yet, once the compressor delay shows up. When will UDI inclement the "You know what I mean" program line? Probably not good to play with the Mode on the stat but rather just raise the temperature. Changing the mode raises all kinds of conditions like Home/Away, A/C was off in the first place due to spring or fall weather, and possibly a few more unseen conditions.

My wife says the same thing when I continuously clink the fork against the side of my plate or glass. I used the exact pattern sequence I taught her too. Somebody once told me, when a woman finds out they are not the only pebble on the beach they usually become a little bolder. Who wants a pet rock? ....."I don't understand what you just asked me" We are now entering dangerous ground. Please watch your step!

What was her head doing in the cloud anyway? Price of Dom Perignon predicted to increase by 300% this week.

OMG! You mean Alexa is a GMO product? It must be bad for us. Wait.....? !G.M.O.... O.M.G! Signal echo? Anybody succeed in changing their response phrase from Alexa? "Roxanne! Turn on your love lights tonight......". ... head in the cloud....

You are going to want to add some conditions to your program to stop the A/C from turning on in the winter when somebody closes the door. If you can control your stat you can likely read the stats of the heat/cool mode also. This will take two programs and no use of the Else clause though.

OK. What is "blah...blah...blah...", programmed to do though?

With an ISY I have never needed to press any link buttons, except for battery devices, to link them to ISY. Those instructions are for linking without an ISY as provided by SmartHome. Just supply the Insteon three byte address.

Does the camera app not use a common IP address/URL for the lot of the cameras? Should have been a change one IP Address:Port and done? Does each cam have a custom IP:Port that needed to be individually setup?

Same with the girls sometimes. Sometimes the dimbulbs are cheaper. Some of the brighter ones do cost more. Some are high maintenance. I picked up one with the rounder bottoms back in the early 70s and she still lights up well when I throw the stitch. Teken. Not nice to spit coffee on your keyboard.

Looks like you have it. We will be expecting big things from your kichen in the future!

Posts can be deleted easily.

As per Stu above and another way to look at is. Disable/Enable applies to triggers only, not the execution. Program 2 doesn't have any triggers and a disabled program is the place to use conditions when trigger interference is not desired in that program. This is commonly used for time frames and State variables when the trigger could upset a running program and they are only wanted for their filter condition value. Having said all that, if you disable a program while it is running it will stop it at the next Wait or Repeat line. Making sense?

I am convinced if all Cree bulb reviews were done after 6 months of ownership nobody would be buying them anymore. I have a about a dozen CREE bulbs and they were all great at the beginning. I have one dead one, two that flicker badly with dimming, one that doesn't match the rest in the chandelier now (dims on a different curve), a BR40 bulb$$$ that flick completely out, occasionally, now replaced with another brand., and a another PAR38 that just doesn't work occasionally. IMHO, CREE bulbs have the same problem the PLMs have, cheap filter capacitors on their power supplies. Works great until the receipt is thrown out. I guess I need to get my ship together and call them. I buy mostly the cheap brands now and have no problems but they are always rated "dimmable".

I apologise if this is not exactly what you are asking for without fully understanding your code. Use the "don't trigger me until I let you" approach. Program 1 [enabled] If whatever Then Run Program 2 (If) Else -- Program 2 [disabled] If non-triggerable conditions Then Disable program 1 Do something WAIT a long time, <---Program 1 can't touch us Do something else Enable Program 1 Else Do the negative conditions

The only thing I could think to make this happen is a burned out memory bit in the device in question. To prove this, you could try... -remove the device from the scene causing the problem. -create a new dummy scene -add the device in question into the dummy scene -add the device back into the scene in question -never use the dummy scene This may occupy the defective memory space in the device with the dummy scene link. Then the used scene would occupy a new byte or memory location. It would be worth the experiment and the warning that your device's eeprom memory is failing and shopping time.

There is nothing to trigger your program except the temperature changing. Something has to call the attention of the ISY engine and that would be a temperature change. Then your logic will be evaluated and run the appropriate Then or Else. IOW: If the temperature never changes after you save your program, or ISY boots up, your program will never run.

See Stu's answer above. However, ISY must see this change via all the mechanisms to get there and... ISY must not think the stat is in Off mode when it powers up or the first time the program will be triggered is when the stat sends something other than Off. Querying the stat does not trigger a program unless it causes something to change that is being used as a trigger in that program. If querying the stat causes a status change then ISY is out of sync due to nothing changed since it powered up or signals have been missed due to comm failures. Of course once ISY is up to speed and in sync with your stat then the program works just fine, with good comms. Querying the stat after ISY power up is a good idea to get sync'ed.