unknown preset if switching the Thermostat from manual to Auto

[fft1010]

I agree to the following

• I have read the documentation right now
• I have read the FAQs right now
• I am aware of the latest release notes
• I am aware that an integration that was installed via HACS also needs to be updated via HACS
• The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
• I am running the latest version of the custom_component (and Home Assistant)

The problem

Hi,
I installed raspimatic and made the thermostat available. It has schedules, which can be accessed thru Rasperrymatic.

I can also access the thermostat as a climate from HomeAssitant. See

It works in Manual Heating mote, it also show changes from the thermostat. My only problem is, that when I switch from Manual to "Automatic", it show the error as seen in the screenshot.
Sorry for german
Die Voreinstellung ist ungültig. Gültige Voreinstellungen sind: boost, none, week_program_1, ... _3. Default seems to be WP 1

I just tried the dropdown to "boot" and "Ohne" WP 1, WP 2, WP 3 manually by selecting them, and than they work.

What version of HomematicIP (local) has the issue?

1.67.0

What was the last working version of HomematicIP (local)?

No response

What type of installation are you running?

Home Assistant OS

What type of installation are you running for your homematic backend?

RaspberryMatic Standalone

Which version of your homematic backend are you running?

3.77.7.20240826

What hardware are you running for your system?

Pi5

Which config details do you use

• TLS
• callback data (see)

Which interfaces do you use?

• Homematic IP
• Homematic (Bidcos-RF)
• Groups (Heating-Group)
• BidCos-Wired (HM-Wired)

Diagnostics information (no logs here)

config_entry-homematicip_local-01JAFDQ4HP2TAR20YQNR3D4NV1.json
``

Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!

Same as in the screenshot, exept it's english :-)

2024-10-21 21:23:38.243 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806254500304] Preset mode  is not valid. Valid preset modes are: boost, none, week_program_1, week_program_2, week_program_3
2024-10-21 21:23:57.492 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806254500304] Preset mode  is not valid. Valid preset modes are: boost, none
2024-10-21 21:23:57.600 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806254500304] Preset mode week_program_1 is not valid. Valid preset modes are: boost, none
2024-10-21 21:23:57.677 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806254500304] Preset mode  is not valid. Valid preset modes are: boost, none, week_program_1, week_program_2, week_program_3
2024-10-21 21:24:38.849 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806254500304] Preset mode  is not valid. Valid preset modes are: boost, none, week_program_1, week_program_2, week_program_3
2024-10-21 21:24:39.035 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806254500304] Preset mode  is not valid. Valid preset modes are: boost, none, week_program_1, week_program_2, week_program_3
2024-10-22 05:27:44.487 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806253393248] Preset mode  is not valid. Valid preset modes are: boost, none, week_program_1, week_program_2, week_program_3
2024-10-22 05:28:05.170 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139806253393248] Preset mode  is not valid. Valid preset modes are: boost, none, week_program_1, week_program_2, week_program_3

Additional information

No response

[SukramJ]

Hierzu gibt es bereits eine Discussion #1452
Letztendlich ist das ein Problem im Frontend.

[fft1010]

Hi @SukramJ ,
schwierig für mich zu beurteilen, da in der config nix steht, was ich dem Fehler zuordnen kann

type: thermostat
entity: climate.hmip_etrv_2_i9f_00395f29b18802
show_current_as_primary: true
name: HoOf Thermometer Jürgen
features:
  - type: climate-preset-modes
    style: dropdown
  - type: climate-hvac-modes

Oder "isso" und man kann da nix machen bis dbuezas/eq3btsmart#104 gefixt ist?

Viele Grüße
Juergen

[SukramJ]

Also das referenzierte Issue hat nix damit zu tun.
Diesen Fehler gibt es schon sehr lange und über verschieden Integrationen hinweg.
Ich kann da nichts machen, da es ein Frontend issue ist, wie bereits in der Discussion referenziert.