From 8861a897329df38601b2b2da16b2100154f9655d Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Mon, 12 Oct 2020 07:52:38 -0400 Subject: [PATCH] Update to new names of renamed config panels (#15197) These were renamed quite some time ago, but found a few older references and updated them. Entity Registry -> Entities Area Registry -> Areas Customization -> Customizations Development Tools -> Developer Tools --- source/_docs/configuration/customizing-devices.markdown | 2 +- source/_integrations/config.markdown | 6 +++--- source/_integrations/denonavr.markdown | 2 +- source/_integrations/insteon.markdown | 8 ++++---- source/_integrations/konnected.markdown | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index 21f5ec32f87..eaa60e43981 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -20,7 +20,7 @@ By default, all of your devices will be visible and have a default icon determin ### Customization using the UI -Under the *Configuration* menu you'll find the *Customization* menu. If this menu item is not visible, enable advanced mode on your [profile page](/docs/authentication/#your-account-profile) first. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). You may also need to add the following to your `configuration.yaml` file, depending when you started using Home Assistant: +Under the *Configuration* menu you'll find the *Customizations* menu. If this menu item is not visible, enable advanced mode on your [profile page](/docs/authentication/#your-account-profile) first. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). You may also need to add the following to your `configuration.yaml` file, depending when you started using Home Assistant: ```yaml homeassistant: diff --git a/source/_integrations/config.markdown b/source/_integrations/config.markdown index 26f1f8a16f0..52e9604fffe 100644 --- a/source/_integrations/config.markdown +++ b/source/_integrations/config.markdown @@ -44,11 +44,11 @@ This section enables you to control Home Assistant from within Home Assistant. C This section enables you to associate users with their device tracker entities using the person component. -### Entity Registry +### Entities This section enables you to override the name, change the entity ID or disable an entity in Home Assistant. -### Area Registry +### Areas This section enables you to organize entities to physical areas of your home. @@ -64,6 +64,6 @@ Similar to the automation editor, this section enables you to create and modify This section enables you to control your Z-Wave network and devices from within Home Assistant. You can add and remove devices, as well as change device specific configuration variables. -### Customization +### Customizations This section enables you to customize entities within Home Assistant. Use this to set friendly names, change icons, and modify other attributes. diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index ed24723bf80..eadf88edef6 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -97,7 +97,7 @@ A few notes: - The `denonavr` platform supports some additional functionalities like album covers, custom input source names and auto discovery. - Marantz receivers seem to a have quite a similar interface. Thus if you own one, give it a try. - To remotely power on Marantz receivers with Home Assistant, the Auto-Standby feature must be enabled in the receiver's settings. -- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under "Development Tools/States" in the front panel. +- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under **Developer Tools** -> **States**. #### Service `denonavr.get_command` diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index a6928543e7b..4fedce8b697 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -48,7 +48,7 @@ In order for a device to be discovered, it must be linked to the INSTEON Modem a ## Linking Devices to the INSTEON Modem -In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Development Tools] service calls. The following services are available: +In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Developer Tools] service calls. The following services are available: - **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking mode. The IM can be set as a controller or a responder. If the IM is a controller, put the IM into linking mode then press the SET button on the device. If the IM is a responder, press the SET button on the device then put the IM into linking mode. - **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the SET button on the corresponding device to complete the process. @@ -59,7 +59,7 @@ In order for any two Insteon devices to talk with one another, they must be link If you are looking for more advanced options, you can use the [insteon_tools] command-line tool that is distributed with the [pyinsteon] Python module. Please see the documentation on the [pyinsteon] GitHub site. Alternatively, you can download [HouseLinc], which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important. [understanding linking]: https://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking -[Development Tools]: /docs/tools/dev-tools/ +[Developer Tools]: /docs/tools/dev-tools/ [HouseLinc]: https://www.smarthome.com/houselinc.html [Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal [insteon_tools]: https://github.com/pyinsteon/pyinsteon @@ -285,7 +285,7 @@ In order for a device to be discovered, it must be linked to the INSTEON Modem a ### Linking Devices to the INSTEON Modem -In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Development Tools] service calls. The following services are available: +In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Developer Tools] service calls. The following services are available: - **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking mode. The IM can be set as a controller or a responder. If the IM is a controller, put the IM into linking mode then press the SET button on the device. If the IM is a responder, press the SET button on the device then put the IM into linking mode. - **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the SET button on the corresponding device to complete the process. @@ -296,7 +296,7 @@ In order for any two Insteon devices to talk with one another, they must be link If you are looking for more advanced options, you can use the [insteon_tools] command line tool that is distributed with the [pyinsteon] Python module. Please see the documentation on the [pyinsteon] GitHub site. Alternatively, you can download [HouseLinc] which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important. [understanding linking]: https://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking -[Development Tools]: /docs/tools/dev-tools/ +[Developer Tools]: /docs/tools/dev-tools/ [HouseLinc]: https://www.smarthome.com/houselinc.html [Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal [insteon_tools]: https://github.com/pyinsteon/pyinsteon diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown index f0b53a5148e..3f853699c9b 100644 --- a/source/_integrations/konnected.markdown +++ b/source/_integrations/konnected.markdown @@ -305,7 +305,7 @@ konnected: ## Unique IDs and the Entity Registry -Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI on the _Entity Registry_ page (under _Configuration_). +Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Configuration** -> **Entities**. Unique IDs are internally generated as follows: