Configuration | |||
  |
On the "EnOcean inputs" the objects are configured, which are processed as inputs. Typical devices for inputs are motion sensors , switches, window contacts, etc.. |
  | |
  | |||
  | Name |
Give the input a name. The name improves the clarity and enables you to reference this input using the name in another place, for example in the operations or time-delays. |
  |
  | Location |
Assign the input to a room. This allows you to quickly navigate between the different inputs of the SmartHome server by using system telephone or app. |
|
  | Type |
The type determines the behavior of the object. |
|
  | Datapointtype |
The datapoint type determines the range of values and possibly the unit that is used in the visualization. |
|
  | Settings |
You can use the |
|
  | Delete |
By pushing the delete button, you remove the input from configuration. |
|
  | Product-Signature |
Here you can select the type of sensor. If your device is not listed, you can try it with the setting "Universal switch". |
|
  | Receive-ID |
Every telegram, sent by the sensor, has a unique ID. This ID has to be entered
here, so that the Smart Home Server can evaluate the received data. |
|
  | Channel |
Various sensors, e.g. the universal switches, have more than one channels. If no input field appears, no channel setting is required for the selected sensor. |
|
  | Invert |
Each binary input can be inverted. |
|
  | Initial Value |
From the start of the system until the reception of the first date the
smarthome server treats the status of the input as undefined.
This has consequences for the gates. Gates with an undefined input are not
executed. |
|
FAQs | |||
  |
Where can I get the ID of the sensor that needs to be configured under "Receive ID" ? |
  | |
  | |||
  | |||
  |