Why Is My Hubitat Dashboard So Slow?
- Hub CPU or memory overloaded
- A chatty device flooding the hub with events
- Heavy or inefficient custom apps and drivers
Problem Description
Your Hubitat dashboard loads but is slow, laggy, or times out, with tiles taking seconds to render or respond. The hub runs everything locally, so a sluggish dashboard usually points to the hub being CPU or memory constrained from too many devices, heavy custom apps, or a chatty device flooding the hub.
Why This Happens in Real Homes
A slow Hubitat dashboard is a symptom of the hub itself being loaded, since everything runs locally, so the fix is finding what is eating CPU or memory. In real homes a single chatty power-metering device or a heavy community app drags performance down over days until a reboot.
Reboot to confirm, then hunt the chatty device or app in the logs and trim oversized dashboards before assuming the hub is failing.
Symptoms
- Tiles take seconds to load or respond
- Dashboard lags when tapping controls
- Slower over time until a reboot
- Slow only on large dashboards
- Whole hub feels sluggish
- High hub load in the logs
- Slower after adding apps or devices
- Occasional timeouts
Recognize these? Here's what usually causes it.
Common Causes
- Hub CPU or memory overloaded
- A chatty device flooding the hub with events
- Heavy or inefficient custom apps and drivers
- Too many devices or tiles on one dashboard
- Zigbee or Z-Wave mesh retries adding load
- Memory leak needing a periodic reboot
- Database growth over time
- Logging left on debug for many devices
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
Step-by-Step Solution
Check hub CPU and memory load
In the Hubitat web interface, go to the hub About page or Settings > Hub Information. Look at CPU usage and free memory. If CPU is consistently above 70% or free memory drops below 100MB, the hub is overloaded. The Hubitat Elevation C-7 and C-8 hubs have limited hardware resources — they run well with moderate device counts but can struggle with 100+ devices or many complex Rule Machine rules running simultaneously.
Identify resource-heavy apps
Go to Apps in the web interface. Check each app for excessive logging or polling. Common offenders: Rule Machine rules with many conditions and actions that evaluate frequently, custom apps that poll external APIs, dashboards with live-updating tiles for many devices. Temporarily disable suspicious apps one at a time and check if hub performance improves. The Logs page shows which apps are generating the most log entries — high log volume often indicates an app running too frequently.
Remove Z-Wave ghost nodes
Ghost nodes are Z-Wave devices that failed to pair properly or were removed without exclusion. They appear in Settings > Z-Wave Details as entries with no route or cluster information. Ghost nodes continuously flood the Z-Wave mesh with route discovery requests, slowing down the hub and all Z-Wave devices. Click Remove on each ghost node. If the Remove button is grayed out, click Refresh first, wait 30 seconds, then try Remove again. Stubborn ghosts may need a Z-Wave radio reset (last resort).
Optimize dashboard tile count
Each dashboard tile maintains a WebSocket connection to the hub. Dashboards with 30+ tiles create significant overhead. Split large dashboards into smaller ones organized by room or function. Remove tiles for devices you rarely check on the dashboard — you can still control those devices through automations or voice assistants. Use attribute tiles instead of device tiles when you only need to display one value (like temperature) rather than full device controls.
Perform a soft reset if performance degraded over time
If the hub was fast when new and gradually slowed, the database may need cleanup. Go to Settings > Reboot Hub for a simple restart. If that does not help, a soft reset rebuilds the hub database without losing device pairings. Go to the hub diagnostic page (http://[hub-ip]:8081) and select Soft Reset. After the reset completes, restore your latest backup. This clears accumulated database bloat from years of log entries and event history.
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.
- Hub CPU or memory overloaded
- A chatty device flooding the hub with events
- Heavy or inefficient custom apps and drivers
- Too many devices or tiles on one dashboard
- Zigbee or Z-Wave mesh retries adding load
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Hubitat Elevation C-8 owners.
4 Pack Zigbee Door Sensor, Mini Smart Contact Sensors for...
2 Pack Zigbee Door Sensor, Mini Smart Contact Sensors for...
Z-Wave Long Range Double Switch (White) ZEN30 800LR for F...
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 C-8.
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.
