SmartThings is not so smart once again. I have a routine that uses temperature from a sensor to turn on or off an electric heater during a certain time frame. The routine is: T, W, Th from 5pm-7:59am (next day), if Living Temp is Equal to or below 76 degrees Turn On Living Heat. Problem is, if the…

And now another problem. The routine runs from 5pm to 7:59am (next day) T, W, Th. It didn’t trigger at 5pm because the temp was below 76 when it hit 5pm and now at midnight the routine stopped running, even though I have it set to run from 5pm to 7:59am (next day). At 12:17am the temp dropped to 75…

[image] lexis350: I will make extra routines to turn on/off before the time range, but I shouldn’t have to. If the option is not really equal or below, but really is Drops below, then the verbiage in the app should be changed. The comparison being made is ‘equal or below’ so the condition is …

[image] orangebucket: The above issue could be mitigated if time ranges were ordinary conditions that triggered the automation when they start and end. Again they aren’t for whatever reason. However a number of users choose to use two Routines to toggle the state of a virtual or real binary devi…

Why don’t you use “Range" instead of “Equal or below “? [image] Try routine similar like this one [image] This should keep temperature between 70-72 at that time period, even if temperature drops below 70 prior to start time

That’s exactly what’s happening, it only triggers if True not when evaluated. My guess is they don’t have enough infrastructure to handle it that way. I assume it would add hundreds of thousands of requests every time routines evaluate which Samsung’s infrastructure probably can’t handle. Anyway, I…

I started over, took out spanning into the next day and added on/off routines to turn on/off before the next time frame hit. It’s 10 routines (see below). I thought I had it working, but the temp was above the off trigger at 5:05 pm and it never turned off. T W Th F 12:01am - 7:55am on at 76 (equa…

I never even saw range as an option for temperature because when I choose temperature as a trigger the android keyboard opens up and blocks the range option. I never knew it was there, can’t see it. I had to close the keyboard then I saw range. Again, bad programming, the keyboard should only pop up…

[image] lexis350: My guess is they don’t have enough infrastructure to handle it that way. I assume it would add hundreds of thousands of requests every time routines evaluate which Samsung’s infrastructure probably can’t handle. My understanding is that Routines, being Rules based automation…

For those kind of routines I usually create virtual devices that represent triggers and/or preconditions. In this case thermometer to change temperature, switch to represent time period, and fan to represent your heater. [image] Then I create routines and test triggers. I just created 2 initial…

This is virtual setup per your specs Create 1 virtual switch and call it 8pm - 5am, and setup on routines tab to turn on TWTF at 8pm and to turn Off on WTFS at 5am like in screenshot [image] Then set up 2 routines for turning heater/plug on and off as on. Be sure to have when all or when any con…

Temperature: Equal to or below - does not work

General Discussion

orangebucket (Graham) October 15, 2024, 8:58am 19

Topic		Replies	Views
Period of time-condition seems to prevent a routine from triggering SmartApps & Automations	27	3512	March 15, 2023
Automation Help - Timed Automation Doesn’t Seem To Be Triggering SmartApps & Automations	46	1340	July 17, 2023
Routines not triggering Devices & Integrations	44	4274	July 28, 2023
Looking for a virtual thermostat with a low & high temp Connected Things	26	1258	February 13, 2025
SmartThings Automation won’t trigger with no motion on motion sensor Automation Ideas	24	1091	February 5, 2023

Temperature: Equal to or below - does not work

Related topics