Thermostat device matter

[goeran03]

Is it planned to implement a thermostat device in matter? A virtual device at least would be probably give the possibility to be flexible. A simple behavior with a thermo sensor, a relay and a given switching point could be realized that way with scripts I guess, and more complex solutions as well. If there is thermostat functionality already in Tasmota , this could be linked to matter.

[sfromis]

Tasmota does indeed have a Thermostat feature. As I'm not using this, IDK how simple it would be to integrate.

I suppose that it could be feasible by mapping Matter inputs/actions to the corresponding "standard Tasmota" ways of handling these, and then letting the Thermostat feature operate on that. Just uninformed speculation of course 😄

It would be another case with a Matter-compatible thermostat device.

[s-hadinger]

@goeran03 Are you already using the Thermostat feature?

[goeran03]

Not yet

[benjaminnestler]

I'm currently working on a thermostat cluster integration but in the first step not for the tasmota Thermostat feature. I want to adopt a Tuya based thermostat to the thermostat cluster of Matter.

[s-hadinger]

Awesome

[benjaminnestler]

Some pictures to show my progress

| | |
| | |
| | |

[vincedarley]

This looks very interesting. I'm currently in the situation of using dumb relays (Sonoff 4CH-R3) as thermostats with Home Assistant (HASS)'s Basic Thermostat doing all of the control logic (given a Xiaomi temperature sensor reading in each area).

I'm looking at how best to make this more robust so that even if HASS is down, the system generally operates very comfortably. As I see it, most more sophisticated thermostats have 4 different modes (variously named Comfort, Eco/Night, Away, Vacation/Frost), each of which has its own set-point. And then there is a "heating scheme" which is a schedule (perhaps 24 hour, perhaps 1 week long), which says what mode to use on the given day/time. Once the mode is set, the temperature set-point is known.

There seem to be 4 options of increasing sophistication:

1. Tasmota only knows about a temperature set-point, which HASS tells it (~Hourly)
2. Tasmota knows about a temperature set-point per mode, and HASS tells it the mode (~Several times per day)
3. Tasmota knows about a 24-hour “heating scheme” and HASS tells it the scheme to use (~2 times per week?).
4. Tasmota knows about a full week’s “heating scheme”, including weekend or day of week variations, and HASS only tells it to change for special purposes (e.g. homeowner is on vacation for a week, so HASS only needed very rarely).

As we go down this list we move from 1,2 where HASS is a critical part of the system (= basic daily heating functionality will be uncomfortable if HASS goes down at the wrong time) to 3 and especially 4 where HASS is non-critical, and the user’s comfort would not be impacted if HASS goes down. In 4, and perhaps 3, you could imagine a user being willing to open the web portal to the Tasmota device (or HomeKit/Matter on their phone) to make occasional adjustments and HASS not even being required at all.

Of course it would be nice to support temporary modifications to 3&4 where a HASS automation or a user could tell the Tasmota thermostat - “Boost the temperature in this room +1 degree until the next scheduled change" or “We’re not going to be home today, the house can be in Eco mode for the next 6 hours”. On expiry the thermostat would revert to its standard programming. Some of the KNX thermostats I've been reading about support this kind of thing.

Any clarity on how far in the above I can get with Tasmota today?

[Cptmeme]

Are there any updates regarding this? I am interested in integrating a tuya space heater I have into matter.