Updated external content (Jenkins build 360)

pull/1569/head
openHAB Build Server 2021-04-04 04:45:33 +00:00
parent eebe6fb592
commit f09954d353
13 changed files with 25 additions and 26 deletions

View File

@ -18,6 +18,8 @@ This binding allows to monitor and control Zehnder ComfoAir serial controlled ve
Though the binding is developed based on the protocol description for Zehnder ComfoAir devices it should also work for mostly identical systems from different manufacturers, like StorkAir WHR930, Wernig G90-380 and Paul Santos 370 DC.
It was also successfully tested on a Wernig G90-160.
**NOTE:** This binding does not work with the ComfoAir Q-series (e.g. Q350 or Q450). These ventilation units use a CAN bus for communication and a different protocol.
### Limitations
* Either the ComfoAir binding or the CCEase Comfocontrol can be active, but not together.

View File

@ -29,7 +29,7 @@ First of all you have to configure an EnOcean transceiver (gateway).
A directly connected USB300 can be auto discovered, an EnOceanPi has to be added manually to openHAB.
Both gateways are represented by an _EnOcean gateway_ in openHAB.
If you want to place the gateway for better reception apart from your openHAB server, you can forward its serial messages over TCP/IP (_ser2net_).
In this case you have to define the path to the gateway like this rfc2217://x.x.x.x:3001.
In this case you have to define the path to the gateway like this rfc2217://x.x.x.x:3001. When using _ser2net_ make sure to use _telnet_ instead of _raw_ in the _set2net_ config file.
If everything is running fine you should see the _base id_ of your gateway in the properties of your bridge.
Another way to improve sending and reception reliability is to setup a wired connection.

View File

@ -77,6 +77,7 @@ Please see the example below.
|-------------------------------------------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
| bridge | N.A | bridge does not expose any channel |
| gateway | status | status of your Tahoma gateway |
| gateway | scenarios | used to run the scenarios defined in the cloud portal |
| gate | gate_command | used for controlling your gate (open, close, stop, pedestrian) |
| gate | gate_state | get state of your gate (open, closed, pedestrian) |
| gate | gate_position | get position (0-100%) of your gate (where supported) |
@ -135,6 +136,9 @@ Please see the example below.
| myfox camera | shutter | controlling of the camera shutter |
| myfox alarm | myfox_alarm_command | used for sending commands to Somfy Myfox alarm device |
To run a scenario inside a rule for example, the ID of the scenario will be required.
You can list all the scenarios IDs with the following console command: `somfytahoma <bridgeUID> scenarios`.
### Remarks
All things which have a RSSI (relative received signal) state, expose a channel "rssi".

View File

@ -59,7 +59,6 @@
</parameter>
<parameter name="portNumber" type="integer" required="true">
<description>Port number of the network proxy</description>
<required>false</required>
<label>Port</label>
</parameter>
<parameter name="interval" type="decimal" required="true">

View File

@ -26,7 +26,6 @@
<parameter name="precision" type="integer" min="0" max="3">
<label>Sensor Precision</label>
<description>Sensor precision after floating point.</description>
<required>false</required>
<default>3</default>
</parameter>

View File

@ -27,20 +27,18 @@
<representation-property>ownId</representation-property>
<config-description>
<parameter name="shutterRun" type="text">
<parameter name="shutterRun" type="text" required="true">
<label>Shutter Run</label>
<description>Time (in ms) to go from max position (e.g. CLOSED) to the other position (e.g. OPEN). Example: 12000
(=12sec).
Use AUTO (default) to calibrate the shutter automatically (UP->DOWN->Position%) the first time a Position
command (%)
is sent.</description>
<required>true</required>
<default>AUTO</default>
</parameter>
<parameter name="where" type="text">
<parameter name="where" type="text" required="true">
<label>OpenWebNet Device Address (where)</label>
<description>It identifies one ZigBee device. Example: 765432101#9</description>
<required>true</required>
</parameter>
</config-description>

View File

@ -14,7 +14,6 @@
<parameter name="deviceId" type="text" required="true">
<label>MAC Address</label>
<description>The MAC address identifies a specific S20 Socket.</description>
<required>true</required>
</parameter>
</config-description>

View File

@ -27,7 +27,6 @@
<label>IP150 Password</label>
<description>Password for accessing IP150</description>
<context>password</context>
<required>true</required>
</parameter>
<parameter name="pcPassword" type="text" required="true">
<label>PC Password</label>
@ -39,7 +38,6 @@
<label>Network Address</label>
<description>IP address or host name of IP150</description>
<context>network-address</context>
<required>true</required>
</parameter>
<parameter name="port" type="integer" required="true">
<label>Port</label>

View File

@ -10,10 +10,9 @@
STM.</description>
<config-description>
<parameter name="port" type="text">
<parameter name="port" type="text" required="true">
<label>Serial Port</label>
<description>Serial Port the PHC modules are connected to</description>
<required>true</required>
<context>serial-port</context>
<limitToOptions>false</limitToOptions>
</parameter>
@ -35,10 +34,9 @@
</channel-groups>
<config-description>
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5">
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5" required="true">
<label>Address</label>
<description>Address of the module as binary, like the DIP switches.</description>
<required>true</required>
</parameter>
</config-description>
@ -58,10 +56,9 @@
</channel-groups>
<config-description>
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5">
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5" required="true">
<label>Address</label>
<description>Address of the module as binary, like the DIP switches.</description>
<required>true</required>
</parameter>
</config-description>
</thing-type>
@ -80,10 +77,9 @@
</channel-groups>
<config-description>
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5">
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5" required="true">
<label>Address</label>
<description>Address of the module as binary, like the DIP switches.</description>
<required>true</required>
</parameter>
<parameter name="upDownTime1" type="integer" min="1" max="65535">
<advanced>true</advanced>
@ -125,10 +121,9 @@
</channel-groups>
<config-description>
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5">
<parameter name="address" type="text" pattern="[0-1]{5}" min="5" max="5" required="true">
<label>Address</label>
<description>Address of the module as binary, like the DIP switches.</description>
<required>true</required>
</parameter>
<parameter name="dimTime1" type="integer" min="1" max="255">
<advanced>true</advanced>

View File

@ -72,10 +72,9 @@
<label>Text Value</label>
<state readOnly="true"/>
<config-description>
<parameter name="property" type="text">
<parameter name="property" type="text" required="true">
<label>Property</label>
<description>The Property of the Device.</description>
<required>true</required>
</parameter>
</config-description>
</channel-type>
@ -85,10 +84,9 @@
<label>Number Value</label>
<state readOnly="true"/>
<config-description>
<parameter name="property" type="text">
<parameter name="property" type="text" required="true">
<label>Property</label>
<description>The Property of the Device.</description>
<required>true</required>
</parameter>
</config-description>
</channel-type>

View File

@ -36,12 +36,11 @@
</channels>
<config-description>
<parameter name="port" type="text">
<parameter name="port" type="text" required="true">
<label>Serial Port</label>
<context>serial-port</context>
<limitToOptions>false</limitToOptions>
<description>Serial Port the RME Rain Manager is connected to</description>
<required>true</required>
</parameter>
</config-description>
</thing-type>

View File

@ -389,4 +389,11 @@
<description>Operating mode of the Somfy thermostatic valve</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="scenarios">
<item-type>String</item-type>
<label>Scenarios</label>
<description>The scenarios defined in the cloud portal</description>
<autoUpdatePolicy>recommend</autoUpdatePolicy>
</channel-type>
</thing:thing-descriptions>

View File

@ -11,6 +11,7 @@
<label>Somfy Tahoma Gateway</label>
<channels>
<channel id="status" typeId="status"></channel>
<channel id="scenarios" typeId="scenarios"></channel>
</channels>
<representation-property>id</representation-property>
<config-description-ref uri="thing-type:somfytahoma:gateway"/>