Heating at the dashboard level

Development
1

Hello everyone,

I am currently on the Netatmo module. I would therefore like to be able to view the set temperature of my thermostat, and more particularly, adjust this temperature (button + / -).

I assume this should be done on the dashboard.

capture1
capture1393Ă—160 5.01 KB

Is it a good idea to add a control on the header of this box with a plus and minus button with the set temperature in between?

Or create a new box? This can also be done to avoid overloading the box where we have all the devices.

What do you think?

Thanks in advance :slight_smile:

2

capture_setpoint
capture_setpoint404Ă—122 3.46 KB

Here’s the idea I had for the setpoint. I don’t think it’s amazing. But it’s already pretty good.

3

It’s not bad, just the + and - buttons lack contrast. UI isn’t easy :wink:

4

I’m a dev but more back / devops so UI is more than difficult for me … :smiley:
And for me i3 is pretty on a computer so you can understand that the UI and I are two different things :smiley:

If someone is good at this, it would be super cool if they could help me :smiley:

5

I find it interesting to have just one box
for the perceived temperature and the desired temperature.

It might be a good idea to place the + button and the - button one above the other with the desired temperature next to it to be in the same style as the perceived temperature.

To try. It’s just my opinion.

6

Hello,

I’m also thinking about the heating question, I started a service to add Heatzy (pilot wire module) compatibility.
I had a similar idea, to have the perceived temperature and the setpoint temperature on the same box.

We can synchronize to see what we can do, on my side I’m just starting with Gladys, so I’m struggling a bit ^^
I should publish a first PR tomorrow normally!

7

That will indeed allow synchronization.

Good luck, it remains accessible, don’t hesitate to look at the other well-made services that can help you with the code.

Great :slight_smile:

8

I think it would be better to create a new box :slight_smile: A « temperature Â» box for the house, something a bit design could be nice

Some inspirations:

1.4 kW.h
1.4 kW.h1552Ă—1116 223 KB
Kitchen
Kitchen2080Ă—1268 334 KB

9

I like the ideas, I will try to draw inspiration from them :slight_smile:

10

Small question, would it be more interesting for me to separate the netatmo code and the new box code?

I think I’ll first code the netatmo service (adding connected equipment, connecting to the service, retrieving values) and then make another PR with a new box

What do you think?

11

Additionally, I am adding points that will be problematic.

If I want to manage the temperature of the house / rooms. I need to be able to identify a device so that it is, for example, the element that manages the heating of the entire house. So it becomes complicated. Because a thermostat is associated with a house. Because you can manage multiple houses and multiple thermostats.

So it needs to be planned in the core of gladys.

What do you think @pierre-gilles?

12

I think that indeed, heating management should be in the core!

The netatmo service should only be a compatibility layer that sends orders :slight_smile:

13

This is what I started doing by creating a « heating Â» device category. We can share our code if necessary.

However, I do not know if we can manage the different types of heating at once. Thinking about a special heating box, I realize that we are in two different cases:

  • a thermostat that reports the temperature and waits for a setpoint temperature, with management at the house level
  • a module that does not report the temperature, but manages on/off and different modes/programs (I don’t know netatmo well, maybe it’s the same case), with management at the level of a single radiator or zone depending on the connections

So maybe we need two different boxes?