Functional specification
As a Gladys user, I want to be able to control my heating. To do this, I see a few possibilities:
- Via a calendar, or static programming
- Via a calendar with priority to sensors
- Manually, via a kind of thermostat or central control
- Automatically, using other sensors
1. Via a calendar
A « calendar » type interface over a week allows you to choose from what time to what time the heating is on or off, with an additional heating setpoint.
Example:
- Monday: 21°C from 7am to 9am, off from 9am to 5pm, 19°C from 5pm to 9pm, 17°C from 9pm to 7am.
- Tuesday: etc. until Sunday
2. Via a calendar with priority to sensors
The calendar interface is always active, but if a scene changes the setpoint temperatures, then it will take priority. As soon as this setpoint temperature is removed or the heating is turned off, it is the calendar that takes over again.
Example:
- The calendar heats every day between 6am and 9am and between 4pm and 9pm. During the day, the heating is off.
- A scene detects my presence at 9am (#telework) and turns on the heating by increasing the setpoint temperature. Despite the deactivation scheduled in the calendar, it is the scene that keeps control of the heating.
- At 5pm, the scene turns off the heating and sends a signal to Gladys to « take over » and let the calendar run its course.
3. Manually
A thermostat on the dashboard allows you to control the heating temperature per room. No automation is present here, it is the user who chooses via Gladys how they want to heat their different rooms.
If a physical thermostat is added to Gladys, it can be used linked or instead of the one displayed on the dashboard. It will always be the priority to the physical thermostat.
If the heating management calendar is in use, but the user changes the thermostat via the dashboard, then it is the user who has control instead. A small warning message (in info mode) may remind that the calendar (or a scene) was managing the setpoint temperature.
4. Automatically (WIP)
What is the best solution to use external sensors in a practical way and not through 25,000 scenes, a bit of calendar, etc.?
TODO
A link between the thermostatic equipment, the radiator valves or the central valve (I am thinking of my case) with temperature sensors.
Each valve is coupled with its sensor(s).
A system of setpoints for each valve/sensor pair.
Exceeding the threshold on a sensor connected to a valve would trigger the request on the valve or stop it.
Finally, of course, the visual management of a schedule.
Not forgetting a possible coupling of the valves with the window sensors, if a door/window is opened in the room where there is a valve, it is stopped to avoid heating in vain.
In the same way, if the house is empty, you can decide to turn off the heating, with a delay … … to be seen … or start remotely when a user arrives or decides …