jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Insteon component configuration (#7084)

Browse Source
This commit is contained in:
Klaas Schoute 2018-10-25 23:46:43 +02:00 committed by Franck Nijhof
parent 54e6af2f19
commit 6646ff4a7e
1 changed files with 124 additions and 141 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

255
source/_components/insteon.markdown
View File

@ -13,12 +13,8 @@ ha_iot_class: "Local Push"
ha_version: 0.77 ha_version: 0.77
--- ---
This component adds "local push" support for INSTEON Modems allowing This component adds "local push" support for INSTEON Modems allowing linked INSTEON devices to be used within Home Assistant as binary sensors, lights, fans, sensors and switches. Device support is provided by the
linked INSTEON devices to be used within Home Assistant as binary sensors, underlying [insteonplm] package. It is known to work with the [2413U] USB and [2412S] RS242 flavors of PLM and the [2448A7] USB stick. It has also been tested to work with the [2242] and [2245] Hubs.
lights, fans, sensors and switches. Device support is provided by the
underlying [insteonplm] package. It is known to work with the [2413U] USB and
[2412S] RS242 flavors of PLM and the [2448A7] USB stick. It has also been
tested to work with the [2242] and [2245] Hubs.
[insteonplm]: https://github.com/nugget/python-insteonplm [insteonplm]: https://github.com/nugget/python-insteonplm
[2413U]: https://www.insteon.com/powerlinc-modem-usb [2413U]: https://www.insteon.com/powerlinc-modem-usb
@ -27,11 +23,9 @@ tested to work with the [2242] and [2245] Hubs.
[2245]: https://www.insteon.com/insteon-hub/ [2245]: https://www.insteon.com/insteon-hub/
[2242]: https://www.insteon.com/support-knowledgebase/2014/9/26/insteon-hub-owners-manual [2242]: https://www.insteon.com/support-knowledgebase/2014/9/26/insteon-hub-owners-manual
### {% linkable_title INSTEON Modem configuration %} ### {% linkable_title INSTEON Modem configuration %}
To set up an INSTEON Powerline Modem (PLM) device such as the [2413U], use the To set up an INSTEON Powerline Modem (PLM) device such as the [2413U], use the following configuration:
following configuration:
```yaml ```yaml
# PLM configuration variables # PLM configuration variables
@ -81,92 +75,111 @@ insteon:
x10_all_lights_on: HOUSECODE x10_all_lights_on: HOUSECODE
x10_all_lights_off: HOUSECODE x10_all_lights_off: HOUSECODE
``` ```
Configuration variables:
- **port** (*Required for PLM setup*): The serial or USB port for your device, {% configuration %}
e.g., `/dev/ttyUSB0` or `COM3` port:
- **host** (*Required for Hub setup*): The host name or IP address of the Hub. description: The serial or USB port for your device, e.g., `/dev/ttyUSB0` or `COM3`.
- **ip_port** (*Optional for Hub setup*): The IP port number of the Hub. For required: Required for PLM setup
Hub model [2245] (i.e. Hub version 2) the default port is 25105. For the Hub type: string
model [2242] (i.e. Hub version 1) the default port is 9761. Use the Insteon host:
app to find the port number for your specific Hub. description: The host name or IP address of the Hub.
- **username** (*Required for Hub version 2 setup*): The username to login in required: Required for Hub setup
to the local Hub. This is required for Hub [2245] (i.e. Hub version 2) setup. type: string
You can find your Hub username on the bottom of the Hub or you can use the ip_port:
Insteon app. description: The IP port number of the Hub. For Hub model [2245] (i.e. Hub version 2) the default port is 25105. For the Hub model [2242] (i.e. Hub version 1) the default port is 9761. Use the Insteon app to find the port number for your specific Hub.
- **password** (*Required for Hub version 2 setup*): The password to login in required: Optional for Hub setup
to the local Hub. This is required for Hub [2245] (i.e. Hub version 2) setup. type: integer
You can find your Hub password on the bottom of the Hub or you can use the username:
Insteon app. description: The username to login in to the local Hub. You can find your Hub username on the bottom of the Hub or you can use the Insteon app.
- **hub_version** (*Required for Hub version 1 setup*): The Hub version number required: Required for Hub version 2 setup
where model [2242] is Hub version 1 and model [2245] is Hub version 2. type: string
(Default is 2) password:
- **device_override** (*Optional*): Override the default device definition description: The password to login in to the local Hub. You can find your Hub password on the bottom of the Hub or you can use the Insteon app.
- *ADDRESS* is found on the device itself in the form 1A.2B.3C or 1a2b3c required: Required for Hub version 2 setup
- *CATEGORY* is found in the back of the device's User Guide in the form of type: string
0x00 - 0xff hub_version:
- *SUBCATEGORY* is found in the back of the device's User Guide in the form description: The Hub version number where model [2242] is Hub version 1 and model [2245] is Hub version 2.
of 0x00 - 0xff required: Required for Hub version 1 setup
- *FIRMWARE* and *PRODUCT_KEY* are more advanced options and will typically default: 2
not be used. type: integer
- **x10_devices** (*Optional*): Define X10 devices to control or respond to device_override:
- *HOUSECODE* is the X10 housecode values a - p description: Override the default device definition.
- *UNITCODE* is the X10 unit code values 1 - 16 required: false
- *PLATFORM* is the Home Assistant Platform to associate the device with. type: list
The following platforms are supported keys:
- binary_sensor: Used for on/off devices or keypad buttons that are read-only. address:
- light: Used for dimmable X10 devices description: is found on the device itself in the form 1A.2B.3C or 1a2b3c.
- switch: Used for On/Off X10 devices required: true
- *STEPS* is the number of dim/bright steps the device supports. Used for type: string
dimmable X10 devices only. Default value is 22. cat:
- **x10_all_units_off** (*Optional*): Creates a binary_sensor that responds description: is found in the back of the device's User Guide in the form of 0x00 - 0xff.
to the X10 standard command for All Units Off. required: false
- **x10_all_lights_on** (*Optional*): Creates a binary_sensor that responds type: integer
to the X10 standard command for All Lights On subcat:
- **x10_all_lights_off** (*Optional*): Creates a binary_sensor that responds description: is found in the back of the device's User Guide in the form of 0x00 - 0xff.
to the X10 standard command for All Lights Off required: false
type: integer
firmware:
description: are more advanced options and will typically not be used.
required: false
type: string
product_key:
description: are more advanced options and will typically not be used.
required: false
type: integer
x10_devices:
description: Define X10 devices to control or respond to.
required: false
type: list
keys:
housecode:
description: is the X10 housecode values a - p
required: true
type: string
unitcode:
description: is the X10 unit code values 1 - 16
required: true
type: integer
platform:
description: "is the Home Assistant Platform to associate the device with. The following platforms are supported: binary_sensor: Used for on/off devices or keypad buttons that are read-only. light: Used for dimmable X10 devices. switch: Used for On/Off X10 devices."
required: true
type: string
dim_steps:
description: is the number of dim/bright steps the device supports. Used for dimmable X10 devices only.
required: false
default: 22
type: integer
x10_all_units_off:
description: Creates a binary_sensor that responds to the X10 standard command for All Units Off.
required: false
type: string
x10_all_lights_on:
description: Creates a binary_sensor that responds to the X10 standard command for All Lights On
required: false
type: string
x10_all_lights_off:
description: Creates a binary_sensor that responds to the X10 standard command for All Lights Off
required: false
type: string
{% endconfiguration %}
### {% linkable_title Autodiscovery %} ### {% linkable_title Autodiscovery %}
The first time autodiscovery runs, the duration may require up to 20 seconds The first time autodiscovery runs, the duration may require up to 20 seconds per device. Subsequent startups will occur much quicker using cached device information. If a device is not recognized during autodiscovery, you can add the device to the **device_override** configuration.
per device. Subsequent startups will occur much quicker using cached device
information. If a device is not recognized during autodiscovery, you can add
the device to the **device_override** configuration.
In order for a device to be discovered, it must be linked to the INSTEON Modem In order for a device to be discovered, it must be linked to the INSTEON Modem as either a responder or a controller.
as either a responder or a controller.
### {% linkable_title Linking Devices to the INSTEON Modem %} ### {% linkable_title Linking Devices to the INSTEON Modem %}
In order for any two Insteon devices to talk with one another, they must be In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Development Tools] service calls. The following services are available:
linked. For an overview of device linking, please read the Insteon page on
[understanding linking]. The Insteon Modem module supports All-Linking through
[Development Tools] service calls. The following services are available:
- **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking - **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking mode. The IM can be set as a controller or a responder. If the IM is a controller, put the IM into linking mode then press the SET button on the device. If the IM is a responder, press the SET button on the device then put the IM into linking mode.
mode. The IM can be set as a controller or a responder. If the IM is a - **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the SET button on the corresponding device to complete the process.
controller, put the IM into linking mode then press the SET button on the - **insteon.load_all_link_database**: Load the All-Link Database for a device. WARNING - Loading a device All-Link database may take a LONG time and may need to be repeated to obtain all records.
device. If the IM is a responder, press the SET button on the device then - **insteon.print_all_link_database**: Print the All-Link Database for a device. Requires that the All-Link Database is loaded first.
put the IM into linking mode. - **insteon.print_im_all_link_database**: Print the All-Link Database for the INSTEON Modem (IM).
- **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an
All-Link record from the All-Link Database of the IM and a device. Once the IM
is set to delete the link, press the SET button on the corresponding device
to complete the process.
- **insteon.load_all_link_database**: Load the All-Link Database for a
device. WARNING - Loading a device All-Link database may take a LONG time and
may need to be repeated to obtain all records.
- **insteon.print_all_link_database**: Print the All-Link Database for a
device. Requires that the All-Link Database is loaded first.
- **insteon.print_im_all_link_database**: Print the All-Link Database for
the INSTEON Modem (IM).
If you are looking for more advanced options, you can use the If you are looking for more advanced options, you can use the [insteonplm_interactive] command line tool that is distributed with the [insteonplm] Python module. Please see the documentation on the [insteonplm] GitHub site. Alternatively, you can download [HouseLinc] which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important.
[insteonplm_interactive] command line tool that is distributed with the
[insteonplm] Python module. Please see the documentation on the [insteonplm]
GitHub site. Alternatively, you can download [HouseLinc] which runs on any
Windows PC, or you can use [Insteon Terminal] which is open source and runs
on most platforms. SmartHome no longer supports HouseLinc, but it still
works. Insteon Terminal is a very useful tool but please read the disclaimers
carefully, they are important.
[understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking [understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking
[Development Tools]: https://www.home-assistant.io/docs/tools/dev-tools/ [Development Tools]: https://www.home-assistant.io/docs/tools/dev-tools/
@ -176,32 +189,20 @@ carefully, they are important.
### {% linkable_title Customization %} ### {% linkable_title Customization %}
The only configuration item that is necessary is the PLM port or Hub IP The only configuration item that is necessary is the PLM port or Hub IP address, username and password so that Home Assistant can connect to the INSTEON Modem. This will expose all the supported INSTEON devices which exist in the modem’s ALL-Link database. However, devices will only be shown by their INSTEON hex address (e.g., “1A.2B.3C”) which can be a bit unwieldy. As you link and unlink devices using the ‘Set’ buttons, they’ll be added and removed from Home Assistant automatically.
address, username and password so that Home Assistant can connect to the
INSTEON Modem. This will expose all the supported INSTEON devices which exist
in the modem’s ALL-Link database. However, devices will only be shown by their
INSTEON hex address (e.g., “1A.2B.3C”) which can be a bit unwieldy. As you link
and unlink devices using the ‘Set’ buttons, they’ll be added and removed from
Home Assistant automatically.
You can use the normal Home Assistant [device customization] section of your You can use the normal Home Assistant [device customization] section of your configuration to assign friendly names and special icons to your devices. This is especially useful for setting device_class on your binary_sensor INSTEON devices.
configuration to assign friendly names and special icons to your devices. This
is especially useful for setting device_class on your binary_sensor INSTEON
devices.
[device customization]: /getting-started/customizing-devices/ [device customization]: /getting-started/customizing-devices/
### {% linkable_title Device Overrides %} ### {% linkable_title Device Overrides %}
INSTEON devices are added to Home Assistant using the platform(s) that make the INSTEON devices are added to Home Assistant using the platform(s) that make the most sense given the model and features of the hardware. The features of the INSTEON devices are built into the Home Assistant platform. Changing the platform is not recommended.
most sense given the model and features of the hardware. The features of the
INSTEON devices are built into the Home Assistant platform. Changing the There are two primary uses for the **device_override** feature:
platform is not recommended. There are two primary uses for the
**device_override** feature. - Devices that do not respond during autodiscovery. This is common for battery operated devices.
- Devices that do not respond during autodiscovery. This is common for battery - Devices that have not been fully developed. This allows an unknown device to be mapped to a device that operates similarly to another device.
operated devices.
- Devices that have not been fully developed. This allows an unknown device to
be mapped to a device that operates similarly to another device.
### {% linkable_title Example Configuration with Options%} ### {% linkable_title Example Configuration with Options%}
@ -226,10 +227,7 @@ insteon:
### {% linkable_title What NOT to do %} ### {% linkable_title What NOT to do %}
Insteon Modem is a top-level component and device discovery will identify Insteon Modem is a top-level component and device discovery will identify the Home Assistant platform the device belongs in. As such, do not declare Insteon devices in other platforms. For example, this configuration will NOT work:
the Home Assistant platform the device belongs in. As such, do not
declare Insteon devices in other platforms. For example, this configuration
will NOT work:
```yaml ```yaml
light: light:
@ -239,26 +237,18 @@ light:
### {% linkable_title Events and Mini-Remotes %} ### {% linkable_title Events and Mini-Remotes %}
Mini-Remote devices do not appear as Home Assistant entities. They generate Mini-Remote devices do not appear as Home Assistant entities, they generate events. The following events are available:
events. The following events are available:
- **insteon.button_on** - **insteon.button_on**
- **address**: (required) The Insteon device address in lower case without - **address**: (required) The Insteon device address in lower case without dots (e.g., 1a2b3c)
dots (e.g., 1a2b3c) - **button**: (Optional) The button id in lower case. For a 4-button remote the values are `a` to `d`. For an 8 button remote the values are `a` to `g`. For a one-button remote this field is not used.
- **button**: (Optional) The button id in lower case. For a 4-button remote
the values are `a` to `d`. For an 8 button remote the values are `a` to `g`. For
a one-button remote this field is not used.
- **insteon.button_of** - **insteon.button_of**
- **address**: (required) The Insteon device address in lower case without - **address**: (required) The Insteon device address in lower case without dots (e.g., 1a2b3c)
dots (e.g., 1a2b3c) - **button**: (Optional) The button id in lower case. For a 4-button remote the values are a to d. For an 8 button remote the values are `a` to `g`. For a one-button remote this field is not used.
- **button**: (Optional) The button id in lower case. For a 4-button remote
the values are a to d. For an 8 button remote the values are `a` to `g`. For
a one-button remote this field is not used.
This allows the mini-remotes to be configured as triggers for automations. Here This allows the mini-remotes to be configured as triggers for automations. Here is an example of how to use these events for automations:
is an example of how to use these events for automations:
``` ```yaml
automation: automation:
# 4 or 8 button remote with button c pressed # 4 or 8 button remote with button c pressed
trigger: trigger:
@ -292,17 +282,10 @@ automation:
### {% linkable_title Known Issues with the INSTEON Hub %} ### {% linkable_title Known Issues with the INSTEON Hub %}
The INSTEON Hub has three known issues that are inherent to the design of the The INSTEON Hub has three known issues that are inherent to the design of the Hub:
Hub:
1. If you see multiple error messages in the log file stating the Hub 1. If you see multiple error messages in the log file stating the Hub connection is closed, and reconnection has failed, this generally requires the Hub to be restarted to reconnect.
connection is closed, and reconnection has failed, this generally requires
the Hub to be restarted to reconnect.
2. You cannot use both Home Assistant and the INSTEON app. If you do, the 2. You cannot use both Home Assistant and the INSTEON app. If you do, the changes made in the app will not appear in Home Assistant. Changes made in Home Assistant will appear in the app after a period of time, however.
changes made in the app will not appear in Home Assistant. Changes made in
Home Assistant will appear in the app after a period of time, however.
3. The Hub response times can be very slow. This is due to the Hub polling 3. The Hub response times can be very slow. This is due to the Hub polling devices frequently. Since only one INSTEON message can be broadcast at a time, messages to and from Home Assistant can be delayed.
devices frequently. Since only one INSTEON message can be broadcast at a time,
messages to and from Home Assistant can be delayed.