mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-27 19:26:50 +00:00
Update URLs (#27202)
This commit is contained in:
Sven Serlier
GitHub
parent
a70252be61
commit
773fdd0a4e
@ -15,7 +15,7 @@ ha_codeowners:
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Be aware that `emulated_hue` doesn't work for new users of **Google Home** with `emulated_hue`. If you've not previously set this up and had it working, use the [Google Assistant component](/integrations/google_assistant/) or [Nabu Casa cloud](/integrations/cloud) component.
|
||||
Be aware that `emulated_hue` doesn't work for new users of **Google Home** with `emulated_hue`. If you've not previously set this up and had it working, use the [Google Assistant](/integrations/google_assistant/) integration or [Nabu Casa cloud](/integrations/cloud) integration.
|
||||
|
||||
</div>
|
||||
|
||||
@ -41,13 +41,13 @@ If you added or upgraded to a newer Alexa device and devices are not found, you
|
||||
|
||||
<div class='note'>
|
||||
|
||||
[Sleep Cycle](https://www.sleepcycle.com) and [Sleep as Android](https://sleep.urbandroid.org): smart alarm clock app can use emulated_hue to turn on and off entities. Sleep Cycle only has it implemented in the iOS app, see [Sleep Cycle support](https://support.sleepcycle.com/hc/en-us/articles/207670385-Does-Sleep-Cycle-integrates-with-Phillips-Hue-). The app requires the same configuration as Google Home and does not work if the type is defined as Alexa in the configuration.
|
||||
[Sleep Cycle](https://www.sleepcycle.com) and [Sleep as Android](https://sleep.urbandroid.org): smart alarm clock app can use emulated_hue to turn on and off entities. Sleep Cycle only has it implemented in the iOS app, see [Sleep Cycle support](https://support.sleepcycle.com/hc/articles/207670385-Does-Sleep-Cycle-integrates-with-Phillips-Hue-). The app requires the same configuration as Google Home and does not work if the type is defined as Alexa in the configuration.
|
||||
|
||||
</div>
|
||||
|
||||
<div class='note'>
|
||||
|
||||
Logitech Harmony remotes cannot connect to this emulator via Android and iOS mobile applications because they require the physical button on the hub to be pressed. The [MyHarmony desktop software](https://support.myharmony.com/en-us/download) must be used with the original cable to connect it, then "Scan for Devices".
|
||||
Logitech Harmony remotes cannot connect to this emulator via Android and iOS mobile applications because they require the physical button on the hub to be pressed. The [MyHarmony desktop software](https://support.myharmony.com/download) must be used with the original cable to connect it, then "Scan for Devices".
|
||||
|
||||
</div>
|
||||
|
||||
@ -174,7 +174,7 @@ On Linux systems (Ubuntu, Debian, etc) execute the following command to allow `e
|
||||
sudo setcap 'cap_net_bind_service=+ep' /srv/homeassistant/homeassistant_venv/bin/python3
|
||||
```
|
||||
|
||||
Please note that your path may be different depending on your installation method. For example, if you followed the [Virtualenv instructions](/docs/installation/virtualenv/), your path will be `/srv/homeassistant/bin/python3`.
|
||||
Please note that your path may be different depending on your installation method. For example, if you followed the [Virtualenv instructions](/installation/linux/), your path will be `/srv/homeassistant/bin/python3`.
|
||||
|
||||
### License
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ ha_integration_type: integration
|
||||
|
||||
The [EnOcean](https://en.wikipedia.org/wiki/EnOcean) standard is supported by many different vendors. There are switches and sensors of many different kinds, and typically they employ energy harvesting to get power such that no batteries are necessary.
|
||||
|
||||
The EnOcean integration adds support for some of these devices. You will need a controller like the [USB300](https://www.enocean.com/en/enocean_modules/usb-300/) in order for it to work.
|
||||
The EnOcean integration adds support for some of these devices. You will need a controller like the [USB300](https://www.enocean.com/product/usb-300/) in order for it to work.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -44,7 +44,7 @@ The following devices have been confirmed to work out of the box:
|
||||
- EnOcean STM-330 temperature sensor
|
||||
- Hoppe SecuSignal window handle from Somfy
|
||||
|
||||
If you own a device not listed here, please check whether your device can talk in one of the listed [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) (EEP). If it does, it will most likely work. The available profiles are usually listed somewhere in the device manual.
|
||||
If you own a device not listed here, please check whether your device can talk in one of the listed [EnOcean Equipment Profiles](https://www.enocean-alliance.org/specifications/) (EEP). If it does, it will most likely work. The available profiles are usually listed somewhere in the device manual.
|
||||
|
||||
Support for tech-in messages is not implemented.
|
||||
|
||||
@ -58,10 +58,10 @@ This can typically be one of those batteryless wall switches.
|
||||
Tested with:
|
||||
|
||||
- Eltako FT55 which uses the EnOcean PTM 215 module
|
||||
- [TRIO2SYS Wall switches](https://www.trio2sys.fr/index.php/fr/produits-enocean-sans-fil-sans-pile-interoperable/emetteur-sans-fils-sans-pile-interoperable-enocean) which uses the EnOcean PTM210 DB module
|
||||
- [TRIO2SYS Wall switches](https://www.trio2sys.fr/index.php/produits-enocean-sans-fil-sans-pile-interoperable/emetteur-sans-fils-sans-pile-interoperable-enocean) which uses the EnOcean PTM210 DB module
|
||||
- Omnio WS-CH-102
|
||||
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) are supported:
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/specifications/) are supported:
|
||||
|
||||
- F6-02-01 (Light and Blind Control - Application Style 2)
|
||||
- F6-02-02 (Light and Blind Control - Application Style 1)
|
||||
@ -107,7 +107,7 @@ Sample automation to switch lights on and off:
|
||||
```yaml
|
||||
# Example automation to turn lights on/off on button release
|
||||
automation:
|
||||
- alias: "hall light switches"
|
||||
- alias: "Hall light switches"
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: button_pressed
|
||||
@ -122,7 +122,7 @@ automation:
|
||||
|
||||
{% endraw %}
|
||||
|
||||
You can find the `event_data` `id` by going to "Developer Tools" -> "Events" and listening to “button_pressed” events. Then hit a button on the device and you should see an event.
|
||||
You can find the `event_data` `id` by going to {% my developer_events title="Developer Tools -> Events" %} and listening to “button_pressed” events. Then hit a button on the device and you should see an event.
|
||||
|
||||
## Light
|
||||
|
||||
@ -207,7 +207,7 @@ sensor:
|
||||
|
||||
### Humidity sensor
|
||||
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) are supported:
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/specifications/) are supported:
|
||||
|
||||
- Any profile that contains the humidity value at position **DB2.7** to **DB2.0**
|
||||
- **A5-04-01** - Temp. and Humidity Sensor, Range 0°C to +40°C and 0% to 100%
|
||||
@ -229,7 +229,7 @@ sensor:
|
||||
|
||||
This sensor has been tested with a generic STM-330 sensor, which is used in most indoor temperature sensor devices.
|
||||
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) are supported:
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/specifications/) are supported:
|
||||
|
||||
- Any profile that contains an 8-bit temperature at position DB1.7 to DB1.0. 10-bit is not supported.
|
||||
- **A5-02-01** to **A5-02-1B** - Temperature Sensor with various temperature ranges
|
||||
|
||||
@ -14,7 +14,7 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Global Caché [GC-100](https://www.globalcache.com/products/gc-100/) can be integrated into Home Assistant. GC-100 is a TCP-controllable
|
||||
The Global Caché GC-100 can be integrated into Home Assistant. GC-100 is a TCP-controllable
|
||||
hardware device which has an array of relays, RS232 serial ports, and flexible ports which can be programmed to be either digital inputs or IR blaster outputs. There are a variety of submodels of the GC-100 which have different amounts of each I/O type.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -11,9 +11,9 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `itach` remote platform allows you to control IR devices with a [Global Caché iTach Device](https://www.globalcache.com/products/itach/ip2irspecs) and GC-100 devices. The Global Cache IR API are similar across their product line. See API documentation links at the end of this page.
|
||||
The `itach` remote platform allows you to control IR devices with a Global Caché iTach Device and GC-100 devices. The Global Cache IR API are similar across their product line. See API documentation links at the end of this page.
|
||||
|
||||
In order to utilize the digital input (binary sensor) and relay (switch) features of your Global Cache device you will need to use the [gc100 component](/integrations/gc100) and associated platforms.
|
||||
In order to utilize the digital input (binary sensor) and relay (switch) features of your Global Cache device you will need to use the [gc100 integration](/integrations/gc100) and associated platforms.
|
||||
|
||||
To use your iTach remote in your installation, you will need to know the IR commands for your devices in Pronto hex format and add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -57,7 +57,7 @@ device_names:
|
||||
required: false
|
||||
type: string
|
||||
name:
|
||||
description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.<name>`. The name will default to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details.
|
||||
description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.<name>`. The name will default to `notify` if not supplied. See the [Notifications integration](/integrations/notify) for more details.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -100,7 +100,7 @@ This example also uses the [matrix `notify` platform](#notifications).
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
# The Matrix component
|
||||
# The Matrix integration
|
||||
matrix:
|
||||
homeserver: https://matrix.org
|
||||
username: "@my_matrix_user:matrix.org"
|
||||
@ -155,7 +155,7 @@ This configuration will:
|
||||
|
||||
The `matrix` platform allows you to deliver notifications from Home Assistant to a [Matrix](https://matrix.org/) room. Rooms can be both direct as well as group chats.
|
||||
|
||||
To enable Matrix notifications in your installation, you first need to configure the [Matrix component](#configuration). Then, add the following to your `configuration.yaml` file:
|
||||
To enable Matrix notifications in your installation, you first need to configure the [Matrix integration](#configuration). Then, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user