Updated external content (Jenkins build 1370)
openHAB Build Server
parent
fc95b8a9f5
commit
aeb09fb94d
File diff suppressed because one or more lines are too long
|
|
@ -79,11 +79,12 @@ None
|
|||
|
||||
### Zone
|
||||
|
||||
| Channel Type ID | Item Type | Description |
|
||||
|-------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Temperature | Number | Allows for viewing the current actual temperature of the zone. |
|
||||
| SetPointStatus | String | Allows for viewing the current set point mode of the zone. |
|
||||
| SetPoint | Number | Allows for viewing and permanently overriding the temperature set point of the zone. Sending 0 cancels any active set point overrides. |
|
||||
| Channel Type ID | Item Type | Description |
|
||||
|-----------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Temperature | Number:Temperature | Allows for viewing the current actual temperature of the zone. |
|
||||
| SetPointStatus | String | Allows for viewing the current set point mode of the zone. |
|
||||
| SetPoint | Number:Temperature | Allows for viewing and permanently overriding the temperature set point of the zone. Sending 0 cancels any active set point overrides. |
|
||||
|
|
||||
|
||||
## Full Example
|
||||
|
||||
|
|
@ -104,9 +105,9 @@ Bridge evohome:account:your_account_alias [ username="your_user_name", password=
|
|||
String DemoMode { channel="evohome:display:your_account_alias:your_display_alias:SystemMode" }
|
||||
|
||||
// evohome Heatingzone
|
||||
Number DemoZoneTemperature { channel="evohome:heatingzone:your_account_alias:your_zone_alias:Temperature" }
|
||||
String DemoZoneSetPointStatus { channel="evohome:heatingzone:your_account_alias:your_zone_alias:SetPointStatus" }
|
||||
Number DemoZoneSetPoint { channel="evohome:heatingzone:your_account_alias:your_zone_alias:SetPoint" }
|
||||
Number:Temperature DemoZoneTemperature { channel="evohome:heatingzone:your_account_alias:your_zone_alias:Temperature" }
|
||||
String DemoZoneSetPointStatus { channel="evohome:heatingzone:your_account_alias:your_zone_alias:SetPointStatus" }
|
||||
Number:Temperature DemoZoneSetPoint { channel="evohome:heatingzone:your_account_alias:your_zone_alias:SetPoint" }
|
||||
```
|
||||
|
||||
### demo.sitemap
|
||||
|
|
|
|||
|
|
@ -52,6 +52,10 @@ If you only configured password authentication for your device, the `user` param
|
|||
The second credential parameter is `password`, which is mandatory.
|
||||
For security reasons it is highly recommended to set both, username and password.
|
||||
|
||||
Another optional and advanced configuration parameter is `timeout`.
|
||||
This parameter applies to all requests to the device (SOAP requests, phonebook retrieval, call lists, ...).
|
||||
It only needs to be changed from the default value of `5` seconds when the remote device is unexpectedly slow and does not respond within that time.
|
||||
|
||||
### `fritzbox`
|
||||
|
||||
The `fritzbox` devices can give additional informations in dedicated channels, controlled
|
||||
|
|
@ -84,12 +88,19 @@ If the `PHONEBOOK` profile shall be used, it is necessary to retrieve the phoneb
|
|||
The `phonebookInterval` is used to set the refresh cycle for phonebooks.
|
||||
It defaults to 600 seconds, and it can be set to 0 if phonebooks are not used.
|
||||
|
||||
Some parameters (e.g. `macOnline`, `wanBlockIPs`) accept lists.
|
||||
Some parameters (e.g. `macOnline`, `wanBlockIPs`) accept lists.
|
||||
List items are configured one per line in the UI, or are comma separated values when using textual config.
|
||||
These parameters that accept list can also contain comments.
|
||||
Comments are separated from the value with a '#' (e.g. `192.168.0.77 # Daughter's iPhone`).
|
||||
The full string is used for the channel label.
|
||||
|
||||
Two more advanced parameters are used for the backup thing action.
|
||||
The `backupDirectory` is the directory where the backup files are stored.
|
||||
The default value is the userdata directory.
|
||||
The `backupPassword` is used to encrypt the backup file.
|
||||
This is equivalent to setting a password in the UI.
|
||||
If no password is given, the user password (parameter `password`) is used.
|
||||
|
||||
### `subdevice`, `subdeviceLan`
|
||||
|
||||
Additional informations (i.e. channels) are available in subdevices of the bridge.
|
||||
|
|
@ -131,18 +142,17 @@ The call-types are the same as provided by the FritzBox, i.e. `1` (inbound), `2`
|
|||
|
||||
### LAN `subdeviceLan` channels
|
||||
|
||||
| channel | item-type | advanced | description |
|
||||
|----------------------------|---------------------------|:--------:|----------------------------------------------------------------|
|
||||
| `wifi24GHzEnable` | `Switch` | | Enable/Disable the 2.4 GHz WiFi device. |
|
||||
| `wifi5GHzEnable` | `Switch` | | Enable/Disable the 5.0 GHz WiFi device. |
|
||||
| `wifiGuestEnable` | `Switch` | | Enable/Disable the guest WiFi. |
|
||||
| `macOnline` | `Switch` | x | Online status of the device with the given MAC |
|
||||
| `macIP` | `String` | x | IP of the device with the given MAC |
|
||||
| `macSignalStrength1` | `Number` | x | Wifi Signal Strength of the device with the given MAC. This is set in case the Device is connected to 2.4Ghz |
|
||||
| `macSpeed1` | `Number:DataTransferRate` | x | Wifi Speed of the device with the given MAC. This is set in case the Device is connected to 2.4Ghz |
|
||||
| `macSignalStrength2` | `Number` | x | Wifi Signal Strength of the device with the given MAC. This is set in case the Device is connected to 5Ghz |
|
||||
| `macSpeed2` | `Number:DataTransferRate` | x | Wifi Speed of the device with the given MAC. This is set in case the Device is connected to 5Ghz |
|
||||
|
||||
| channel | item-type | advanced | description |
|
||||
|----------------------|---------------------------|:--------:|--------------------------------------------------------------------------------------------------------------|
|
||||
| `wifi24GHzEnable` | `Switch` | | Enable/Disable the 2.4 GHz WiFi device. |
|
||||
| `wifi5GHzEnable` | `Switch` | | Enable/Disable the 5.0 GHz WiFi device. |
|
||||
| `wifiGuestEnable` | `Switch` | | Enable/Disable the guest WiFi. |
|
||||
| `macOnline` | `Switch` | x | Online status of the device with the given MAC |
|
||||
| `macOnlineIpAddress` | `String` | x | IP of the MAC (uses same parameter as `macOnline`) |
|
||||
| `macSignalStrength1` | `Number` | x | Wifi Signal Strength of the device with the given MAC. This is set in case the Device is connected to 2.4Ghz |
|
||||
| `macSpeed1` | `Number:DataTransferRate` | x | Wifi Speed of the device with the given MAC. This is set in case the Device is connected to 2.4Ghz |
|
||||
| `macSignalStrength2` | `Number` | x | Wifi Signal Strength of the device with the given MAC. This is set in case the Device is connected to 5Ghz |
|
||||
| `macSpeed2` | `Number:DataTransferRate` | x | Wifi Speed of the device with the given MAC. This is set in case the Device is connected to 5Ghz |
|
||||
Older FritzBox devices may not support 5 GHz WiFi.
|
||||
In this case you have to use the `wifi5GHzEnable` channel for switching the guest WiFi.
|
||||
|
||||
|
|
@ -154,34 +164,36 @@ In this case you have to use the `wifi5GHzEnable` channel for switching the gues
|
|||
| `pppUptime` | `Number:Time` | | Uptime (if using PPP) |
|
||||
| `wanConnectionStatus` | `String` | | Connection Status |
|
||||
| `wanPppConnectionStatus` | `String` | | Connection Status (if using PPP) |
|
||||
| `wanIpAddress` | `String` | x | WAN IP Address |
|
||||
| `wanPppIpAddress` | `String` | x | WAN IP Address (if using PPP) |
|
||||
| `wanIpAddress` | `String` | x | WAN IP Address |
|
||||
| `wanPppIpAddress` | `String` | x | WAN IP Address (if using PPP) |
|
||||
|
||||
### WAN `subdevice` channels
|
||||
|
||||
| channel | item-type | advanced | description |
|
||||
|----------------------------|---------------------------|:--------:|----------------------------------------------------------------|
|
||||
| `dslCRCErrors` | `Number:Dimensionless` | x | DSL CRC Errors |
|
||||
| `dslDownstreamMaxRate` | `Number:DataTransferRate` | x | DSL Max Downstream Rate |
|
||||
| `dslDownstreamCurrRate` | `Number:DataTransferRate` | x | DSL Curr. Downstream Rate |
|
||||
| `dslDownstreamNoiseMargin` | `Number:Dimensionless` | x | DSL Downstream Noise Margin |
|
||||
| `dslDownstreamAttenuation` | `Number:Dimensionless` | x | DSL Downstream Attenuation |
|
||||
| `dslCRCErrors` | `Number:Dimensionless` | x | DSL CRC Errors |
|
||||
| `dslDownstreamMaxRate` | `Number:DataTransferRate` | x | DSL Max Downstream Rate |
|
||||
| `dslDownstreamCurrRate` | `Number:DataTransferRate` | x | DSL Curr. Downstream Rate |
|
||||
| `dslDownstreamNoiseMargin` | `Number:Dimensionless` | x | DSL Downstream Noise Margin |
|
||||
| `dslDownstreamAttenuation` | `Number:Dimensionless` | x | DSL Downstream Attenuation |
|
||||
| `dslEnable` | `Switch` | | DSL Enable |
|
||||
| `dslFECErrors` | `Number:Dimensionless` | x | DSL FEC Errors |
|
||||
| `dslHECErrors` | `Number:Dimensionless` | x | DSL HEC Errors |
|
||||
| `dslStatus` | `Switch` | | DSL Status |
|
||||
| `dslUpstreamMaxRate` | `Number:DataTransferRate` | x | DSL Max Upstream Rate |
|
||||
| `dslUpstreamCurrRate` | `Number:DataTransferRate` | x | DSL Curr. Upstream Rate |
|
||||
| `dslUpstreamNoiseMargin` | `Number:Dimensionless` | x | DSL Upstream Noise Margin |
|
||||
| `dslUpstreamAttenuation` | `Number:Dimensionless` | x | DSL Upstream Attenuation |
|
||||
| `wanAccessType` | `String` | x | Access Type |
|
||||
| `wanMaxDownstreamRate` | `Number:DataTransferRate` | x | Max. Downstream Rate |
|
||||
| `wanMaxUpstreamRate` | `Number:DataTransferRate` | x | Max. Upstream Rate |
|
||||
| `wanPhysicalLinkStatus` | `String` | x | Link Status |
|
||||
| `wanTotalBytesReceived` | `Number:DataAmount` | x | Total Bytes Received |
|
||||
| `wanTotalBytesSent` | `Number:DataAmount` | x | Total Bytes Sent |
|
||||
| `dslFECErrors` | `Number:Dimensionless` | x | DSL FEC Errors |
|
||||
| `dslHECErrors` | `Number:Dimensionless` | x | DSL HEC Errors |
|
||||
| `dslStatus` | `String` | | DSL Status |
|
||||
| `dslUpstreamMaxRate` | `Number:DataTransferRate` | x | DSL Max Upstream Rate |
|
||||
| `dslUpstreamCurrRate` | `Number:DataTransferRate` | x | DSL Curr. Upstream Rate |
|
||||
| `dslUpstreamNoiseMargin` | `Number:Dimensionless` | x | DSL Upstream Noise Margin |
|
||||
| `dslUpstreamAttenuation` | `Number:Dimensionless` | x | DSL Upstream Attenuation |
|
||||
| `wanAccessType` | `String` | x | Access Type |
|
||||
| `wanMaxDownstreamRate` | `Number:DataTransferRate` | x | Max. Downstream Rate |
|
||||
| `wanMaxUpstreamRate` | `Number:DataTransferRate` | x | Max. Upstream Rate |
|
||||
| `wanCurrentDownstreamRate` | `Number:DataTransferRate` | x | Current Downstream Rate (average last 15 seconds) |
|
||||
| `wanCurrentUpstreamRate` | `Number:DataTransferRate` | x | Current Upstream Rate (average last 15 seconds) |
|
||||
| `wanPhysicalLinkStatus` | `String` | x | Link Status |
|
||||
| `wanTotalBytesReceived` | `Number:DataAmount` | x | Total Bytes Received |
|
||||
| `wanTotalBytesSent` | `Number:DataAmount` | x | Total Bytes Sent |
|
||||
|
||||
**Note:** AVM Fritzbox devices use 4-byte-unsigned-integers for `wanTotalBytesReceived` and `wanTotalBytesSent`, because of that the counters are reset after around 4GB data.
|
||||
**Note:** AVM FritzBox devices use 4-byte-unsigned-integers for `wanTotalBytesReceived` and `wanTotalBytesSent`, because of that the counters are reset after around 4GB data.
|
||||
|
||||
## `PHONEBOOK` Profile
|
||||
|
||||
|
|
@ -193,12 +205,15 @@ If only a specific phonebook from the device should be used, this can be specifi
|
|||
The default is to use all available phonebooks from the specified thing.
|
||||
In case the format of the number in the phonebook and the format of the number from the channel are different (e.g. regarding country prefixes), the `matchCount` parameter can be used.
|
||||
The configured `matchCount` is counted from the right end and denotes the number of matching characters needed to consider this number as matching.
|
||||
Negative `matchCount` values skip digits from the left (e.g. if the input number is `033998005671` a `matchCount` of `-1` would remove the leading `0` ).
|
||||
A `matchCount` of `0` is considered as "match everything".
|
||||
Matching is done on normalized versions of the numbers that have all characters except digits, '+' and '*' removed.
|
||||
There is an optional configuration parameter called `phoneNumberIndex` that should be used when linking to a channel with item type `StringListType` (like `Call` in the example below), which determines which number to be picked, i.e. to or from.
|
||||
|
||||
## Rule Action
|
||||
|
||||
### Phonebook lookup
|
||||
|
||||
The phonebooks of a `fritzbox` thing can be used to lookup a number from rules via a thing action:
|
||||
|
||||
`String name = phonebookLookup(String number, String phonebook, int matchCount)`
|
||||
|
|
@ -206,17 +221,36 @@ The phonebooks of a `fritzbox` thing can be used to lookup a number from rules v
|
|||
`phonebook` and `matchCount` are optional parameters.
|
||||
You can omit one or both of these parameters.
|
||||
The configured `matchCount` is counted from the right end and denotes the number of matching characters needed to consider this number as matching.
|
||||
A `matchCount` of `0` is considered as "match everything" and is used as default if no other value is given.
|
||||
Negative `matchCount` values skip digits from the left (e.g. if the input number is `033998005671` a `matchCount` of `-1` would remove the leading `0` ).
|
||||
A `matchCount` of `0` is considered as "match everything" and is used as default if no other value is given.
|
||||
As in the phonebook profile, matching is done on normalized versions of the numbers that have all characters except digits, '+' and '*' removed.
|
||||
The return value is either the phonebook entry (if found) or the input number.
|
||||
|
||||
Example (use all phonebooks, match 5 digits from right):
|
||||
|
||||
```
|
||||
```java
|
||||
val tr064Actions = getActions("tr064","tr064:fritzbox:2a28aee1ee")
|
||||
val result = tr064Actions.phonebookLookup("49157712341234", 5)
|
||||
```
|
||||
|
||||
### Fritz!Box Backup
|
||||
|
||||
The `fritzbox` things can create configuration backups of the Fritz!Box.
|
||||
|
||||
The default configuration of the Fritz!Boxes requires 2-factor-authentication for creating backups.
|
||||
If you see a `Failed to get configuration backup URL: HTTP-Response-Code 500 (Internal Server Error), SOAP-Fault: 866 (second factor authentication required)` warning, you need to disable 2-actor authentication.
|
||||
But beware: depending on your configuration this might be a security issue.
|
||||
The setting can be found under "System -> FRITZ!Box Users -> Login to the Home Network -> Confirm".
|
||||
|
||||
When executed, the action requests a backup file with the given password in the configured path.
|
||||
The backup file is names as `ThingFriendlyName dd.mm.yyyy HHMM.export` (e.g. `My FritzBox 18.06.2021 1720.export`).
|
||||
Files with the same name will be overwritten, so make sure that you trigger the rules at different times if your devices have the same friendly name.
|
||||
|
||||
```java
|
||||
val tr064Actions = getActions("tr064","tr064:fritzbox:2a28aee1ee")
|
||||
tr064Actions.createConfigurationBackup()
|
||||
```
|
||||
|
||||
## A note on textual configuration
|
||||
|
||||
Textual configuration through a `.things` file is possible but, at present, strongly discouraged because it is significantly more error-prone
|
||||
|
|
@ -244,7 +278,6 @@ The channel are automatically generated and it is simpler to use the Main User I
|
|||
```
|
||||
Switch PresXX "[%s]" {channel="tr064:subdeviceLan:rootuid:LAN:macOnline_XX_3AXX_3AXX_3AXX_3AXX_3AXX"}
|
||||
Switch PresYY "[%s]" {channel="tr064:subdeviceLan:rootuid:LAN:macOnline_YY_3AYY_3AYY_3AYY_3AYY_3AYY"}
|
||||
|
||||
```
|
||||
|
||||
Example `*.items` file using the `PHONEBOOK` profile for storing the name of a caller in an item. it matches 8 digits from the right of the "from" number (note the escaping of `:` to `_3A`):
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ The following table summarises the channels available for the ZW164 -:
|
|||
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|
||||
|--------------|------------|--------------|----------|-----------|
|
||||
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
|
||||
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
|
||||
| Alarm (burglar) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Sound tone to play | sound_tone_play | sound_tone_play | | |
|
||||
| Sound volume | sound_volume | sound_volume | | |
|
||||
| Alarm 1 | alarm_general1 | alarm_general | Alarm | Switch |
|
||||
|
|
@ -104,9 +104,9 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| ON | Alarm |
|
||||
|
||||
### Alarm (burglar)
|
||||
Indicates if the burglar alarm is triggered.
|
||||
Indicates if the tamper alarm is triggered.
|
||||
|
||||
The ```alarm_burglar``` channel is of type ```alarm_burglar``` and supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_tamper``` channel is of type ```alarm_tamper``` and supports the ```Switch``` item. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
|
|||
|
|
@ -55,6 +55,7 @@ The following table summarises the channels available for the ZWA009 -:
|
|||
| Sensor (relative humidity) | sensor_relhumidity | sensor_relhumidity | Humidity | Number |
|
||||
| Alarm | alarm_general | alarm_general | Alarm | Switch |
|
||||
| Alarm (battery) | alarm_battery | alarm_battery | LowBattery | Switch |
|
||||
| Alarm (heat) | alarm_heat | alarm_heat | Fire | Switch |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
||||
### Binary Sensor
|
||||
|
|
@ -110,6 +111,20 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Alarm (heat)
|
||||
Alarm when thresholds of paramaters 5 & 6 are exceeded
|
||||
|
||||
Indicates if a heat alarm is triggered.
|
||||
|
||||
The ```alarm_heat``` channel is of type ```alarm_heat``` and supports the ```Switch``` item and is in the ```Fire``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
| Value | Label |
|
||||
|-------|-----------|
|
||||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Battery Level
|
||||
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
|
||||
|
||||
|
|
|
|||
|
|
@ -49,8 +49,9 @@ The following table summarises the channels available for the ZWA024 -:
|
|||
| Sensor (temperature) | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
|
||||
| Sensor (relative humidity) | sensor_relhumidity | sensor_relhumidity | Humidity | Number |
|
||||
| Alarm (system) | alarm_system | alarm_system | | Switch |
|
||||
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
|
||||
| Alarm (burglar) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
|
||||
| Alarm (battery) | alarm_battery | alarm_battery | LowBattery | Switch |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
||||
### Binary Sensor
|
||||
|
|
@ -98,9 +99,9 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| ON | Alarm |
|
||||
|
||||
### Alarm (burglar)
|
||||
Indicates if the burglar alarm is triggered.
|
||||
Indicates if the tamper alarm is triggered.
|
||||
|
||||
The ```alarm_burglar``` channel is of type ```alarm_burglar``` and supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_tamper``` channel is of type ```alarm_tamper``` and supports the ```Switch``` item. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
@ -121,6 +122,20 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Alarm (battery)
|
||||
Triggers REPLACE\_BATTERY\_SOON (according to paramter 39), & REPLACE\_BATTERY\_NOW (battery below 2.0V)
|
||||
|
||||
Indicates if the low battery alarm is triggered.
|
||||
|
||||
The ```alarm_battery``` channel is of type ```alarm_battery``` and supports the ```Switch``` item and is in the ```LowBattery``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
| Value | Label |
|
||||
|-------|-----------|
|
||||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Battery Level
|
||||
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ The following table summarises the channels available for the DWZWAVE25 -:
|
|||
| Binary Sensor | sensor_binary | sensor_binary | | Switch |
|
||||
| Alarm (tamper) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Sensor (Binary) | sensor_door | sensor_door | Door | Contact |
|
||||
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
|
||||
| Alarm Battery Status | alarm_battery | alarm_battery | LowBattery | Switch |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
||||
### Binary Sensor
|
||||
|
|
@ -102,10 +102,10 @@ The following state translation is provided for this channel to the ```Contact``
|
|||
| OPEN | Open |
|
||||
| CLOSED | Closed |
|
||||
|
||||
### Alarm (power)
|
||||
Indicates if a power alarm is triggered.
|
||||
### Alarm Battery Status
|
||||
Indicates if the low battery alarm is triggered.
|
||||
|
||||
The ```alarm_power``` channel is of type ```alarm_power``` and supports the ```Switch``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_battery``` channel is of type ```alarm_battery``` and supports the ```Switch``` item and is in the ```LowBattery``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
|
|||
|
|
@ -25,11 +25,9 @@ The TILT-ZWAVE2.5-ECO does not permanently listen for messages sent from the con
|
|||
|
||||
### Inclusion Information
|
||||
|
||||
1. Start by placing the controller into inclusion mode.
|
||||
|
||||
2. Activate inclusion mode for the sensor by inserting the battery. When the inclusion process is complete the red LED will turn on for approximately 10 seconds and then it will go out. If the LED continues to flash, repeat the inclusion process.
|
||||
|
||||
3. Test the garage door sensor before mounting it. Hold the sensor in your hand. Flip the sensor upside-down and watch the LED while doing so. The LED will flash each time the position of the sensor is changed. If your Z- Wave network has a software interface you may verify that the messages from the sensor are being received each time the sensor is flipped.
|
||||
1. Start by placing the controller into inclusion mode.
|
||||
2. Activate inclusion mode for the sensor by inserting the battery. When the inclusion process is complete the red LED will turn on for approximately 10 seconds and then it will go out. If the LED continues to flash, repeat the inclusion process.
|
||||
3. Test the garage door sensor before mounting it. Hold the sensor in your hand. Flip the sensor upside-down and watch the LED while doing so. The LED will flash each time the position of the sensor is changed. If your Z- Wave network has a software interface you may verify that the messages from the sensor are being received each time the sensor is flipped.
|
||||
|
||||
If you need to repeat the inclusion process, repeat STEP ONE above, then for STEP TWO you will need to simply remove the cover of the sensor, remove the battery for 5 seconds, reinsert the battery, and replace the sensor cover. This will re-enter the sensor in inclusion mode.
|
||||
|
||||
|
|
@ -48,6 +46,10 @@ To save power, this sensor sleeps most of the time and is therefore not awake to
|
|||
|
||||
The sensor will wake up every so often and when the case is closed, it will send a Wake-Up Notification to allow the life line master node controller that the sensor is now available for any queued messages that the controller may have for the sensor. **The time between Wake-Up Notifications can be configured with the Wake-Up Notification command class to be between 1 hour and 1 week with interval steps of 200 seconds.**
|
||||
|
||||
### General Usage Information
|
||||
|
||||
|
||||
|
||||
## Channels
|
||||
|
||||
The following table summarises the channels available for the TILT-ZWAVE2.5-ECO -:
|
||||
|
|
@ -55,7 +57,7 @@ The following table summarises the channels available for the TILT-ZWAVE2.5-ECO
|
|||
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|
||||
|--------------|------------|--------------|----------|-----------|
|
||||
| Binary Sensor [Deprecated]| sensor_binary | sensor_binary | | Switch |
|
||||
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
|
||||
| Alarm Battery Status | alarm_battery | alarm_battery | LowBattery | Switch |
|
||||
| Alarm (access) | alarm_access | alarm_access | Door | Switch |
|
||||
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
|
||||
| Door State | sensor_door | sensor_door | Door | Contact |
|
||||
|
|
@ -76,10 +78,10 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
|
||||
**Note:** This channel is marked as deprecated so should not be used.
|
||||
|
||||
### Alarm (power)
|
||||
Indicates if a power alarm is triggered.
|
||||
### Alarm Battery Status
|
||||
Indicates if the low battery alarm is triggered.
|
||||
|
||||
The ```alarm_power``` channel is of type ```alarm_power``` and supports the ```Switch``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_battery``` channel is of type ```alarm_battery``` and supports the ```Switch``` item and is in the ```LowBattery``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,224 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Comet Z-Wave - ZWave
|
||||
---
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Comet Z-Wave Radator thermostat 700226
|
||||
This describes the Z-Wave device *Comet Z-Wave*, manufactured by *Eurotronics* with the thing type UID of ```eurotronic_cometzwave_00_000```.
|
||||
|
||||
The device is in the category of *Radiator Control*, defining Controls on radiators used to heat up rooms.
|
||||
|
||||
|
||||
|
||||
|
||||
The Comet Z-Wave supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
|
||||
|
||||
## Overview
|
||||
|
||||
Comet Z-Wave is an energy-saving radiator controller compatible with the Z-Wave wireless standard.
|
||||
|
||||
FLiRS (Frequently Listening Receiver Slave):
|
||||
|
||||
Comet Z-Wave uses the Z-Wave function FLiRS as a radiator thermostat. As a FLiRS device, the radiator thermostat reacts to incoming commands such as temperature changes with a particularly short latency period
|
||||
|
||||
### Inclusion Information
|
||||
|
||||
Put your primary Z-Wave controller in inclusion mode and press v or ^button to activate add mode. If Comet Z-Wave was added successfully, the LED display will show the receivedNode ID
|
||||
|
||||
### Exclusion Information
|
||||
|
||||
Please put your Z-Wave controller into the exclusion mode. Then press and hold the button in the battery compartment for 5 seconds until “LE” appears in the display
|
||||
|
||||
### General Usage Information
|
||||
|
||||
|
||||
|
||||
## Channels
|
||||
|
||||
The following table summarises the channels available for the Comet Z-Wave -:
|
||||
|
||||
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|
||||
|--------------|------------|--------------|----------|-----------|
|
||||
| Basic | basic_number | basic_number | | Number |
|
||||
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
|
||||
| Sensor (temperature) | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
|
||||
| Thermostat mode | thermostat_mode | thermostat_mode | Temperature | Number |
|
||||
|
||||
### Basic
|
||||
Basic class operation mode
|
||||
|
||||
|
||||
|
||||
The ```basic_number``` channel is of type ```basic_number``` and supports the ```Number``` item. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
### Dimmer
|
||||
The brightness channel allows to control the brightness of a light.
|
||||
It is also possible to switch the light on and off.
|
||||
|
||||
The ```switch_dimmer``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
|
||||
|
||||
### Sensor (temperature)
|
||||
Indicates the current temperature.
|
||||
|
||||
The ```sensor_temperature``` channel is of type ```sensor_temperature``` and supports the ```Number:Temperature``` item and is in the ```Temperature``` category.
|
||||
|
||||
### Thermostat mode
|
||||
Sets the thermostat.
|
||||
|
||||
The ```thermostat_mode``` channel is of type ```thermostat_mode``` and supports the ```Number``` item and is in the ```Temperature``` category.
|
||||
The following state translation is provided for this channel to the ```Number``` item type -:
|
||||
|
||||
| Value | Label |
|
||||
|-------|-----------|
|
||||
| 0 | Off |
|
||||
| 1 | Heat |
|
||||
| 2 | Cool |
|
||||
| 3 | Auto |
|
||||
| 4 | Aux Heat |
|
||||
| 5 | Resume |
|
||||
| 6 | Fan Only |
|
||||
| 7 | Furnace |
|
||||
| 8 | Dry Air |
|
||||
| 9 | Moist Air |
|
||||
| 10 | Auto Changeover |
|
||||
| 11 | Heat Economy |
|
||||
| 12 | Cool Economy |
|
||||
| 13 | Away |
|
||||
|
||||
|
||||
|
||||
## Device Configuration
|
||||
|
||||
The following table provides a summary of the 5 configuration parameters available in the Comet Z-Wave.
|
||||
Detailed information on each parameter can be found in the sections below.
|
||||
|
||||
| Param | Name | Description |
|
||||
|-------|-------|-------------|
|
||||
| 1 | LCD invert | LCD invert |
|
||||
| 2 | LCD Timeout | 0x05-0x1E Timeout after 5 seconds - 30 seconds default: 0x05 |
|
||||
| 4 | Battery status update | Battery status update frequence |
|
||||
| 5 | Actual temperature update | Temperature upddate policy |
|
||||
| 7 | Window open detection | Window-open detection sensitivity |
|
||||
|
||||
### Parameter 1: LCD invert
|
||||
|
||||
LCD invert
|
||||
0x00 LCD content normal
|
||||
|
||||
0x01 LCD mirrored content
|
||||
|
||||
default: 0x00 This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
The following option values may be configured, in addition to values in the range 0 to 1 -:
|
||||
|
||||
| Value | Description |
|
||||
|--------|-------------|
|
||||
| 0 | normal |
|
||||
| 1 | inverted |
|
||||
|
||||
The manufacturer defined default value is ```0``` (normal).
|
||||
|
||||
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 2: LCD Timeout
|
||||
|
||||
0x05-0x1E Timeout after 5 seconds - 30 seconds default: 0x05
|
||||
0x05-0x1E Timeout after 5 seconds - 30 seconds
|
||||
|
||||
default: 0x05
|
||||
Values in the range 0 to 0 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 4: Battery status update
|
||||
|
||||
Battery status update frequence
|
||||
0x00 Batteriestatus Send only event-controlled as system warning
|
||||
|
||||
0x01 Batteriestatus send 1x a day
|
||||
|
||||
default: 0x00
|
||||
Values in the range 0 to 0 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 5: Actual temperature update
|
||||
|
||||
Temperature upddate policy
|
||||
0x00 Send Actual-Temperature not automatically
|
||||
|
||||
0x01-0x32 0x32 With temperature difference of 0.1°C - 5.0°C
|
||||
|
||||
transfer actual temperature
|
||||
|
||||
default: 0x05 (When Delta = 0,5°C report
|
||||
Values in the range 0 to 0 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 7: Window open detection
|
||||
|
||||
Window-open detection sensitivity
|
||||
0x00 Deactivated
|
||||
|
||||
0x01 low sensitivity
|
||||
|
||||
0x02 medium sensitivity
|
||||
|
||||
0x03 high sensivity
|
||||
|
||||
default: 0x01 low sinsitive
|
||||
Values in the range 0 to 0 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
## Association Groups
|
||||
|
||||
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
|
||||
|
||||
The Comet Z-Wave supports 1 association group.
|
||||
|
||||
### Group 1: Lifeline
|
||||
|
||||
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
|
||||
Lifeline
|
||||
Should be set to your controller.
|
||||
|
||||
Association group 1 supports 1 node.
|
||||
|
||||
## Technical Information
|
||||
|
||||
### Endpoints
|
||||
|
||||
#### Endpoint 0
|
||||
|
||||
| Command Class | Comment |
|
||||
|---------------|---------|
|
||||
| COMMAND_CLASS_NO_OPERATION_V1| |
|
||||
| COMMAND_CLASS_BASIC_V1| |
|
||||
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
|
||||
| COMMAND_CLASS_SENSOR_MULTILEVEL_V10| |
|
||||
| COMMAND_CLASS_THERMOSTAT_MODE_V1| |
|
||||
|
||||
### Documentation Links
|
||||
|
||||
* [Image](https://opensmarthouse.org/zwavedatabase/1549/reference/Comet-Z-Wave-EN-2023-01-23.pdf)
|
||||
|
||||
---
|
||||
|
||||
Did you spot an error in the above definition or want to improve the content?
|
||||
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1549).
|
||||
|
|
@ -60,7 +60,8 @@ The following table summarises the channels available for the ZSE18 -:
|
|||
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|
||||
|--------------|------------|--------------|----------|-----------|
|
||||
| Binary Sensor | sensor_binary | sensor_binary | | Switch |
|
||||
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
|
||||
| Alarm (vibration) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Motion via Notification Report | alarm_motion | alarm_motion | Motion | Switch |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
||||
### Binary Sensor
|
||||
|
|
@ -75,10 +76,22 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| ON | Triggered |
|
||||
| OFF | Untriggered |
|
||||
|
||||
### Alarm (burglar)
|
||||
Indicates if the burglar alarm is triggered.
|
||||
### Alarm (vibration)
|
||||
Indicates if the tamper alarm is triggered.
|
||||
|
||||
The ```alarm_burglar``` channel is of type ```alarm_burglar``` and supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_tamper``` channel is of type ```alarm_tamper``` and supports the ```Switch``` item. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
| Value | Label |
|
||||
|-------|-----------|
|
||||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Motion via Notification Report
|
||||
Indicates if a motion alarm is triggered.
|
||||
|
||||
The ```alarm_motion``` channel is of type ```alarm_motion``` and supports the ```Switch``` item and is in the ```Motion``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
@ -96,7 +109,7 @@ This channel provides the battery level as a percentage and also reflects the lo
|
|||
|
||||
## Device Configuration
|
||||
|
||||
The following table provides a summary of the 7 configuration parameters available in the ZSE18.
|
||||
The following table provides a summary of the 8 configuration parameters available in the ZSE18.
|
||||
Detailed information on each parameter can be found in the sections below.
|
||||
|
||||
| Param | Name | Description |
|
||||
|
|
@ -106,6 +119,7 @@ Detailed information on each parameter can be found in the sections below.
|
|||
| 15 | reverse BASIC SET | 0: 255 motion, 0 timeout. 1: 0 motion, 255 timeout |
|
||||
| 17 | vibration sensor | 0=disabled, 1=enabled |
|
||||
| 18 | trigger interval | 3=6 seconds, 65535=65538 seconds (add 3 seconds to value set) |
|
||||
| 19 | Notification (Alarm) or Binary Reports | Enable or disable binary sensor reports when motion is detected. |
|
||||
| 20 | LED Indicator | 0=disabled, 1=enabled (default) |
|
||||
| 32 | Low Battery Alert | percent battery left |
|
||||
| | Wakeup Interval | Sets the interval at which the device will accept commands from the controller |
|
||||
|
|
@ -172,6 +186,17 @@ The manufacturer defined default value is ```27```.
|
|||
This parameter has the configuration ID ```config_18_2``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 19: Notification (Alarm) or Binary Reports
|
||||
|
||||
Enable or disable binary sensor reports when motion is detected.
|
||||
Values: 0 – don’t send binary sensor reports when motion is detected, send notification reports instead (default); 1 – send binary sensor reports when motion is detected instead of the notification report.
|
||||
Values in the range 0 to 1 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_19_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 20: LED Indicator
|
||||
|
||||
0=disabled, 1=enabled (default)
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ The following table summarises the channels available for the ZSE29 -:
|
|||
|--------------|------------|--------------|----------|-----------|
|
||||
| Binary Sensor | sensor_binary | sensor_binary | | Switch |
|
||||
| Alarm (motion) | alarm_motion | alarm_motion | Motion | Switch |
|
||||
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
|
||||
| Alarm Battery Status | alarm_battery | alarm_battery | LowBattery | Switch |
|
||||
| Alarm (tamper) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
||||
|
|
@ -78,10 +78,10 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Alarm (power)
|
||||
Indicates if a power alarm is triggered.
|
||||
### Alarm Battery Status
|
||||
Indicates if the low battery alarm is triggered.
|
||||
|
||||
The ```alarm_power``` channel is of type ```alarm_power``` and supports the ```Switch``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_battery``` channel is of type ```alarm_battery``` and supports the ```Switch``` item and is in the ```LowBattery``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ The following table summarises the channels available for the ZSE29 -:
|
|||
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|
||||
|--------------|------------|--------------|----------|-----------|
|
||||
| Sensor (luminance) | sensor_luminance | sensor_luminance | | Number |
|
||||
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
|
||||
| Alarm Battery Status | alarm_battery | alarm_battery | LowBattery | Switch |
|
||||
| Alarm (motion) | alarm_motion | alarm_motion | Motion | Switch |
|
||||
| Alarm (tamper) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
|
@ -61,10 +61,10 @@ Indicates the current light reading.
|
|||
|
||||
The ```sensor_luminance``` channel is of type ```sensor_luminance``` and supports the ```Number``` item. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
### Alarm (power)
|
||||
Indicates if a power alarm is triggered.
|
||||
### Alarm Battery Status
|
||||
Indicates if the low battery alarm is triggered.
|
||||
|
||||
The ```alarm_power``` channel is of type ```alarm_power``` and supports the ```Switch``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
The ```alarm_battery``` channel is of type ```alarm_battery``` and supports the ```Switch``` item and is in the ```LowBattery``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ The following table summarises the channels available for the ZSE43 -:
|
|||
|--------------|------------|--------------|----------|-----------|
|
||||
| Binary Sensor | sensor_binary | sensor_binary | | Switch |
|
||||
| Alarm (access) | alarm_access | alarm_access | Door | Switch |
|
||||
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
|
||||
| Alarm (vibration) | alarm_tamper | alarm_tamper | | Switch |
|
||||
| Door State | sensor_door | sensor_door | Door | Contact |
|
||||
| Battery Level | battery-level | system.battery_level | Battery | Number |
|
||||
|
||||
|
|
@ -86,10 +86,12 @@ The following state translation is provided for this channel to the ```Switch```
|
|||
| OFF | OK |
|
||||
| ON | Alarm |
|
||||
|
||||
### Alarm (burglar)
|
||||
Indicates if the burglar alarm is triggered.
|
||||
### Alarm (vibration)
|
||||
Vibration
|
||||
|
||||
The ```alarm_burglar``` channel is of type ```alarm_burglar``` and supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
|
||||
Indicates if the tamper alarm is triggered.
|
||||
|
||||
The ```alarm_tamper``` channel is of type ```alarm_tamper``` and supports the ```Switch``` item. This is a read only channel so will only be updated following state changes from the device.
|
||||
|
||||
The following state translation is provided for this channel to the ```Switch``` item type -:
|
||||
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ This channel provides the battery level as a percentage and also reflects the lo
|
|||
|
||||
## Device Configuration
|
||||
|
||||
The following table provides a summary of the 8 configuration parameters available in the ZSE44.
|
||||
The following table provides a summary of the 16 configuration parameters available in the ZSE44.
|
||||
Detailed information on each parameter can be found in the sections below.
|
||||
|
||||
| Param | Name | Description |
|
||||
|
|
@ -106,6 +106,14 @@ Detailed information on each parameter can be found in the sections below.
|
|||
| 2 | Low Battery | When the sensor should report low battery |
|
||||
| 3 | Temperature Reporting Threshold | Sensor will send a new temperature report if difference exceeds this threshold |
|
||||
| 4 | Humidity Reporting Threshold | Sensor will send a new humidity report if difference exceeds this threshold value |
|
||||
| 5 | Temperature Alarm High | Set the temperature level for a heat alert notification to be sent to your hub and devices associated in Group 2. |
|
||||
| 6 | High Temperature Alarm Reporting | Decide if and how the sensor should report a heat alert. |
|
||||
| 7 | Temperature Alarm Low | Set the temperature level for a freeze / low temperature alert notification to be sent to your hub and devices associated in Group 3. |
|
||||
| 8 | Low Temperature Alarm Reporting | Decide if and how the sensor should report a low temperature / freeze alert. |
|
||||
| 9 | Humidity Alerts High | Set the humidity level for a high humidity alert notification to be sent to your hub and devices associated in Group 4. |
|
||||
| 10 | High Humidity Alarm Reporting | Decide if and how the sensor should report a high humidity alert. |
|
||||
| 11 | Humidity Alerts Low | Set the humidity level for a low humidity alert notification to be sent to your hub and devices associated in Group 5. |
|
||||
| 12 | Low Humidity Alarm Reporting | Decide if and how the sensor should report a low humidity alert. |
|
||||
| 13 | Temperature Scale | Celsius/Fahrenheit Selection |
|
||||
| 14 | Temperature Offset | Temperature Offset |
|
||||
| 16 | Temperature Reporting Interval | Sensor will report temperature at least as often as this value |
|
||||
|
|
@ -157,6 +165,94 @@ The manufacturer defined default value is ```10```.
|
|||
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 5: Temperature Alarm High
|
||||
|
||||
Set the temperature level for a heat alert notification to be sent to your hub and devices associated in Group 2.
|
||||
Set the temperature level for a high heat alert notification to be sent to your hub and devices associated in Group 2.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 50 to 120 may be set.
|
||||
|
||||
The manufacturer defined default value is ```120```.
|
||||
|
||||
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 6: High Temperature Alarm Reporting
|
||||
|
||||
Decide if and how the sensor should report a heat alert.
|
||||
Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 2 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 2; 4 – Basic Set Off command sent to devices in Group 2 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 2; 6 – Basic Set On and Off commands sent to devices in Group 2 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 2 (default).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 0 to 7 may be set.
|
||||
|
||||
The manufacturer defined default value is ```7```.
|
||||
|
||||
This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 7: Temperature Alarm Low
|
||||
|
||||
Set the temperature level for a freeze / low temperature alert notification to be sent to your hub and devices associated in Group 3.
|
||||
Set the temperature level for a freeze / low temperature alert notification to be sent to your hub and devices associated in Group 3.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 10 to 100 may be set.
|
||||
|
||||
The manufacturer defined default value is ```10```.
|
||||
|
||||
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 8: Low Temperature Alarm Reporting
|
||||
|
||||
Decide if and how the sensor should report a low temperature / freeze alert.
|
||||
Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 3 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 3; 4 – Basic Set Off command sent to devices in Group 3 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 3; 6 – Basic Set On and Off commands sent to devices in Group 3 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 3 (default).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 0 to 7 may be set.
|
||||
|
||||
The manufacturer defined default value is ```7```.
|
||||
|
||||
This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 9: Humidity Alerts High
|
||||
|
||||
Set the humidity level for a high humidity alert notification to be sent to your hub and devices associated in Group 4.
|
||||
Values: 0 – disabled (default); 1 – 100 (%).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 0 to 100 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_9_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 10: High Humidity Alarm Reporting
|
||||
|
||||
Decide if and how the sensor should report a high humidity alert.
|
||||
Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 4 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 4; 4 – Basic Set Off command sent to devices in Group 4 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 4; 6 – Basic Set On and Off commands sent to devices in Group 4 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 4 (default).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 0 to 7 may be set.
|
||||
|
||||
The manufacturer defined default value is ```7```.
|
||||
|
||||
This parameter has the configuration ID ```config_10_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 11: Humidity Alerts Low
|
||||
|
||||
Set the humidity level for a low humidity alert notification to be sent to your hub and devices associated in Group 5.
|
||||
Values: 0 – disabled (default); 1 – 100 (%).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 0 to 100 may be set.
|
||||
|
||||
The manufacturer defined default value is ```0```.
|
||||
|
||||
This parameter has the configuration ID ```config_11_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 12: Low Humidity Alarm Reporting
|
||||
|
||||
Decide if and how the sensor should report a low humidity alert.
|
||||
Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 5 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 5; 4 – Basic Set Off command sent to devices in Group 5 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 5; 6 – Basic Set On and Off commands sent to devices in Group 5 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 5 (default).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
|
||||
Values in the range 0 to 7 may be set.
|
||||
|
||||
The manufacturer defined default value is ```7```.
|
||||
|
||||
This parameter has the configuration ID ```config_12_1``` and is of type ```INTEGER```.
|
||||
|
||||
|
||||
### Parameter 13: Temperature Scale
|
||||
|
||||
Celsius/Fahrenheit Selection
|
||||
|
|
@ -302,6 +398,7 @@ Association group 5 supports 5 nodes.
|
|||
### Documentation Links
|
||||
|
||||
* [Manual](https://opensmarthouse.org/zwavedatabase/1468/reference/zse44.pdf)
|
||||
* [parameters](https://opensmarthouse.org/zwavedatabase/1468/reference/zse44_1.pdf)
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -29,6 +29,8 @@
|
|||
</channel-group>
|
||||
</channel-groups>
|
||||
|
||||
<representation-property>serialNumber</representation-property>
|
||||
|
||||
<config-description>
|
||||
<parameter-group name="receiverProperties">
|
||||
<label>Receiver Properties</label>
|
||||
|
|
|
|||
|
|
@ -20,19 +20,27 @@
|
|||
</state>
|
||||
</channel-type>
|
||||
<channel-type id="temperature">
|
||||
<item-type>Number</item-type>
|
||||
<item-type>Number:Temperature</item-type>
|
||||
<label>Temperature</label>
|
||||
<description>Current zone temperature</description>
|
||||
<category>temperature</category>
|
||||
<state readOnly="true" pattern="%.1f °C">
|
||||
<tags>
|
||||
<tag>Measurement</tag>
|
||||
<tag>Temperature</tag>
|
||||
</tags>
|
||||
<state readOnly="true" pattern="%.1f %unit%">
|
||||
</state>
|
||||
</channel-type>
|
||||
<channel-type id="setpoint">
|
||||
<item-type>Number</item-type>
|
||||
<item-type>Number:Temperature</item-type>
|
||||
<label>Set Point</label>
|
||||
<description>Gets or sets the set point of this zone (0 cancels the override).</description>
|
||||
<category>heating</category>
|
||||
<state min="0.0" max="35.0" step="0.5" pattern="%.1f °C"/>
|
||||
<tags>
|
||||
<tag>Setpoint</tag>
|
||||
<tag>Temperature</tag>
|
||||
</tags>
|
||||
<state min="0.0" max="35.0" step="0.5" pattern="%.1f %unit%"/>
|
||||
</channel-type>
|
||||
<channel-type id="setpointstatus">
|
||||
<item-type>String</item-type>
|
||||
|
|
|
|||
|
|
@ -27,6 +27,12 @@
|
|||
<label>Refresh Interval</label>
|
||||
<default>60</default>
|
||||
</parameter>
|
||||
<parameter name="timeout" type="integer" unit="s">
|
||||
<label>Timeout</label>
|
||||
<description>Timeout for all requests (SOAP requests, phone book retrieval, call lists, ...).</description>
|
||||
<default>5</default>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
</config-description>
|
||||
</bridge-type>
|
||||
|
||||
|
|
@ -54,6 +60,12 @@
|
|||
<label>Refresh Interval</label>
|
||||
<default>60</default>
|
||||
</parameter>
|
||||
<parameter name="timeout" type="integer" unit="s">
|
||||
<label>Timeout</label>
|
||||
<description>Timeout for all requests (SOAP requests, phone book retrieval, call lists, ...).</description>
|
||||
<default>5</default>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
<parameter name="tamIndices" type="text" multiple="true">
|
||||
<label>TAM</label>
|
||||
<description>List of answering machines (starting with 0).</description>
|
||||
|
|
@ -100,6 +112,17 @@
|
|||
<default>600</default>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
<parameter name="backupDirectory" type="text">
|
||||
<label>Backup Directory</label>
|
||||
<description>The directory where configuration backups are stored (default to userdata directory).</description>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
<parameter name="backupPassword" type="text">
|
||||
<label>Backup Password</label>
|
||||
<description>The password used to encrypt the backup data.</description>
|
||||
<context>password</context>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
</config-description>
|
||||
</bridge-type>
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Indoor Siren 6 and Doorbell 6<br /> <h1>Overview</h1><p>Siren 6 is your home’s
|
|||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_burglar" typeId="alarm_burglar">
|
||||
<channel id="alarm_tamper" typeId="alarm_tamper">
|
||||
<label>Alarm (burglar)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
|
||||
|
|
|
|||
|
|
@ -47,7 +47,13 @@ Temperature and Humidity Sensor<br /> <h1>Overview</h1><p>Small sensor that offe
|
|||
<channel id="alarm_battery" typeId="alarm_battery">
|
||||
<label>Alarm (battery)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_heat" typeId="alarm_heat">
|
||||
<label>Alarm (heat)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=HEAT</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="battery-level" typeId="system.battery-level">
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ Multisensor 7<br /> <h1>Overview</h1><p>Aeotec MultiSensor 7 was developed to de
|
|||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=SYSTEM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_burglar" typeId="alarm_burglar">
|
||||
<channel id="alarm_tamper" typeId="alarm_tamper">
|
||||
<label>Alarm (burglar)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
|
||||
|
|
@ -62,6 +62,12 @@ Multisensor 7<br /> <h1>Overview</h1><p>Aeotec MultiSensor 7 was developed to de
|
|||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_battery" typeId="alarm_battery">
|
||||
<label>Alarm (battery)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="battery-level" typeId="system.battery-level">
|
||||
<properties>
|
||||
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
|
||||
|
|
|
|||
|
|
@ -168,7 +168,22 @@
|
|||
<label>Heat alarm</label>
|
||||
<description>Indicates if a heat alarm is triggered
|
||||
</description>
|
||||
<category>Fire</category>
|
||||
<category>temperature_hot</category>
|
||||
<state readOnly="true">
|
||||
<options>
|
||||
<option value="OFF">OK</option>
|
||||
<option value="ON">Alarm</option>
|
||||
</options>
|
||||
</state>
|
||||
</channel-type>
|
||||
|
||||
<!-- Cold Temperature Alarm Channel -->
|
||||
<channel-type id="alarm_cold">
|
||||
<item-type>Switch</item-type>
|
||||
<label>Freeze alarm</label>
|
||||
<description>Indicates if a low temp alarm is triggered
|
||||
</description>
|
||||
<category>temperature_cold</category>
|
||||
<state readOnly="true">
|
||||
<options>
|
||||
<option value="OFF">OK</option>
|
||||
|
|
@ -287,6 +302,21 @@
|
|||
</options>
|
||||
</state>
|
||||
</channel-type>
|
||||
|
||||
<!-- Weather Alarm Channel -->
|
||||
<channel-type id="alarm_humidity">
|
||||
<item-type>Switch</item-type>
|
||||
<label>Humidity-Moisture Alarm</label>
|
||||
<description>
|
||||
</description>
|
||||
<category>Humidity</category>
|
||||
<state readOnly="true">
|
||||
<options>
|
||||
<option value="OFF">OK</option>
|
||||
<option value="ON">Alarm</option>
|
||||
</options>
|
||||
</state>
|
||||
</channel-type>
|
||||
|
||||
<!-- Barrier Position -->
|
||||
<channel-type id="barrier_position">
|
||||
|
|
|
|||
|
|
@ -32,8 +32,8 @@ Z-Wave Door/Window Sensor<br /> <h1>Overview</h1><p>Z-Wave+ enabled device which
|
|||
<property name="binding:*:OpenClosedType">COMMAND_CLASS_ALARM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_power" typeId="alarm_power">
|
||||
<label>Alarm (power)</label>
|
||||
<channel id="alarm_battery" typeId="alarm_battery">
|
||||
<label>Alarm Battery Status</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
</properties>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
<thing-type id="eco_tiltzwave25_00_000" listed="false">
|
||||
<label>TILT-ZWAVE2.5-ECO Z-wave Plus Gold Plated Reliability Garage Door Tilt Sensor</label>
|
||||
<description><![CDATA[
|
||||
Z-wave Plus Gold Plated Reliability Garage Door Tilt Sensor<br /> <h1>Overview</h1><ul><li>Z-Wave PlusTM enabled device which transmits when a garage door is opened or closed</li> <li>Uses a tilt sensor to detect the angle of a door and transmits open/closed status</li> <li>Reports tamper condition if cover is removed </li> </ul> <br /> <h2>Inclusion Information</h2><p>1. Start by placing the controller into inclusion mode.</p> <p>2. Activate inclusion mode for the sensor by inserting the battery. When the inclusion process is complete the red LED will turn on for approximately 10 seconds and then it will go out. If the LED continues to flash, repeat the inclusion process.</p> <p>3. Test the garage door sensor before mounting it. Hold the sensor in your hand. Flip the sensor upside-down and watch the LED while doing so. The LED will flash each time the position of the sensor is changed. If your Z- Wave network has a software interface you may verify that the messages from the sensor are being received each time the sensor is flipped.</p> <p>If you need to repeat the inclusion process, repeat STEP ONE above, then for STEP TWO you will need to simply remove the cover of the sensor, remove the battery for 5 seconds, reinsert the battery, and replace the sensor cover. This will re-enter the sensor in inclusion mode.</p> <br /> <h2>Exclusion Information</h2><p>Exclusion mode on the sensor is activated on the sensor by the exact same procedure as inclusion.</p> <br /> <h2>Wakeup Information</h2><p>To save power, this sensor sleeps most of the time and is therefore not awake to receive messages from a gateway for testing. Removing the top case from the sensor will put in device into a tampered mode in which the sensor will stay awake and able to receive messages. Most of the time an end user would not do this, but if the sensor needs to be configured after inclusion, an end user can follow the instructions below for sending Wake-Up notifications.</p> <p>The sensor will wake up every so often and when the case is closed, it will send a Wake-Up Notification to allow the life line master node controller that the sensor is now available for any queued messages that the controller may have for the sensor. <strong>The time between Wake-Up Notifications can be configured with the Wake-Up Notification command class to be between 1 hour and 1 week with interval steps of 200 seconds.</strong></p>
|
||||
Z-wave Plus Gold Plated Reliability Garage Door Tilt Sensor<br /> <h1>Overview</h1><ul><li>Z-Wave PlusTM enabled device which transmits when a garage door is opened or closed</li> <li>Uses a tilt sensor to detect the angle of a door and transmits open/closed status</li> <li>Reports tamper condition if cover is removed </li> </ul> <br /> <h2>Inclusion Information</h2><ol><li>Start by placing the controller into inclusion mode.</li><li>Activate inclusion mode for the sensor by inserting the battery. When the inclusion process is complete the red LED will turn on for approximately 10 seconds and then it will go out. If the LED continues to flash, repeat the inclusion process.</li><li>Test the garage door sensor before mounting it. Hold the sensor in your hand. Flip the sensor upside-down and watch the LED while doing so. The LED will flash each time the position of the sensor is changed. If your Z- Wave network has a software interface you may verify that the messages from the sensor are being received each time the sensor is flipped.</li></ol> <p>If you need to repeat the inclusion process, repeat STEP ONE above, then for STEP TWO you will need to simply remove the cover of the sensor, remove the battery for 5 seconds, reinsert the battery, and replace the sensor cover. This will re-enter the sensor in inclusion mode.</p> <br /> <h2>Exclusion Information</h2><p>Exclusion mode on the sensor is activated on the sensor by the exact same procedure as inclusion.</p> <br /> <h2>Wakeup Information</h2><p>To save power, this sensor sleeps most of the time and is therefore not awake to receive messages from a gateway for testing. Removing the top case from the sensor will put in device into a tampered mode in which the sensor will stay awake and able to receive messages. Most of the time an end user would not do this, but if the sensor needs to be configured after inclusion, an end user can follow the instructions below for sending Wake-Up notifications.</p> <p>The sensor will wake up every so often and when the case is closed, it will send a Wake-Up Notification to allow the life line master node controller that the sensor is now available for any queued messages that the controller may have for the sensor. <strong>The time between Wake-Up Notifications can be configured with the Wake-Up Notification command class to be between 1 hour and 1 week with interval steps of 200 seconds.</strong></p>
|
||||
]]></description>
|
||||
<category>GarageDoor</category>
|
||||
|
||||
|
|
@ -20,8 +20,8 @@ Z-wave Plus Gold Plated Reliability Garage Door Tilt Sensor<br /> <h1>Overview</
|
|||
<property name="binding:*:OnOffType">COMMAND_CLASS_SENSOR_BINARY</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_power" typeId="alarm_power">
|
||||
<label>Alarm (power)</label>
|
||||
<channel id="alarm_battery" typeId="alarm_battery">
|
||||
<label>Alarm Battery Status</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
</properties>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,151 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<thing:thing-descriptions bindingId="zwave"
|
||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
||||
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
|
||||
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
|
||||
https://openhab.org/schemas/thing-description/v1.0.0">
|
||||
|
||||
<thing-type id="eurotronic_cometzwave_00_000" listed="false">
|
||||
<label>Comet Z-Wave Radator thermostat 700226</label>
|
||||
<description><![CDATA[
|
||||
Radator thermostat 700226<br /> <h1>Overview</h1><p>Comet Z-Wave is an energy-saving radiator controller compatible with the Z-Wave wireless standard.</p><p>FLiRS (Frequently Listening Receiver Slave): </p><p>Comet Z-Wave uses the Z-Wave function FLiRS as a radiator thermostat. As a FLiRS device, the radiator thermostat reacts to incoming commands such as temperature changes with a particularly short latency period</p> <br /> <h2>Inclusion Information</h2><p>Put your primary Z-Wave controller in inclusion mode and press v or ^button to activate add mode. If Comet Z-Wave was added successfully, the LED display will show the receivedNode ID<br /></p> <br /> <h2>Exclusion Information</h2><p>Please put your Z-Wave controller into the exclusion mode. Then press and hold the button in the battery compartment for 5 seconds until “LE” appears in the display</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
|
||||
]]></description>
|
||||
<category>RadiatorControl</category>
|
||||
|
||||
<!-- CHANNEL DEFINITIONS -->
|
||||
<channels>
|
||||
<channel id="basic_basic_number" typeId="basic_number">
|
||||
<label>Basic</label>
|
||||
<properties>
|
||||
<property name="binding:*:DecimalType">COMMAND_CLASS_BASIC</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="switch_dimmer" typeId="switch_dimmer">
|
||||
<label>Dimmer</label>
|
||||
<properties>
|
||||
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
|
||||
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="sensor_temperature" typeId="sensor_temperature">
|
||||
<label>Sensor (temperature)</label>
|
||||
<properties>
|
||||
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="thermostat_mode" typeId="eurotronic_cometzwave_00_000_thermostat_mode">
|
||||
<label>Thermostat mode</label>
|
||||
<properties>
|
||||
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_MODE</property>
|
||||
</properties>
|
||||
</channel>
|
||||
</channels>
|
||||
|
||||
<!-- DEVICE PROPERTY DEFINITIONS -->
|
||||
<properties>
|
||||
<property name="vendor">Eurotronics</property>
|
||||
<property name="modelId">Comet Z-Wave</property>
|
||||
<property name="manufacturerId">0148</property>
|
||||
<property name="manufacturerRef">0004:0003</property>
|
||||
<property name="dbReference">1549</property>
|
||||
<property name="defaultAssociations">1</property>
|
||||
</properties>
|
||||
|
||||
<!-- CONFIGURATION DESCRIPTIONS -->
|
||||
<config-description>
|
||||
|
||||
<!-- GROUP DEFINITIONS -->
|
||||
<parameter-group name="configuration">
|
||||
<context>setup</context>
|
||||
<label>Configuration Parameters</label>
|
||||
</parameter-group>
|
||||
|
||||
<parameter-group name="association">
|
||||
<context>link</context>
|
||||
<label>Association Groups</label>
|
||||
</parameter-group>
|
||||
|
||||
<!-- PARAMETER DEFINITIONS -->
|
||||
<parameter name="config_1_1" type="integer" groupName="configuration">
|
||||
<label>1: LCD invert</label>
|
||||
<description><![CDATA[
|
||||
LCD invert<br /> <h1>Overview</h1><p>0x00 LCD content normal</p><p>0x01 LCD mirrored content </p><p>default: 0x00 </p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<options>
|
||||
<option value="0">normal</option>
|
||||
<option value="1">inverted</option>
|
||||
</options>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_2_1" type="integer" groupName="configuration">
|
||||
<label>2: LCD Timeout</label>
|
||||
<description><![CDATA[
|
||||
0x05-0x1E Timeout after 5 seconds - 30 seconds default: 0x05<br /> <h1>Overview</h1><p>0x05-0x1E Timeout after 5 seconds - 30 seconds</p><p>default: 0x05</p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_4_1" type="integer" groupName="configuration">
|
||||
<label>4: Battery status update</label>
|
||||
<description><![CDATA[
|
||||
Battery status update frequence<br /> <h1>Overview</h1><p>0x00 Batteriestatus Send only event-controlled as system warning </p><p>0x01 Batteriestatus send 1x a day </p><p>default: 0x00</p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_5_1" type="integer" groupName="configuration">
|
||||
<label>5: Actual temperature update</label>
|
||||
<description><![CDATA[
|
||||
Temperature upddate policy<br /> <h1>Overview</h1><p>0x00 Send Actual-Temperature not automatically </p><p>0x01-0x32 0x32 With temperature difference of 0.1°C - 5.0°C </p><p>transfer actual temperature </p><p>default: 0x05 (When Delta = 0,5°C report</p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_7_1" type="integer" groupName="configuration">
|
||||
<label>7: Window open detection</label>
|
||||
<description><![CDATA[
|
||||
Window-open detection sensitivity<br /> <h1>Overview</h1><p>0x00 Deactivated</p><p>0x01 low sensitivity</p><p>0x02 medium sensitivity </p><p>0x03 high sensivity </p><p>default: 0x01 low sinsitive</p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<!-- ASSOCIATION DEFINITIONS -->
|
||||
<parameter name="group_1" type="text" groupName="association" multiple="true">
|
||||
<label>1: Lifeline</label>
|
||||
<description><![CDATA[
|
||||
Lifeline<br /> <h1>Overview</h1><p>Should be set to your controller.</p>
|
||||
]]></description>
|
||||
<multipleLimit>1</multipleLimit>
|
||||
</parameter>
|
||||
|
||||
<!-- STATIC DEFINITIONS -->
|
||||
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
|
||||
<label>Node ID</label>
|
||||
<advanced>true</advanced>
|
||||
</parameter>
|
||||
|
||||
</config-description>
|
||||
|
||||
</thing-type>
|
||||
|
||||
<channel-type id="eurotronic_cometzwave_00_000_thermostat_mode">
|
||||
<item-type>Number</item-type>
|
||||
<label>Thermostat Mode</label>
|
||||
<description>Sets the thermostat mode</description>
|
||||
<category>Temperature</category>
|
||||
<state pattern="%s">
|
||||
<options>
|
||||
<option value="0">Off</option>
|
||||
<option value="1">Heat</option>
|
||||
<option value="11">Economy Heat</option>
|
||||
</options>
|
||||
</state>
|
||||
</channel-type>
|
||||
|
||||
</thing:thing-descriptions>
|
||||
|
|
@ -20,10 +20,16 @@ Motion & Vibration Sensor<br /> <h1>Overview</h1><p>Motion detection, built-
|
|||
<property name="binding:*:OnOffType">COMMAND_CLASS_SENSOR_BINARY</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_burglar" typeId="alarm_burglar">
|
||||
<label>Alarm (burglar)</label>
|
||||
<channel id="alarm_tamper" typeId="alarm_tamper">
|
||||
<label>Alarm (vibration)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_motion" typeId="alarm_motion">
|
||||
<label>Motion via Notification Report</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="battery-level" typeId="system.battery-level">
|
||||
|
|
@ -101,6 +107,15 @@ Motion & Vibration Sensor<br /> <h1>Overview</h1><p>Motion detection, built-
|
|||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_19_1" type="integer" groupName="configuration">
|
||||
<label>19: Notification (Alarm) or Binary Reports</label>
|
||||
<description><![CDATA[
|
||||
Enable or disable binary sensor reports when motion is detected.<br /> <h1>Overview</h1><p>Values: 0 – don’t send binary sensor reports when motion is detected, send notification reports instead (default); 1 – send binary sensor reports when motion is detected instead of the notification report.<br /></p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_20_1" type="integer" groupName="configuration">
|
||||
<label>20: LED Indicator</label>
|
||||
<description><![CDATA[
|
||||
|
|
|
|||
|
|
@ -26,10 +26,10 @@ Outdoor Motion Sensor<br /> <h1>Overview</h1><p>OUTDOOR SENSOR: Introducing the
|
|||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR,event=8</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_power" typeId="alarm_power">
|
||||
<label>Alarm (power)</label>
|
||||
<channel id="alarm_battery" typeId="alarm_battery">
|
||||
<label>Alarm Battery Status</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_tamper" typeId="alarm_tamper">
|
||||
|
|
|
|||
|
|
@ -20,10 +20,10 @@ Outdoor Motion Sensor v2<br /> <h1>Overview</h1><p>OUTDOOR SENSOR: Introducing t
|
|||
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=LUMINANCE</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_power" typeId="alarm_power">
|
||||
<label>Alarm (power)</label>
|
||||
<channel id="alarm_battery" typeId="alarm_battery">
|
||||
<label>Alarm Battery Status</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_motion" typeId="alarm_motion">
|
||||
|
|
|
|||
|
|
@ -23,11 +23,11 @@ Tilt / Shock Sensor<br /> <h1>Overview</h1><p>Battery Powered Tilt / Shock senso
|
|||
<channel id="alarm_access" typeId="alarm_access">
|
||||
<label>Alarm (access)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=ACCESS_CONTROL</property>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
|
||||
</properties>
|
||||
</channel>
|
||||
<channel id="alarm_burglar" typeId="alarm_burglar">
|
||||
<label>Alarm (burglar)</label>
|
||||
<channel id="alarm_tamper" typeId="alarm_tamper">
|
||||
<label>Alarm (vibration)</label>
|
||||
<properties>
|
||||
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
|
||||
</properties>
|
||||
|
|
|
|||
|
|
@ -104,6 +104,86 @@ Sensor will send a new temperature report if difference exceeds this threshold<b
|
|||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_5_1" type="integer" groupName="configuration">
|
||||
<label>5: Temperature Alarm High</label>
|
||||
<description><![CDATA[
|
||||
Set the temperature level for a heat alert notification to be sent to your hub and devices associated in Group 2.<br /> <h1>Overview</h1><p>Set the temperature level for a high heat alert notification to be sent to your hub and devices associated in Group 2.<br /></p>
|
||||
]]></description>
|
||||
<default>120</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_6_1" type="integer" groupName="configuration">
|
||||
<label>6: High Temperature Alarm Reporting</label>
|
||||
<description><![CDATA[
|
||||
Decide if and how the sensor should report a heat alert.<br /> <h1>Overview</h1><p>Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 2 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 2; 4 – Basic Set Off command sent to devices in Group 2 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 2; 6 – Basic Set On and Off commands sent to devices in Group 2 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 2 (default).<br /></p>
|
||||
]]></description>
|
||||
<default>7</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_7_1" type="integer" groupName="configuration">
|
||||
<label>7: Temperature Alarm Low</label>
|
||||
<description><![CDATA[
|
||||
Set the temperature level for a freeze / low temperature alert notification to be sent to your hub and devices associated in Group 3.<br /> <h1>Overview</h1><p>Set the temperature level for a freeze / low temperature alert notification to be sent to your hub and devices associated in Group 3.<br /></p>
|
||||
]]></description>
|
||||
<default>10</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_8_1" type="integer" groupName="configuration">
|
||||
<label>8: Low Temperature Alarm Reporting</label>
|
||||
<description><![CDATA[
|
||||
Decide if and how the sensor should report a low temperature / freeze alert.<br /> <h1>Overview</h1><p>Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 3 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 3; 4 – Basic Set Off command sent to devices in Group 3 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 3; 6 – Basic Set On and Off commands sent to devices in Group 3 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 3 (default).<br /></p>
|
||||
]]></description>
|
||||
<default>7</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_9_1" type="integer" groupName="configuration">
|
||||
<label>9: Humidity Alerts High</label>
|
||||
<description><![CDATA[
|
||||
Set the humidity level for a high humidity alert notification to be sent to your hub and devices associated in Group 4.<br /> <h1>Overview</h1><p>Values: 0 – disabled (default); 1 – 100 (%).<br /></p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_10_1" type="integer" groupName="configuration">
|
||||
<label>10: High Humidity Alarm Reporting</label>
|
||||
<description><![CDATA[
|
||||
Decide if and how the sensor should report a high humidity alert.<br /> <h1>Overview</h1><p>Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 4 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 4; 4 – Basic Set Off command sent to devices in Group 4 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 4; 6 – Basic Set On and Off commands sent to devices in Group 4 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 4 (default).<br /></p>
|
||||
]]></description>
|
||||
<default>7</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_11_1" type="integer" groupName="configuration">
|
||||
<label>11: Humidity Alerts Low</label>
|
||||
<description><![CDATA[
|
||||
Set the humidity level for a low humidity alert notification to be sent to your hub and devices associated in Group 5.<br /> <h1>Overview</h1><p>Values: 0 – disabled (default); 1 – 100 (%).<br /></p>
|
||||
]]></description>
|
||||
<default>0</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_12_1" type="integer" groupName="configuration">
|
||||
<label>12: Low Humidity Alarm Reporting</label>
|
||||
<description><![CDATA[
|
||||
Decide if and how the sensor should report a low humidity alert.<br /> <h1>Overview</h1><p>Values: 0 – no notifications sent to the hub or association groups; 1 – notification sent to the hub only; 2 – Basic Set On command sent to devices in Group 5 only; 3 – notification sent to the hub (lifeline) and Basic Set On to the devices associated in Group 5; 4 – Basic Set Off command sent to devices in Group 5 only; 5 – notification sent to the hub and Basic Set Off to the devices associated in Group 5; 6 – Basic Set On and Off commands sent to devices in Group 5 only; 7 – notification sent to the hub and Basic Set On and Off to the devices associated in Group 5 (default).<br /></p>
|
||||
]]></description>
|
||||
<default>7</default>
|
||||
<advanced>true</advanced>
|
||||
<limitToOptions>false</limitToOptions>
|
||||
</parameter>
|
||||
|
||||
<parameter name="config_13_1" type="integer" groupName="configuration">
|
||||
<label>13: Temperature Scale</label>
|
||||
<description><.
|
||||
The app follows the basic principles of the other openHAB UIs, like Basic UI, and presents your predefined openHAB [sitemap(s)](https://www.openhab.org/docs/configuration/sitemaps.html) and other UIs.
|
||||
|
||||
<a href="https://play.google.com/store/apps/details?id=org.openhab.habdroid">
|
||||
<img alt="Get it on Google Play" src="images/en_badge_web_generic.png" width="240px">
|
||||
|
|
@ -29,7 +29,7 @@ The app follows the basic principles of the other openHAB UIs, like Basic UI, an
|
|||
## Getting Started
|
||||
|
||||
On first start the app tries to discover your openHAB server.
|
||||
This will only work on local networks and when the server does not enforce either authentication or HTTPS.
|
||||
This will only work on local networks and when the server doesn't enforce authentication.
|
||||
If it fails, you can click on `Go to settings` and manually enter the server settings.
|
||||
|
||||
The URL field(s) might look like one of the following examples:
|
||||
|
|
@ -66,7 +66,7 @@ If you want to use openHAB Android on a wall mounted tablet, go to settings and
|
|||
It's required to have a voice recognizer app installed on the Android device, e.g. [by Google](https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox).
|
||||
Voice recognizer apps may send the recorded sound to a server to convert it into text.
|
||||
|
||||
To run your voice command rule please make sure that `Default Human Language Interpreter` is set to `Rule-based Interpreter` (http://openhab:8080/#!/settings/services/org.openhab.voice) and that the correct Item is selected at `Other Services` => `Rule Voice Interpreter` => `Voice Command Item` (http://openhab:8080/#!/settings/services/org.openhab.rulehli/select/).
|
||||
To run your voice command rule please make sure that `Default Human Language Interpreter` is set to `Rule-based Interpreter` (http://openhab:8080/settings/services/org.openhab.voice) and that the correct Item is selected at `Other Services` => `Rule Voice Interpreter` => `Voice Command Item` (http://openhab:8080/settings/services/org.openhab.rulehli).
|
||||
|
||||
### Send device information to openHAB
|
||||
|
||||
|
|
@ -318,10 +318,10 @@ The variable `%httpcode` is returned by the plugin and contains the HTTP code re
|
|||
In case of an error the plugin returns an error code.
|
||||
|
||||
| Error Code | Description |
|
||||
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| 10 | Tasker plugin is disabled |
|
||||
| 11 | The app couldn't establish a connection |
|
||||
| 1000+ | A connection was established, but an error occurred. The error code is 1000 + the HTTP code, e.g. 1401 means [Unauthenticated](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_client_errors). |
|
||||
| > 1000 | A connection was established, but an error occurred. The error code is 1000 + the HTTP code, e.g. 1401 means [Unauthenticated](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_client_errors). |
|
||||
|
||||
### Quick Access Device Controls
|
||||
|
||||
|
|
@ -375,7 +375,8 @@ This has a few disadvantages:
|
|||
|
||||
### I have issues with openHAB 3 UI or HABPanel
|
||||
|
||||
The app uses Android WebViews to render all UIs except Sitemaps. Please make sure you're running the latest WebView version: https://play.google.com/store/apps/details?id=com.google.android.webview
|
||||
The app uses Android WebViews to render all UIs except Sitemaps.
|
||||
Please make sure you're running the latest WebView version: https://play.google.com/store/apps/details?id=com.google.android.webview
|
||||
|
||||
### Chart loading is too slow
|
||||
|
||||
|
|
@ -384,7 +385,9 @@ If you experience slow chart loading times and your server isn't powerful, open
|
|||
|
||||
### Icons look pixelated
|
||||
|
||||
For good looking icons, the best approach is using SVG icons. Bitmap icons have a fixed size that doesn't scale with screen pixel density, so depending on the device, they may be scaled up by a large factor. When using SVG icons, ideally use icons that don't have a fixed size (in other words, they shouldn't have a 'width' and 'height' attribute on the root tag), as otherwise scaling might become necessary again: the app renders SVGs at their native size scaled by screen density, but scales them to a common size; when using icons without fixed size, the app can render them at precisely the needed size.
|
||||
For good looking icons, the best approach is using SVG icons.
|
||||
Bitmap icons have a fixed size that doesn't scale with screen pixel density, so depending on the device, they may be scaled up by a large factor.
|
||||
When using SVG icons, ideally use icons that don't have a fixed size (in other words, they shouldn't have a 'width' and 'height' attribute on the root tag), as otherwise scaling might become necessary again: the app renders SVGs at their native size scaled by screen density, but scales them to a common size; when using icons without fixed size, the app can render them at precisely the needed size.
|
||||
|
||||
## Trademark Disclaimer
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
## Install log now on port 81 ## February 23, 2023
|
||||
As there have been conflicts with the hotspot function, the install time web
|
||||
log was now moved to port 81. The standard port 80 is reserved for the hotspot.
|
||||
|
||||
## Raspberry Imager ## August 17, 2022
|
||||
Now openHABian can be selected directly within Raspberry Imager to write the
|
||||
image to an SD card.
|
||||
|
|
|
|||
|
|
@ -258,7 +258,7 @@ Take care this listing may be outdated. We try to make install options independe
|
|||
|
||||
## openHABian Configuration Tool
|
||||
|
||||
The following instructions are developed for a Raspberry Pi but should be applicable to all hardware / all openHABian environments.
|
||||
The following instructions are written for a Raspberry Pi but should be applicable to all hardware / all openHABian environments.
|
||||
Once connected to the command line console of your system, please execute the openHABian configuration tool by typing the following command:
|
||||
|
||||
(Hint: sudo executes a command with elevated rights and will hence ask for your password. The default is `openhabian`).
|
||||
|
|
@ -278,18 +278,13 @@ Press <kbd>Esc</kbd> twice to exit the configuration tool.
|
|||
|
||||
### Linux Hints
|
||||
|
||||
Many helpful articles can be found on the internet, for example:
|
||||
If you're a newbie to Linux, you sooner or later will have to know some Linux if you want to copy some files or are on the search for a solution to a problem.
|
||||
To prepare, take a few minutes to study these tutorials and get to know the most basic commands and tools to be able to navigate on your Linux system, edit configurations, check the system state or look at log files.
|
||||
|
||||
- "Learn the ways of Linux-fu, for free" interactively with exercises at [linuxjourney.com](https://linuxjourney.com).
|
||||
- The official Raspberry Pi help articles over at [raspberrypi.org](https://www.raspberrypi.org/help)
|
||||
- "Now what?", Tutorial on the Command line console at [LinuxCommand.org](http://linuxcommand.org/index.php)
|
||||
|
||||
_The good news:_ openHABian helps you to stay away from Linux - _The bad news:_ not for long...
|
||||
|
||||
Regardless of if you want to copy some files or are on the search for a solution to a problem, sooner or later you'll have to know some Linux.
|
||||
Take a few minutes to study the above Tutorials and get to know the most basic commands and tools to be able to navigate on your Linux system, edit configurations, check the system state or look at log files.
|
||||
It's not complicated and something that doesn't hurt on one's résumé.
|
||||
|
||||
### First steps with openHAB
|
||||
|
||||
After your first setup of openHABian is successful and you are able to access the openHAB dashboard, you should dig into the possibilites.
|
||||
|
|
@ -513,7 +508,7 @@ You'll also see commits "fly by" when executing the "Update" function within the
|
|||
### Did my Installation succeed? What to do in case of a problem?
|
||||
openHABian setup will take 15 up to 45 minutes to complete all steps, depending on your device's performance and your internet connection.
|
||||
|
||||
Watch the progress on the console or the web interface at <https://yourIP/> or <http://openhabian/> if that name has become available.
|
||||
Watch the progress on the console or the web interface at <https://yourIP:81/> or <http://openhabian/> if that name has become available.
|
||||
Double-check the IP address and name with your router while you wait.
|
||||
If there is absolutely no output for more than 10 minutes, your installation has failed in the first initialization phase.
|
||||
There probably is a problem with the way your router or local network are setup.
|
||||
|
|
|
|||
Loading…
Reference in New Issue