# Complete Thermostat feature **URL:** \ **Category:** Demandes livrées\ **Created:** [September 27, 2025, 9:47am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719 "2025-09-27T09:47:28Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 23, 2026, 7:33pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/21 "2026-02-23T19:33:24Z")
> [@Terdious](#): > > But then, could two users have the same thermostat features with different settings on two dashboards? > > Or are features no longer selectable if they’re already in a dashboard? 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 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [February 23, 2026, 8:18pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/22 "2026-02-23T20:18:46Z")
Thanks for the clarifications @Will_71 ! > [@Will\_71](#): > > ### My uncertainties concern the control management: > > - Either via **scenes** , a bit like for the Alarm box, exposing the different presets (Night, Away, Eco, Comfort…), the heating status info, and everyone remains free to control their devices within the scenes. > - Or directly via the **selection of a device in the settings** (may be complicated to implement depending on each person’s configuration). Indeed, the question arises. 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 🙂 ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 23, 2026, 8:40pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/23 "2026-02-23T20:40:17Z")
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. ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/0/a/0aee0afc772c40fc181dc0f2dab4c65f59a4c185.png) Depending on the heating state (ON or OFF), which will depend on the schedule and the measured temperature, one can control a device, ---
**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\ **Post date:** [February 23, 2026, 9:01pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/24 "2026-02-23T21:01:21Z")
> [@pierre-gilles](#): > > create a « Thermostat » integration, with a room-by-room configuration (or group-by-group) I really like the idea and I think it’s actually what most closely resembles Jeedom’s [thermostat plugin](https://doc.jeedom.com/fr_FR/plugins/wellness/thermostat/). I’m not saying it’s the most beautiful widget in the world, though. Personally on Gladys, I use scenes to change the commands for the pilot wires, and my triggers are extracted from a CalDAV calendar, with a stop if a window opens and if we switch to Tempo Peak Hour (Heure Pleine). ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [February 24, 2026, 7:54am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/25 "2026-02-24T07:54:31Z")
> [@Will\_71](#): > > The point of scenes for me 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. I understand, that’s something to think about 🙂 The other possibility is to actually put a schedule in the Thermostat integration, specific to the thermostat. ---
**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\ **Post date:** [February 24, 2026, 8:10am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/26 "2026-02-24T08:10:33Z")
I really like the idea, yes for my part. 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!! And at the same time ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 24, 2026, 8:48am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/27 "2026-02-24T08:48:22Z")
> [@pierre-gilles](#): > > The other option is to outright include a schedule in the Thermostat integration, specific to the thermostat. I’ve thought about it. I’ll run tests and suggest some ideas with images to try. That way everyone can get an idea. It’s always easier when testing. ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 24, 2026, 8:51am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/28 "2026-02-24T08:51:31Z")
> [@Terdious](#): > > And at the same time, like you have for the « Energy Consumption » selection on the dashboard there will be the thermostat option with the configured thermostats… 😍 Like this @Terdious ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/c/7/c72ce0a1e1e05c3af61a7df34fc50c1a389a070b.png) ---
**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\ **Post date:** [February 24, 2026, 8:52am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/29 "2026-02-24T08:52:25Z")
That’s what I imagine, but I don’t think it changes the current approach you had started ^^ 😉 ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 24, 2026, 8:52am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/30 "2026-02-24T08:52:56Z")
I thought of it that way from the start. ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [February 24, 2026, 4:29pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/31 "2026-02-24T16:29:24Z")
[quote=« pierre-gilles, post:25, topic:9719 »] add a schedule to the Thermostat integration [/quote ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 24, 2026, 8:13pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/32 "2026-02-24T20:13:35Z")
> [@GBoulvin](#): > > I mean that the calendar present in Gladys already does the job. Could a simple link be enough? 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. ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [February 24, 2026, 8:24pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/33 "2026-02-24T20:24:37Z")
I agree with you @Will_71, it has to be super simple to create a schedule! ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 24, 2026, 8:33pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/34 "2026-02-24T20:33:39Z")
When I have something presentable for the thermostat part I’ll make an image so those who want to test can Today I added the ---
**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\ **Post date:** [February 24, 2026, 8:41pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/35 "2026-02-24T20:41:50Z")
> [@Will\_71](#): > > Today I added the ability to add an actuator (I added a controllable socket) in the settings and it works pretty well. Do you only scan Zigbee actuators? ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 24, 2026, 9:14pm UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/36 "2026-02-24T21:14:10Z")
No, the goal will be to include all known switches, regardless of the technology. ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [February 25, 2026, 7:27am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/37 "2026-02-25T07:27:46Z")
> [@Will\_71](#): > > When I have something presentable for the thermostat part I’ll make an image so those who want to test So you created a Thermostat integration? Where is the configuration done? 🙂 ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 25, 2026, 9:05am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/38 "2026-02-25T09:05:11Z")
Not for now — I’ve put the settings in the dashboard’s edit mode. I’ll give you more details tonight when I get home from work. But something to consider is whether we leave it like this or add a thermostat integration ---
**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\ **Post date:** [February 25, 2026, 9:22am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/39 "2026-02-25T09:22:33Z")
I largely agree with @pierre-gilles on the integration side : - It preserves the approach taken with Energy Monitoring (Suivi de l’énergie). - It therefore allows creating global thermostats. - More logical for global / multi-account management. - And I ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [February 25, 2026, 9:27am UTC](https://community.gladysassistant.com/t/feature-thermostat-complete/9719/40 "2026-02-25T09:27:51Z")
To manage schedules, it will probably be easier with an integration. [Previous page](https://community.gladysassistant.com/t/feature-thermostat-complete/9719.md?page=1) [Next page](https://community.gladysassistant.com/t/feature-thermostat-complete/9719.md?page=3)