Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
8e24861fb1
24 changed files with 504 additions and 92 deletions
|
|
@ -28,6 +28,7 @@ This platform should work with all Hikvision cameras, and has been confirmed to
|
|||
- DS-2CD3132-I
|
||||
- DS-2CD2232-I5
|
||||
- DS-2CD2032-I
|
||||
- DS-2CD2042WD-I
|
||||
- DS-2CD2142FWD-I
|
||||
|
||||
To enable this sensor, the following lines are required in your `configuration.yaml`:
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ cover:
|
|||
|
||||
##### {% linkable_title RFY %}
|
||||
|
||||
The [RFXtrx433e](http://www.rfxcom.com/RFXtrx433E-USB-43392MHz-Transceiver/en) is required for RFY support, however it does not support receive for the RFY protocol - as such devices cannot be automatically added. Instead, configure the device in the [rfxmngr](http://www.rfxcom.com/downloads.htm) tool. Make a note of the assigned ID and Unit Code and then add a device to the configuration with the following id `071a0000[id][unit_code]`. Eg, if the id was `0a` `00` `01`, and the unit code was `01` then the fully qualified id would be `071a00000a000101`.
|
||||
The [RFXtrx433e](http://www.rfxcom.com/RFXtrx433E-USB-43392MHz-Transceiver/en) is required for RFY support, however it does not support receive for the RFY protocol - as such devices cannot be automatically added. Instead, configure the device in the [rfxmngr](http://www.rfxcom.com/downloads.htm) tool. Make a note of the assigned ID and Unit Code and then add a device to the configuration with the following id `071a0000[id][unit_code]`. Eg, if the id was `0a` `00` `01`, and the unit code was `01` then the fully qualified id would be `071a00000a000101`, if you set your id/code to single digit in the rfxmngr eg, id: `1` `02` `04` and unit code: `1` you will need to add `0` before, so `102031` becomes `071a000001020301`.
|
||||
|
||||
##### {% linkable_title Common %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Home Assistant 0.39"
|
||||
title: "Home Assistant 0.41"
|
||||
description: ""
|
||||
date: 2016-12-16 17:00
|
||||
sidebar: true
|
||||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Other
|
||||
ha_release: 0.39
|
||||
ha_release: 0.41
|
||||
---
|
||||
|
||||
Details about the latest release can always be found at:
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Rflink Light"
|
||||
description: "Instructions how to integrate Rflink lights into Home Assistant."
|
||||
title: "RFLink Light"
|
||||
description: "Instructions how to integrate RFLink lights into Home Assistant."
|
||||
date: 2016-01-04
|
||||
sidebar: true
|
||||
comments: false
|
||||
|
|
@ -12,11 +12,11 @@ ha_category: Light
|
|||
ha_release: 0.38
|
||||
---
|
||||
|
||||
The `rflink` component support devices that use [Rflink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo Rflink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
|
||||
The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First you have to set up your [rflink hub](/components/rflink/).
|
||||
|
||||
After configuring the Rflink hub lights will be automatically discovered and added.
|
||||
After configuring the RFLink hub lights will be automatically discovered and added.
|
||||
|
||||
New/unknown lights can be assigned to a default group automatically by specifying the `new_devices_group` option with a group name. If the group doesn't exist it will be created.
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ sensor:
|
|||
new_devices_group: "New Rflink Lights"
|
||||
```
|
||||
|
||||
Rflink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
|
||||
RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
|
||||
|
||||
Once the ID of a light is known it can be used to configure the light in HA, for example to add it to a different group, hide it or configure a nice name.
|
||||
|
||||
|
|
@ -39,6 +39,9 @@ Configuring a device as light with a nice name:
|
|||
# Example configuration.yaml entry
|
||||
light:
|
||||
platform: rflink
|
||||
device_defaults:
|
||||
fire_event: true
|
||||
signal_repetitions: 2
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Living room
|
||||
|
|
@ -59,12 +62,15 @@ Device configuration variables:
|
|||
- **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
|
||||
- **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
|
||||
- **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1)
|
||||
- **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
|
||||
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
|
||||
|
||||
|
||||
### {% linkable_title Light state %}
|
||||
|
||||
Initially the state of a light is unknown. When the light is turned on or off (via frontend or 433Mhz remote) the state is known and will be shown in the frontend.
|
||||
Initially the state of a light is unknown. When the light is turned on or off (via frontend or remote) the state is known and will be shown in the frontend.
|
||||
|
||||
Sometimes a light is controlled by multiple 433Mhz remotes, each remote has its own code programmed in the light. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
|
||||
Sometimes a light is controlled by multiple remotes, each remote has its own code programmed in the light. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -82,7 +88,7 @@ Any on/off command from any allias ID updates the current state of the light. Ho
|
|||
|
||||
### {% linkable_title Light types %}
|
||||
|
||||
Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated `on` command as they turn into a pulsating state until `on` is pressed again (for example KlikAanKlikUit). The Rflink component support three types of lights to make things work in every situation:
|
||||
Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated `on` command as they turn into a pulsating state until `on` is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation:
|
||||
|
||||
- *Hybrid*: This type sends a `dim` followed by an a `on` command; and `off` commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple `on` signals will cause dimmers to go into disco mode.
|
||||
- *Switchable*: Device type that sends only `on` and `off` commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).
|
||||
|
|
@ -93,7 +99,7 @@ By default new lights are assigned the `switchable` type. Protocol supporting di
|
|||
|
||||
### {% linkable_title Hiding/ignoring lights %}
|
||||
|
||||
Lights are added automatically when the Rflink gateway intercepts a 433Mhz command in the ether. To prevent cluttering the frontend use any of these methods:
|
||||
Lights are added automatically when the RFLink gateway intercepts a wireless command in the ether. To prevent cluttering the frontend use any of these methods:
|
||||
|
||||
- Configure a `new_devices_group` for lights and optionally add it to a different `view`.
|
||||
- Hide unwanted devices using [customizations](/getting-started/customizing-devices/)
|
||||
|
|
|
|||
|
|
@ -25,8 +25,8 @@ mqtt_eventstream:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **publish_topic** (*Required*): Topic for publishing local events
|
||||
- **subscribe_topic** (*Required*): Topic to receive events from the remote server.
|
||||
- **publish_topic** (*Optional*): Topic for publishing local events
|
||||
- **subscribe_topic** (*Optional*): Topic to receive events from the remote server.
|
||||
|
||||
## Multiple Instances
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Rflink"
|
||||
description: "Instructions how to integrate Rflink gateway into Home Assistant."
|
||||
title: "RFLink"
|
||||
description: "Instructions how to integrate RFLink gateway into Home Assistant."
|
||||
date: 2016-01-04
|
||||
sidebar: true
|
||||
comments: false
|
||||
|
|
@ -12,17 +12,23 @@ ha_category: Hub
|
|||
ha_release: 0.38
|
||||
---
|
||||
|
||||
The `rflink` component support devices that use [Rflink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo Rflink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). Rflink gateway is firmware for the Arduino MEGA 2560 that allows communication with 433 Mhz devices using cheap hardware (Arduino + 433 Mhz tranceiver).
|
||||
The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
The 433 Mhz spectrum is used by many manufacturers mostly using their own protocol/standard and includes devices like: light switches, blinds, weather stations, alarms and various other sensors.
|
||||
|
||||
A complete list of devices supported by Rflink can be found [here](http://www.nemcon.nl/blog2/devlist)
|
||||
RFLink Gateway supports a number of RF frequencies, using a wide range of low-cost hardware. Their website provides details for various RF transmitter, receiver and transceiver modules for 433Mhz, 868Mhz and 2.4 Ghz [here.](http://www.nemcon.nl/blog2/wiring)
|
||||
|
||||
<p class='note'>
|
||||
Note: Versions later than R44 adds support for Ikea Ansluta, Philips Living Colors Gen1, MySensors devices.
|
||||
</p>
|
||||
|
||||
A complete list of devices supported by RFLink can be found [here](http://www.nemcon.nl/blog2/devlist)
|
||||
|
||||
This component is tested with the following hardware/software:
|
||||
|
||||
- Nodo Rflink Gateway V1.4/Rflink R44
|
||||
- Nodo RFLink Gateway V1.4/RFLink R46
|
||||
|
||||
To enable Rflink in your installation, add the following to your `configuration.yaml` file:
|
||||
To enable RFLink in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -32,9 +38,9 @@ rflink:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **port** (*Required*): The path to Rflink usb/serial device or TCP port in TCP mode.
|
||||
- **port** (*Required*): The path to RFLink USB/serial device or TCP port in TCP mode.
|
||||
- **host** (*Optional*): Switches to TCP mode, connects to host instead of to USB/serial.
|
||||
- **wait_for_ack** (*Optional*): Wait for Rflink to ackowledge commands sent before sending new command (slower but more reliable). Defaults to `True`
|
||||
- **wait_for_ack** (*Optional*): Wait for RFLink to ackowledge commands sent before sending new command (slower but more reliable). Defaults to `True`
|
||||
- **ignore_devices** (*Optional*): List of devices id's to ignore. Supports wildcards (*) at the end.
|
||||
- **reconnect_interval** (*Optional*): Time in seconds between reconnect attempts.
|
||||
|
||||
|
|
@ -52,9 +58,9 @@ rflink:
|
|||
|
||||
### {% linkable_title TCP mode %}
|
||||
|
||||
TCP mode allows connect to a Rflink device over TCP/IP network. This is for example useful if placing the Rflink device next to the HA server is not optimal or desired (eg: bad reception).
|
||||
TCP mode allows connect to a RFLink device over TCP/IP network. This is for example useful if placing the RFLink device next to the HA server is not optimal or desired (eg: bad reception).
|
||||
|
||||
To expose the usb/serial interface over TCP on a different host (Linux) the following command can be used:
|
||||
To expose the USB/serial interface over TCP on a different host (Linux) the following command can be used:
|
||||
|
||||
```bash
|
||||
$ socat /dev/ttyACM0,b57600 TCP-LISTEN:1234,reuseaddr
|
||||
|
|
@ -65,7 +71,7 @@ Other methods of exposing the serial interface over TCP are possible (eg: ESP826
|
|||
Tested with Wifi serial bridge [esp-link V2.2.3](https://github.com/jeelabs/esp-link/releases/tag/v2.2.3) running on a NodeMCU (ESP8266 Wifi module) with ESP8266 TXD0 (pin D10) and RXD0 (pin D9) connected to Arduino MEGA 2560 RX (Pin 2) and TX (Pin 3) respectively.
|
||||
|
||||
<p class='note warning'>
|
||||
Due to different logical levels, a voltage level shifter is required between the 3.3V NodeMCU and 5V Arduino MEGA 2560 pins.
|
||||
Due to different logic levels, a voltage level shifter is required between the 3.3V NodeMCU and 5V Arduino MEGA 2560 pins. The BSS138 bidirectional logic level converter has been tested for serial pins and the [link](https://www.aliexpress.com/item/8CH-IIC-I2C-Logic-Level-Converter-Bi-Directional-Module-DC-DC-5V-to-3-3V-Setp/32238089139.html) is recommended for the CC2500 transceiver (used for Ikea Ansluta and Living Colors)
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
|
|
@ -81,7 +87,7 @@ rflink:
|
|||
|
||||
### {% linkable_title Ignoring devices %}
|
||||
|
||||
Rflink platform can be configured to completely ignore a device on a platform level. This is useful when you have neighbors which also use 433 Mhz technology.
|
||||
RFLink platform can be configured to completely ignore a device on a platform level. This is useful when you have neighbors which also use 433 Mhz technology.
|
||||
|
||||
For example:
|
||||
|
||||
|
|
@ -102,15 +108,15 @@ Wildcards only work at the end of the ID, not in the middle of front!
|
|||
|
||||
### {% linkable_title Device support %}
|
||||
|
||||
Even though a lot of devices are supported by Rflink, not all have been tested/implemented. If you have a device supported by Rflink but not by this component please consider testing and adding support yourself or [create an issue](https://github.com/home-assistant/home-assistant/issues/new) and mention `@aequitas` in the description.
|
||||
Even though a lot of devices are supported by RFLink, not all have been tested/implemented. If you have a device supported by RFLink but not by this component please consider testing and adding support yourself or [create an issue](https://github.com/home-assistant/home-assistant/issues/new) and mention `@aequitas` in the description.
|
||||
|
||||
### {% linkable_title Device Incorrectly Identified %}
|
||||
|
||||
If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can be overcome with the RFlink 'RF Signal Learning' mechanism from RFLink Rev 46 (11 March 2017). http://www.nemcon.nl/blog2/faq#RFFind.
|
||||
If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can be overcome with the RFlink 'RF Signal Learning' mechanism from RFLink Rev 46 (11 March 2017). [Link to further detail.](http://www.nemcon.nl/blog2/faq#RFFind)
|
||||
|
||||
### {% linkable_title Technical overview %}
|
||||
|
||||
- The`rflink` Python module a asyncio transport/protocol is setup that fires an callback for every (valid/supported) packet received by the Rflink gateway.
|
||||
- The`rflink` Python module a asyncio transport/protocol is setup that fires an callback for every (valid/supported) packet received by the RFLink gateway.
|
||||
- This component uses this callback to distribute 'rflink packet events' over the HASS bus which can be subscribed to by entities/platform implementations.
|
||||
- The platform implementions take care of creating new devices (if enabled) for unsees incoming packet id's.
|
||||
- Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entitiy logic is maintained in this main component.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Rflink Sensor"
|
||||
description: "Instructions how to integrate Rflink sensors into Home Assistant."
|
||||
title: "RFLink Sensor"
|
||||
description: "Instructions how to integrate RFLink sensors into Home Assistant."
|
||||
date: 2016-01-04
|
||||
sidebar: true
|
||||
comments: false
|
||||
|
|
@ -12,11 +12,11 @@ ha_category: Sensor
|
|||
ha_release: 0.38
|
||||
---
|
||||
|
||||
The `rflink` component support devices that use [Rflink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo Rflink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
|
||||
The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First you have to set up your [rflink hub](/components/rflink/).
|
||||
|
||||
After configuring the Rflink hub sensors will be automatically discovered and added.
|
||||
After configuring the RFLink hub sensors will be automatically discovered and added.
|
||||
|
||||
New/unknown sensors can be assigned to a default group automatically by specifying the `new_devices_group` option with a group name. If the group doesn't exist it will be created.
|
||||
|
||||
|
|
@ -26,10 +26,10 @@ For example:
|
|||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: rflink
|
||||
new_devices_group: "New Rflink Sensors"
|
||||
new_devices_group: "New RFLink Sensors"
|
||||
```
|
||||
|
||||
Rflink sensor ID's are composed of: protocol, id and type (optional). For example: `alectov1_0334_temp`. Some sensors emit multiple types of data. Each will be created as its own
|
||||
RFLink sensor ID's are composed of: protocol, id and type (optional). For example: `alectov1_0334_temp`. Some sensors emit multiple types of data. Each will be created as its own
|
||||
|
||||
Once the ID of a sensor is known it can be used to configure the sensor in HA, for example to add it to a different group, hide it or configure a nice name.
|
||||
|
||||
|
|
@ -52,14 +52,14 @@ Configuration variables:
|
|||
|
||||
Device configuration variables:
|
||||
|
||||
- **name** (*Optional*): Name for the device, defaults to Rflink ID.
|
||||
- **name** (*Optional*): Name for the device, defaults to RFLink ID.
|
||||
- **sensor_type** (*Required*): Override automatically detected type of sensor.
|
||||
- **unit_of_measurement** (*Optional*): Override automatically detected unit of sensor.
|
||||
- **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
|
||||
- **aliasses** (*Optional*): Alternative RFLink ID's this device is known by.
|
||||
|
||||
### {% linkable_title Hiding/ignoring sensors %}
|
||||
|
||||
Sensors are added automatically when the Rflink gateway intercepts a 433Mhz command in the ether. To prevent cluttering the frontend use any of these methods:
|
||||
Sensors are added automatically when the RFLink gateway intercepts a wireless command in the ether. To prevent cluttering the frontend use any of these methods:
|
||||
|
||||
- Configure a `new_devices_group` for sensors and optionally add it to a different `view`.
|
||||
- Hide unwanted devices using [customizations](/getting-started/customizing-devices/)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Rflink Switch"
|
||||
description: "Instructions how to integrate Rflink switches into Home Assistant."
|
||||
title: "RFLink Switch"
|
||||
description: "Instructions how to integrate RFLink switches into Home Assistant."
|
||||
date: 2016-01-04
|
||||
sidebar: true
|
||||
comments: false
|
||||
|
|
@ -12,13 +12,13 @@ ha_category: Switch
|
|||
ha_release: 0.38
|
||||
---
|
||||
|
||||
The `rflink` component support devices that use [Rflink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo Rflink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
|
||||
The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First you have to set up your [rflink hub](/components/rflink/).
|
||||
|
||||
The Rflink component does not know the difference between a `switch` and a `light`. Therefore all switchable devices are automatically added as `light` by default.
|
||||
The RFLink component does not know the difference between a `switch` and a `light`. Therefore all switchable devices are automatically added as `light` by default.
|
||||
|
||||
Rflink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
|
||||
RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
|
||||
|
||||
Once the ID of a switch is known it can be used to configure it as a switch type in HA, for example to add it to a different group, hide it or configure a nice name.
|
||||
|
||||
|
|
@ -43,21 +43,21 @@ Configuration variables:
|
|||
|
||||
- **devices** (*Optional*): A list of devices with their name to use in the frontend.
|
||||
- **device_defaults**: (*Optional*)
|
||||
- **fire_event_** (*Optional*): Set default `fire_event` for Rflink switch devices (see below).
|
||||
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for Rflink switch devices (see below).
|
||||
- **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
|
||||
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
|
||||
|
||||
Device configuration variables:
|
||||
|
||||
- **name** (*Optional*): Name for the device, defaults to Rflink ID.
|
||||
- **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
|
||||
- **name** (*Optional*): Name for the device, defaults to RFLink ID.
|
||||
- **aliasses** (*Optional*): Alternative RFLink ID's this device is known by.
|
||||
- **fire_event_** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
|
||||
- **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1)
|
||||
- **signal_repetitions** (*Optional*): Repeat every RFLink command this number of times (default: 1)
|
||||
|
||||
### {% linkable_title Switch state %}
|
||||
|
||||
Initially the state of a switch is unknown. When the switch is turned on or off (via frontend or 433Mhz remote) the state is known and will be shown in the frontend.
|
||||
Initially the state of a switch is unknown. When the switch is turned on or off (via frontend or wireless remote) the state is known and will be shown in the frontend.
|
||||
|
||||
Sometimes a switch is controlled by multiple 433Mhz remotes, each remote has its own code programmed in the switch. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
|
||||
Sometimes a switch is controlled by multiple wireless remotes, each remote has its own code programmed in the switch. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue