Thermostat: request for improvements

Following the great announcement Gladys Assistant 5.2 : un vrai thermostat et des contrats d’énergie pour tous les pays 🎉, I share my first tests and feedback (yes, I know, I should have tested before :frowning: )

My first hot feedback

  • When you choose a room for the thermostat, it would be nice to filter the elements related to this room because you have access to everything that is not necessarily:


    image
    .
  • for the opening sensors, have the possibility to select multiple (in the living room I have several)
  • after thinking about filtering with the room, for my ground floor, I have the living room and the kitchen that are open together so I would need to be able to select the opening sensors of the living room and the kitchen :frowning:
  • for the setpoint, I don’t know what to do because the two we see are virtual MQTT devices and I don’t see a setpoint (well temperature) feature of my Mitsubishi heat pump.

    Should I create a virtual living room setpoint device and « associate » it with the air conditioning setpoint temperature?
  • for the temperature, we don’t have access to the average temperature of the room? Or if we do multi-selection, can it calculate an average for us?
    image

I will come back after the setpoint part is resolved on my side, in any case great integration! :wink:

Hi @mutmut, and thanks for these very detailed feedback! :folded_hands: And yes, you could have tested before :rofl:

  • Filtering by room + open living room/kitchen: I agree with you on both points. The cleanest solution would be to filter by default on the thermostat room, while allowing to extend to other rooms (or all devices) for cases like yours where multiple rooms form a single volume.
  • Multiple opening sensors: This is a real demand, especially for living rooms with multiple windows or French doors. Multi-selection with a logic of „at least one sensor open → heating off“ seems to be the expected behavior.
  • Average temperature: same idea. With multiple selectable temperature sensors, an average (or even a min/max choice) would be very useful in a large room.
  • Your heat pump setting: to understand why it doesn’t appear, could you tell us what type of functionality (category and type) your Mitsubishi heat pump sends to Gladys, and via which integration it is connected (MQTT, Zigbee2MQTT, other)? A screenshot of the device page, with its functionalities, or the MQTT payload of the heat pump would help us see if the setting is exposed and in what form.

I know the next PR for the thermostat will be to add the pilot wires. It’s already in progress.

All points (including the test :wink: ) are fine for me!

I use Melcloud Home as an external integration.


image
I can see the Setpoint temperature feature but nothing in my thermostat menu.

Yes, strange. As it’s a set temperature, it should appear, though. My NetAtmo has the same feature and shows up fine.
I’ll check and let you know.