There is no preset for “running on a schedule”, i.e. House at 16°C at night, 19°C during breakfast, 16°C during the day, 19°C when coming back from work monday to friday while it’s 19°C all day starting at 10 AM on week-ends
The HVAC has an Auto mode but the way I understand, that’s a mode that chooses if and when the heating and AC and fans and (des)humidifier should run, not a mode that selects the schedule for just the heating. At least, that’s not how the Netatmo integration uses Modes vs Presets.
And, more importantly, when I go on vacation, I select the “Away” or “Frost guard” preset and when I come back, I choose the “Schedule” preset (which is created by the Netatmo integration and not a default preset, hence my FR here). I never change the mode (which has Auto, Heat [at the maximum temp] and off), it has to remain on Auto for the Thermostat to work.
This time I agree but earlier you said “Netatmo integration decided to use auto for what you are asking to be Planning.”
The Netatmo integration is using “Schedule” for what I want to be “Schedule” (which should be translated to “Planning” in French, yes).
So what is my point? I wish HA had a default preset called Schedule instead of relying on integrations to create it. That default preset would have translations in every language and come with a default icon (the icon could be calendar_month or schedule).
That’s not a guarantee. You can add these translations yourself to netatmo and be done with it without even needing this FR and other people would benefit from it. The translation strings exist, they just need to be added to your language. Moving the preset to core won’t magically make the translation occur.
No but it’s a step in the right direction, the right direction being unified design with unified translations. If you translate Schedule for the Netatmo integration, it won’t be translated for the Nest (or whatever, I don’t know what presets are used by Nest) translation.
But that won’t solve the absence of icons.
I made some translations in Lokalise last week after I opened the issue on Github but I’m not too sure of how the translations work (I’m a greteful user of HA, not a developer). I thought the line 177 you specifically mentionned showed it used a hard-coded name rather than a translation from the json file. But I’m way out of my depth here.
I believe other people would benefit from having a default Schedule preset in HA Core. And I’ll argue it will be a greater benefit.
I’m not trying to do things my way or anything. I just identified an issue, I’m offering an idea (and just an idea, I wouldn’t be able to offer a PR) to solve it. If you want it to solve it another way that’s fine, I just wanted to make the issue knows.
The issue here is that the devices do not stick to a unified design, so unified translations in the core will not work.
It even looks like Netatmo is one of the brands that do not follow the common trend for such devices.
It’s the hard coded English translation, other languages use the exact same setup but in whatever language it represents. It’s not really hard, find the word schedule, find what it equals (right next to it), and change it to whatever you need.
Not really, netatmo is the only climate entity with the preset, just searched the codebase. All other "schedule" translations are for select entities, not climate devices.
“Prog” is for programmation (you program the radiator to turn on in the morning etc, it’s a Schedule).
In fact, I will argue that the vast majority of climate entities have some sort of schedule preset, that’s the whole point thermostats, connected radiator valves and the like: to have the heating or cooling schedule to match your work life.
I just searched for prog, program, and schedule, any other words? Only hits are netatmo and overkiz for climates. I think you’re just getting “lucky” with your thermostats.
My thermostat has a program mode, however when you set it in program mode, you can no longer use it as a smart thermostat as it disables that functionality (removing all functionality from HA) and it’s not a selectable option from the smarthome mode itself. This is a zwave thermostat, widely used that also exists as a wifi version and a zigbee version.
You’re more than welcome to search for these terms yourself in the codebase, but I think you’re overstating everything related to smart home thermostats just to make your case about this FR.
EDIT: Just went through some heavy hitter climate devices, and most of them treat “program” outside of preset. Meaning it’s not really a mode you can put the device in.
The whole thread is now turning into a proof that there is no standard, so HA can not handle it centrally. It has to be handled locally in the different integrations.
Well, I hadn’t thought about the fact using the program/schedule mode would disable all functionalities from HA.
I didn’t say there was a standard and that HA should respect it. It’s just that when presets include “Home”, “Away”, “Eco”, “Comfort”, it felt natural to me that there should be a presets that says “That shit is handled by the device on its own” and that would help standardise the way climate entities work inside HA.
Nothing is really handled by the device.
The integration handles the import of values into HA state machine and HA and others provide cards for that state machine.
The issue here is that cards are rarely linked to a specific integration. They are generic in the displaying of data.
