Automation Driver Definition#

This object represents the automation driver, which consists of an automation protocol defining the version of the supported protocol (e.g.: Bluetooth 4.1) as well as the definition of all available commands, events and properties.

Being a versioned object, it is possible to have multiple driver definition versions running at the same time. A possible scenario for this feature is similar as to having an integration running for a specific set of machines, and another group of the same machine types running a new version for testing purposes for new features/bug fixes.

A driver definition is composed of the following elements:

• Properties
• Events
• Commands

This object should contain all the necessary definitions to address all necessary characteristics of the machine interface in order to fully support the automation integration. Depending on the selected protocol and version, additional attributes can be defined for each of the object entities.

If a new version of the protocol is required for some reason (new features, bug fix, etc), it is mandatory to create a new version for this change to be possible. The reason behind this, is to allow a rollback if the productive tests fail.