Home Home    Forum    Blog   

LumenLink

Modified: 2008/04/13 00:05 by admin - Uncategorized

Edit

Prerequisites

  • Microsoft Windows 98, Windows Me, Windows 2000, or newer.



  • In order to recieve on the fly node level changes, you must associate all devices/nodes with the RZC0P. This is done via the System Setup -> Advanced-> HAI Setup menu in the Vizia RF Primary Remote. See the RZC0P intructions for details.

On the RZCPG remote, use the HAI setup option, choose RZC0P and add "+" all the devices you want to get notification for. You can use the "4 ON" key to add all (typical). Then press the (.) button, which will start the associations. Finally, when using "back", all the routes will get calculated.

Edit

Features

  • Auto-discovers your Z-Wave network.
  • Displays levels of all devices (such as light brightness)
  • Displays names and types of devices.
  • Allows editing of node names.
  • Change levels of selected nodes.
  • Change levels of nodes grouped in RZC0P.
  • Define groups in the RZC0P.
  • Export metadata to Elk Products ElkRP application.

Edit

Installation

  1. Unzip the downloaded file to any location on your hard drive.
  2. Double click the exe file.

Edit

Usage

  • Upon startup you will need to choose a serial port. If you choose the wrong port you will need to wait 30 sends for the port test to timeout.

After the RZC0P is found...

  • If this is the 1st time the application has been run, all z-wave nodes will be discovered. This should only take a few seconds.

  • Once this is done the main window will be displayed and any missing names will be automatically retrieved from the top of the list to the bottom.

  • Each node's level is also requested at this time. Once the node levels are retrieved, no polling is necessary as the application will sense any light/node state changes.

  • Changing a node name in the grid actually sends the new name to the vizia rf node and can be confirmed by reviewing the device list in the Vizia RF remote control.

  • The RZ0CP can not store group names (as it does with node names) and the group nodes can not be easily and reliably retrieved so if group info is not saved to the xml file, the groups will have to be added again if you want them in your list.

  • You will be asked if you want to save the configuration to a file when you exit. When restarting with a saved config file, your vizia network will not be rediscovered. So if you add/remove any nodes or changed their names with the remote they will be out of sync and you'll need to do a Rediscover Network from the Nodes menu.

  • All sent commands are retried up to 3 times (with 30 second timeouts).

  • Sending commands is done in a serial/linear fashion, so if you attempt to send a command while another command is being sent in the background, you must wait for the 1st command to finish being sent before your request will be processed. This is because each send command has at least one acknowledgement it needs to wait for, which can sometimes take several seconds.

  • Command responses to node names and levels are received asynchronously (they can happen at any time).

Edit

Program Data

The configuration file is saved to the windows common program data folder: %ProgramData%\LumenLink\LumenLink.xml.

The location of this folder depends on the version of Microsoft Windows being use.

  • In Microsoft Windows Vista this will usually be:

C:\ProgramData\LumenLink\LumenLink.xml

  • In Microsoft Windows 98, Windows Me, Windows 2000, and Windows XP this will usually be:

C:\Documents and Settings\All Users\Application Data\LumenLink\LumenLink.xml

Edit

ElkRP Import support

You can export your node and group information to a file that can then be imported into an Elk M1 automation panel.

Requirements:

  • ElkRP 1.6.22 or later
  • Elk M1 with firmware 4.5.4/5.1.4 or later (to avoid the light bounce issue)
  • An Elk M1XSP serial expander with the Vizia RF firmware (this was tested with beta 20.0.1)

Export from LumenLink:

  • Ensure your list of nodes is up to date. If it isn't you can Rediscover the Network.
  • From the File menu click ElkRP Export.

Import into ElkRP:

Once the file has been exported, run ElkRP 1.6.22 or later.

In the main window, on the left pane (Folder Items), expand Automation then right click on Lighting. Click "Import Lighting Data...".

In the "Import Lighting Data" dialog box that appears:

  1. Keep Export File Format to the first choice Universal Devices...
  2. Browse to find the file written by LumenLink (normally called ElkLightImport.xml)
  3. In Handling of Existing Data, choose the appropriate option depending on whether you want to nuke previous data or not.
  4. In Handling of the "Opt" Flag, always use Set (enable)... if you want your Zwave lights to work properly. You can always fix that later in the Lighting section of ElkRP, but you have to do it for proper Zwave operation.
  5. In Handling of the "Show" Flag, the best option is usually Set (enable)... if you want all lights to appear in ElkRM. You can always pick and choose later in the Lighting section of ElkRP.
  6. In Handling of Voice Descriptions, choose as needed. LumenLink will not fill these for you, so you'll have to manually assign voice descriptions to the lights later.

Now clean up the new entries in Lighting to your liking, Send to Control, then Save. You're done!

Now open ElkRM or the M1XEP applet and watch Elk update the light status when you flip a switch...