Broadlink Switch - Use entity_id instead of friendly_name for entity_id

[timmo001]

Description:

The current version of this component uses the friendly_name instead of the set entity_id as set in the config. This fixes this issue. In the example, the entity_id would be 'tv_phillips' and the friendly_name 'Phillips TV Power'.

Example entry for configuration.yaml (if applicable):

switch:
  - platform: broadlink
    host: 192.168.1.2
    mac: 'B4:43:0D:CC:0F:58'
    timeout: 15
    switches:
      tv_phillips:
        friendly_name: "Phillips TV Power"
        command_on: 'JgAcAB0dHB44HhweGx4cHR06HB0cHhwdHB8bHhwADQUAAAAAAAAAAAAAAAA='
        command_off: 'JgAaABweOR4bHhwdHB4dHRw6HhsdHR0dOTocAA0FAAAAAAAAAAAAAAAAAAA='

Breaking Change

Users who were using this switch with the entity_id and the friendly_name as different names will need to update their automations/groups to use the entity_id instead of the friendly_name.

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

[VDRainer]

Fixes issue #11628

[VDRainer]

Why label "docs-missing"?
I think the docs are correct when this PR is merged.

[Danielhiversen]

Yes, you are right.
But we need a breaking-change note, that describes how the user should update the config

[timmo001]

See updated description. Is this what you needed?

[Danielhiversen]

👍

[Yonsm]

class BroadlinkSP1Switch(BroadlinkRMSwitch):
...
super().init(friendly_name, device, None, None) # Case an error (missing one param) on:

switch:

• platform: broadlink
  host: 192.168.1.20
  mac: 34:EA:34:B8:36:AC
  friendly_name: Outlet
  type: spmini2

[Danielhiversen]

This is already merged, so please open an issue.