(Repost from Built-in apps group because of no reaction there)
Hubitat Elevation C7 Pro Currently running version: 2.4.3.173.
I'm trying to set up thermostat control for Tado Smart Radiator Thermostat X thermostatic headers. I've added them as Google Nest Matter Thermostat and when trying to create the thermostat app i keep getting errors like this:
Changing the device type to Generic Matter Thermostat does the same. Any ideas?
Thank you.
Hi S Jelen,
This looks like a bug in the Thermostat Controller 2.0 app, which isn’t commonly used with TRVs (no cooling, no fans ...)
Out of curiosity, what’s your use case here? Why do you need the Thermostat Controller app in your setup?
I have heating controlled by TRVs only, we get central heating in the building. I want to tie the TRVs to independent temperature sensors positioned in the room, so they wouldn't work based on the temperature right next to the radiator, which is always higher, but based on the spot where we mostly are.
Yes, that kind of use (a remote temperature sensor) for the Thermostat Controller does make sense. However, when I tried it a few years ago, my experience wasn’t very good — the room temperature swing was much higher compared to using the TRV’s built-in temperature sensor. But in the end it really depends on the specific room — every environment is different...
Have you already tried a very simple solution — setting a negative temperature offset in the Tado app?
1 Like
Yeah, I can just set the header temperature offset, or a higher temperature on the TRVs. But it defeats the point of having Hubitat as the central point of home environment control. I bought it with the idea of not having to register into a dozen online services and having a dozen mobile apps, one for each aspect of my home.
1 Like
I'm trying to figure out who or what called the commands in the logs in the screenshot in the first post. Did you really select the device in Thermostat Controller only 0.594 seconds after you added it to your hub, or did something else (e.g., you running one of those commands) happen in the meantime? [EDIT: OK, maybe that's the device Thermostat Controller created...that would make more sense. The below would probably need to be checked on both devices, that plus your actual thermostat(s).]
You can probably work around it by calling setSupportedThermostatFanModes({"auto"}] or something youself, but yeah, there is a bit of a gap with TRVs here, at least with some drivers.
1 Like
I've tried playing around with Fan Modes before to no effect, I've seen this advice in some old thread about TRVs, but I'll give it one more go, thanks.