I recently downloaded the SmartThings app to control multiple devices (Kasa plugs, Samsung TVs, and nest thermostat).
I recently hooked up an aroma machine to push scent into my hvac system so that it spreads the scent across my home. To not waste the scent when the hvac is not running, I decided I would use a plug to trigger on/off whenever the status of the nest thermostat is running. I created power on routines for when the nest state changes to cooling, heating and fan only. I than created power off routines for when the state changes back to idle.
It seems to be working when the state changes to cooling and heating. But when the fan auto runs, the SmartThings app shows the status as “idle” and therefore, does not power on the plug. Is anyone else having issues with the nest status remaining as idle when the fan is running?
Please note, if I manually toggle the fan from auto to on in the ST app (which runs on a timer), that works. However, the problem is when you have the fan set to auto. When it kicks on randomly, it seems that the status doesn’t change from idle. Any work around or fix for this? I should also note, I have a 3rd generation Nest Learning thermostat.
I see the same behavior with my Nest thermostat. Seems that something in the integration isn’t updating. I’d start with Nest support since cloud to cloud integrations are the responsibility of the product vendor.
Thanks for the details. I just got off the phone with Nest support. Of course I was pointed to contact SmartThings support.
However, I did decide to download the Google Home app just to see if I could just do the automation there. Come to realize, they don’t even list a nest state for the fan. So I’m wondering if maybe these earlier generation nest thermostats just don’t provide a status/state update for when the fan auto runs? Does anyone have a nest 4th generation thermostat where this is not an issue?
I had the same issue with the learning thermostat (gen 3). I want to turn on all my house’s exhaust fans whenever my furnace runs. I run the furnace fan for 30 minutes every hour but the state won’t change from idle when the scheduled fan turns on. State only changes when heating, cooling or when I run the fan manually. I just got the gen 4 learning thermostat and lo and behold, I get an error trying to add it to smartthings via matter. I’m going to reach out to smartthings to try to diagnose the issue, and I’ll update this thread if I figure it out and the state changes correctly.
I didn’t. The smartthings support ticket went nowhere. There has been a firmware upgrade in the gen4 but still no dice on getting this thing added to smartthings. Quite a bummer. For context, I have a 2015 smartthings hub which doesnt support thread. That shouldn’t matter though since the nest gen4 does matter over wifi.
Ok I finally got it hooked up to smartthings with matter. I have a shared SSID that does both 2.4 Ghz and 5 Ghz. I had to force my phone and thermostat on the 2.4 band for the setup to work. Disappointingly, the thermostat state only shows auto, cool, heat, off. It gets no indication if just the fan is on. So it looks like there is no improvement with the nest gen 4 smarthings integrstion compared to gen 3
(Kind of interesting how they build this string in the driver…)
Can try to remotely log in to my machine at home to get the other details.
Just wanted to show that the Matter thermostat driver is a bit nonchalant when it comes to supported modes. (IIRC, there’s a TODO in the code that states that.) And the way how commands and capabilities are handled in general doesn’t seem right.
The “problem” is, that everything with a thermostatMode gets all commands, regardless of what the device supports (supportedThermostatModes).
Heating-only and Cooling-only devices do have different profile names, but pretty much same content:
Impossible to resolve that without a major rewrite with sub drivers for different thermostat devices… Go through all profiles, check what’s common (temp), put that in the main driver, create sub drivers, one for heat/cool-only and so on.
And that’s why the log from a Matter thermostat driver looks like this:
2024-12-16T01:14:39.375103943Z INFO Matter Thermostat <MatterDevice: 8ec26f03-cb7c-4b8a-b1e3-269160950f4b [DA7D3F61B
120BF52-CE81214862A6803D-14] (Smart Radiator Valve)> emitting event: {"attribute_id":"supportedThermostatModes","capa
bility_id":"thermostatMode","component_id":"main","state":{"value":["off","auto","heat"]},"visibility":{"displayed":f
alse}}
2024-12-16T01:14:39.391379568Z DEBUG Matter Thermostat Smart Radiator Valve device thread event handled
2024-12-16T01:14:39.393035110Z DEBUG Matter Thermostat Smart Radiator Valve device thread event handled
2024-12-16T01:14:39.400443943Z DEBUG Matter Thermostat Smart Radiator Valve device thread event handled
2024-12-16T01:14:39.401589943Z DEBUG Matter Thermostat Smart Radiator Valve device thread event handled
2024-12-16T01:14:39.405898360Z DEBUG Matter Thermostat Smart Radiator Valve device thread event handled
2024-12-16T01:14:39.415491151Z DEBUG Matter Thermostat Smart Radiator Valve device thread event handled
2024-12-16T01:14:43.569822652Z TRACE Matter Thermostat Received event with handler device_lifecycle
2024-12-16T01:14:43.769851152Z INFO Matter Thermostat <MatterDevice: 8ec26f03-cb7c-4b8a-b1e3-269160950f4b [DA7D3F61B
120BF52-CE81214862A6803D-14] (Smart Radiator Valve)> received lifecycle event: infoChanged
2024-12-16T01:14:43.869339652Z TRACE Matter Thermostat Found DeviceLifecycleDispatcher handler in matter-thermostat
2024-12-16T01:14:43.871981068Z WARN Matter Thermostat Device does not support cluster 0x0402 not adding subscribed a
ttribute
2024-12-16T01:14:43.873677693Z WARN Matter Thermostat Device does not support cluster 0x0402 not adding subscribed a
ttribute
2024-12-16T01:14:43.875715610Z WARN Matter Thermostat Device does not support cluster 0x0402 not adding subscribed a
ttribute
2024-12-16T01:14:43.877572777Z WARN Matter Thermostat Device does not support cluster 0x002F not adding subscribed a
ttribute
2024-12-16T01:14:43.879405402Z WARN Matter Thermostat Device does not support cluster 0x0402 not adding subscribed a
ttribute
2024-12-16T01:14:43.881268402Z WARN Matter Thermostat Device does not support cluster 0x0402 not adding subscribed a
ttribute
2024-12-16T01:14:43.883117985Z WARN Matter Thermostat Device does not support cluster 0x0402 not adding subscribed a
ttribute
2024-12-16T01:14:43.885043235Z WARN Matter Thermostat Device does not support cluster 0x002F not adding subscribed a
ttribute
Forgive my lack of knowledge, but couldn’t you just be all-encompassing in the main driver (temp, humidity, state, etc) and if a thermostat doesn’t support a certain capability or attribute, that’s fine?
I mean, it’s a design decision, making the driver very complex and can’t be easily changed now. There’s the fact that the supportedThermostatModes change after the device was added and an unsupported command is send. Not what I expected…
(I want to add a switch/toggleSwitch for the thermostat mode to the device tile)
Anyway. This thread is about the fan of a Nest device and let’s wait for the logcat.