mirror of
https://github.com/home-assistant/core.git
synced 2025-06-24 23:17:08 +00:00
2109b7a1b9
* Use entity_id for backend, friendly name for frontend Closes https://github.com/home-assistant/home-assistant/issues/3434 Command line switches had the option to set a `friendly_name` reportedly for use in the front end. However, if set, it was also being used as the `entity_id`. This did not seem like obvious behavior to me. This PR changes the behavior so the entity_id is the object_id, which must already be unique, and is an obvious place to have a very predictable slug (even if long or unsightly), and the friendly name (if set) is used for the display. Example: ```yaml switch: platform: command_line switches: rf_kitchen_light_one: command_on: switch_command on kitchen command_off: switch_command off kitchen command_state: query_command kitchen value_template: '{{ value == "online" }}' friendly_name: "Beautiful bright kitchen light!" ``` If you were using in an automation or from dev tools, would use: `switch.rf_kitchen_light_one`, but your front end would still show `Beautiful bright kitchen light!` * Add new arg to test_assumed_state_should_be_true_if_command_state_is_false * Import ENTITY_ID _FORMAT from existing, rename device_name to object_id * Rename `device_name` to `object_id` * Test that `entity_id` and `name` are set as expected