Release 3.1.15 (Beta) Is Now Available

[handyman300]

I split the program and now the wait happens as it should. Thanks

 

I still cannot get the state variable to be set to 1. I even created a separate program with the variable all by itself in the then and I run it and it will not change.

[TJF1960]

Humm. Thats odd. I know that when a variable is created it will not show up in a programs drop down box until the new variable is saved, but did you rename it or make any changes to the variable without saving it?

 

Tim

[sanders2222]

Sometimes I think I've experienced strange behavior with programs not running correctly. Even if you run them manually. I've seen other posts where variables in sub-directories are sometimes not evaluated correctly. Try creating a new program in your root directly that will set the variable and see if that works.

 

Jim

[handyman300]

Nope everything saved. I even rebooted the isy99i and tried to set the state variable from the then statement by itself again and I can't set it.

 

I added two more state variables and created a program to set them to 1 and a second program to set them to 0. After creating the two additional variables then miraculously the 2nd state variable $Door_Open_Away_On is setting correctly but the two new ones do not. I updated my programs and they worked as they should. I then went back to make sure I could repeat the problem and now all four work correctly and I can set them.

 

I don't know why they didn't work initially and what caused them to start working but something is amiss. I had them originally in a folder (no conditions) but I never moved them and they are still in the folder.

 

Running 3.1.15 on this particular installation.

[Michel Kohanim]

Hello elvisimprsntr,

 

Thanks so very much for the update ... please do be kind enough to keep an eye and, if possible, provide as much information (even if completely irrelevant) at the time that this happens again.

 

Hello handyman300, Tim, and sanders2222,

 

We found some minor bugs which might be contributing to variables (specifically integer) not being initialized. We should have 3.1.16 our shortly with the fixes therein.

 

With kind regards,

Michel

[bocarob]

Just a fyi It looks like when you combine time in the if portion of the program with a var int or state it becomes unstable the var does not seem to be read and the program is true all the time I will forward a example on the road but when i removed the var and replaced it with a device the program worked just fine.

 

Regards

 

Robert

[sanders2222]

Just a fyi It looks like when you combine time in the if portion of the program with a var int or state it becomes unstable

You are a patient man Robert to trace this bug down. I had similar issues using variables but my workaround used 'flag' programs as a backup in my condition statements. If this issue gets resolved, I'll be able to simplify many of my programs, which introduces a host of other issues. And I still need to get my ELK wired in and working. (Sigh)

[Michel Kohanim]

Hello all,

 

Release 3.1.16 is now available.

 

With kind regards,

Michel