Event Triggers

[macrho]

I'm missing something really basic.

I have an EcoLink Tilt Sensor on my right garage door. I'm utilizing the two statuses that are attached to the sensor:

1) Off-Closed-No Motion status with a value of 0
2) On-Open-Motion status with a value of 255

I can see that these events fire in my log:

Device: Outside Garage Sensor Binary Reserved Set to On/Open/Motion
Device: Outside Garage Sensor Binary Reserved Set to Off/Closed/No Motion

So it appears when I'm opening and closing the garage door, I'm getting notice that these events happened. So far, so good.

My open event is setup as:

IF This device changes and becomes...
Outside Garage Right Tilt Sensor changes and becomes a custom value or value range of 255 to 255

and my close event is setup as

IF This device changes and becomes...
Outside Garage Right Tilt Sensor changes and becomes a custom value or value range of 0 to 0

The THEN piece is sending a pushover message

If I run each of the events by clicking on the Play icon, I receive my pushover message, as expected, so I know that piece works.

When my garage door tilt sensors change, I get no pushover notification

What did I do wrong?

[S-F]

Your trigger of custom value seems to be the issue. It should be changes and becomes On/Open/Motion or Off/Closed/No Motion as your log shows. I don't have this device so I can't tell you exactly what it should be but something like that.

[macrho]

I don't see a way to use the status, only the value is available

[S-F]

Could you post a screenshot of your options?

Check mine out.

[macrho]

This is what I see:

[randy]

Same here. I have modified the status text and graphics, but your log entries indicate HomeSeer is picking up the text.

.

[randy]

This is what I see:

There is something wrong in the way the device was imported. I would make sure you are using the latest Z-Wave plug-in, then try rescanning the device (it must be awake). There are other steps if this doesn't work, but that is the best place to start.

[macrho]

I'll delete and re-add the device, I had done the original add at a distance
Most of my battery devices are giving me headaches

[S-F]

You might not need to remove the device from your Z-Wave interface. Just delete all of the child devices and then rescan the root device first. That will rebuild all of the child devices.

[randy]

I'll delete and re-add the device, I had done the original add at a distance
Most of my battery devices are giving me headaches

Just a few quick pointers on battery devices

• With a Z-Stick or a Z-Troller, keep them very close to the controller. With the Z-Net you have a little more latitude.
• The device must be awake during inclusion and be kept awake during the entire process. Sometimes the devices don't stay awake during the interrogation after inclusion, you can sometimes help the process by waking them up again during the process.
• Rescan if you see any errors during the inclusion. Again, be sure the device is awake during the entire process. On the door tilt sensors I hit the include/wakeup a couple of times during the process.
• For all my battery operated devices I use this same process with the device near the controller. After confirming that it is included properly, I place the device and do a couple of optimize passes after it is in its final location. It must be awakened immediately before optimizing. I usually carry a laptop or tablet to the device so that I can initiate the optimization while at the device.

[macrho]

Still not having luck though I did see the statuses populated but nothing displays in the log when the status changes.

Here is from the "rescan":

May-29 4:31:37 PM 
* 
Z-Wave 
Z-NET: Device Outside Garage Right Tilt Sensor Optimization not executed, the node cannot be reached. 
May-29 4:31:18 PM 
* 
Z-Wave 
Z-NET: Device Outside Garage Right Tilt Sensor Optimization not executed, the node cannot be reached. 
May-29 4:31:01 PM 
* 
Z-Wave Warning 
The device at node 29 should result in 3 child devices being created, but the node interrogation currently has 0. This may still result in a successful child creation. 
May-29 4:31:01 PM 
* 
Z-Wave Error 
Node 29 did not provide Wake-Up Command Class information - it will not be processed further. 
May-29 4:31:01 PM 
* 
Z-Wave 
All associations for node 29 have been retrieved successfully. 
May-29 4:31:00 PM 
* 
Z-Wave 
Getting association information for node 29 
May-29 4:31:00 PM 
* 
Z-Wave 
Node 29 is Z-Wave version: Lib: 3.4 App: 2 
May-29 4:31:00 PM 
* 
Z-Wave 
Node: 29 Controls Class(es): BASIC 
May-29 4:31:00 PM 
* 
Z-Wave 
Node: 29 Supports Class(es): SENSOR_BINARY_V2, ALARM_V2, MANUFACTURER_SPECIFIC, VERSION_V2, ASSOCIATION, WAKE_UP, BATTERY, CONFIGURATION 
May-29 4:31:00 PM 
* 
Z-Wave 
* 
May-29 4:31:00 PM 
* 
Z-Wave 
Device synchronization needs to create devices for one new node. 
May-29 4:31:00 PM 
* 
Z-Wave 
* 
May-29 4:31:00 PM 
* 
Z-Wave 
Syncing Z-Wave nodes with device list...

[randy]

Still not having luck though I did see the statuses populated but nothing displays in the log when the status changes.

Here is from the "rescan":

May-29 4:31:37 PM 
* 
Z-Wave 
Z-NET: Device Outside Garage Right Tilt Sensor Optimization not executed, the node cannot be reached. 
May-29 4:31:18 PM 
* 
Z-Wave 
Z-NET: Device Outside Garage Right Tilt Sensor Optimization not executed, the node cannot be reached. 
May-29 4:31:01 PM 
* 
Z-Wave Warning 
The device at node 29 should result in 3 child devices being created, but the node interrogation currently has 0. This may still result in a successful child creation. 
May-29 4:31:01 PM 
* 
Z-Wave Error 
Node 29 did not provide Wake-Up Command Class information - it will not be processed further. 
May-29 4:31:01 PM 
* 
Z-Wave 
All associations for node 29 have been retrieved successfully. 
May-29 4:31:00 PM 
* 
Z-Wave 
Getting association information for node 29 
May-29 4:31:00 PM 
* 
Z-Wave 
Node 29 is Z-Wave version: Lib: 3.4 App: 2 
May-29 4:31:00 PM 
* 
Z-Wave 
Node: 29 Controls Class(es): BASIC 
May-29 4:31:00 PM 
* 
Z-Wave 
Node: 29 Supports Class(es): SENSOR_BINARY_V2, ALARM_V2, MANUFACTURER_SPECIFIC, VERSION_V2, ASSOCIATION, WAKE_UP, BATTERY, CONFIGURATION 
May-29 4:31:00 PM 
* 
Z-Wave 
* 
May-29 4:31:00 PM 
* 
Z-Wave 
Device synchronization needs to create devices for one new node. 
May-29 4:31:00 PM 
* 
Z-Wave 
* 
May-29 4:31:00 PM 
* 
Z-Wave 
Syncing Z-Wave nodes with device list...

Those log entries show that the device was not awake during the whole interrogation. Did you do as I suggested above and make sure the device stayed awake during the whole process? You will get the longest awake period, by removing the battery for about 15-30 seconds, then reinstalling it immediately before you rescan. If you are including them for the first time, remove the battery, then put your controller in the Add/Include mode and immediately install the battery. Just remember to be fast. In either case it is best to be close to the Z-Net - within 5-10 feet should be fine.

[macrho]

Thanks for the tip. I brought the tilt sensor inside and kept it within 5 feet of the Z-NET. After a couple of attempts it was able to successfully interrogate the device. I'm now able to get notifications when my garage door is either open or closed

Now I'm attempting to create a virtual device that will allow me to open or close the garage door.

[Uncle Michael]

Is it just me being an old fuddy, or are there applications where Z-wave is just not well-suited, and even X10 wireless (not PLC) is easier to setup and use?

[randy]

Is it just me being an old fuddy, or are there applications where Z-wave is just not well-suited, and even X10 wireless (not PLC) is easier to setup and use?

You're just being an old fuddy

All kidding aside, Z-Wave is very good, but there is a learning curve to getting devices to work properly, especially battery operated devices. The inclusion and interrogation process is crucial, so that all of the devices capabilities can be properly provided to the controlling software. Once that is done and the network is properly optimized, it is now very reliable. It was until last fall before the Z-Wave plug-in got to the point where it was 99% reliable. Mine hasn't had a failed command since. The door sensor we are talking about in this thread is on my mailbox, outside on the street, easily 70+ feet and 3 walls from the controller, yet it communicates directly.

Now that we have every device installed it is almost boring, I find myself trying to figure out new things to do just so I can fiddle with the system. I have said in other posts that my wife even appreciates and relies on home automation, where she was very skeptical last year at this time.