Documentation

Welcome to the documentation of the resol-vbus project. The resol-vbus Node.js module allows you to connect to RESOL VBus-enabled devices, get their live or recorded data, filter them and then store them in many different formats.

VBus Models

Currently the VBus uses three different protocol versions, each specialized for a certain use case. Each of these three different versions has an associated model class which inherits from the abstract Header class.

This Header class provides uniform access to properties and methods that are applicable for all sub-classes. Each Header sub-class knows how to generate a Header ID from its properties. Header IDs include information about the source and the destination of the Header as well as other information that identifies that Header.

Packet

The version 1 Packets are sent by the RESOL VBus-enabled device in regular intervals and carry payload data like sensor temperatures, relais speeds, date and time. Those Packets have a predefined structure which is documented in the Chapter H of the VBus Protocol Specification.

Datagram

The version 2 Datagrams allow remote access to device values that are part of the device’s display menu interface. Each of these values has an unique index that can be used to read or write the value using a datagram.

Telegram

The version 3 Telegrams are mostly used to communicate with external sensors and actors in a very efficient way.

HeaderSet

In addition to those model classes there is a HeaderSet class which works like an intelligent array. Adding an instance of one of the Header sub-classes to a HeaderSet automatically replaces an older version of this instance with the same Header ID if present.

HeaderSetConsolidator

TBD

Specification

Instances of the Packet class carry optional binary payload in them. The Specification class is capable of enumerating and converting the information within that payload to a human- or machine-readable format. It basically is a JavaScript implementation of Chapter H of the VBus Protocol Specification.

Connections

Connections are used to access the live data stream of a RESOL VBus-enabled device. Connections know how to decode the incoming binary data stream according to the VBus Protocol Specification. Once a valid piece of information has been decoded the Connection emits an event. In addition to that Connections can send valid information to the remote side as well.

The resol-vbus module includes the following sub-classes of the abstract Connection class:

  • SerialConnection
  • TcpConnection

Converters

Converters take instances of the Header and HeaderSet classes and converts them to a different format. Some converters also support parsing the format they created back into Header and / or HeaderSet instances.

The resol-vbus module includes the following sub-classes of the abstract Converter class:

  • VBusRecordingConverter
  • DLxJsonConverter
  • TextConverter

Recorders

A Recorder provides access to HeaderSet stores (e.g. dataloggers) by allowing to either playback the HeaderSets in the store, record HeaderSets to the store or synchronize two Recorders.

The synchronization operation builds on top of this two operations and is able to find unsynced HeaderSets in the source Recorder. Thoses unsynced HeaderSets are then played back from the source Recorder and recorded in the destination Recorder.

The resol-vbus module includes the following sub-classes of the abstract Recorder class:

  • FileSystemRecorder
  • DLxRecorder

Customizers

A Customizer provides functionality to transfer a set of configuration values from or to a device.

The resol-vbus module includes the following sub-classes of the abstract Customizer class:

  • ConnectionCustomizer

DataSources

The resol-vbus module includes the following sub-classes of the abstract DataSource class:

  • SerialDataSource
  • TcpDataSource

DataSourceProviders

The resol-vbus module includes the following sub-classes of the abstract DataSourceProvider class:

  • SerialDataSourceProvider
  • TcpDataSourceProvider