mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 07:17:14 +00:00
LiteJet: Add held_more_than and held_less_than options for the automa… (#1463)
* LiteJet: Add held_more_than and held_less_than options for the automation trigger. LiteJet: Fix unrelated documentation details. * LiteJet: Formatting tweak.
This commit is contained in:
parent
a8e5bebb9d
commit
3e563c57da
@ -8,7 +8,7 @@ comments: false
|
|||||||
sharing: true
|
sharing: true
|
||||||
footer: true
|
footer: true
|
||||||
ha_category: Hub
|
ha_category: Hub
|
||||||
ha_iot_class: "Local Polling"
|
ha_iot_class: "Local Push"
|
||||||
ha_release: 0.32
|
ha_release: 0.32
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -27,18 +27,12 @@ Your LiteJet MCP should be configured for 19.2 K baud, 8 data bits, 1 stop bit,
|
|||||||
|
|
||||||
You can also configure the Home Assistant to ignore lights, scenes, and switches via their name. This is highly recommended since LiteJet has a fixed number of each of these and with most systems many will be unused.
|
You can also configure the Home Assistant to ignore lights, scenes, and switches via their name. This is highly recommended since LiteJet has a fixed number of each of these and with most systems many will be unused.
|
||||||
|
|
||||||
```yaml
|
|
||||||
litejet:
|
|
||||||
```
|
|
||||||
|
|
||||||
Configuration variables:
|
Configuration variables:
|
||||||
|
|
||||||
- **port** (*Required*): The path to the serial port connected to the LiteJet.
|
- **port** (*Required*): The path to the serial port connected to the LiteJet.
|
||||||
- **exclude_names** (*Optional*): A list of light or switch names that should be ignored.
|
- **exclude_names** (*Optional*): A list of light or switch names that should be ignored.
|
||||||
- **include_switches** (*Optional*): Cause entities to be created for all the LiteJet switches. Default is `false`. This can be useful when debugging your lighting as you can press/release switches remotely.
|
- **include_switches** (*Optional*): Cause entities to be created for all the LiteJet switches. Default is `false`. This can be useful when debugging your lighting as you can press/release switches remotely.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
litejet:
|
litejet:
|
||||||
exclude_names:
|
exclude_names:
|
||||||
@ -49,3 +43,26 @@ litejet:
|
|||||||
- 'LV Rel #'
|
- 'LV Rel #'
|
||||||
- 'Fan #'
|
- 'Fan #'
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Trigger
|
||||||
|
|
||||||
|
LiteJet switches can be used as triggers too to allow those buttons to behave differently based on hold time. For example, automation can distinguish quick tap versus long hold.
|
||||||
|
|
||||||
|
- **platform** (*Required*): Must be 'litejet'.
|
||||||
|
- **number** (*Required*): The switch number to be monitored.
|
||||||
|
- **held_more_than** (*Optional*): The minimum time the switch must be held before the trigger can activate.
|
||||||
|
- **held_less_than** (*Optional*): The maximum time the switch can be held for the trigger to activate.
|
||||||
|
|
||||||
|
The trigger will activate at the earliest moment both `held_more_than` and `held_less_than` are known to be satisfied. If neither are specified, the trigger activates the moment the switch is pressed. If only `held_more_than` is specified, the trigger will activate the moment the switch has been held down at least that time. If `held_less_than` specified, the trigger can only activate when the switch is released.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
automation:
|
||||||
|
- trigger:
|
||||||
|
platform: litejet
|
||||||
|
number: 55
|
||||||
|
held_more_than:
|
||||||
|
milliseconds: 1000
|
||||||
|
held_less_than:
|
||||||
|
milliseconds: 2000
|
||||||
|
...
|
||||||
|
```
|
||||||
|
Loading…
x
Reference in New Issue
Block a user