Add the service lock.open to the docs (#7419)

It is implemented, so probably it should be documented.
This commit is contained in:
Luis Martinez de Bartolome Izquierdo 2018-12-05 08:45:40 +01:00 committed by Franck Nijhof
parent b3acc596ea
commit 128e14809e

View File

@ -12,7 +12,7 @@ footer: true
Keeps track which locks are in your environment, their state and allows you to control them. Keeps track which locks are in your environment, their state and allows you to control them.
* Maintains a state per lock and a combined state `all_locks`. * Maintains a state per lock and a combined state `all_locks`.
* Registers services `lock.lock` and `lock.unlock` to control locks. * Registers services `lock.lock`, `lock.unlock` and `lock.open` (unlatch) to control locks.
### {% linkable_title Services %} ### {% linkable_title Services %}
@ -54,7 +54,7 @@ action:
### {% linkable_title Use the services %} ### {% linkable_title Use the services %}
Go to the **Developer Tools**, then to **Call Service** in the frontend, and choose `lock.lock` or `lock.unlock` from the list of available services (**Services:** on the left). Enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**. Go to the **Developer Tools**, then to **Call Service** in the frontend, and choose `lock.lock`, `lock.unlock` or `lock.open` from the list of available services (**Services:** on the left). Enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
```json ```json
{"entity_id":"lock.front_door"} {"entity_id":"lock.front_door"}