Newbie (Sort of) having trojuble with variables.

[JLOB]

I’ve recently upgraded ISY-994i Pro from firmware 4.7.3 to 5.0.14.   I’ve been waiting for the ability to preserve a given device state and then restore that state at a later time.  I can’t find any examples of how this is accomplished.  

For example; I have a group of lights, now on at various on levels.  I want to quickly bring them all up to 100%.  I THEN want to return these devices to their previous levels.  They are not in scenes, nor can they be.  

Can someone please point me in the right direction, or better yet, show me an example?  I’d appreciate it.

Thanks for your time.

JLOB

fyi:  In anticipation of this facility, I have set up both an integer and a state variable for each light, or switch as it was added to the system.  They’re just sitting there waiting to be utilized.

 

[Bumbershoot]

1 hour ago, JLOB said:

I’ve recently upgraded ISY-994i Pro from firmware 4.7.3 to 5.0.14.   I’ve been waiting for the ability to preserve a given device state and then restore that state at a later time.  I can’t find any examples of how this is accomplished.  

For example; I have a group of lights, now on at various on levels.  I want to quickly bring them all up to 100%.  I THEN want to return these devices to their previous levels.  They are not in scenes, nor can they be.  

Can someone please point me in the right direction, or better yet, show me an example?  I’d appreciate it.

Thanks for your time.

JLOB

fyi:  In anticipation of this facility, I have set up both an integer and a state variable for each light, or switch as it was added to the system.  They’re just sitting there waiting to be utilized.

 

Here's a couple of screenshots of simple programs that:

1. Set the variable to the status of the light
2. Set the status of the light to the variable

You need to click on the little symbol ">" in the "Action" pane of the program editor and cycle through the choices until you get the desired variable/device for your program.

[JLOB]

Thank you sir.  That's EXACTLY what I needed.  At 79,  I occasionally need some hand holding.  I really appreciate it. 

J.

ps:  You wouldn't be familiar with programming the Insteon Motion Sensor 2844-222 by any chance,  would you?

[Bumbershoot]

2 minutes ago, JLOB said:

ps:  You wouldn't be familiar with programming the Insteon Motion Sensor 2844-222 by any chance,  would you?

That's not too hard.  If you want to let the sensor turn the light on/off, then no "programming" is required.  You can just link the sensor (make it a scene controller) to a device (normally a SwitchLink) and set the "Timeout" value to something you want (defaults to 30 seconds).  Probably the better way is below:

If you want to use a program to control the device (normally a SwitchLink) that the sensor is connected to (through a scene), then you can set the sensor "Report" value to "On Only", and turn the device (light) off with a program that looks like this:

WestHallOnOff - [ID 0045][Parent 0004]

If
        'Devices / dirWestHall / msWestHallNorth-Sensor' is switched On
 
Then
        Wait  1 minute 
        Set 'Scenes / scnWestHallLights' Off
 
Else
   - No Actions - (To add one, press 'Action')
 
Controls lighting in the west hallway upon motion.  

Linking the sensor to a device (putting it in a scene, as a controller, with a SwitchLink as a responder) means that there's no delay in turning on the light when motion is sensed, which in most cases is desirable.  You can easily set/change the length of time that the light stays on in the program, without having to access the "Set" button on the sensor, which in my case often involves a ladder.  I'm not that fond of ladders anymore...

[JLOB]

Bumbershoot,

Thanks for all that info.  I’ll need to get back to you on that.   Seems I’m not anywhere near where I thought I was with variables.   I’m definitely missing something pertinent.  I had set up variables for most of my lights.  I set them ALL up as integer, since I didn’t know much about what state did.  I had worked with one or two other integer  variables,  using them as switches for run/not run programs.  As an example, I have an integer variable named  iAway.  It’s either 1 or 0.  Switched on, the garage doors lock, the heat/AC reverts to “saving” mode, and the lighting programs are totally different as should be for an unoccupied property.  It worked well.

Switching to firmware 5.x appears to have swapped most, but not all, of my created integer variables to state variables, both in the variables list, and also the references in the programs.  As a result, things aren’t working properly, I seem to not know the difference, or usage, between the two types, and I’m generally at sea.  When I figure this all out, I’ll revisit the motion sensor issue.

Thanks,

JLOB

[JLOB]

Bumbershoot,

I’ve finally got the variable situation all figured out, thanks to your patient and descriptive help.  I’ve looked at the notes you provided on the motion sensor, but I’m still a bit confused.  What I really need to do is use this device as an occupancy sensor.  I have a mate in this house who, while not as senile as I might be, still can’t remember to turn off the kitchen lights.  Ideally I’d have a “Do While” routine that would monitor motion, and report when it stops.  I’d add five minutes (in case she returns) and then trigger the off function.  The only “On” for the lights would come from the wall switch, or Alexa.

Any thoughts?

Thanks.

JLOB

 

[Bumbershoot]

1 hour ago, JLOB said:

Bumbershoot,

I’ve finally got the variable situation all figured out, thanks to your patient and descriptive help.  I’ve looked at the notes you provided on the motion sensor, but I’m still a bit confused.  What I really need to do is use this device as an occupancy sensor.  I have a mate in this house who, while not as senile as I might be, still can’t remember to turn off the kitchen lights.  Ideally I’d have a “Do While” routine that would monitor motion, and report when it stops.  I’d add five minutes (in case she returns) and then trigger the off function.  The only “On” for the lights would come from the wall switch, or Alexa.

Any thoughts?

Thanks.

JLOB

 

Should be easy enough (though I don't actually do this, so I haven't tested it).  If you just want to turn off a light after motion ceases, then you don't have to link the motion sensor to the switch:

LightOff - [ID 0107][Parent 00A7]

If
        'Devices / dirMasterBath / Master Closet Motion Sensor.1' Status is Off
 
Then
        Wait  5 minutes 
        Set 'Devices / dirMasterBath / sloMasterBathClosetLights' Off
 
Else
   - No Actions - (To add one, press 'Action')

It sounds like you're dealing with a person who can turn the light on when they enter, but never turns it off when they leave.  This should turn the lights off 5 minutes after motion is no longer detected.  There's a potential issue with the Motion Sensor II that I haven't tested: There is a "Condition" value of "Never".  I don't know what that does.  I would default that value to "Always".

[apostolakisl]

Your original program I think should work as well (except change the 1 minute to 5) (and also don't link the switch to the motion detector as mentioned).  I assume every time the motion detector detects motion, it sends an "on" (I don't have any motion sensors to confirm this assumption but I do think it is a good one).  So every time it picks up motion, it will re-trigger the program and start the wait all over again.  After 5 minutes of no "on's" sent by the motion detector, the wait completes and shuts of the light.

[JLOB]

On 2/15/2019 at 2:42 PM, Bumbershoot said:

Should be easy enough (though I don't actually do this, so I haven't tested it).  If you just want to turn off a light after motion ceases, then you don't have to link the motion sensor to the switch:

LightOff - [ID 0107][Parent 00A7]

If
        'Devices / dirMasterBath / Master Closet Motion Sensor.1' Status is Off
 
Then
        Wait  5 minutes 
        Set 'Devices / dirMasterBath / sloMasterBathClosetLights' Off
 
Else
   - No Actions - (To add one, press 'Action')

It sounds like you're dealing with a person who can turn the light on when they enter, but never turns it off when they leave.  This should turn the lights off 5 minutes after motion is no longer detected.  There's a potential issue with the Motion Sensor II that I haven't tested: There is a "Condition" value of "Never".  I don't know what that does.  I would default that value to "Always".

Once again your instructions were flawless.  All is well, and the lights no longer burn in vain.  Thanks again for all your help.

JLOB