Turn on Smart Life device at sunset automatically
How this automation works
Automate your smart devices by linking Timberwolf Server to Smart Life scenes. This runs whenever your selected Timberwolf Server boolean object changes to true, triggering a specific scene in Smart Life. Ideal for integrating building automation with your smart home lighting, climate, or security systems.
If
Trigger ingredients
SwichedAt
ObjectName
Then
Action fields
which_scene
Services used in this Applet
You might also like...
-
16.1K
-
-
Turn off Smart Life device when you leave home
15.9K
-
-
Press button widget to activate a Smart Life scene
10.3K
-
Related services
Create your own Smart Life and Timberwolf Server workflow
Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.
43 triggers, queries, and actions
Battery low
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when residual electricity in the lock under threshold.
Camera detects motion
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified camera detects motion. To use this trigger, camera’s motion detection should be turned on.
Camera detects sound
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified camera detects sound. To use this trigger, camera’s sound detection should be turned on.
Device or group is turned off
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified device/group is turned off.
Device or group is turned on
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified device/group is turned on.
Door sensor is closed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the door sensor is closed.
Door sensor is open
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the door sensor is open.
Input incorrect password repetitiously
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when someone input incorrect password repetitiously.
Leak detected
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when water leak detected.
Object value has changed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a Timberwolf Server object has changed.
Person is detected
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when PIR detects person.
Shake detected
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when sensor shake detected
History of Camera detected sound
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the specified camera detected sound. To use this query, camera’s sound detection must have been turned on.
History of Device turned off
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the specified device/group was turned off.
History of Device was turned on
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when the specified device/group was turned on.
History of Leak detected
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the sensor detected a water leak.
History of low Battery alerts
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when residual electricity in the lock dropped below the threshold. Note: this query will only return future events after this Applet is created.
History of motion detections by Camera
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when a Camera detected motion. To use this query, Camera motion detected should be turned on.
History of repetitious incorrect password alerts
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when someone input an incorrect password repetitiously.
History of Shake detected
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when sensor detected a shake
History of Sound or Light Detected
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when water sound or light were detected.
History of Timberwolf object value changes
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This returns a list of value changes recorded after this query is created.
History of when a Person was detected
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when PIR detected person.
History of when Door sensor was closed
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the door sensor was closed.
Activate Scene
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will activate the specified scene.
Set AC temperature
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set your AC to a specified temperature by remote controller.
Set light brightness
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set your light to a specified brightness.
Set light color
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set the light to specified color.
Set value
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
Set a Timberwolf Server object to a specified value. The selected Timberwolf Server will convert the textual value to the datatype of the target object. You can connect the target object to another subsystem like KNX, 1-Wire, Modbus, MQTT, HTTP or Timeseries
Start Cool Mode
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set your AC to Cool Mode.
Start Heat Mode
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set your AC to Heat Mode.
Switch off
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set a boolean Timberwolf object false.
Switch on
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set a boolean Timberwolf object true. You may connect the object on your Timberwolf Server to other services like KNX, 1Wire, Modbus oder MQTT.
Turn off
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will turn off the device/group of your choosing.
Turn off oscillation function of fan
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will turn off the oscillation function of your fan by IR remote controller.
Turn on
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will turn on the device/group of your choosing.
Activate Scene
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will activate the specified scene.
Battery low
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when residual electricity in the lock under threshold.
Camera detects motion
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified camera detects motion. To use this trigger, camera’s motion detection should be turned on.
Camera detects sound
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified camera detects sound. To use this trigger, camera’s sound detection should be turned on.
Device or group is turned off
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified device/group is turned off.
Device or group is turned on
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the specified device/group is turned on.
Door sensor is closed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the door sensor is closed.
Door sensor is open
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the door sensor is open.
History of Camera detected sound
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the specified camera detected sound. To use this query, camera’s sound detection must have been turned on.
History of Device turned off
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the specified device/group was turned off.
History of Device was turned on
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when the specified device/group was turned on.
History of Leak detected
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the sensor detected a water leak.
Build an automation in seconds!
If
Select a trigger the automation will use
Then
Select an action the automation will perform
You can add delays, queries, and more actions in the next step!
More on Smart Life and Timberwolf Server
About Smart Life
Smart Life provides extraordinary experience with your smart home appliances, including smart plugs, smart lights, air conditioners, humidifiers... As long as your device works with Smart Life, you'll be able to build automation tasks through IFTTT like turning on the living room light when you're back home.
Smart Life provides extraordinary experience with your smart home appliances, including smart plugs, smart lights, air conditioners, humidifiers... As long as your device works with Smart Life, you'll be able to build automation tasks through IFTTT like turning on the living room light when you're back home.
About Timberwolf Server
The Timberwolf Server is a very powerful multi-protocol gateway with visualisation, logic, Influx time series database, graphical analysis with Grafana and extensible with Docker Containers.
The Timberwolf Server locally supports 10 protocols in parallel with tens of thousands of data points that can be linked and recorded at will with each other and with other IFTTT services.
Cloud based services meets local Smarthome installation.
Documentation about Timberwolf Server integration with IFTTT
The Timberwolf Server is a very powerful multi-protocol gateway with visualisation, logic, Influx time series database, graphical analysis with Grafana and extensible with Docker Containers.
The Timberwolf Server locally supports 10 protocols in parallel with tens of thousands of data points that can be linked and recorded at will with each other and with other IFTTT services.
Cloud based services meets local Smarthome installation.
Documentation about Timberwolf Server integration with IFTTT