From 0253fb5738ea045ddcdddc524d0a4d77ec2d8afc Mon Sep 17 00:00:00 2001 From: MrMep Date: Fri, 30 Dec 2016 20:40:41 +0100 Subject: [PATCH] Update keyboard_remote.markdown (#1677) The option name is "type", not "key_value", see source. --- source/_components/keyboard_remote.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/keyboard_remote.markdown b/source/_components/keyboard_remote.markdown index f5fdf73b1e0..62dd5844035 100644 --- a/source/_components/keyboard_remote.markdown +++ b/source/_components/keyboard_remote.markdown @@ -24,13 +24,13 @@ The `evdev` package is used to interface with the keyboard and thus this is Linu # Example configuration.yaml entry keyboard_remote: device_descriptor: '/dev/input/by-id/foo' - key_value: 'key_up' + type: 'key_up' ``` Configuration variables: - **device_descriptor** (*Required*): List of URLS for your feeds. -- **key_value** (*Required*): Possible values are `key_up`, `key_down`, and `key_hold`. Be careful, `key_hold` will fire a lot of events. +- **type** (*Required*): Possible values are `key_up`, `key_down`, and `key_hold`. Be careful, `key_hold` will fire a lot of events. And an automation rule to breathe life into it: