RTH2 thermostat does not appear as a device

[mgherzan]

The problem

The RTH2 room thermostat is properly exposed in over the REST API (tested with Postman) but does not appear as a device in HomeAssistant, even after multiple reloads of the plugin.

    {
        "@type": "device",
        "rootDeviceId": "64-da-a0-40-b0-c5",
        "id": "hdm:ZigBee:001e5e090290fb8e",
        "deviceServiceIds": [
            "CommunicationQuality",
            "Thermostat",
            "BatteryLevel",
            "DisplayConfiguration",
            "TemperatureLevel",
            "HumidityLevel",
            "TerminalConfiguration",
            "Linking",
            "TemperatureOffset"
        ],
        "manufacturer": "BOSCH",
        "roomId": "hz_1",
        "deviceModel": "RTH2_BAT",
        "serial": "001E5E090290FB8E",
        "profile": "GENERIC",
        "name": "BoschTherno1",
        "status": "AVAILABLE",
        "parentDeviceId": "roomClimateControl_hz_1",
        "childDeviceIds": [],
        "supportedProfiles": []
    },

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-12-02 23:23:13.859 DEBUG (SyncWorker_7) [boschshcpy] Obtain unique_id for 'shc40b0c5' via zeroconf: '64-da-a0-40-b0-c5'
2023-12-02 23:23:13.875 DEBUG (SyncWorker_9) [boschshcpy] Obtain unique_id for 'shc40b0c5' via zeroconf: '64-da-a0-40-b0-c5'
2023-12-02 23:23:13.956 DEBUG (SyncWorker_7) [boschshcpy] Skipping device id ventilationService which has no services that are supported by this library
2023-12-02 23:23:13.956 DEBUG (SyncWorker_7) [boschshcpy] Skipping device id hdm:PhilipsHueBridge:PhilipsHueBridgeManager which has no services that are supported by this library
2023-12-02 23:23:14.232 DEBUG (SHCPollingThread) [boschshcpy] Subscribed for long poll. Poll id: faknkhdci-33
2023-12-02 23:26:35.768 DEBUG (SHCPollingThread) [boschshcpy] Long poll: {'path': '/devices/hdm:ZigBee:18fc2600000a1737/services/TemperatureLevel', '@type': 'DeviceServiceData', 'id': 'TemperatureLevel', 'state': {'@type': 'temperatureLevelState', 'temperature': 21.2}, 'deviceId': 'hdm:ZigBee:18fc2600000a1737'}
2023-12-02 23:26:38.847 DEBUG (SHCPollingThread) [boschshcpy] Long poll: {'path': '/devices/hdm:ZigBee:001e5e090290fb8e/services/HumidityLevel', '@type': 'DeviceServiceData', 'id': 'HumidityLevel', 'state': {'@type': 'humidityLevelState', 'humidity': 41.81}, 'deviceId': 'hdm:ZigBee:001e5e090290fb8e'}
2023-12-02 23:26:38.902 DEBUG (SHCPollingThread) [boschshcpy] Long poll: {'iconId': 'icon_room_bathroom', 'extProperties': {'humidity': '41.81'}, '@type': 'room', 'name': 'Badezimmer', 'id': 'hz_1'}

Additional information

No response

[home-assistant[bot]]

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)}}

[tschamm]

The RTH2 devices are only supported in the custom component, you can install that via HACS.

[hbast]

The RTH2 devices are only supported in the custom component, you can install that via HACS.

Is there a tutorial for this, or can you please give me a tip on how it works?

[mgherzan]

The custom component works indeed like a charm, so many thanks for that! But it is a bit bitter that such a significant manufacturer does not invest effort/resources into a "proper"/official/non-HACS integration.