Add myuplink binary_sensor platform

[astrandb]

Breaking change

Proposed change

Some device_points should be added as binary sensors instead of as ordinary sensors.
This PR will analyze the meta-data from API and if a device_point can have exactly two values (0 or 1) a binary sensor will be created.

Side-effect: The new binary sensors will be accompanied by stale sensors with same name after first run of this version. The user can delete these stale sensors manually from the UI but a better solution would be to delete them automatically.

This is no problem for the platforms that are included in HA 2024.3. After that, there can be stale entities when new platforms are merged or the filtering criteria are changed.

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: Add myuplink binary sensor home-assistant.io#31394

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.

[home-assistant]

Hey there @pajzo, mind taking a look at this pull request as it has been labeled with an integration (myuplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of myuplink can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign myuplink Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[pajzo]

@astrandb just a side note, I'm planning adding system notifications as binary sensor also, but will await this PR to be merged.

[astrandb]

@astrandb just a side note, I'm planning adding system notifications as binary sensor also, but will await this PR to be merged.

Excellent!
The notifications appear on the systemId level and not on the device_id level. Same for hasAlarm and perhaps some more.
Perhaps we should create a System device with the current "Device-devices" linked in the HA device hierarcy. You add a via_device keyword on the "Device-device" device_info attribute.

[MartinHjelmare]

Side-effect: The new binary sensors will be accompanied by stale sensors with same name after first run of this version. The user can delete these stale sensors manually from the UI but a better solution would be to delete them automatically.

We haven't released any entities under the wrong platform yet, as far as I know, so we won't generate any stale entities if we release this approach with matching platforms in the March release.

[astrandb]

That's correct. It is only super-early adopters that are running the dev branch that will see some garbage. But they can cleanup themselves.
I hope that we manage to add binary_sensors and switches and perhaps numbers before March. Climate and select will come later when we have more diagnostic data from other systems.

[MartinHjelmare]

Please add tests or exclude the new modules from coverage calculation via entries in .coveragerc.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[astrandb]

I prefer to wait with the tests until the structure is sorted out according to your comments. Then it will be a breeze to add them.

[MartinHjelmare]

Thanks!