Turn off functional light of your hood when your WeMo bulbs are turned off
Other popular Home Connect Hood workflows and automations
-
-
-
Turn on the Ambient Light on the Hood at a specific date and time.
5
-
-
Turn off your hood light every evening before going to bed
43
-
-
Get an email when the hood grease filter is saturated
28
-
-
Get an email when the regenerative carbon filter of your hood is saturated
5
-
-
Turn off your hood light and Philips Hue lights every evening before going to bed
1
-
-
Get an email when Home Connect Hood publishes a new trigger or action
2
-
-
Turn on functional light of your hood when your WeMo bulbs are turned on
-
-
Get notified when the mulled wine is at the perfect temperature
1
-
Create your own Home Connect Hood and Wireless Tag 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.
74 triggers, queries, and actions
Ambient light 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 every time the ambient light is turned off. Please note that this trigger is not supported by all hoods.
Ambient light 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 every time the ambient light is turned on. Please note that this trigger is not supported by all hoods.
Back in range
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 specified tag comes out of "out of range" state. Only tags with auto-update is enabled can come out of "out of range" state.
Brightness returns to normal
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 specified tag senses that its ambient light intensity returns between the upper and lower thresholds configured at light options screen inside the WirelessTag app.
Carbon filter saturation nearly reached
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 every time the carbon filter saturation is nearly reached.
Door or window 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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window is closed.
Door or window is opened
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 specified motion sensor tag(s) or reed sensor(s) detect that a door or window is open.
Functional light 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 every time the functional light is turned off.
Functional light 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 every time the functional light is turned on.
Grease filter saturation reached
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 every time the grease filter saturation is reached.
Hood Favourite button (long press)
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 triggers fires every time the hood favourite button is long (>3s) pressed. Please note that this trigger is not supported by all hoods.
Hood Favourite button (short press)
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 triggers fires every time the hood favourite button is short (<3s) pressed. Please note that this trigger is not supported by all hoods.
Hood 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 every time your hood is turned off.
Hood 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 every time your hood is turned on.
Humidity or moisture is too high
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 specified tag with humidity or moisture monitoring enabled, detects "too wet" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture is too 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 a specified tag with humidity or moisture monitoring enabled, detects "too dry" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture returns to normal
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 specified tag with humidity or moisture monitoring enabled, returns within normal humidity range. Adjust the upper/lower thresholds from the humidity/moisture options screen inside the WirelessTag app.
Motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
Movement 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 specified PIR KumoSensor detects movement.
New KumoApp message
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 every time a specific KumoApp produces a log message with KumoApp.Log call with a specific type.
Out of range
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 specified tag goes out of range. Note that the system can only determine whether a tag is out of range, if the "auto-update" is enabled.
Regenerative carbon filter saturation reached
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 every time the regenerative carbon filter saturation is reached.
Sensor detects water
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 specified water sensor tag detects water with its resistive sensor, or when you short circuit its tip.
Sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
Tag is moved
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
Tag Manager Offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
Tag Manager Online
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 specified tag manager is back online.
Temperature is too high
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 specified tag senses that its ambient temperature exceeds an upper threshold configured at temperature options screen inside the WirelessTag app.
Temperature is too 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 a specified tag senses that its ambient temperature falls below an lower threshold configured at temperature options screen inside the WirelessTag app.
Temperature returns to normal
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 specified tag senses that its ambient temperature returns between the upper and lower thresholds configured at temperature options screen inside the WirelessTag app.
Too bright
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 specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. For example, this can be used to detect fridge door open.
Too dark
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 specified tag senses that its ambient light exceeds an lower threshold configured at light options screen inside the WirelessTag app. For example, this can be used to turn on a light in a room.
Update received
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 every time a temperature/humidity/lux update is received from specified sensor/tag(s).
Current Tag Manager State
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.
The query returns if the specified tag manager is online or offline, as well as how many hours it has been online.
Current Tag State
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 specified door/window sensor/tag's current state, including temperature, humidity/lux (when available) and motion state such as door open/close, moved, or detected motion (for PIR sensor)
History of door or window is 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 when a specified motion sensor tag(s) or reed sensor(s) detect that a door or window was closed.
History of door or window is opened
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 specified motion sensor tag(s) or reed sensor(s) detect that a door or window was open.
History of High Temperature 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 a specified tag senses that its ambient temperature exceeded an upper threshold configured at temperature options screen inside the WirelessTag app. Note: this query will only return future events after this Applet
History of humidity or moisture is too high
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 specified tag with humidity or moisture monitoring enabled, detects "too wet" state.
History of KumoApp messages
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 every time a specific KumoApp produces a log message with KumoApp.Log call with a specific type.
History of motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
History of sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
History of tag manager offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
History of tag moves
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
History of tag out of range
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 specified tag goes out of range. Note that the system can only determine whether a tag was out of range, if the "auto-update" was enabled.
History of temperature returning to normal
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 tag sensed that its ambient temperature had returned between the upper and lower thresholds configured on the temperature options screen inside the WirelessTag app. Note: this query will only return future e
History of too bright
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 specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. Note: this query will only return future events after this Applet is created.
History of update received
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 temperature/humidity/lux update was received from specified sensor/tag(s).
History of when Grease filter saturation was reached
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 grease filter saturation was reached.
History of when regenerative carbon filter saturation reached a threshold
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 regenerative carbon filter saturation was reached. Note: this query will only return future events after this Applet is created.
History of when temperature was too low
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 specified tag sensed that its ambient temperature fell below a threshold. Note: this query will only return future events after this Applet is created.
History of when the tag manager was online
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 tag manager was back online.
Arm motion sensor
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 arms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be armed using this action.
Beep a tag
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 beep the tag. NOTE: Only compatible with the Motion Sensor Tags with buzzer.
Disable brightness monitoring
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 disable brightness/ambient light intensity monitoring on a tag.
Disable humidity or moisture monitoring
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 disable humidity or moisture monitoring on a tag.
Disable temperature monitoring
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 disable temperature monitoring on a tag.
Disarm motion sensor
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 disarms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be disarmed using this action.
Enable brightness monitoring
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 enable brightness/ambient light intensity monitoring on a tag. NOTE: Only compatible with Tags with ambient light sensor.
Enable humidity or moisture monitoring
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 enable humidity or moisture monitoring on a tag. NOTE: Only compatible with Tags with humidity or moisture sensor.
Enable temperature monitoring
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 enable temperature monitoring on a tag.
Run a KumoApp
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 start a KumoApp installed under the current user account. If the KumoApp is running, nothing will happen. If a KumoApp does not register any event handler or timer, it will automatically stop after executing the first time, allowing this action to run multiple times without user intervention.
Start program
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 start the selected hood program.
Stop a KumoApp
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 stop a KumoApp. If the KumoApp is not running, nothing will happen.
Stop beeping a tag
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 stop the tag beeping. This action can also be used to test tag connectivity.
Turn off ambient light
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 ambient light of your hood. Please note that this action is not supported by all hoods.
Turn off functional light
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 functional light of your hood.
Turn off hood
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 hood.
Turn off light or switch
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 LED on the tag or a WeMo device.
Turn on ambient light
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 ambient light of your hood with the selected color. Please note that this action is not supported by all hoods.
Turn on functional light
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 functional light of your hood with the selected brightness.
Turn on hood
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 your hood with the default program.
Turn on light or switch
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 LED on the tag or a WeMo device.
Update Temperature/Humidity/Lux
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 force an update to read the current temperature, humidity and ambient light (when available).
Ambient light 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 every time the ambient light is turned off. Please note that this trigger is not supported by all hoods.
Ambient light 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 every time the ambient light is turned on. Please note that this trigger is not supported by all hoods.
Arm motion sensor
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 arms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be armed using this action.
Back in range
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 specified tag comes out of "out of range" state. Only tags with auto-update is enabled can come out of "out of range" state.
Beep a tag
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 beep the tag. NOTE: Only compatible with the Motion Sensor Tags with buzzer.
Brightness returns to normal
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 specified tag senses that its ambient light intensity returns between the upper and lower thresholds configured at light options screen inside the WirelessTag app.
Carbon filter saturation nearly reached
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 every time the carbon filter saturation is nearly reached.
Current Tag Manager State
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.
The query returns if the specified tag manager is online or offline, as well as how many hours it has been online.
Current Tag State
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 specified door/window sensor/tag's current state, including temperature, humidity/lux (when available) and motion state such as door open/close, moved, or detected motion (for PIR sensor)
Disable brightness monitoring
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 disable brightness/ambient light intensity monitoring on a tag.
Disable humidity or moisture monitoring
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 disable humidity or moisture monitoring on a tag.
Disable temperature monitoring
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 disable temperature monitoring on a tag.
Disarm motion sensor
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 disarms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be disarmed using this action.
Door or window 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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window is closed.
Door or window is opened
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 specified motion sensor tag(s) or reed sensor(s) detect that a door or window is open.
Enable brightness monitoring
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 enable brightness/ambient light intensity monitoring on a tag. NOTE: Only compatible with Tags with ambient light sensor.
Enable humidity or moisture monitoring
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 enable humidity or moisture monitoring on a tag. NOTE: Only compatible with Tags with humidity or moisture sensor.
Enable temperature monitoring
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 enable temperature monitoring on a tag.
Functional light 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 every time the functional light is turned off.
Functional light 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 every time the functional light is turned on.
Grease filter saturation reached
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 every time the grease filter saturation is reached.
History of door or window is 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 when a specified motion sensor tag(s) or reed sensor(s) detect that a door or window was closed.
History of door or window is opened
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 specified motion sensor tag(s) or reed sensor(s) detect that a door or window was open.
History of High Temperature 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 a specified tag senses that its ambient temperature exceeded an upper threshold configured at temperature options screen inside the WirelessTag app. Note: this query will only return future events after this Applet
History of humidity or moisture is too high
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 specified tag with humidity or moisture monitoring enabled, detects "too wet" state.
History of KumoApp messages
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 every time a specific KumoApp produces a log message with KumoApp.Log call with a specific type.
History of motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
History of sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
History of tag manager offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
History of tag moves
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
History of tag out of range
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 specified tag goes out of range. Note that the system can only determine whether a tag was out of range, if the "auto-update" was enabled.
History of temperature returning to normal
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 tag sensed that its ambient temperature had returned between the upper and lower thresholds configured on the temperature options screen inside the WirelessTag app. Note: this query will only return future e
History of too bright
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 specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. Note: this query will only return future events after this Applet is created.
History of update received
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 temperature/humidity/lux update was received from specified sensor/tag(s).
History of when Grease filter saturation was reached
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 grease filter saturation was reached.
History of when regenerative carbon filter saturation reached a threshold
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 regenerative carbon filter saturation was reached. Note: this query will only return future events after this Applet is created.
History of when temperature was too low
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 specified tag sensed that its ambient temperature fell below a threshold. Note: this query will only return future events after this Applet is created.
History of when the tag manager was online
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 tag manager was back online.
Hood Favourite button (long press)
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 triggers fires every time the hood favourite button is long (>3s) pressed. Please note that this trigger is not supported by all hoods.
Hood Favourite button (short press)
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 triggers fires every time the hood favourite button is short (<3s) pressed. Please note that this trigger is not supported by all hoods.
Hood 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 every time your hood is turned off.
Hood 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 every time your hood is turned on.
Humidity or moisture is too high
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 specified tag with humidity or moisture monitoring enabled, detects "too wet" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture is too 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 a specified tag with humidity or moisture monitoring enabled, detects "too dry" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture returns to normal
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 specified tag with humidity or moisture monitoring enabled, returns within normal humidity range. Adjust the upper/lower thresholds from the humidity/moisture options screen inside the WirelessTag app.
Motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
Movement 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 specified PIR KumoSensor detects movement.
New KumoApp message
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 every time a specific KumoApp produces a log message with KumoApp.Log call with a specific type.
Out of range
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 specified tag goes out of range. Note that the system can only determine whether a tag is out of range, if the "auto-update" is enabled.
Regenerative carbon filter saturation reached
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 every time the regenerative carbon filter saturation is reached.
Run a KumoApp
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 start a KumoApp installed under the current user account. If the KumoApp is running, nothing will happen. If a KumoApp does not register any event handler or timer, it will automatically stop after executing the first time, allowing this action to run multiple times without user intervention.
Sensor detects water
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 specified water sensor tag detects water with its resistive sensor, or when you short circuit its tip.
Sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
Start program
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 start the selected hood program.
Stop a KumoApp
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 stop a KumoApp. If the KumoApp is not running, nothing will happen.
Stop beeping a tag
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 stop the tag beeping. This action can also be used to test tag connectivity.
Tag is moved
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
Tag Manager Offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
Tag Manager Online
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 specified tag manager is back online.
Temperature is too high
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 specified tag senses that its ambient temperature exceeds an upper threshold configured at temperature options screen inside the WirelessTag app.
Temperature is too 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 a specified tag senses that its ambient temperature falls below an lower threshold configured at temperature options screen inside the WirelessTag app.
Temperature returns to normal
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 specified tag senses that its ambient temperature returns between the upper and lower thresholds configured at temperature options screen inside the WirelessTag app.
Too bright
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 specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. For example, this can be used to detect fridge door open.
Too dark
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 specified tag senses that its ambient light exceeds an lower threshold configured at light options screen inside the WirelessTag app. For example, this can be used to turn on a light in a room.
Turn off ambient light
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 ambient light of your hood. Please note that this action is not supported by all hoods.
Turn off functional light
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 functional light of your hood.
Turn off hood
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 hood.
Turn off light or switch
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 LED on the tag or a WeMo device.
Turn on ambient light
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 ambient light of your hood with the selected color. Please note that this action is not supported by all hoods.
Turn on functional light
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 functional light of your hood with the selected brightness.
Turn on hood
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 your hood with the default program.
Turn on light or switch
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 LED on the tag or a WeMo device.
Update received
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 every time a temperature/humidity/lux update is received from specified sensor/tag(s).
Update Temperature/Humidity/Lux
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 force an update to read the current temperature, humidity and ambient light (when available).
GET STARTED
How to connect to a Home Connect Hood automation
Find an automation using Home Connect Hood
Find an automation to connect to, or create your own!Connect IFTTT to your Home Connect Hood account
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!Upgrade your automations with
-
Connect to more Applets
Connect up to 20 automations with Pro, and unlimited automations with Pro+ -
Add multiple actions with exclusive services
Add real-time data and multiple actions for smarter automations -
Get access to faster speeds
Get faster updates and more actions with higher rate limits and quicker checks
More on Discord and Instagram
About Home Connect Hood
Home Connect is featured on a wide range of connected home appliances from Bosch, Siemens, Neff, Gaggenau and Thermador. With Home Connect you can connect your home appliances to other devices and services making your home appliance truly smart. Monitor and control your home appliances with Home Connect whether you are at home or out and about.
Home Connect is featured on a wide range of connected home appliances from Bosch, Siemens, Neff, Gaggenau and Thermador. With Home Connect you can connect your home appliances to other devices and services making your home appliance truly smart. Monitor and control your home appliances with Home Connect whether you are at home or out and about.
About Wireless Tag
Wireless Sensor Tag monitors and records motion events, temperature, humidity, ambient light, water leaks and can be used to find keys through beeps.
Wireless Sensor Tag monitors and records motion events, temperature, humidity, ambient light, water leaks and can be used to find keys through beeps.