As with device objects in other drivers, each ZWaveDevice has a Points extension that serves as the container for proxy points. The default view for any Points extension is the Point Manager (in this case, the “ZWave Point Manager”). Use it to review (and if necessary), edit ZWave proxy points under any ZWaveDevice. For more details, see ZWave Point Manager.
Unlike point managers in almost all other drivers, you do not add proxy points using the ZWave Point Manager (no “New” or “Add” buttons, nor any “Learn mode” with a button and pane). All available proxy points are automatically created. Of course you can add alarm or history extensions, link into other station logic, and “bind” to Px widgets in PxPages, just
as with any other proxy points.
In addition to proxy points, some data is modeled by dynamically added “child components” directly under each ZWaveDevice. As with proxy points, these child components will vary from one device to another, based on the Z-Wave command classes each device supports.
See the following procedures:
To review ZWave proxy points
Once a ZWaveDevice is added, any available proxy points are already included. These will vary by the number and types of Z-Wave command classes that the device supports. You can get statuses and values back immediately, to review and use as needed.
To review (and edit) ZWave proxy points in a device:
-
In the Device Manager, in the Exts column, double-click the Points icon
in the row representing the device you wish to review points.
This brings up the ZWave Point Manager.
-
Double-click any point for an Edit dialog.
To edit multiple points, hold the Ctrl key and click points to select, then click the
button.
In the Edit dialog you can (re)Name the point(s), edit or change point Facets, and change Tuning Policy Name, if needed. Additional properties are also available for editing, but are rarely if ever needed (Device Facets, for example).
Default point names are dependent on the command class, and typically use a “camel case” convention, starting with a lowercase letter—for example: “
switchToggle” or “dimmer”.For more information, see ZWave Point Manager, ZWave proxy points, and ZWave proxy points by default name.
To review ZWave device child components
Once a ZWaveDevice is added, all dynamic “child components” are already included. These will vary by the number and types of Z-Wave command classes that the device supports. You can expand the parent device to review and sometimes write values to properties in these child components. Or, as needed you can invoke actions, or link properties or actions into station control logic.
To review ZWave “child components” for any ZWaveDevice:
-
In the Nav tree, expand the ZWaveDevice to see child components. All components listed under “Points” are dependent on the command classes supported.
Default names are sometimes reflective of the command class, and typically use a “camel case” convention, starting with a lowercase letter—for example: “
manufacturerSpecific” or “switchAll”.Double-click any child component to see its properties (by themselves).
Or, you can go to the property sheet of a ZWaveDevice to see these same child components listed, and then expand any of interest.
-
Right-click a child component to see any available actions.
For more information, see ZWaveDevice and ZWaveDevice child components.