Embedded Automation Forum  

Go Back   Embedded Automation Forum > mHome Products > mControl Application Notes > Using Z-Wave with mControl
Register Forums FAQ Members List Calendar Search Today's Posts Mark Forums Read

Using Z-Wave with mControl Tips and tricks on how to use Z-Wave with mControl

Reply
 
Thread Tools Display Modes
  #1  
Old 05-13-2010, 05:48 AM
Ted Singh's Avatar
Ted Singh Ted Singh is offline
Senior Member
Site Admin
 
Join Date: Nov 2005
Posts: 980
Default Using Z-Wave Sensors (Motion, Door/Window)

The following steps will allow you to use Z-Wave sensors within mControl, including motion sensors and door/window sensors.

Notes:
1. This functionality was added in mControl v2.1 Build 3784 (or mControl v2.1 RC5 B3)
2. We have tested the functionality with the following devices, but should apply for other devices:
>> Intermatic CA9000 Passive Infrared (PIR) Sensor (US)
>> Aeon Door/Window Sensor (Model: DSB04100-ZWUS)



1. Use the Z-Wave Adapter Utility to add the sensor devices to your Z-Wave adapter. Use the "Start Remove Device" and "Start Add Device" to perform this step - remember, you will likely have to "Start Remove Device" before you can "Start Add Device".



2. Once added, select the device in the "ID of the device to operate on" list box and select the "Device Associations" button.
(a) To have the device inform the Z-Wave Adapter (and mControl), select the "Associated with Controller" check box. To unassociate, uncheck this option.
(b) To have the device inform other Z-Wave devices, select the devices and in the "Not Associated" section and use the "<-" to move them to the "Associated" section. To unassociate, select the devices in the "Associated" section and use the "->" to move them to the "Not Associated" section



Press "OK" to save these changes. These associations are stored on the device itself and tell the device which devices to inform of any status changes.

Please note with this step:
- It may be necessary to ensure sensors are "awake" to accept these configuration changes
- Some devices must be close to the adapter to accept the changes (e.g., 1m or 3ft away)

3. Once you have exited the Z-Wave Adapter Utility and started the mControl server, you can add the devices to mControl.



4. You can use the device within an mControl macro.




A typical log file entry for this macro is shown:

Quote:
>> Immediate status from sensor
2010-05-12 22:36:37.030 00:01:26.7571996 (015) D0 ZWAVE event: NodeID=10, LevelChanged: 255
2010-05-12 22:36:37.139 00:01:26.8687230 (015) I0 Broadcasted notification: ["ZWAVE:10", "100"] for device [Sensor]
>> Motion macro is triggered and operated on
2010-05-12 22:36:37.139 00:01:26.8731484 (020) M0 [Motion] macro started by trigger [New Condition Group] (ID=540315FD)
2010-05-12 22:36:37.139 00:01:26.8771688 (020) M0 [Motion] macro action: [Lamp ON 100] (ID=540315FD)
2010-05-12 22:36:37.155 00:01:26.8806290 (020) M0 Automation command [4, "5", "ON 100", 100, "ZWCTRL", 1] (ID=540315FD)
2010-05-12 22:36:37.264 00:01:26.9891007 (020) M0 [Motion] macro action: [Delay 00:00:10] (ID=540315FD)
2010-05-12 22:36:37.342 00:01:27.0678568 (015) D0 ZWAVE event: NodeID=5, LevelChanged: 99
2010-05-12 22:36:42.271 00:01:31.9972463 (015) D0 ZWAVE event: NodeID=10, LevelChanged: 0
2010-05-12 22:36:42.271 00:01:31.9973731 (015) I0 Broadcasted notification: ["ZWAVE:10", "0"] for device [Sensor]
2010-05-12 22:36:43.519 00:01:33.2448805 (015) D0 ZWAVE event: NodeID=7, PollFailed for property Level
2010-05-12 22:36:47.279 00:01:37.0041608 (020) M0 [Motion] macro action: [Lamp OFF] (ID=540315FD)
2010-05-12 22:36:47.279 00:01:37.0042527 (020) M0 Automation command [4, "5", "OFF", 100, "ZWCTRL", 1] (ID=540315FD)
2010-05-12 22:36:47.388 00:01:37.1132557 (020) M0 [Motion] macro stopped (total execution time=00:00:10.2360000) (ID=540315FD)

Last edited by Ted Singh; 05-13-2010 at 05:50 AM.
Reply With Quote
  #2  
Old 07-29-2010, 01:52 PM
hadiesper hadiesper is offline
Member
 
Join Date: Mar 2009
Posts: 58
Default

Has anyone tried this with ACT products? Is it an absolute must to associate the controller to the sensor for it to work? Cant you just add the motion sensor to the network?
Reply With Quote
  #3  
Old 08-11-2010, 05:38 AM
Michael K Michael K is offline
Junior Member
 
Join Date: Dec 2008
Posts: 5
Default

I was able to get the CA9000 working however the range of operation (distance from CA9000 to HA23C USB Z-Wave Controller) was very limited. The device would not work properly when it was more than 12-15ft away. When within range, the CA9000 worked the way it is suppose. Outside the 15ft range, mControl would not provide updates of its status.

Has anyone else experienced this problem with the CA9000?

I am thinking about purchasing/using an Aeon Z-Wave Door/Window Sensor instead of the CA9000, has anyone had good experience with this Aeon product and would be able to comment on its range?

Thank you in advance.
Reply With Quote
  #4  
Old 08-11-2010, 06:03 AM
hadiesper hadiesper is offline
Member
 
Join Date: Mar 2009
Posts: 58
Default

Interesting work Michael, I can understand why the sensor would behave in this way. How i did this is kind of wasteful, but it is very reliable and works and well (not too wasteful if you have 2-3 motion sensors to install).

What i did was, I installed the motion sensor in lighting mode and associated it with a Z-wave switch (any switch that is unused). This switch was even installed in the false ceiling and not connected to anything.

Now the macro in mcontrol would be triggered on status change of the Z-wave switch not the PIR. so PIR->Switch->mcontrol.

This works great and with no distance issues. Unfortunately you will have to bear the cost of an additional z-wave module! and lets face it, its not the right way of doing things
Reply With Quote
  #5  
Old 08-12-2010, 12:55 AM
Michael K Michael K is offline
Junior Member
 
Join Date: Dec 2008
Posts: 5
Default

Thank you for the suggestion hadiesper, it worked well.

I added the motion sensor (PIR) to my network and using the Z-Wave Adapter Utility and associated it with a Z-Wave dimmer switch (as described in this post) in close proximity. In my macro, I use the status change of the PIR and not the dimmer switch. Is there a particular reason you used the switch's status in your macro?

I didn't fully understand what you meant by "What i did was, I installed the motion sensor in lighting mode and associated it with a Z-wave switch"

My distance issue is solved however I noticed the PIR would randomly trigger after about 30 minutes of normal operation when no motion was present and continue to trigger on a minute interval. Did you experience that at all?

Thank you.
Reply With Quote
  #6  
Old 08-12-2010, 09:00 AM
hadiesper hadiesper is offline
Member
 
Join Date: Mar 2009
Posts: 58
Default

Interesting that worked for you Michael. what PIR are you using? Are you saying you didnt associate it with the controller? you simply added it then associated it with a nearby Zwave switch.

What I meant was pretty much the same thing btw, but PIR status change was not working for me so I configured zwave switch status change. I think it is because of the PIR model being used. Im using ACT ZIR. what about you?
Reply With Quote
  #7  
Old 08-12-2010, 10:23 AM
Michael K Michael K is offline
Junior Member
 
Join Date: Dec 2008
Posts: 5
Default

I am using the Intermatic CA9000.

I should clarify, I did associate it with the controller (check box at the top of the dialog box for associations) as well as a nearby switch as outlined in the instructions provided in the forum.

Does the ACT motion detector work reliably?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 06:59 PM.


Powered by vBulletin® Version 3.8.3
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.