jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Remove url prefix pt 2 (#5014)

Browse source 
* Migrate the non blog posts to use no domain

* Update demo links

* Remove Zanzito references from owntracks docs
This commit is contained in:
Paulus Schoutsen 2018-03-24 22:14:34 -07:00 • committed by GitHub
parent d3fc349b50
commit 41955dc31a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
102 changed files with 243 additions and 257 deletions
Download patch file Download diff file Expand all files Collapse all files

6
source/_components/switch.command_line.markdown
View file

@ -40,7 +40,7 @@ Configuration variables:
A note on `friendly_name`:
When set, the `friendly_name` had been previously used for API calls and backend configuration instead of the `object_id` ("identifier"), but [this behavior is changing](https://github.com/home-assistant/home-assistant/pull/4343) to make the `friendly_name` for display purposes only. This allows users to set an `identifier` that emphasizes uniqueness and predictability for API and config purposes but have a prettier `friendly_name` still show up in the UI. As an additional benefit, if a user wanted to change the `friendly_name` / display name (e.g., from "Kitchen Lightswitch" to "Kitchen Switch" or "Living Room Light", or remove the `friendly_name` altogether), he or she could do so without needing to change existing automations or API calls. See aREST device below for an example.
When set, the `friendly_name` had been previously used for API calls and backend configuration instead of the `object_id` ("identifier"), but [this behavior is changing](https://github.com/home-assistant/home-assistant/pull/4343) to make the `friendly_name` for display purposes only. This allows users to set an `identifier` that emphasizes uniqueness and predictability for API and config purposes but have a prettier `friendly_name` still show up in the UI. As an additional benefit, if a user wanted to change the `friendly_name` / display name (e.g., from "Kitchen Lightswitch" to "Kitchen Switch" or "Living Room Light", or remove the `friendly_name` altogether), he or she could do so without needing to change existing automations or API calls. See aREST device below for an example.
## {% linkable_title Examples %}
@ -63,7 +63,7 @@ switch:
friendly_name: Kitchen Lightswitch
```
Given this example, in the UI one would see the `friendly_name` of "Kitchen Light". However, the `identifier` is `arest_pin_four`, making the `entity_id` `switch.arest_pin_four`, which is what one would use in [`automation`](https://home-assistant.io/components/automation/) or in [API calls](https://home-assistant.io/developers/).
Given this example, in the UI one would see the `friendly_name` of "Kitchen Light". However, the `identifier` is `arest_pin_four`, making the `entity_id` `switch.arest_pin_four`, which is what one would use in [`automation`](/components/automation/) or in [API calls](/developers/).
### {% linkable_title Shutdown your local host %}
@ -85,7 +85,7 @@ switch:
### {% linkable_title Control your VLC player %}
This switch will control a local VLC media player ([Source](https://community.home-assistant.io/t/vlc-player/106)).
This switch will control a local VLC media player ([Source](https://community.home-assistant.io/t/vlc-player/106)).
```yaml