Domotcl

Download

Terminology

Operation

Actions

Nodes

Drivers

Development

Nodes

Local node

Most drivers will normally be installed in the local node.

Remote node

Server node

MQTT node

Homevision node

An existing Homevision installation can be used in combination with domotcl. This allows for a gradual conversion from a system where Homevision is in control, to a setup where it acts as an interface module for the existing sensors and devices. To use Homevision with domotcl, a homevision node has to be created. The configuration of the node specifies how domotcl talks to the Homevision controller.

Modules

Many familiar Homevision object types can be added to domotcl by adding modules to the homevision node. Devices within these modules generally take an address in the form of a device ID that refers to the device ID of the Homevision object. These can be found in the various object summary screens in HomeVisionXL. No drivers exist for a number of Homevision object types that make no sense to use from Homevision, like timers and periodic- and scheduled events. Such objects are already available in domotcl. The Homevision controller itself can be controlled and monitored via the controller module.

HomeVisionXL controller interface configuration

HomeVisionXL

The controller module also provides server devices. Such devices listen on a TCP port for incoming connections of clients that may need to talk to the Homevision controller. By setting up an inethost device, HomevisionXL can still be used to update the Homevision schedule. In HomeVisionXL, the controller interface would then have to be configured as shown in the picture on the right.