From 574111a72054950ce7de640b01c60b458d35201d Mon Sep 17 00:00:00 2001 From: rafale77 Date: Tue, 14 Aug 2018 02:03:46 +0800 Subject: [PATCH] Update to reflect new pull under review (#5217) * Update to reflect new pull under review Addresses multi-camera setups with naming issues * Update switch.amcrest.markdown * Update switch.amcrest.markdown * :rocket: Trigger rebuild * :pencil2: Tweaks * :pencil2: Rewording --- source/_components/switch.amcrest.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/switch.amcrest.markdown b/source/_components/switch.amcrest.markdown index d9ed4564b22..d494df7b02b 100644 --- a/source/_components/switch.amcrest.markdown +++ b/source/_components/switch.amcrest.markdown @@ -16,3 +16,7 @@ ha_iot_class: "Local Polling" The `amcrest` switch platform lets you control settings of [Amcrest IP Camera](https://home-assistant.io/components/camera.amcrest/) through Home Assistant. Switches will be configured automatically. Please refer to the [component](/components/amcrest/) configuration on how to setup. + +

+In previous versions, switch devices in setups with multiple cameras, would not have specific entity ID causing them to change randomly after each Home Assistant restart. The current version adds the name of the camera at the end of the switch entity ID, making it more specific and consistent and causes the name option to be required in a multi-camera system. This behavior matches the sensor behavior of the Amcrest component. Because of this, older automations may require updates to the entity ID. +