In there anyone that is on work on a driver for Tado heating system?
Someone have found an alternative solution to integrate in smartthings after the end of the smartapp?
1 Like
You can get partial integration by using an Alexa routine (not a smartthings routine) as an intermediary, but it doesn’t provide all control options, so I don’t know if it would work for you or not. 
The idea it was to have direct integration… it’s strange that nobody works on it considering the number of smartthings useres have this system
1 Like
I’m thinking about buying Tado TRVs.
It would be nice to have a direct integration with Tado, but how about using IFTTT? It sounds like it should do the job.
https://support.tado.com/en/articles/3448874-which-ifttt-services-does-tado-offer
Edit: This makes it look promising:
If this is still interesting for anyone using the Tado V3+ thermostats - I managed to finally integrate basic functionality into smartthings again.
This is possible via Homeassistant and a custom project by t0bst4r called “Home Assistant Matter Hub”
Basically building a Matter Hub functionality in Homeassistant and integrate (matter compatible) selected entities to then allowing Smartthings to install this Matter Hub and its connected (Homeassistant) devices with it.
Better explained here:
(Successfully in Homeassistant installed) Tado thermostats show up and can be used in routines, too.
For me: Only thing missing as of now is the tado mode “programme / auto”, which starts your pre-progammed heating pattern made within tado.
Right now, you only can choose between “Heating” or “off”, which may be a missing Matter functionality issue.
I also was able to integrate some more Wifi Tuya Devices (Heating, Fan) a AVM Fritz SmartPlug and a Govee Lightstrip in Smartthings using this virtual Matter Hub!
1 Like
That’s because the ThermostatSystemMode auto is not what it seems. It has nothing to do with schedules:
https://leconiot.com/matter/1.2/appclusters.html#ref_SystemModeEnum
| Name | Summary |
|---|---|
| Off | The Thermostat does not generate demand for Cooling or Heating |
| Auto | Demand is generated for either Cooling or Heating, as required |
| Cool | Demand is only generated for Cooling |
| Heat | Demand is only generated for Heating |
| EmergencyHeat | 2nd stage heating is in use to achieve desired temperature |
| … | … |
Since TRVs are “heating only” devices (with the heating-only profile), auto wouldn’t make sense.
They actually fixed the supported modes recently. My Matter TRVs had an auto mode for a long time. And when you’ve send an unsupported mode, it was added to the list of supported modes…
1 Like
Tado doesn’t support IFTTT now, so that’s not an option.
Thanks for mentioning HA as a solution. I think if I started using HA, I would probably stop using SmartThings.