Troubleshooting Browser Console Logs

Troubleshooting: Browser Console Logs

Browser console logs capture errors and warnings from LCM's frontend components — dashboard strategies, custom cards, and Lovelace rendering. They are essential for diagnosing UI issues.

Opening the Browser Console

Chrome / Edge

1. Open your Home Assistant dashboard in the browser.
2. Press F12 (or Ctrl+Shift+J on Windows/Linux, Cmd+Option+J on Mac).
3. Click the Console tab.

Firefox

1. Open your Home Assistant dashboard in the browser.
2. Press F12 (or Ctrl+Shift+K on Windows/Linux, Cmd+Option+K on Mac).
3. Click the Console tab.

Safari

1. Enable the developer menu: Safari → Settings → Advanced → Show Develop menu.
2. Open your Home Assistant dashboard.
3. Press Cmd+Option+C or go to Develop → Show JavaScript Console.

Home Assistant Companion App (Mobile)

The companion app does not expose a browser console directly. To capture frontend logs on mobile:

1. Open your HA instance in a mobile browser (Chrome, Safari) instead of the companion app.
2. For Android: connect the device via USB, open chrome://inspect on your desktop Chrome, and use remote debugging.
3. For iOS: connect the device via USB, open Safari on your Mac, and use Develop → [device name] → [HA tab].

Capturing Console Logs for a Bug Report

1. Open the browser console before reproducing the issue.
2. Clear the console (click the 🚫 icon or type clear()) to remove old messages.
3. Reproduce the issue.
4. Look for red (errors) and yellow (warnings) messages. Include all of them — don't try to pick out which ones seem relevant.
5. Right-click in the console and select Save as... to download the full console log, or copy and paste the messages.

Tip: Share the full console output rather than individual error lines. Like backend logs, surrounding context matters — an earlier warning may explain a later error.

Common Frontend Issues

These are the types of issues where console logs are needed:

• Cards not rendering or showing errors
• Dashboard strategy not generating views
• Missing or incorrect entity data in the UI
• JavaScript errors after updating LCM or HA

What to Include in a Bug Report

• The full console output from before reproducing through the issue
• Your browser name and version (e.g., Chrome 130, Safari 18)
• Whether you're using the companion app or a browser
• A screenshot of the issue alongside the console logs

← Back to Troubleshooting