home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.08k stars 31.09k forks source link

Bosch SHC Lights Entities (from Ledvance) not available in HA any more #109788

Closed wsirhc closed 9 months ago

wsirhc commented 9 months ago

The problem

I'm not sure if this issue is related to HA or the Bosch SHC Modules, due to the "boshshcpy"-Module does find all my ledvance lights entities by running the scripts manually. This issue was originally addressed to: https://github.com/tschamm/boschshc-hass/issues/103

Currently using Integration Version 0.4.85.

All Lights Integrations worked well since Juli 2023 and corresponding HA-Version.

What version of Home Assistant Core has the issue?

2024.1.6

What was the last working version of Home Assistant Core?

2023.7

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Bosch SHC

Link to integration documentation on our website

https://www.home-assistant.io/integrations/bosch_shc

Diagnostics information

Already opened an issue in Bosch SHC Git Repo: https://github.com/tschamm/boschshc-hass/issues/103

Example YAML snippet

No response

Anything in the logs that might be useful for us?

RAW-Scan of Bosch SHC Devices using boschshcpy scripts:
{
    "@type": "device",
    "rootDeviceId": "64-da-a0-03-55-30",
    "id": "hdm:ZigBee:0123456789abcdef",
    "deviceServiceIds": [
      "CommunicationQuality",
      "MultiLevelSwitch",
      "HSBColorActuator",
      "BinarySwitch"
    ],
    "manufacturer": "LEDVANCE",
    "roomId": "hz_2",
    "deviceModel": "LEDVANCE_LIGHT",
    "serial": "0123456789ABCFED",
    "profile": "GENERIC",
    "iconId": "icon_ledvance_light_strip",
    "name": "Farbstreifen",
    "status": "AVAILABLE",
    "childDeviceIds": [],
    "supportedProfiles": []
  },
  {
    "@type": "device",
    "rootDeviceId": "64-da-a0-03-55-30",
    "id": "hdm:ZigBee:0123456789abcdef",
    "deviceServiceIds": [
      "CommunicationQuality",
      "HSBColorActuator",
      "MultiLevelSwitch",
      "BinarySwitch"
    ],
    "manufacturer": "LEDVANCE",
    "roomId": "hz_5",
    "deviceModel": "LEDVANCE_LIGHT",
    "serial": "0123456789ABCFED",
    "profile": "GENERIC",
    "iconId": "icon_ledvance_gu10",
    "name": "Terrasse_RGBW",
    "status": "UNAVAILABLE",
    "childDeviceIds": [],
    "supportedProfiles": []
  },
  {
    "@type": "device",
    "rootDeviceId": "64-da-a0-03-55-30",
    "id": "hdm:ZigBee:0123456789abcdef",
    "deviceServiceIds": [
      "CommunicationQuality",
      "MultiLevelSwitch",
      "HSBColorActuator",
      "BinarySwitch"
    ],
    "manufacturer": "LEDVANCE",
    "roomId": "hz_8",
    "deviceModel": "LEDVANCE_LIGHT",
    "serial": "0123456789ABCFED",
    "profile": "GENERIC",
    "iconId": "icon_philips_hue_bulb_a19",
    "name": "Arbeitszimmerlampe",
    "status": "AVAILABLE",
    "childDeviceIds": [],
    "supportedProfiles": []
  }

Additional information

No response

home-assistant[bot] commented 9 months ago

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

Code owner commands Code owners of `bosch_shc` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign bosch_shc` Removes the current integration label and assignees on the issue, 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 issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


bosch_shc documentation bosch_shc source (message by IssueLinks)

joostlek commented 9 months ago

This is an issue in a custom component. We don't do support for custom components.