Other popular Emfit QS workflows and automations
-
Turn off Yeelight when Emfit QS detects you're in bedby
-
Add Emfit QS bed exit events to Google Sheetsby
-
Log sleep in iOS Health when you fall asleep with Emfit QSby
-
Turn on Yeelight lights when you get out of bedby
-
Log and share Emfit QS sleep events to Google services and Telegramby
-
Turn off D-Link Smart Plug when Emfit QS detects bedtimeby
-
Turn off SmartThings light when Emfit QS bed return detectedby
-
Turn on Philips Hue lights when you get out of bedby
-
Mute Android ringtone when Emfit QS detects sleepby
Automate Emfit QS and Hubitat from your AI assistant
Ask Perplexity to create Emfit QS applets based on sensor events, right from your AI assistant, with IFTTT MCP.
Set up IFTTT MCPCreate your own Emfit QS 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.
27 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 Event
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 device generates event (bed exit, fall asleep etc)
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.
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 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.
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 Event
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 device generates event (bed exit, fall asleep etc)
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.
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 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.
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.
Build an automation in seconds!
If
Device closes
Then
Change Mode
You can add delays, queries, and more actions in the chat.
GET STARTED
How to connect to a Emfit QS automation
Find an Applet using Emfit QS 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.
More on Emfit QS and Hubitat
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.