I have a teenager who is bad about leaving the lights in her room on. To help teach/remind her to get in a good habit, I added following program, however since I'm new to this I must have forgot to cross a t or dot an i somewhere. Please have a look, and see why I may be getting false positives.

 

I will get the text that fan has been on in room with no motion detected for 30 minutes, but then when I check the room the fan is off.

Any guidance is appreciated.

 

If

On Mon-Fri

From 6:00:00AM

To 10:00:00PM (same day)

And Status 'Room1 Motion Sensor' is Off

And Status 'Room1 Fan' is On

 

Then

Wait 30 minutes

Send Notification to 'Group1' content 'Room1 Fan Message'

Wait 30 minutes

Set 'Room1 Fan' Fast Off

 

Thanks

The program turns the fan Off 30 minutes after sending the text.

If you are checking the fan before the 30 minute wait when the program would shut it off, and it is off, what does the ISY show for a status of the fan?

I will check at next false on, and report back.

Oh and yes I'm checking the fan immediately after the notification, so it should not be off at that point. This is to allow time for her to go turn of her fan that she forgot to get her in a good habit, but if it still does not get turned off within 30 minutes it will go off anyway.

The Program logic does not false unless a change was not saved. The ISY might not see the fan status change if there is a comm problem between the device controlling the fan and the PLM.

 

What is controlling the fan?

The fan is being controlled by a 2477S Dual Band SwitchLinc On/Off Switch.

 

So after rethinking the program logic, one thing comes to mind.

 

After the first...Then

Wait 30 minutes

Send Notification to 'Group1' content 'Room1 Fan Message'

 

Would the program just blindly send the notification 30 minutes after the 'if' criteria were met? or is the 'if' criteria assumed still? In other words does the current way it's written only check at the beginning, but not current status again just prior to the notification being sent?

Any time a Wait or Repeat is executing (includes the entire Wait time) and the If conditions change the Wait/Repeat is terminated, the If reevaluated. This can result in the Then clause starting over or the Else clause running.

Referring to TJF1960's question above, is there a way I can have the notification message, include current ISY device status? I see variable options, and have used them before (like current date time), but not sure how to get ISY device status.

What exactly do you mean by ISY device status ?

 

-Xathros

Referring to TJF1960's question above, is there a way I can have the notification message, include current ISY device status? I see variable options, and have used them before (like current date time), but not sure how to get ISY device status.

Only if that device is what triggered the notify program. In that case: In Custom Notification select Alert. You can select Node Name or Node Address which will supply the name or address of the device which ran the notification email.

If the notify program was triggered by an If Status of device then select Action to report the status of the device. If it was triggered by If Control device then select Control.

by "ISY device status", what I meant was what ISY shows as the current devices status of the fan (on or off).

What you can do as a work around until the feature you want is available is create a simple program which monitors the status of the device and switches an integer variable to 1 when it is on and 0 when off. Then have the text/email send you the variable value so you will know whether was on or off when notified.

 

If

Status RoomFan1 is on

Then

set $iRoomFan1 = 1

Else

Set $iRommFan1 = 0

Or you can use Custom Email Substitution Variables to get device status as shown here:

 

http://wiki.universal-devices.com/index ... _Variables

 

For Example: $(sys.node.11 22 AA 1.ST) for the Status of device 11.22.AA

 

-Xathros

Or you can use Custom Email Substitution Variables to get device status as shown here:

 

http://wiki.universal-devices.com/index ... _Variables

 

For Example: $(sys.node.11 22 AA 1.ST) for the Status of device 11.22.AA

 

-Xathros

Ah, I didn't realize you could pull status of other devices and have them displayed, I knew you could with variables. I haven't played much with notifications. Thats great info, Thanks.