Homematic weird bug with HA automation

Third party integrations
1

I am trying to change different profiles with home assistant on my thermostats.

I use the following code:

service: homematic.set_device_value
data:
  address: INT0000001
  channel: 1
  param: ACTIVE_PROFILE
  value: '1'
  value_type: int

This works well. But now things get weird:
When trying to change the active profile via an automation, changing into active_profile ‘1’ will result the change of modes from ‘auto’ to ‘manual’ wihtin the thermostat. This ONLY happens when the service is called from the automation, not from the developer tools or when changing profiles from within the CCU.

automation:

alias: Heizung Auto-Profil (CCU)
description: Schaltet die Heizung auf Auto/Profil 1(CCU)
trigger:
  - platform: state
    entity_id: binary_sensor.people_away
    to: 'on'
    for:
      hours: 0
      minutes: 0
      seconds: 0
  - platform: state
    entity_id: input_boolean.away_mode
    to: 'off'
condition:
  - condition: and
    conditions:
      - condition: state
        entity_id: input_boolean.away_mode
        state: 'off'
      - condition: state
        entity_id: binary_sensor.people_away
        state: 'on'
      - condition: state
        entity_id: input_boolean.guest_mode
        state: 'off'
action:
  - service: homematic.set_device_value
    data:
      address: INT0000001
      channel: 1
      parameter: ACTIVE_PROFILE
      value: '1'
      value_type: int
mode: single

I also do not know where to report this bug.

2

@danielperna84 can you help answering this?

3

Nope. I don’t use such automations.

That being said, from my experience thermostats behave weird and inconsistent even within the CCU. IIRC old RF thermostats do things differently than IP thermostats when controlled via the CCU.

The main problem is, that for some thermostats you have to switch to manual mode before you can perform certain tasks, and for others you don’t. It always works when switching to manual I believe, which is why it’s implemented that way. Removing that switch to manual mode therefore would break other thermostats that depend on this.

I don’t understand though why it’s doing things differently depending on the source of the change. What I have explained above is actually more related to turning the climate entity on or off via the corresponding services. Using homematic.set_device_value is internally different than e.g. climate.turn_on. The latter probably is doing the switch to manual.

4

It turned out that - for what ever reason - raspberrymatic/the device was having issues. The group settings (and later also device settings) were not correctly applied to the device - I figured that my observered issue could be related to that, restarted raspberrymatic and removed the group and added the device to a new group - now everything seems to be working as expected.

Thanks for the help.