Block older versions of custom integration mydolphin_plus since they cause crashes

[bdraco]

Proposed change

Block older versions of custom integration mydolphin_plus since they cause crashes

sh00t2kill/dolphin-robot#185

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)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[elad-bar]

It's kind of strong to say it crashes when in fact all post in issues are about disconnection of the broker without reconnect

[bdraco]

We could change it to "performs non-thread-safe operations which may cause a crash" but I don't think users will understand what that means

[TheJulianJES]

The initial post in the linked issue also mentions that it's causing a crash for them eventually. So, crashes do seem to actively happen because of the non-thread-safe operations.

[elad-bar]

complaints are about crashes that being reported when ppl were asked what exactly happens they wrote that the connection is fetting lost, there is an issue caused by unsafe thread failure, but it doesn't crash the HA,
In v1.0.11 it could crash, but since 1.0.12 it was about lost connection without ability to recover it up until reload integration,
1.0.12 was released short after HA demanded to change the code with the threadsafe (which is totally make sense).

[bdraco]

What is the lowest version number where all thread safety and connection issues are fixed?

[elad-bar]

v1.0.12

[bdraco]

That doesn't seem correct since there is a change from async_dispatcher_send to dispatcher_send in https://github.com/sh00t2kill/dolphin-robot/releases/tag/v1.0.13 sh00t2kill/dolphin-robot@v1.0.12...v1.0.13#diff-828cb7ff01d2f3c404ae9d5309c114cba3785865a6bfa12fadde36473eedeeafR658

[frenck]

Thanks, @bdraco 👍

../Frenck