Skip to content

Troubleshooting Home Assistant

Troubleshooting Debug Logs

Something not working as expected? This guide helps you find and solve the most common problems in Home Assistant.


┌─────────────────────────────────────────────────────────────┐
│ TROUBLESHOOTING WORKFLOW │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. CHECK LOGS → Settings → System → Logs │
│ 2. IDENTIFY → Find error messages (red lines) │
│ 3. SEARCH ONLINE → Google the error message │
│ 4. COMMUNITY → Home Assistant Forum/Discord │
│ 5. RESTART → Often solves simple problems │
│ │
└─────────────────────────────────────────────────────────────┘
Log TypeLocation
Core logsSettings → System → Logs
Supervisor logsSettings → System → Logs → Supervisor
Add-on logsSettings → Add-ons → [Add-on] → Log
Full log file/config/home-assistant.log
# configuration.yaml
logger:
default: info
logs:
# Enable debug for specific component
homeassistant.components.zha: debug
homeassistant.components.mqtt: debug
# Or a specific integration
custom_components.hacs: debug

Symptom: Blank screen or “Unable to connect”

Section titled “Symptom: Blank screen or “Unable to connect””
  1. Wait 5-10 minutes - Startup can take time

  2. Check if HA is running:

    Terminal window
    # SSH into your server
    ha core info
  3. View startup logs:

    Terminal window
    ha core logs
  4. Common fixes:

    • Check configuration.yaml for syntax errors
    • Remove recently added integrations
    • Boot in safe mode
Terminal window
# Via SSH or terminal
ha core restart --safe-mode

Safe mode starts HA without custom integrations and add-ons.

# Validate configuration BEFORE restart
# Settings → System → Developer Tools → YAML → Check Configuration
# Or via command line:
ha core check

CauseSolution
Weak signalAdd more routers (powered devices)
InterferenceMove coordinator away from USB 3.0 / WiFi router
FirmwareUpdate coordinator firmware
Crowded channelChange Zigbee channel (11, 15, 20, 25)
  1. Put device in pairing mode (see manual)

  2. Ensure coordinator is ready:

    • Zigbee2MQTT: Permit Join enabled
    • ZHA: Add device enabled
  3. Place device CLOSE to coordinator during pairing

  4. Factory reset device and try again

  5. Check device is supported:

Terminal window
# Find USB device
ls -la /dev/serial/by-id/
# Use the permanent device name in configuration:
# /dev/serial/by-id/usb-Silicon_Labs_CP2102-xxxxx
# NOT /dev/ttyUSB0 (can change)

CheckSolution
Same networkDevice must be on same subnet
mDNSEnable mDNS on your router
IP addressFind IP via router or Shelly app
FirewallAllow UDP port 5683 (CoAP)
# Check WiFi signal strength
# Entity: sensor.device_wifi_signal
# If signal is weak:
# 1. Move device closer to AP
# 2. Add WiFi repeater
# 3. Switch to 2.4 GHz (better range)

  1. Is automation enabled?

    • Check toggle in Automations list
  2. Trigger correct?

    • Settings → Automations → [Automation] → Trace
    • Check “Last triggered”
  3. Conditions met?

    • Test each condition individually
    • Use Developer Tools → States
  4. Actions failing?

    • Check logs for errors
    • Test action manually via Services
# Developer Tools → Services
service: automation.trigger
target:
entity_id: automation.your_automation
data:
skip_condition: true # Skip conditions
  1. Go to Settings → Automations

  2. Click on the automation

  3. Click Traces (trace icon)

  4. See exactly what happened on last run:

    • Which triggers activated
    • Which conditions were true/false
    • Which actions ran/failed

Terminal window
# Stop Home Assistant
ha core stop
# Wait 30 seconds
# Start again
ha core start
Terminal window
# Backup first!
cp /config/home-assistant_v2.db /config/home-assistant_v2.db.backup
# Delete database (loses history)
rm /config/home-assistant_v2.db
# Restart - new database created automatically
ha core restart

See Performance Guide for database optimization.


ProblemSolution
Missing dependenciesRestart HA, check logs
Incompatible versionUpdate integration
Configuration errorCheck integration docs
Credentials expiredRe-authenticate
  1. Go to Settings → Devices & Services

  2. Find the integration

  3. Click Configure or Re-authenticate

  4. Follow OAuth flow again

Terminal window
# Reinstall HACS integration
1. Remove integration from Devices & Services
2. Delete folder: /config/custom_components/[integration]
3. Restart HA
4. Install again via HACS

  1. Clear browser cache:

    • Chrome: Ctrl+Shift+Del
    • Safari: Cmd+Alt+E
  2. Hard refresh:

    • Windows: Ctrl+Shift+R
    • Mac: Cmd+Shift+R
  3. Try incognito window

  4. Check resources loaded:

    • F12 → Console → Look for red errors
# Check resource is added:
# Settings → Dashboards → Resources
# Or in configuration.yaml:
lovelace:
mode: yaml
resources:
- url: /hacsfiles/button-card/button-card.js
type: module

Terminal window
# Via command line
ha auth reset --username YOUR_USERNAME --password NEW_PASSWORD
Terminal window
# Remove TOTP for user
ha auth totp remove --username YOUR_USERNAME
# Add temporarily to configuration.yaml:
homeassistant:
auth_providers:
- type: trusted_networks
trusted_networks:
- 192.168.1.0/24
allow_bypass_login: true
- type: homeassistant
# Restart, log in, remove again

Terminal window
# System info
ha info
ha core info
ha supervisor info
# Logs
ha core logs
ha supervisor logs
ha host logs
# Restart
ha core restart
ha supervisor restart
ha host reboot
# Update
ha core update
ha supervisor update
# Backup
ha backups new
ha backups list
ToolUse
StatesView/change entity states
ServicesTest services manually
TemplateTest Jinja2 templates
EventsView/fire events
StatisticsFix statistics problems

  • Checked logs for error messages
  • Searched for the error on Google
  • Checked Home Assistant documentation
  • Restarted Home Assistant
  • Updated to latest version
  • Tested in Safe Mode

Always include:

**Home Assistant version:** 2025.x.x
**Installation type:** HAOS / Docker / Core
**Hardware:** RPi4 / Intel NUC / VM
**Problem:** Short description
**Logs:**

[Relevant log lines]

**What you've tried:**
- List of attempted solutions

Ofte stillede spørgsmål

Why is my Home Assistant slow?
The most common causes are: large database (reduce purge_keep_days), too many integrations polling, or slow storage (SD card). See the Performance guide for solutions.
How do I find out what's wrong?
Always start with logs: Settings → System → Logs. Look for red error lines. Copy the error message and search on Google or Home Assistant Community forum.
My automation was working but suddenly stopped?
Check Automation trace to see what's happening. Often it's a condition that's no longer met, an entity that changed name, or an integration that went offline.
How do I restart without losing my settings?
A normal restart (Settings → System → Restart) preserves all settings. You only lose data if you delete configuration files or the database.


Last updated: December 2025


Kommentarer