Jump to content


Submitter

SUPPORT TOPIC File Information

  • Submitted: Jul 09 2011 11:55 AM
  • Last Updated: Mar 30 2012 06:02 PM
  • File Size: 942bytes
  • Views: 2742
  • Downloads: 60
  • Author: 123, Markh and etc6849
  • Contact: Premise support forum

Previous Versions

  • 11 Sep 2011 Download VRC0P Z-Wave module for Premise
  • 11 Sep 2011 Download VRC0P Z-Wave module for Premise
  • 09 Sep 2011 Download VRC0P Z-Wave module for Premise
  • 09 Sep 2011 Download VRC0P Z-Wave module for Premise
  • 09 Jul 2011 Download VRC0P Z-Wave module for Premise
  • 09 Jul 2011 Download VRC0P Z-Wave module for Premise

Download VRC0P Z-Wave module for Premise r33

- - - - -



Screenshots
How to obtain the XDO file
Since the VRC0P driver is under constant revision as the authors buy more and more Z-Wave devices, Markh set up a project site on code.google.com.  At this point, the driver is 100% stable and you should never see any transmission errors.  If you do, you should try a network rediscovery using your primary controller.

The most current XDO file will change, but can always be directly downloaded from here:
https://zwave-driver...aRF/ViziaRF.xdo

Or from here:
http://code.google.c...n/trunk/ViziaRF

If you're browser opens the file instead of giving an option to download it, simply go to File->Save As and name the file, keeping XDO extension.


Our plan going forward is to modify the version information found under the properties for sys://Schema/Modules/Leviton so you always know which version you have.
This link will detail the revision history:
https://code.google....ise/source/list

A work in progress guide to Premise + Z-Wave can be found at this wiki:
https://code.google....-premise/w/list

What's supported
1. Switches
2. Dimmers
3. Humidity and Temperature sensors (Tested: HM-TS001)
3. Motion sensors (Tested: ZIR000, HSM100)
4. Door sensors (Tested: HM-DW001, HRDS1, SM103)
5. Flood sensor (Tested: HM-FS001)
6. Thermostats (Tested: TZEMT400)
7. Controllers (allows controller buttons to trigger Premise events; Tested: VRCZ04-M0, VRCZ04-MR)
8. Locks (only supported on VRC0Pv3.  The VRC0Pv3 has a +3 on written on it's back.)
You MUST verify the VRC0P you order supports locks as the model numbers are the same for the old and new (version 3) VRC0P.

Getting started
To Install:
1. Navigate to Modules.Leviton and delete it if you are using a previous version.
NOTE: if you don't do this you'll end up with duplicate GUIDs and SYS will crash.  However, SYS is recoverable from this type of mistake.
2. Right click on import and import the updated XDO.
3. Navigate to Devices.CustomDevices
4. Right click new -> ViziaRF
5. Navigate to Devices.CustomDevices.ViziaRF
6. Set VRC0Pv3 to true by clicking the checkbox called VRC0Pv3.  If you are using an older VRC0P that does not have +3 on the back label, do not check this box.
7. Set Network to whatever COM port you're using.
8. Set the NodeID for the VRC0P that is connected to Premise.
This is very important.  This is the only NodeID that will not be automatically obtained.  This NodeID can be found via your primary z-wave controller.
9. Now navigate to Devices.CustomDevices.ViziaRF.Devices and toggle "Discover Devices."  
9.1. You should ensure that you see packets being sent back and forth between Premise and the VRC0P.  From the task bar, navigate to View->Port Spy.
10. When Discovery completes, initialization will automatically start.  For each device, initialization gets the z-wave name and location, the model and version information, and lastly any current associations.  It is recommended to wait until the Initializing boolean found under Devices.CustomDevices.ViziaRF.Devices is false before proceeding.

Recommended Z-Wave setup
A Z-Wave network requires a primary controller.  This is completely separate from Premise.  Once your network is setup via a primary controller, the VRC0P and VRC0Pv3 are RS232 secondary controllers that allow Premise to communicate with the Z-Wave network once it is properly set up.  Once the primary controller has setup the network, it is not necessary to keep it plugged in.

This module has been tested extensively with the Leviton ViziaRF and ViziaRF+ Z-Wave line.  As such, the primary controllers used included the ControlThink USB stick or the Leviton USB RF Installer tool.  The software used with these primary controllers included Leviton's RF Installer Tool Kit.  This software will work with the ControlThink USB stick IF you update its firmware to 4.5.2 or newer.  

Other brands of primary controllers may work fine with the VRC0P.  However, this has not been verified.

IMPORTANT NOTE:  You MUST verify the VRC0P you order supports locks as the model numbers are the same for the old and new (version 3) VRC0P.  If you don't want lock support, it doesn't matter which VRC0P you order.  The newer VRC0P is also firmware upgradeable where the previous two versions were not.

I ordered the newer VRC0P+3 from below.  The VRC0P is what connects to your Premise sever:
http://www.asihome.c...roducts_id=3437

I recommend using this USB stick as the primary controller.  If using this stick, Leviton supplies free software to properly setup your network.  Once you run the setup, you can unplug the USB stick if you'd like.  If installing a large network, you probably want to use a laptop and walk around with the USB stick plugged in while as the software sets things up.
http://www.asihome.c...roducts_id=4546

What's New in Version r33 (See full changelog)

  • New additions:
  • A new home object class called ZWaveLock is used for minibrowser and the automation browser. This new version better works with the lock's ability to manage user codes, so the ZWave home object class' code is much more simplified. To use it create a new home object of type "ZWaveLock" and bind it to the lock device object. The "Lock" home class (that had to be downloaded separately) will no longer be supported. The GUI IDs are different between the classes though, so the old Lock home class can work side by side the new ZWaveLock home class. What this means is that a user only needs to import a single module to have full lock support for the AB and MB.
  • I fixed a bug in how controller buttons were handled.
  • I fixed a text formatting bug in how device level events were reported.
  • I already added your thermostat change, but will add the other changes next week and hopefully remember how to use
  • I improved the structure of local manipulations and also gave it its own ZWaveLocalManipulations home class. Again, this will make things easier for users to install later. ZWaveLocalManipulations lets you do more with a switch. For example, after adding a ZWaveLocalManipulations home object to a room, bind it with a switch or dimmer. Set some time periodicity (default is 6 seconds). You then define a property change script to monitor LocalManipulationsInTimePeriod in order to perform actions based on the number of local presses. After 6 seconds, LocalManipulationsInTimePeriod will reset to zero, but this can be changed by modifying TimePeriod.
  • I ran into an issue with these two lines from sys://Schema/Modules/Leviton/Classes/Group/OnChangePowerState and sys://Schema/Modules/Leviton/Classes/Group/OnChangeBrightness:
  • if sysevent.srcProperty.name <> "Brightness" and sysevent.srcProperty.name <> "Trigger" then
  • if sysevent.srcProperty.name <> "PowerState" and sysevent.srcProperty.name <> "Trigger" then
  • I modified the group logic to use boolean flags instead of srcProperty as the srcproperty seems to lose its meaning after SYS executes more than a few levels deep!?!
  • See: http://cocoontech.com/forums/topic/9745-school-of-hard-knocks/page__view__findpost__p__151088
  • I modifed the onChangeOnNewData script to more properly account for the receive line length = 0 case (I believe we should set this.RxNextLine = true following receipt of a transmission of zero length).
  • I made many changes to the controller class to allow for setting associations for the up/down buttons on Vizia RF zone controllers. Now, Premise can use these buttons to do trigger scripts under keypad buttons that are created under Home in Premise Builder. The up/down buttons are disabled by default, to enable set UpDown to true for the controller object. The up/down buttons represent a hidden association; eventhough the zone controller report only 4 possible associations, the up/down buttons can be used as GroupID 5. This is what this module exploits.






  • 157 Total Files
  • 8 Total Categories
  • 25 Total Authors
  • 19854 Total Downloads
  • Premise Web Services Latest File
  • John in VA Latest Submitter

0 user(s) are online (in the past 15 minutes)

0 members, 0 guests, 0 anonymous users