Handle StorageError in the Broadlink integration

[felipediel]

Proposed change

In learning mode, devices of type 0x2737, 0x5f36 and RM4 series raise a StorageError when we try to read the code before it is stored in memory. It is simple to deal with this error, we just need to wait and retry.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
script:
  learn_tv_power_button:
    sequence:
      - service: remote.learn_command
        data:
          entity_id: remote.bedroom
          device: tv
          command: power

Additional information

• This PR fixes or closes issue: fixes The device storage is full when trying to learn new codes on broadlink.remote component #35875
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[probot-home-assistant]

Hey there @Danielhiversen, mind taking a look at this pull request as its been labeled with a integration (broadlink) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Should we tag this for a patch release?

[elupus]

Looks good to me

[felipediel]

@MartinHjelmare I think it's a good idea.

[ciumagcatalin]

I am able to replicate this on 0.111.4. I also had same issue on 0.110.2 and I just upgraded.
I have 2 rm mini 3 and one works (it is 3 years old). The new one that I just got does not work.

[ciumagcatalin]

I am able to replicate this on 0.111.4. I also had same issue on 0.110.2 and I just upgraded.
I have 2 rm mini 3 and one works (it is 3 years old). The new one that I just got does not work.

I actually made it work after I put the "type" parameter in the remote and the switch. Not sure why is needed if optional. And the steps was to learn the commands and then add the switch.

[felipediel]

@ciumagcatalin The problem was with your config. It is necessary to inform the type for the latest Broadlink devices (see the troubleshooting section in the docs). Things will get simpler after this PR.