Troubleshooting

Troubleshooting

This section helps you diagnose issues with Lock Code Manager and file effective bug reports.

Before Filing an Issue

1. Check the wiki — Many questions are answered in the Features documentation.
2. Update to the latest version — Your issue may already be fixed. Check releases for recent changes.
3. Reproduce with debug logging — Enable debug logs before reproducing the issue so you capture the full trace. See Troubleshooting: Debug Logs.
4. Gather device diagnostics — Download diagnostics for your lock device so maintainers can see exactly what HA knows about it. See Troubleshooting: Device Diagnostics.
5. For frontend issues — Open the browser console before reproducing to capture JavaScript errors. See Troubleshooting: Browser Console Logs.

Filing a Bug Report

Use the bug report template to file an issue. A good bug report includes:

• Clear description of what happened vs. what you expected
• Steps to reproduce the issue
• Debug logs captured while reproducing (see Troubleshooting: Debug Logs)
• Device diagnostics for your lock (see Troubleshooting: Device Diagnostics)
• Browser console logs for frontend/dashboard issues (see Troubleshooting: Browser Console Logs)
• HA and LCM versions

Subpages

• Troubleshooting: Debug Logs — How to enable debug logging for LCM
• Troubleshooting: Device Diagnostics — How to download diagnostics for your lock device
• Troubleshooting: Browser Console Logs — How to capture browser console logs for frontend issues