Aeotec Recessed Door Sensor - No Program Control

[jmltech]

Running v. 5.0.12

I have a couple of Z-wave Aeotec recessed door sensors.  They were added into the ISY fine (so I think).  One sensor address is ZW023, and loaded two entries: ZW023_104 Binary Sensor and ZW023_1 Notify Sensor.  When opening/closing the door, the Binary Sensor changes from Off/On.  The Notify Sensor just shows a battery level.

The issue that I have is in the program control.  Under Programs, under "If" the sensor isn't listed under the  'Control' condition.  It is only listed under 'Status'.  However, the program doesn't run under status since you need Control.

Is there something else that is needed for the Binary Sensor for this device to show up under "Control" so that I can add a notification when this sensor is switched 'ON"?

Thanks,

Joe

 

[lilyoyo1]

The change in status should still trigger a program. What are you trying to do and what is the program. That you have written

[jmltech]

The issue is that I can't write a program, since the device isn't listed under "Control".  Other devices are listed, but this device isn't.  If I choose "Status', then the device is listed in the drop down selection.  However, I want to have a program send a notification when the device turns on or off.  For this to happen, you need to have the device under "Control" but I can't select it since it isn't listed in the drop down selection.

[paulbates]

I use a technique with 2 node statuses in this program. Hearbeat is only ever 1 or -1 (like on and off). This program triggers when the state doesn't change:

FR Comm Check - [ID 001C][Parent 002C]

If
        'HVAC / Family Room' Heartbeat is -1
     Or 'HVAC / Family Room' Heartbeat is 1
 
Then
        Wait  4 minutes 
        Resource 'Pushover HVAC Log - Familyroom Venstar Down'
        Send Notification to 'Default' content 'HVAC FR Venstar Down'
 
Else
   - No Actions - (To add one, press 'Action')
 

 

I believe you could write a program like the below and it will only trigger when the change happens. The isy isn't evaluating the status, its evaluating the last change in status.

if

     status door is open
 or status door is closed

then

   send notification

You can put a 15 second Wait statement in first to test it, an if it doesn't work you can disable the program during the wait.  You may also want the wait because the occupants open and close the door several times in a row and you really only want one notification per event

Paul

[jmltech]

The status is changing okay whenever the door is open or closed.  The problem is that the sensor isn't list under "Control", only under "Status"

This device doesn't have a heartbeat that I can tell.

If I include the device as a "status = ON", it never runs because the ISY needs the 'Control' to trigger a notification.  My motion sensors are listed in "Control", but this devices isn't, even though on the main screen I can see the binary status change from Off to On when I open the door, and change from On to Off when I close the door.

[paulbates]

The heartbeat was an example that the concept does work and I probably confused things with that. I probably missed on saying open and closed vs on / off. Try this:

if
        status door is on
   or status door is off
then
       send notification

That program should always trigger when the state changes and that will only be when the door opens or closes. And the state only changes when and on or off is sent. This is the same effect as "If Control". It won't take long to give this program a try.

Paul

[jmltech]

I tried it... didn't work

I think the ISY only runs a program when the control changes.  The status doesn't trigger the program, only a control will trigger.

Hence back to my original issue... why isn't this device listed as a selection in the dropdown menu under Control.  It is only listed under Status. 

Probably a version 5.x thing that needs to be updated.  Maybe Michael will chime in?

 

 

[dbuss]

1 hour ago, jlyczak said:

I tried it... didn't work

I think the ISY only runs a program when the control changes.  The status doesn't trigger the program, only a control will trigger.

Hence back to my original issue... why isn't this device listed as a selection in the dropdown menu under Control.  It is only listed under Status. 

Probably a version 5.x thing that needs to be updated.  Maybe Michael will chime in?

 

 

 

" I think the ISY only runs a program when the control changes.  The status doesn't trigger the program, only a control will trigger."

That's interesting. I have programs that run on status change in both 4.6.2 and 5.0.12 with Insteon and Z-Wave devices in both versions of firmware.

[lilyoyo1]

2 hours ago, jlyczak said:

I tried it... didn't work

I think the ISY only runs a program when the control changes.  The status doesn't trigger the program, only a control will trigger.

Hence back to my original issue... why isn't this device listed as a selection in the dropdown menu under Control.  It is only listed under Status. 

Probably a version 5.x thing that needs to be updated.  Maybe Michael will chime in?

 

 

I have many programs that trigger without issue based on status not control. These programs not only control other devices without issue but also send notifications as well.

[jmltech]

I followed paulbates suggestion for testing....

If
        'Garage23-HouseDoor-Binary Sen' Status is On
     Or 'Garage23-HouseDoor-Binary Sen' Status is Off
 
Then
        $i.DoorOpened += 1
 
Else
   - No Actions - (To add one, press 'Action')

The variable never changes no matter how many times I open or close the door.

 

 

 

 

[jmltech]

 

35 minutes ago, lilyoyo1 said:

I have many programs that trigger without issue based on status not control. These programs not only control other devices without issue but also send notifications as well.

I may be thinking of the 'Integer' and 'Stat' variables.

I'll try excluding and including and try again... probably tomorrow.

Thanks for everyone's replies.

[lilyoyo1]

What is it that you want to accomplish

[jmltech]

Whenever the door opens to send a notification. The program that I originally had wasn’t working for this device, so I simplified it using the example that was previously given. The program just doesn’t run. However on the main device screen it does show the status change whenever i open or close the door.

[lilyoyo1]

Is your information configured properly to receive notifications?

[jmltech]

Finally was able to get it working.  I had given up on the door sensor, but recently I started having trouble with the Kwikset z-wave lock sending notifications when the door keypad was used to unlock.  So, I excluded both the door sensor and the Kwikset lock, made a backup copy on the ISY, did a reset, loaded the backup copy, then included both the door sensor and the kwikset lock.   All is well now and the programs are sending their notifications when the status changes, as expected.

[junkycosmos]

hi jmltech

I am curious for your feedback on this aeotec door recessed door sensor.  Could you mind noting how long you have been using it, battery life so far etc?

 

I just picked one up to test and was able to add it straight into 5.0.12 where I see it showing up with two nodes like you mentioned.  

Notify Sensor: showing battery %

Binary Sensor: showing door status on or off 

 

[junkycosmos]

forgot to ask .. 

Should this device show up in Actions: CONTROL ?   Or only in Actions: STATUS?     Mine too is only showing in status.   I was able to write a program that works but I'm used to seeing devices in both although I'm just getting used to v5 firmware.