"valves_unsupported":[
"climate.bathroom_floor_heating"
],
What hvac modes does this climate entity support? It’s listed under unsupported.
It doesn’t seem to support any
Would it be possible to ignore the hvac_mode, and just set the temperature ?
or can I add hvac_modes to my thermostat?
Is this a generic thermostat (then yes) or is it an entity of an integration?
Strange… I just found this. Maybe you should open an issue in the home assistant github repo. You need at least off and heat.
Thanks, I’ve opened a issue: Tuya Integration is missing hvac_modes · Issue #129903 · home-assistant/core · GitHub
1 Like
yes its all logical :)…but normaly the the temp at the thermostat rises faster than in the room, so the Calibrated target temp should change during heating im right? In my case its constant, equal if the diff (room-thermostat) is 4 (directly after window is closed in the morning) or -3 (after heating a while)!
1 Like
i have 2 tuya thermostats (wifi) and they work fine!
Did you connect them through Tuya Integration ?
I specifically have this brand: MAGNUM Remote Control - Magnum Heating
Maybe you let it work for some time an have a look hat your history graph. Select temperature sensor, climate and your window entity.
yes i connected them through the tuya integration! TRV801w
The only thing is, that they have “heat_cool” instead of “heat” as HVAC mode!
You mean like this?
The red marked areas is the heating in the morning, where yellow is the target temp, blue the temp at the trv and red the room temp. At leat in the morning, the target temp should change! By the way its equal if v4 or v5 the result is the same!
But you’ve enabled generic calibration today, right?
is it possible to use another temperatur for the night? I mean use a scheduler to use a lower temp or turn of in the night?
generic calibration was enabled since i have this blueprint, so nearly since one year!
Looking for some assistance please with a schedule selector and schedule adjustments - previously used a single schedule and now have an input helper setup with entries matching the schedule names (e.g. Winter, Summer etc.).
I then have a series of adjustments like this:
days:
- Mon
- Tue
- Wed
- Thu
- Fri
scheduler: Winter Schedule
comfort: "20"
- time: "11:00"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
scheduler: Winter Schedule
comfort: "23"
- time: "14:00"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
scheduler: Winter Schedule
comfort: "19"
- time: "18:00"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
scheduler: Winter Schedule
comfort: "22"
- time: "21:00"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
scheduler: Winter Schedule
comfort: "21"
- time: "6:30"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
comfort: "21"
scheduler: Shoulder Schedule
- time: "11:00"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
scheduler: Shoulder Schedule
comfort: "22"type or paste code here
However its only applying the adjustments from the Winter Schedule even when the selector for Summer is selected (there are schedule adjustments with the summer schedule selector included too).
My config:
Schedule selector:
Link to trace output:
Looks good now for me, i have only one problem with the calibration. (have no trace, because it was @ night)
why is there all night 21C, it should be 18C, what do you need more to check these?
could it be that there was no changes nessecery because it was heater then 18C so no trigger?
the beginning was vented the radiator
edit:
description: ""
use_blueprint:
path: panhans/advanced_heating_control_dev.yaml
input:
input_trvs:
- climate.wohnzimmer_comet_dect
input_temperature_sensor: sensor.thermal_comfort_wohnzimmer_hitzeindex
input_temperature_comfort_static: 21
input_temperature_eco_static: 18
input_temperature_comfort: input_number.advanced_heating_control_wohnzimmer_comfort_temperatur
input_temperature_eco: input_number.advanced_heating_control_wohnzimmer_eco_temperatur
input_mode_party:
- input_boolean.advanced_heating_control_wohnzimmer_party_mode
input_persons:
- person.xxx
- person.xxx
input_people_entering_home_duration:
hours: 0
minutes: 2
seconds: 0
input_people_leaving_home_duration:
hours: 0
minutes: 5
seconds: 0
input_scheduler_selector: input_select.advanced_heating_control_scheduler
input_schedulers:
- schedule.advanced_heating_control_wohnzimmer_zeitplan
- schedule.advanced_heating_control_wohnzimmer_urlaub
- schedule.advanced_heating_control_wohnzimmer_homeoffice
input_reset_temperature: true
input_away_offset: 1
input_away_scheduler_mode: true
input_windows:
- binary_sensor.wohnzimmer_comet_dect_window_open
input_calibration_generic: true
input_calibration_key_word: external
input_mode_winter: input_boolean.heizperiode
input_mode_outside_temperature: sensor.penthouse_temperature_feels_like
input_mode_outside_temperature_threshold: 17
input_mode_room_temperature_threshold: 21
input_mode_guest: input_boolean.advanced_heating_control_wohnzimmer_guest_mode
input_calibration_delta: 0.5
Hi,
since changing to 5.0 rc1_b I regularly get these errors in the log when automations are triggered:
Logger: blueprints.panhans.heatingcontrol
Quelle: components/system_log/__init__.py:331
Erstmals aufgetreten: 07:31:25 (6 Vorkommnisse)
Zuletzt protokolliert: 07:35:41
AHC - Change - automation_name thermostat: climate.thermostat_wohnbereich mode: heat new_target: 0.0 current_target: 22
AHC - Change - automation_name thermostat: climate.thermostat_a_kinderzimmer mode: heat new_target: 0.0 current_target: 17
AHC - Change - automation_name thermostat: climate.thermostat_essbereich mode: heat new_target: 0.0 current_target: 22
AHC - Change - automation_name thermostat: climate.thermostat_wohnbereich mode: heat new_target: 17.0 current_target: 22
AHC - Change - automation_name thermostat: climate.thermostat_essbereich mode: heat new_target: 17.0 current_target: 22
Unfortunately I cannot make much out of it. Could you please give me a hint where the issue might be?
Thanks a lot
Yes, have a look into the heating adjustments. There are also examples in the description.
But it works. In my test environment I am able to manipulate the climate temperature und sensor temperature and I can see the result in the thermostats temperature directly. Maybe it looks like it doesn’t have any impact because the aggressive mode equalize the new target temperatures a little. You can try to disable generic calibration for one day and compare the graph with the one you’ve posted.
I will check this.
Hard to say without a trace.
May you update to the latest version and check your log level. Set it to debug.
I’m blind or I can’t find there somethink. Do you have a more detailed description?