Skip to content

Add ELV-SH-SB8 Status Board switch support to homematicip_cloud#161668

Draft
lackas wants to merge 2 commits intohome-assistant:devfrom
lackas:add-hmip-sb8-switch
Draft

Add ELV-SH-SB8 Status Board switch support to homematicip_cloud#161668
lackas wants to merge 2 commits intohome-assistant:devfrom
lackas:add-hmip-sb8-switch

Conversation

@lackas
Copy link
Contributor

@lackas lackas commented Jan 27, 2026

Proposed change

Add switch entity support for the ELV-SH-SB8 Status Board device. This device has 8 SWITCH_CHANNEL outputs that control LEDs for visual status indication.

The device uses the same channel structure as the existing OpenCollector8Module (HMIP-MOD-OC8), so it is added to the existing multi-switch isinstance check.

Note: This PR depends on homematicip-rest-api PR hahn-th/homematicip-rest-api#622 being merged first.

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

Checklist

  • I understand the code I am submitting and can explain how it works.
  • 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.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

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

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

Adds support for the ELV-SH-SB8 Status Board (8 LED outputs).
Each LED is exposed as a switch entity.

Depends on homematicip-rest-api PR home-assistant#622.
- Add test fixture with 2 switch channels
- Add test_hmip_status_board_switch test
@home-assistant
Copy link

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

Code owner commands

Code owners of homematicip_cloud 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 homematicip_cloud 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, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

@epenet epenet added waiting-for-upstream We're waiting for a change upstream and removed waiting-for-upstream We're waiting for a change upstream labels Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants