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-23 01:06:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add doc for homekit TV remote key press event (#11382)

Browse Source 
* Add doc for homekit TV remote key press event

* Update source/_integrations/homekit.markdown

Co-authored-by: J. Nick Koston <nick@koston.org>

* ✏️ Tweak

Co-authored-by: J. Nick Koston <nick@koston.org>
Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
This commit is contained in:
Nick Whyte 2020-05-19 23:57:47 +10:00 committed by GitHub
parent 6dcfd81ecc
commit d032beb948
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
source/_integrations/homekit.markdown
View File

@ -479,6 +479,31 @@ The following integrations are currently supported:
| switch | Switch | Represented as a switch by default but can be changed by using `type` within `entity_config`. |
| water_heater | WaterHeater | All `water_heater` devices. |
## iOS Remote Widget
Entities exposed as `TelevisionMediaPlayer` are controllable within the Apple Remote widget in
Control Center. Play, pause, volume up and volume down should work out of the box depending on the `supported_features`
of the entity. However, if your television can be controlled in other ways outside of the `media_player` entity, (i.e.
service calls to an IR blaster), it is possible to build an automation to take advantage of these events.
When a key is pressed within the Control Center Remote widget, the event `homekit_tv_remote_key_pressed` will be fired.
The key name will be available in the event data in the `key_name` field:
```yaml
automation:
trigger:
platform: event
event_type: homekit_tv_remote_key_pressed
event_data:
key_name: arrow_right
# Send the arrow right key via a broadlink IR blaster
action:
service: broadlink.send
host: 192.168.1.55
packet: XXXXXXXX
```
## Troubleshooting
### Resetting when created via YAML