![]() |
|
|||||||
| Using Z-Wave with mControl Tips and tricks on how to use Z-Wave with mControl |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
|
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:
Last edited by Ted Singh; 05-13-2010 at 05:50 AM. |
|
#2
|
|||
|
|||
|
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?
|
|
#3
|
|||
|
|||
|
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. |
|
#4
|
|||
|
|||
|
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
|
|
#5
|
|||
|
|||
|
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. |
|
#6
|
|||
|
|||
|
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? |
|
#7
|
|||
|
|||
|
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? |
![]() |
| Thread Tools | |
| Display Modes | |
|
|