Why Won't My Hubitat Rule Machine Work?
- Trigger event not firing (device not reporting)
- Condition or required expression blocking the rule
- Wrong trigger type chosen
Problem Description
A Rule Machine rule on your Hubitat does not work as expected, it does not trigger, triggers at the wrong time, or runs its actions incompletely. Rule Machine is powerful but strict about triggers, conditions, and actions, so most failures come down to the trigger not firing, a condition blocking the rule, or the actions targeting a stale device.
Why This Happens in Real Homes
Rule Machine failures are almost always the trigger or a condition, not a broken hub, since a rule that runs when you press Run Actions proves the actions work. In real homes the trigger device is not reporting, or a leftover condition is quietly blocking the rule.
Confirm the trigger device reports, walk the conditions, and re-select target devices before rebuilding the rule from scratch.
Symptoms
- Rule never triggers
- Rule triggers but actions do not all run
- Rule fires at the wrong time
- Conditions never evaluate true
- Rule works manually but not on event
- Wrong devices respond
- Rule stopped after an edit
- Actions run out of order
Recognize these? Here's what usually causes it.
Common Causes
- Trigger event not firing (device not reporting)
- Condition or required expression blocking the rule
- Wrong trigger type chosen
- Actions targeting a stale or renamed device
- Time or timezone off for scheduled triggers
- Rule paused or disabled
- Overlapping rules conflicting
- Missing wait or delay causing race conditions
Most fixes happen in the first 3 steps.
Do not factory reset your hub unless absolutely necessary as this removes all paired devices, automations, and settings. You will need to re-pair every single device from scratch which can take hours for a large setup. Always try a simple restart first.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Check if the rule is enabled
Open the Rule Machine rule in Apps. At the top of the rule page, check if the rule shows as Paused or Disabled. If paused, click Resume. Rules can be paused manually, by another rule action, or by a mode restriction. Also check if the rule has a mode restriction set — if the hub is in a mode not included in the rule's allowed modes, the rule will not execute.
Verify trigger devices are reporting events
Go to the device page for the trigger device and check Last Activity. If the timestamp is old, the device is not sending events to the hub. For Zigbee/Z-Wave devices, this usually means a mesh connectivity issue — check signal strength, battery level, or re-pair the device. For cloud devices, check the cloud integration status. The rule cannot fire if the trigger device never sends an event.
Review conditions for logic errors
Open the rule and read through the conditions carefully. A common mistake: using Required Expression with AND when OR is needed. Example: if you set conditions as Motion is Active AND Time is between 6PM and 6AM AND Mode is Home, all three must be true simultaneously. If any one is false, the actions are blocked. Check the Logs page — Rule Machine logs each condition evaluation as TRUE or FALSE, showing exactly which condition blocked execution.
Check for conflicting rules or apps
If another rule or app controls the same device, it can override your rule's actions. Example: Rule A turns a light on at motion, but Simple Automation Rule B turns the same light off every night at 10 PM. If motion triggers at 10:01 PM, Rule A turns the light on, then Rule B immediately turns it off. Check the device's In Use By section to see all apps controlling it. Coordinate the rules or add conditions to prevent conflicts.
Rebuild the rule if it became corrupted
Occasionally, complex rules with many edits can develop internal state issues — conditions that look correct in the UI but evaluate incorrectly. If the logs show nonsensical evaluations, create a new rule from scratch rather than continuing to edit the broken one. Copy the trigger, conditions, and actions to a new Rule Machine rule. Delete the broken rule. Rebuilding is faster than debugging a corrupted rule state.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the hub reconnects then drops every few minutes, check for an IP conflict — two devices sharing the same DHCP address fight each other continuously.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.
- Trigger event not firing (device not reporting)
- Condition or required expression blocking the rule
- Wrong trigger type chosen
- Actions targeting a stale or renamed device
- Time or timezone off for scheduled triggers
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Hubitat Elevation owners.
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Hubitat provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Hubitat Elevation.
Source: hubitat.com
Need More Help? Hubitat Support
Note: The contact information below connects you directly to Hubitat's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
