Components > Driver

Driver for the connection of the Smart EnOcean Gateway (DC-GW / EO-IP) of DigitalConcepts.

Enocean refers to a manufacturer-independent standard for battery-free wireless sensor technology used primarily in the monitoring and control of home and building technology.

Data points of the component

Name	Type	function
Debug Messages	Output	The diagnostic information is displayed there, linked to the [Signal] input of the log window.
Received Telegrams	Output	Output of received telegrams in text form (JSON).
Dynamic	Folder	The Folder Dynamic displays the data points for the available devices.
Send-Results	Output	Output of the response telegrams when sending commands (JSON).
Driver On/Off	Bidirectional	Driver on or off.
Connection State	Output	Returns the status of the connection.

Properties

Name	Standard	function
Devices	0	In the channel editor "Devices", the individual devices can be imported from the gateway.
Connection	None ...	Opens the editor for setting the EnOcean gateway (currently only the gateway from DigitalConcepts). The IP address of the gateway and the port (8080 by default) user name and password are entered here. In the gateway, a password for Admin and for User (password: user) must be entered in the API description so that both areas can be called up in the EisBaer. Only Admin + Pw is entered in EisBaer itself.
Driver On/Off		Driver on or off.

In the folder "Dynamic" a subfolder is created for the individual devices.

Below the device folders, there is a subfolder for each function group (different from device to device, depending on which "profile" (EEP) is supported) and there the shared properties for the function group specific data points. Within the polar bear no management of the data points belonging to an EEP is carried out. Instead, the information provided by the gateway (function groups and their data points) is used to create the SPs.

Below "FunctionGroup 1" are located e.g. one wall switch each 4 SPs for the 4 buttons. In this case, buttonA0 outputs the state of the A0 button. In this special case, the respective string ("pressed" or "released") is not output, but the Boolean interpretation (true / false). "ButtonA0 pressed" is triggered with true every time the button is pressed. Similarly, this applies to "buttonA0 released". Each data point also has an SP with the suffix "ValueDescription" - Here the possible outputs (which are provided by the gateway or which the gateway expects for commands) are output. In this case, the strings would be "pressed" and "released" - but as already said, the polar bear interprets these strings in this case and outputs true or false on the SP "buttonA0".

In the case of a switchable socket with support for EEP D2-01-09, 7 subgroups are created for the various "function groups".

In FG1 is the most important data point for switching the socket. In this case, this data point is called "dimValue" and can process values from 0 to 100 (as%) according to its "ValueDescription". For switching off, a 0 can be sent here and a 100 for switching it on.

In FG7 there are 2 more interesting data points showing the energy consumed and the current power. These values are sent cyclically by the gateway. But it is also possible to explicitly trigger the values via the FG6. Here is the data point "query". Its ValueDescription tells you that it supports the following values as inputs: power, energy, and status. So if the string "power" is sent to this SP, this triggers the message of the current performance.

About the other function groups u.a. Set the minimum / maximum automatic message interval for power and energy or reset the energy counter.

The "Holter heating thermostat (EEP = A5-20-04)" reports various measured values and the status via FG1. Measurements can be triggered via FG2, the valve can be manually controlled and the setpoint temperature can be set.

It should be noted that the device must have at least once a "Valve" command received before, for example. a "temperatureSetpoint" command is accepted. For specific questions, the documentation of the device manufacturer should be consulted.