Turn on SmartThings and Hubitat devices when you get into bed
by
10 ready-made Withings Sleep and Hubitat Applets
Turn one on, or build your own. Withings Sleep can start an automation with "Export my last sleep data", and IFTTT can then run "Change Mode" on Hubitat.-
-
-
Close Hubitat device when your Withings Sleep detects you get into bedby
-
-
Turn off lights or devices when you get out of bedby
-
-
Turn on Hubitat device when you get out of bedby
-
-
Turn off Hubitat device when you get out of bedby
-
-
Turn on Hubitat device when you get into bedby
-
-
Open Hubitat device when you get out of bedby
-
-
Turn off Hubitat lights when Withings Sleep detects you get into bedby
-
-
Set Hubitat to Night mode when you get into bedby
-
Automate Withings Sleep and Hubitat from your AI assistant
Ask Claude to create Withings Sleep applets for you, right from your AI assistant, with IFTTT MCP.
Set up IFTTT MCP
Create your own Withings Sleep and Hubitat 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.
32 triggers, queries, and actions
Device closes
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device closes.
Device opens
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device opens.
Device turns 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device turns off.
Device turns 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device turns on.
Export my last sleep data
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires once your last sleep data is ready for exportation.
Mode changes
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when the Hubitat mode changes.
Motion 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when new motion is detected.
Motion is no longer 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when motion is no longer detected.
Presence 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time your Hubitat device's presence is detected.
Presence is no longer 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time your Hubitat device's presence is no longer detected.
Temperature drops below
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time the temperature drops below the specified threshold.
Temperature rises above
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time the temperature rises above the specified threshold.
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 when your Hubitat device turned off.
History of Mode 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 query returns a list of when the Hubitat mode has changed.
History of my sleep data exports
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 instances of when your sleep data was exported.
History of temperature rises above
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 temperature rises above the specified threshold. Note: this query will only return future events after this Applet is created.
History of when I get into bed
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 your Withings Sleep detects that you get into bed, within the start and end time parameters that you specify.
History of when I get out of bed
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 your Withings Sleep detects that you get out of bed, within the start and end time parameters that you specify.
Recent history of device opens
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 recent times when your Habitat device opened.
Recent history of Device turns 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 recent Hubitat device turns on events.
Change 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 change Hubitat's mode.
Close a device
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 close a Hubitat device.
Dim a device
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 change a device's dimmer level.
Lock a device
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 lock a Hubitat device.
Open a device
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 open a Hubitat device.
Turn off a device
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 your Hubitat switches, lights, sirens, strobes, etc.
Turn on a device
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 a device attached to your Hubitat Elevation system.
Unlock a device
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 unlock a Hubitat device.
Change 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 change Hubitat's mode.
Close a device
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 close a Hubitat device.
Device closes
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device closes.
Device opens
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device opens.
Device turns 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device turns off.
Device turns 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when your Hubitat device turns on.
Dim a device
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 change a device's dimmer level.
Export my last sleep data
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires once your last sleep data is ready for exportation.
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 when your Hubitat device turned off.
History of Mode 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 query returns a list of when the Hubitat mode has changed.
History of my sleep data exports
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 instances of when your sleep data was exported.
History of temperature rises above
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 temperature rises above the specified threshold. Note: this query will only return future events after this Applet is created.
Build an automation in seconds!
If
Select a trigger the automation will use
Device closes
Device opens
Device turns off
Device turns on
Export my last sleep data
Mode changes
Motion is detected
Motion is no longer detected
Presence is detected
Presence is no longer detected
Temperature drops below
Temperature rises above
Water is detected
Water is no longer detected
When I get into bed
When I get out of bed
Then
Select an action the automation will perform
Change Mode
Close a device
Dim a device
Lock a device
Open a device
Turn off a device
Turn on a device
Unlock a device
You can add delays, queries, and more actions in the chat.
GET STARTED
How to connect to a Withings Sleep automation
Find an Applet using Withings Sleep and Hubitat
Find an automation to connect to, or create your own!Connect IFTTT to your accounts
Securely connect the Applet services to your respective accounts.Finalize and customize your Applet
Review trigger and action settings, and click connect. Simple as that!Make more happen with your credits
-
More credits, more possibilities
Get more credits per month to power more automation activity. -
Power more advanced automations
Use credits to power your automations, including actions that require more processing. -
Access faster speeds and higher rate limits
Get faster updates and more actions with increased rate limits and more frequent checks.
Withings Sleep and Hubitat tips, tools, and resources
More on Withings Sleep and Hubitat
About Withings Sleep
Withings Sleep is a sleep sensor that tracks heart rate, sleep cycles and features snoring detection. Improve your sleep environment by using applets to lower the room temperature when you get into bed, turn on the lights when you get out of bed, and more.
About Hubitat
Hubitat Elevation is a powerful home automation platform that works with your connected devices. Hubitat is a local solution, not cloud-dependent, so it’s fast, reliable and private.