I thought about it and I think I could link the different settings to the thermostat device defined initially in the widget.
If person A adds a thermostat widget the settings are saved with the thermostat device.
Person B (or person A on another dashboard) adds a widget with the same thermostat device then the widget will point to the same settings.
If B changes the settings, the settings are changed for A and vice versa.
In general there is only one thermostat in a room and if someone changes the settings they are applied to everyone, otherwise it would quickly be a mess.
At my place for example, for my son no heating — he’s too hot, my wife is always cold and would like to heat the rooms to 25°C and I’m somewhere in between. You can imagine the chaos if everyone had their own settings
I wonder if managing through scenes isn’t too complex, and whether we shouldn’t just create a « Thermostat » integration, with a room-by-room (or group-by-group) configuration
For each « room »/« group of devices » concerned:
Select the temperature sensors
Select On/Off-type heating devices
And then, on the dashboard, we could have a widget like you’re showing, which would control either a particular room/group, or even a global widget if one wants to control an entire house at once.
In my opinion, these are patterns that already exist in other Thermostat applications (Nest, for example). I’d be curious to know how they set that up
The question arises and it’s a complicated subject depending on everyone’s configuration.
I just watched a video about a thermostat in Home Assistant (HA), where you have to juggle creating a virtual device, YAML, editing parameters on the dashboard and creating scenes. What a convoluted contraption…
There’s surely an easier way in Home Assistant (HA), but after the video I just saw I don’t understand why so many people praise HA so much.
The idea of directly controlling an ON/OFF heating device is fine, but if you want to couple it with a schedule it’s trickier.
For me, the point of scenes is creating schedules — in NetAtmo that’s what I have.
I can create a weekly schedule and set time slots where I can apply temperature presets.
J’aime beaucoup l’idée et je pense que c’est même ce qui ressemble le plus au plugin thermostat de jeedom.
Je ne dis pas que c’est le plus beau widget du monde par contre.
Personnellement sur Gladys, je passe par les scènes pour changer les ordres des fils pilote, et mes déclencheurs sont extraits d’un calendrier caldav, avec un arrêt si une fenêtre s’ouvre et si on passe en Tempo Heure Pleine.
As you did for Energy monitoring, having a Thermostat integration where we can configure everything (either by room, or by Thermostat/pilot wire) makes perfect sense!!
Personally I never use the calendar to manage schedules like one might for heating or something else. I really don’t like the idea of opening an extra app just to manage a calendar.
After all, everyone has their own point of view, but I’m not a fan — or else we’d need to be able to edit it directly in Gladys.
