FREE SHIPPING WITHIN AUSTRALIA FOR ALL ORDERS OVER $199
Support
How to access and read Home Assistant logs
When something in Home Assistant Green isn’t working (an integration won’t load, a device drops off, an automation won’t run), the logs will usually give us clues as to why – you just need to know where to look – and what to look for.
This guide will show you:
- Where to find logs on Home Assistant Green
- How to filter and spot the important messages
- The common log clues that explain most issues
- What to copy/paste when you need support
Where to find logs on Home Assistant Green
1: Home Assistant Core Logs (the main ones)
- Go to Settings > System > Logs
- This page shows the Home Assistant Core log (startup, integrations, automations, errors)
Use this for: integrations failing, startup issues, general errors.
2) Add-on Logs (Google Drive Backup, Zigbee2MQTT, Mosquitto, etc.)
- Go to Settings > Add-ons
- Click the add-on
- Open the Logs tab
Use this for: anything related to a specific add-on.
3) Supervisor / Host Logs (rare, but useful)
- Go to Settings > System
- Look for Supervisor / Host related options (varies by version)
- Check logs if you suspect system-level issues (storage, networking, OS)
Use this for:update problems, OS/network issues, storage faults.
Where to find logs on Home Assistant Green
1: Home Assistant Core Logs (the main ones)
- Go to Settings > System > Logs
- This page shows the Home Assistant Core log (startup, integrations, automations, errors)
Use this for: integrations failing, startup issues, general errors.
2) Add-on Logs (Google Drive Backup, Zigbee2MQTT, Mosquitto, etc.)
- Go to Settings > Add-ons
- Click the add-on
- Open the Logs tab
Use this for: anything related to a specific add-on.
3) Supervisor / Host Logs (rare, but useful)
- Go to Settings > System
- Look for Supervisor / Host related options (varies by version)
- Check logs if you suspect system-level issues (storage, networking, OS)
Use this for:update problems, OS/network issues, storage faults.
The 30-second log method
This is usually the fastest way to find issues. When you open the logs, do this:
- Start at the top if it’s just happened. If it was an issue during boot/update, scroll to where the restart/update occurred.
- Search for keywords (browser search: Ctrl+F / Cmd+F):
- error
- warning
- failed
- exception
- timeout
- unavailable
- disconnect
- cannot
- permission
- Look for the FIRST error, not the last one. One failure often causes a chain of follow-on errors.
Common things to look for
1: “Config” or YAML errors (broken config)
Typical clues:
- Invalid config
- ConfigError
- YAMLException
- mapping values are not allowed
- expected <block end>, but found…
What it means: a typo or formatting issue in config files can prevent parts of HA from loading.
Fix approach: undo the last config change or restore a backup made before edits.
2: Integration failing to set up
Typical clues:
- Setup failed for <integration>
- Integration failed to initialise
- Platform error
- Unable to import component
What it means: that an integration can’t start (credentials, connectivity, dependency or version mismatch).
Fix approach:
- Re-authenticate that integration
- Confirm the device/service is reachable
- Check if it started happening after an update
3: Network / DNS problems (very common)
Typical clues:
- Name or service not known
- Temporary failure in name resolution
- Failed to connect
- Connection refused
- No route to host
What it means: Home Assistant Green can’t reach something on your network or the internet.
Fix approach:
- Restart router/switch/AP
- Confirm your HA Green is on the right network
- Check DNS settings
- If using IPs, confirm they haven’t changed
4: Timeouts (device or service not responding)
Typical clues:
- TimeoutError
- Read timed out
- Request timed out
- asyncio.TimeoutError
What it means: the “thing” HA is talking to didn’t respond fast enough.
Fix approach:
- Check device is online
- Reduce load (too many requests can cause timeouts)
- Check Wi-Fi strength if it’s a Wi-Fi device
- Check network cables / connections if it is a network attached device
5: Storage / database issues (important on any appliance)
Typical clues:
- database disk image is malformed
- Recorder
- SQLite
- I/O error
- No space left on device
What it means: your database/storage is struggling or full.
Fix approach:
- Free disk space
- Consider database maintenance
- Restore from a known-good backup if corruption is suspected
6: Zigbee / Z-Wave / MQTT issues (if you use them)
Typical clues:
-
- MQTT connection lost
- Disconnected from broker
- ZHA failed to connect
- Failed to start radio
- Coordinator not found
-
- Check the add-on logs (Mosquitto / Zigbee2MQTT)
- Power cycle your HA Green + coordinator (if needed)
- Confirm the coordinator hasn’t changed port/path after an update
“Warnings” vs “Errors”
Which should you care about and how much weight do you give warnings vs errors?
Errors (care immediately!)
These usually break something:
- Integration setup failures
- Exceptions
- DB/storage issues
- Authentication failures
Warnings (often OK, but watch them)
Warnings can be harmless noise, but repeated warnings can point to the real issue:
- A device repeatedly disconnecting
- Slow response times
- Deprecated config entries (these matter before future updates)
Quick troubleshooting suggestions (before you go nuclear!)
If you’re stuck and need a quick win, try these suggestions:
- Restart Home Assistant (Settings > System > Restart)
- If the issue is an add-on: Restart the add-on
- If it happened after changes: Restore the last known-good backup
- If it happened after an update: check for deprecated warnings and broken integrations
If all else fails, check online (Home Assistant Community Forum, Reddit, Google search) – or try asking your favourite “AI” engine (just be careful of “hallucinations”, it could make things worse!).
Updated on February 17, 2026
