do we need new zero config for this versiyon ?
Do i have to set the days when i want the comfort temp for all days?
Nope, just if you want them for certain days. If you dont set days it will be taken for every day.
And if you specifiy an entry for the same timestamp with the day field that would overwrite the entry without the day field.
I should start with the documentation.
can you explain me what the calibration toggle is doing?
Its for stopping calibration. Just a use case vor Tado users. Some of the Tado thermostats close and open valves completely after calling the calibration service. This results in much noise an drains the battery a lot.
In rc3 the windows detection failed. Thermostat doesnt go off when window is open. Iβm on rc3 and the newest core
I only updated the blueprint and set the new heating plan. Should i delete all ahc first?
Youβre the 2nd one who reports this. Still works in my testing and productive environment. I am still waiting for a trace log.
Could you open the window and share the trace of it?
It seems strange, because last execution was 5 h ago β¦ canβt imagine if the automation was triggered. The traces are uploaded here
Nothin wrong with window detection but with heating adjustments. I will check this later with your configuration. ATM I recommend to leave the adjustments empty.
i can confirm. With empty adjustments, the valve goes off when windows opens.
I will see if I find a way to validate the adjustements.
Δ° have problem timing only first olan is working time is not working
- time: β10:00β
days:- Sat
- Sun
comfort: β23β
eco: β21β
- time: β17:00β
days:- Sat
- Sun
comfort: β23β
eco: β15β
Bug found & fixed. Just give your adjustments another try.
If you post code here, donβt simply paste it. It gets formatted by the forum software. Use this instead:
Δ° re imported and config but now sunday and setting heat 21 but this time must be 23
- time: "07:00"
comfort: "23"
eco: "15"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- time: "08:30"
comfort: "21"
eco: "15"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- time: "17:00"
comfort: "23"
eco: "15"
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- time: "00:00"
comfort: "15"
eco: "15"
- time: "10:00"
days:
- Sat
comfort: "22"
eco: "15"
- time: "09:00"
days:
- Sun
comfort: "21"
eco: "15"
- time: "10:00"
days:
- Sun
comfort: "23"
eco: "15"
Advanced Heating Control is a blueprint with a lot of great ideas .
For an alternative that solves some (but not all) of the issues mentioned in this thread, check out Heating X2: Schedule Thermostats with Calendars
Heating X2 features:
- Schedule by calendar: set the temperature of each room with a local calendar and as many heating events as you like
- Multiple thermostats: One or more thermostats per room: multiple thermostats are synchronised together. Works with smart TRVs, any smart thermostat, or Generic Thermostat
- Manual override: a change on the thermostat, dashboard or by voice assistant remains in effect for a defined period (default 2 hours)
- Door or window open: heating turns off heating in the room if any door or window is left open for a defined period (default 3 minutes) β optional list of zero or more closure sensors.
- Occupancy: heating turns off heating if a room is left unoccupied for a defined period (default 1 hour) β optional list of zero or more motion or human presence sensors.
- Warmup period: occupancy is ignored for a defined period at the start of a calendar event (default 2 hours)
- Away mode: set all rooms to a temperature specified per room (default 5C) when there is no one at home
- Background temperature: used when there is no calendar event (default 5C but specified separately from the frost and away temperatures)
- Zone control: can switch one or multiple heating zone valves, or a boiler that needs a heat demand switch, based on heat demand from a group of thermostats
- Notifications: if thermostats do not respond to a new setting, go offline, or come back online
- Robust: Graceful degradation when a thermostat or a sensor is offline
- Battery-efficient: conserves TRV battery life by only transmitting real changes
- Code generator: uses mail merge (!) to automatically generate YAML code for helpers, timers, template sensors, groups, automations, and dashboard cards from a single EXEL spreadsheet that lists zones, rooms and thermostats
@panhans
Looks good. Window detection works as expected and comfort temp will set correctly. Good job mate
Yes, but as @tirol3 mentioned there is still a bug in the logic. Will fix that soon. Meanwhile the proximity integration getas another update and a breaking change. Hopefully the last one.
Now all features are working. Window detection and comfort temp set at heating plan works as well
Now seems normal i am trying thanks