Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Climate schedules don't work with Bosch BTH-RM230Z #386

Open
2 tasks done
klatka opened this issue Nov 3, 2024 · 10 comments
Open
2 tasks done

Climate schedules don't work with Bosch BTH-RM230Z #386

klatka opened this issue Nov 3, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@klatka
Copy link

klatka commented Nov 3, 2024

Checklist

  • I checked for similar existing issues (both open and closed) before posting.
  • I am running the latest version.

Expected behavior

I have some Bosch BTH-RM230Z connected via Zigbee2Mqtt. These are the attributes from one of the Bosch BTH-RM230Z:

hvac_modes: off, heat, cool
min_temp: 4.5
max_temp: 30
target_temp_step: 0.5
current_temperature: 21.7
target_temp_high: 30
target_temp_low: 20
hvac_action: idle
friendly_name: Bodenheizung Wohnbereich
supported_features: 386

I created a schedule to set the target temperature of this climate entity.

Actual behavior

When my schedule is going to be executed the climate does not change the target temperature.

Logger: homeassistant.core
Quelle: core.py:2781
Erstmals aufgetreten: 2. November 2024 um 23:14:01 (6 Vorkommnisse)
Zuletzt protokolliert: 00:00:00

Error executing service: <ServiceCall climate.set_temperature (c:01JBQHPPC2HZTZNQPGXN33279S): temperature=17.0, entity_id=['climate.bosch_room_thermostat_ii_1']>
Error executing service: <ServiceCall climate.set_temperature (c:01JBR2W0G158D4SH2NFT65ZVR5): temperature=21.0, entity_id=['climate.bosch_room_thermostat_ii_1']>
Error executing service: <ServiceCall climate.set_temperature (c:01JBSBQN0BDX2509YYPTD1F0V8): temperature=21.0, entity_id=['climate.bosch_room_thermostat_ii_1']>
Error executing service: <ServiceCall climate.set_temperature (c:01JBSFG7M2Y1Y0AVGQSDM33E1P): temperature=22.0, entity_id=['climate.bosch_room_thermostat_ii_1']>
Error executing service: <ServiceCall climate.set_temperature (c:01JBT43DC1G3BB5E1QWV5R5BKR): temperature=17.0, entity_id=['climate.bosch_room_thermostat_ii_1']>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2781, in _run_service_call_catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 968, in async_service_temperature_set
    raise ServiceValidationError(
homeassistant.exceptions.ServiceValidationError: Set temperature action was used with the target temperature parameter but the entity does not support it
@klatka klatka added the bug Something isn't working label Nov 3, 2024
@nielsfaber
Copy link
Owner

I agree with the error Set temperature action was used with the target temperature parameter but the entity does not support it.
Your climate entity needs to be set with a temperature range (so low + high limit).
I would expect that scheduler card automatically shows such action, can you verify this?

@klatka
Copy link
Author

klatka commented Nov 4, 2024

image
Unfortunately, the card does not give me the option to set a range.

@nielsfaber
Copy link
Owner

I'm seeing the same here. I will have to investigate what causes this.
Note that I noticed you are using scheduler card v3, changes will be made in v4 (which is currently in beta).
In the mean time you can add or modify the built-in action, such that you get sliders for low and high values. Instructions are here: https://github.com/nielsfaber/scheduler-card?tab=readme-ov-file#actions.

@fealXX
Copy link

fealXX commented Nov 19, 2024

I have the same issue in v4.0.0b1 with the BTH-RM230Z - so the new version does not seem to change this behaviour.

(Possibly related? Wrapping the Thermostat in a BT Component works fine. KartoffelToby/better_thermostat#1422 )

@nielsfaber
Copy link
Owner

Note that you can add the missing action to the card manually via yaml as well.
Something like this should work (untested):

type: custom:scheduler-card
# rest of configuration
customize:
  climate.bosch_room_thermostat_ii_1:
    actions:       # add the custom actions
      - service: set_temperature
        service_data:
          hvac_mode: heat_cool
        variables:
          target_temp_low:
            name: "low setpoint"
            min: 4.5
            max: 30
            step: 0.5
            unit: '°C'
          target_temp_high:
            name: "high setpoint"
            min: 4.5
            max: 30
            step: 0.5
            unit: '°C'
        icon: 'hass:fire'
        name: "regulate[ to {target_temp_low}-{target_temp_high}]"

@Branko069
Copy link

@klatka, und funktioniert es ?

Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Dec 29, 2024
@klatka
Copy link
Author

klatka commented Jan 2, 2025

Bump

@github-actions github-actions bot removed the Stale label Jan 3, 2025
Copy link
Contributor

github-actions bot commented Feb 2, 2025

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Feb 2, 2025
@klatka
Copy link
Author

klatka commented Feb 8, 2025

Bump

@github-actions github-actions bot removed the Stale label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants