jerlands

Light Media We can get a list going Light Media Room Light Foyer Light Downstairs Bathroom I haven't tried many yet 'cause in the middle of a few things.. Jon..

Turn ON What Device?? Turn On What Device?? I think this is going to take some tuning Jon...

I just did this and don't remember I think you have to open the admin console and go to "manage modules." To enable the skill.. log into your echo app and then use the skills tab to search for ISY. you have to associate the skill with your Amazon account also.. Jon...

Overall Great News! I think there's been an overall issue with recognition the last week or so using the emulator so it may be unrelated to the skill... Anyway.. I've just purchased ISY Portal and created my Account however the email verification had no message body in it so I'm unable to acknowledge. Edit: I had it resend and same thing. .. another edit Benoit emailed me the link but I later found the verification in my web client. why MS Outlook clipped the body or if was done by ATT I don't know. Jon...

You can use https://username:password@mysite.dns.org:portnumber and bookmark it. Jon...

I found an easy way to verify run times for different programs is to sort Programs > Summary > Next Scheduled Run Jon...

My understanding is the portal allows ISY to connect to cloud based services (among other things.) UDI's Echo App will require that connection because this is a "certified" app through Amazon. You could use the Hue Emulator and avoid the portal but I believe the official app will offer greater functionality and better integration with ISY. Jon...

That's good troubleshooting and should be an easy fix! Then you'll have a free IOLinc Jon...

Ok.. I don't understand that and the explanation would probably take too long Jon..

"knowing what conditions terminate the program" <-- by this I meant.. e.g., "If Time is 0600AM" this condition will not reevaluate as unmet (no matter what time of day as long as the Wait or Repeat are active) because it doesn't change the status of the program. or.. using an integer variable because a change in the variables state does not affect the status of the program. Jon...

Thanks you.. that helps to clear things up. knowing what conditions terminate the program when using Wait and Repeat will help prevent program errors. I believe the key factor in the definition is "trigger conditions" or those that change the status of the program. Edit: also.. I now think I understand when the conditions are evaluated, at trigger, at completion of clause and at occurrence of Wait and/or Repeat.. Jon...

Is the following true for any program including those not using Wait or Repeat --> When a Program's trigger conditions change/occur, the If clause is evaluated or... is the if clause only reevaluated if in Wait or Repeat? Jon...

What I'm trying to clear up in my thick skull is how Wait and Repeat interact with the conditions of the program, and right now I don't think they do. Should Wait or Repeat be active and the program status change to false (in the case of Else usage) I don't believe the conditions are reevaluated but rather the program terminated as though it had completed the Else structure because Wait and Repeat are acting more like placeholders that allow termination at that point if there is a status change. So.. I would amend Stu's statement to.. "Thus, a Wait or Repeat will execute as expected unless a statement prior to the Wait or Repeat causes a change in the Status of the program." Edit: or the program is restarted Jon...

Umm, not to be difficult but that wording doesn't seem to be correct. It appears it's the status of the program (true/false) that triggers the termination of the program. But I agree with everything up to that following Repeat The conditions can be changed and not affect the status of the program. Jon...

"which causes the program's overall condition to become false... true" <-- This particular sentence (from Scope, Precedence and Execution Order) completes what I found other explanations excluded. The status has to change for the program containing either wait or repeat to be affected. "the program's conditions are reevaluated each time a Wait or Repeat statement is encountered," <--This sentence from the same is confusing because I believe it is not the condition that's evaluated but the "status" (unless by conditions they're referring to the condition of it's status Anyway.. nit-picky crap but I had the wrong idea of what was going on. Jon...

I forgot.. you write those long extended programs Jon...

I don't even think it evaluates but I believe "triggers" is key. It just seems to be reliant upon the status of the program. If an integer variable is part of the condition and that variable changes it makes no matter to the wait or repeat. Jon...

This link and scroll to "Wait Command." A wait stops when the conditions change. <-- This statement does not appear correct to me either as it seems to require a program status change (true/false state of program.) I understand the new (ver 5) and old options for wait and repeat but I believe they terminate whenever the program status changes. Jon..

Firmware and UI (admin console) both need to be the same version. Clear your Java Cache then load 4.3.26 console or.. update to 4.4.1 (maybe the better option.) Then.. post back if you have the same problems. Edit: you'll need to change your UI to 4.3.26 no matter.. Jon...

Thanks LeeG... The Wiki needs to be changed.. "The 'Wait' command, when encountered during program execution, will cause the program's conditions to be reevaluated." so I believe this statement is true... Wait used within Then will execute as long as the program status is true. Wait used within Else will execute as long as the program status is False? and so the same should be true for the "Repeat" command? Jon...

Here's another example... I used an integer variable so it wouldn't change the status. The program was triggered and the light turned on. I then changed the variable (i.Test) to "0" so the condition then became false but the status of the program didn't change and wait completed. If wait reevaluated the condition then wouldn't it stop as the variable had changed? New Program Copy Copy - [ID 00EA][Parent 00CC] If From 7:17:00PM To 7:20:00PM (same day) And $i.Test is 1 Then Set 'Light Media Room' On Wait 1 minute and 15 seconds Set 'Light Media Room' Off Else - No Actions - (To add one, press 'Action') Jon...

Ok.. I'm was being a little facetious :-J My question however is earnest. Does wait cause a reevaluation of the condition? The following program allows wait to complete. New Program - [ID 00DB][Parent 00CC] If Time is 6:43:30PM Then Set 'Light Media Room' On Wait 2 minutes and 15 seconds Set 'Light Media Room' Off Else - No Actions - (To add one, press 'Action') The following program does not allow wait to complete... New Program Copy - [ID 00E9][Parent 00CC] If From 6:50:00PM To 6:51:00PM (same day) Then Set 'Light Media Room' On Wait 2 minutes and 15 seconds Set 'Light Media Room' Off Else - No Actions - (To add one, press 'Action') Jon...

What's confusing me is I had thought "wait" caused a reevaluation of the condition? I'm thinking now that if the status of the program (true/false) changes before "wait" period completes then it (wait) is terminated? a statement like "if time is 0600am" will never become false so wait will complete. A statement like "if time is from 0600am to 0900am" will be true within that period so within that period "wait" will complete up until the statement becomes false. Jon...

Doesn't wait in the else clause put this program in a perpetual 1 minute run cycle? Jon...

First thing is to remove the motion sensor from any scene you might have it in with the garage lights. If they're linked in a scene you'll have no control. Next factory reset the motion sensor to remove any links.. set jumper 5. use programs to control lights with sensor post your programs. Jon...