mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 16:27:19 +00:00
Minor changes
This commit is contained in:
Fabian Affolter
parent
fa5418895b
commit
45d4ce3065
@ -8,12 +8,13 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Binary Sensors
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.23
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `homematic` binary_sensor platform lets you observe the state changes of binary [Homematic](http://www.homematic.com/) sensors through Home Assistant.
|
||||
The `homematic` binary sensor platform lets you observe the state changes of binary [Homematic](http://www.homematic.com/) sensors through Home Assistant.
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
@ -26,12 +27,11 @@ binary_sensor:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **platform** (*Required*: Needed to let Home Assistant know this is a Homematic rollershutter.
|
||||
- **address** (*Required*): The serial number of the device, eg. LEQ1234567
|
||||
- **name** (*Optional*): Name to identify the device.
|
||||
- **button** (*Optional*): Channel of the device to monitor (default: 1)
|
||||
- **button** (*Optional*): Channel of the device to monitor. Defaults to 1.
|
||||
- **param** (*Optional*): For devices with multiple channels and possible events, you may define which event type you want to attatch to this entity. If none is specified all events will turn the state to on.
|
||||
- **hidden** (*Optional*): Hide device from UI. Makes sense for buttons that will only trigger automations etc. (default: False)
|
||||
- **hidden** (*Optional*): Hide device from UI. Makes sense for buttons that will only trigger automations etc. Defaults to `False`.
|
||||
|
||||
Currently the following devices are supported:
|
||||
|
||||
@ -42,7 +42,7 @@ Currently the following devices are supported:
|
||||
- Gong / Doorbell buttons (no parameters needed)
|
||||
|
||||
Beware, that binary sensors might be included in devices that also have other functions. For example: The HM-Sen-MDIR-WM55 motion detector does not only detect motion (no motion == False, motion == True), it also detects the surrounding brightness (configure as sensor to monitor brightness from 0 to 255) and has buttons which can be pressed in different ways. Since buttons can only be pressed or not pressed, we consider them as binary sensors.
|
||||
The way buttons work is, that the entity for the specified parameter will be set to on and off again. So if you press the button shortly, it will flip on and off instantly, which could trigger some automation. If you hold down the button, the entity configured for the long press will be flipped on and off and can trigger another automation. As of now, we don't support the release of the long press and the continuation events that happen inbewteen.
|
||||
The way buttons work is, that the entity for the specified parameter will be set to on and off again. So if you press the button shortly, it will flip on and off instantly, which could trigger some automation. If you hold down the button, the entity configured for the long press will be flipped on and off and can trigger another automation. As of now, we don't support the release of the long press and the continuation events that happen in between.
|
||||
You may leave out the parameter, which will result in a single entity turning on and off on any supported event.
|
||||
|
||||
As an example for a complete configuration of the HM-Sen-MDIR-WM55 device:
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Hub
|
||||
featured: true
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
@ -28,14 +28,14 @@ If you want to see if a specific device you have is supported, head over to the
|
||||
|
||||
There are some devices which expose multiple functionalities. For example: The HM-Sen-MDIR-WM55 motion detector can be configured as 6 individual entities within HA.
|
||||
|
||||
1. Motion detector (binary_sensor platform)
|
||||
2. Button 1 short press (binary_sensor platform)
|
||||
3. Button 1 long press (binary_sensor platform)
|
||||
4. Button 2 short press (binary_sensor platform)
|
||||
5. Button 2 long press (binary_sensor platform)
|
||||
6. Brightness sensor (sensor platform)
|
||||
1. Motion detector ([/components/binary_sensor.homematic/](binary_sensor platform))
|
||||
2. Button 1 short press ([/components/binary_sensor.homematic/](binary_sensor platform))
|
||||
3. Button 1 long press ([/components/binary_sensor.homematic/](binary_sensor platform))
|
||||
4. Button 2 short press ([/components/binary_sensor.homematic/](binary_sensor platform))
|
||||
5. Button 2 long press ([/components/binary_sensor.homematic/](binary_sensor platform))
|
||||
6. Brightness sensor ([/components/sensor.homematic/](sensor platform))
|
||||
|
||||
We also have experimental autodetection support. If you ONLY configure this homematic-component and set autodetect to True, Home Assistant will try to automatically detect and configure each (supported) device paired to your CCU / Homegear. The resulting HA-entities will be named in the fashion of _ADDRESS CHANNEL PARAMETER_. This will provide you with the information which of your devices are supported and may be explicitly configured manually for a more useful integration into Home Assistant. Beware, that autodetection may put heavy load on your CCU and may take some time to complete (maybe 2-3 minutes when a lot of devices are present). Keep an eye on theservice messages on your CCU. If they show up while starting HA, increase the delay parameter in your configuration.
|
||||
We also have experimental autodetection support. If you ONLY configure this homematic component and set autodetect to True, Home Assistant will try to automatically detect and configure each (supported) device paired to your CCU/Homegear. The resulting Home Assistant entities will be named in the fashion of _ADDRESS CHANNEL PARAMETER_. This will provide you with the information which of your devices are supported and may be explicitly configured manually for a more useful integration into Home Assistant. Beware, that autodetection may put heavy load on your CCU and may take some time to complete (maybe 2-3 minutes when a lot of devices are present). Keep an eye on the service messages on your CCU. If they show up while starting Home Assistant, increase the delay parameter in your configuration.
|
||||
Afterwards you may incrementally configure each device the way you want. Manually configured devices will be handled first and won't be processed again when autodetection is still enabled.
|
||||
|
||||
To set up the component, add the following information to your `configuration.yaml` file:
|
||||
@ -52,14 +52,14 @@ homematic:
|
||||
Configuration variables:
|
||||
|
||||
- **local_ip** (*Required*): IP of device running Home Assistant
|
||||
- **local_port** (*Optional*): Port for connection with Home Assistant (default: 8943)
|
||||
- **remote_ip** (*Required*): IP of CCU / Homegear
|
||||
- **remote_port** (*Required*): Port of Homegear / CCU XML-RPC Server (usually 2001)
|
||||
- **autodetect** (*Optional*): <True/False> experimental, detect all devices (default: False)
|
||||
- **resolvenames** (*Optional*): <True/False> Try to fetch device names from HM-CFG-LAN metadata or XML-API on CCU (default: False)
|
||||
- **delay** (*Optional*): <Float> Delay fetching of current state per deivce. Useful to prevent overloading CCU when initially fetching device states. (Default: 0.5)
|
||||
- **local_port** (*Optional*): Port for connection with Home Assistant. Defaults to 8943.
|
||||
- **remote_ip** (*Required*): IP of CCU/Homegear
|
||||
- **remote_port** (*Required*): Port of Homegear/CCU XML-RPC Server (usually 2001)
|
||||
- **autodetect** (*Optional*): <True/False> experimental, detect all devices. Default to `False`.
|
||||
- **resolvenames** (*Optional*): <True/False> Try to fetch device names from HM-CFG-LAN metadata or XML-API on CCU. Defaults to `False`.
|
||||
- **delay** (*Optional*): <Float> Delay fetching of current state per deivce. Useful to prevent overloading CCU when initially fetching device states. Defaults to 0.5.
|
||||
|
||||
To further explain the ```resolvenames``` option:
|
||||
To further explain the `resolvenames` option:
|
||||
We use two approaches to fetch the names of devices. Either one assumes you have properly named your devices in your existing Homematic setup.
|
||||
|
||||
1. Using the metadata devices internally have. When using a HM-CFG-LAN interface, you typically use a configuration software ("HomeMatic-Komponenten konfigurieren" is the name of the shortcut on your desktop by default) to pair and configure your devices. If you have paired devices, you'll see them listed in a table. The leftmost column (Name) is prefilled with default names. You can click such a name and enter whatever you like. But you should Stick to ASCII. So rather use _Kueche_ instead of _Küche_. Which also makes sense because the entity-names in HA are ASCII as well.
|
||||
|
||||
@ -10,11 +10,12 @@ footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Light
|
||||
ha_release: 0.23
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `homematic` light platform lets you control [Homematic](http://www.homematic.com/) lights through Home Assistant.
|
||||
You have the choice to configure switch-devices as light entities within HA if you have lights attatched to the switch and it makes sense for your setup. If the switch uses multiple channels to control different devices, you may mix the configurations.
|
||||
You have the choice to configure switch-devices as light entities within Home Assistant if you have lights attatched to the switch and it makes sense for your setup. If the switch uses multiple channels to control different devices, you may mix the configurations.
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
@ -28,10 +29,9 @@ light:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **platform** (*Required*: Needed to let Home Assistant know this is a Homematic rollershutter.
|
||||
- **address** (*Required*): The serial number of the device, eg. LEQ1234567
|
||||
- **name** (*Optional*): Name to identify the device.
|
||||
- **button** (*Optional*): Channel of the Homematic interface to interact with (Default: 1)
|
||||
- **button** (*Optional*): Channel of the Homematic interface to interact with. Defaults to 1.
|
||||
|
||||
Currently the following devices are supported:
|
||||
- Switch from 1 to 4 channels
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.23
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
@ -27,13 +28,13 @@ sensor:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **platform** (*Required*: Needed to let Home Assistant know this is a Homematic rollershutter.
|
||||
- **address** (*Required*): The serial number of the device, eg. LEQ1234567
|
||||
- **name** (*Optional*): Name to identify the device.
|
||||
- **button** (*Optional*): Channel of the device to monitor (default: 1)
|
||||
- **button** (*Optional*): Channel of the device to monitor. Defaults to 1.
|
||||
- **param** (*Optional*): For devices with multiple channels and possible events, you may define which event type you want to attatch to this entity.
|
||||
|
||||
Currently the following devices are supported:
|
||||
|
||||
- Thermostats / Weather sensors (param: TEMPERATURE, HUMIDITY)
|
||||
- Switch Powermeter (param: POWER, CURRENT, VOLTAGE, FREQUENCY, ENERGY_COUNTER)
|
||||
- Motion detectors (param: BIRGHTNESS)
|
||||
|
||||
@ -10,11 +10,12 @@ footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.23
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `homematic` switch platform lets you control [Homematic](http://www.homematic.com/) switches through Home Assistant.
|
||||
If the switch uses multiple channels to control different devices, you may setup multiple HA entities. Switches may also be configured as light entities if you have lights attatched to them. Besides that, there a switches that have included sensors, which may also be configured as separate HA entities.
|
||||
If the switch uses multiple channels to control different devices, you may setup multiple Home Assistant entities. Switches may also be configured as light entities if you have lights attatched to them. Besides that, there a switches that have included sensors, which may also be configured as separate HA entities.
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
@ -28,12 +29,12 @@ switch:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **platform** (*Required*: Needed to let Home Assistant know this is a Homematic rollershutter.
|
||||
- **address** (*Required*): The serial number of the device, eg. LEQ1234567
|
||||
- **name** (*Optional*): Name to identify the device.
|
||||
- **button** (*Optional*): Channel of the Homematic interface to interact with (Default: 1)
|
||||
- **button** (*Optional*): Channel of the Homematic interface to interact with. Defaults to 1.
|
||||
|
||||
Currently the following devices are supported:
|
||||
|
||||
- Switch from 1 to 4 channels
|
||||
- Dimmer from 1 to 2 channels
|
||||
- Switch with powermeter
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.23
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
@ -26,10 +27,10 @@ thermostat:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **platform** (*Required*: Needed to let Home Assistant know this is a Homematic thermostat.
|
||||
- **address** (*Required*): The serial number of the device, eg. LEQ1234567
|
||||
- **name** (*Optional*): Name to identify the device.
|
||||
|
||||
Currently the following devices are supported:
|
||||
|
||||
- Thermostats
|
||||
- Wall Thermostats
|
||||
Loading…
x
Reference in New Issue
Block a user