Z2M & Bosch Radiator II - Automations - What am i missing?

Hi everyone,

after hours of struggling i’m doubting myself…

Following setup:

  • Dockerized Z2M
    SkyConnect Dongle
    Zigbee2MQTT version [1.40.2]
    Coordinator type: EZSP v9
    Coordinator revision: 7.1.1.0 build 273
    Coordinator IEEE Address: 0xbc026efffe2346ce
    Frontend version: 0.7.4
    zigbee-herdsman-converters version: 20.21.0
    zigbee-herdsman version: 2.1.3
  • Dockerized Home Assistant 2024.10.2

I’m trying to include Bosch Radiator Thermostat II.

So far, everything is working fine (Radiators are found in Z2M, updated with firmware, integrated into HA), completely usable from HA Dashboard - except for the automations… Here i can set the Boost mode or child lock - working fine. But i can’t find the right option from the dropdown for setting a specific temperature, I’ve searched through every option for reasonable name/values etc. What am i doing wrong? What connecting dot’s of knowledge am i missing?

Following yaml is created:

alias: Set temperature
description: ""
triggers:
  - trigger: time
    at: "21:18:00"
conditions: []
actions:
  - device_id: f12bb995c034aa9f38e86d0dde14c2d5
    domain: number
    entity_id: 60d7eec0b943005529814ae7778d6ecf
    type: set_value
    value: 20
mode: single

Also the yaml seems a bit strange with the device id/entity id.
I’m still new to HA and need to get used to the structure/mapping etc.
Is there a option to have the entity_id and device_id human readable?

Hi, so you got yours integrated into HA via the skyconnect dongle, interesting. Mine won’t complete the interview on a Sonoff ZBDongle-E, and I already tested dockerised Z2M as well as ZHA and it was the same.

I’d try a skyconnect dongle, except they are all out of stock.

I checked your thread, no tips that i can derive from my problems sadly…
Only one information, in the Z2M sometimes the interview is not reliable as well.

I had it on ZHA before i migrated to Z2M - worked quite well to be honest. But it was lacking the update of the device firmwware and additional features…

1 Like

I was just stupid, thinking i needed to set it up on the device itself, instead of using the own action HA provides…

In case someone else is questioning this:

alias: Heizung Mo-Fr 06:30 an
description: ""
triggers:
  - at: "06:30:00"
    trigger: time
conditions:
  - condition: time
    weekday:
      - mon
      - tue
      - wed
      - thu
      - fri
actions:
  - data:
      temperature: 20
    target:
      device_id:
        - 9ded9b79e010168655f417a592ac1d92
        - fd48f935e86c2e74ff91754486c7dd1e
    action: climate.set_temperature
mode: single