This document explains the changes made to address WebUI access issues and clarify the deprecation of dashboard auto-creation.
Problem: Users were confused about dashboard creation failing with 404 errors, even though this is expected behavior.
Solution: Added prominent warnings throughout the codebase:
- config.yaml: Clear deprecation notice explaining dashboard creation doesn't work
- sentry_service.py: Warning box displayed when dashboard creation is attempted
- dashboard_manager.py: Deprecation warning in the method itself
- ha_client.py: Prominent warning before attempting API call
Result: Users now understand dashboard creation is deprecated and should use WebUI instead.
Problem: Users were unclear on how to access the WebUI.
Solution: Enhanced startup notification with three clear access methods:
- Sidebar Panel (preferred): Look for "Sentry" in the Home Assistant sidebar
- Add-on Settings: Settings → Add-ons → Home Assistant Sentry → Open Web UI
- Direct Ingress URL:
/hassio/ingress/ha_sentry/
Result: Clear, step-by-step instructions for accessing the WebUI.
Problem: Notification links were not clearly explained.
Solution:
- All notification links use ingress URL format:
/hassio/ingress/ha_sentry/ - Added "Alternative Access Methods" section in notifications
- Emphasized sidebar panel as the easiest access method
Result: Users understand all links point to WebUI, not a dashboard.
- Open your Home Assistant
- Look for the "Sentry" panel in the left sidebar
- Click to open the WebUI
- Go to Settings → Add-ons
- Find Home Assistant Sentry
- Click Open Web UI button
Navigate to: http://your-home-assistant-address:PORT
Default PORT is 8099. This can be customized in the add-on configuration.
Navigate to: /hassio/ingress/ha_sentry/
Or click links in notifications that look like:
[🛡️ Open WebUI](/hassio/ingress/ha_sentry/)[🔍 View Impact](/hassio/ingress/ha_sentry/?mode=whereused&component=component_name)
The WebUI supports flexible port configuration with dual-port mode:
The add-on can listen on two ports simultaneously to support both Home Assistant ingress and direct browser access:
-
Ingress Port (8099) - Always Active
- Required for Home Assistant sidebar panel integration
- Used by Methods 1, 2, and 4 above
- Fixed at port 8099 (HA Supervisor requirement)
- Cannot be changed
-
Direct Access Port - User Configurable
- Used for Method 3 (direct browser access)
- Default: 8099 (single port mode)
- Can be changed to any port 1024-65535
- Useful if port 8099 conflicts with another service
Default (Single Port Mode):
port: 8099- Sidebar panel works ✅
- Direct access:
http://homeassistant:8099✅ - Single web server instance
Custom Port (Dual Port Mode):
port: 8098- Sidebar panel still works ✅ (uses port 8099 internally)
- Direct access:
http://homeassistant:8098✅ - Two web server instances running
Change the default port if:
- Port 8099 is already in use by another service
- You want direct browser access on a different port
- You need to avoid port conflicts on your system
Important: The sidebar panel (Method 1) and add-on "Open Web UI" button (Method 2) will always work regardless of your port setting, as they use Home Assistant's internal ingress routing on port 8099.
The configuration is correct - no changes needed:
enable_web_ui: true # Keep enabled for WebUI accessNote: The auto_create_dashboard option has been removed as it never worked.
Home Assistant add-ons do not have permission to create Lovelace dashboards via the API. This is a limitation of the Home Assistant architecture, not a bug in the add-on.
The API endpoint /api/lovelace/dashboards returns 404 or 403 errors when accessed from add-ons.
Workaround: Use the built-in WebUI which provides:
- Full dependency visualization
- Interactive graphs
- "Where Used" analysis
- Change impact reports
- All features that the dashboard would have provided
Run the test to verify ingress configuration:
python3 tests/test_ingress_url.pyExpected output:
✓ Ingress URL generation test passed
Base URL: /hassio/ingress/ha_sentry/
✓ Addon slug consistency test passed
✓ Ingress configuration test passed
Verify your config.json has:
{
"slug": "ha_sentry",
"ingress": true,
"ingress_port": 8099,
"panel_icon": "mdi:family-tree",
"panel_title": "Sentry"
}- Restart the add-on
- Refresh your browser (Ctrl+F5)
- Check add-on logs for errors
- Verify
ingress: truein config.json
- Try the sidebar panel instead (most reliable)
- Try: Settings → Add-ons → Home Assistant Sentry → Open Web UI
- Check if you're using a reverse proxy that might interfere
- Verify the add-on is running and port 8099 is accessible
The auto_create_dashboard option has been removed. If you're seeing these errors in old logs, they can be safely ignored. Update to the latest version and the errors will no longer occur.
The add-on uses the standard Home Assistant ingress format for frontend navigation:
/hassio/ingress/{addon_slug}/
For this add-on:
/hassio/ingress/ha_sentry/
Note: The backend proxy route /api/hassio_ingress/ha_sentry is used internally by Home Assistant but should not be used directly for navigation.
The WebUI supports URL fragments for direct navigation:
#whereused:component_name- Show "Where Used" view for a component#impact:comp1,comp2- Show impact report for multiple components
Example:
/hassio/ingress/ha_sentry/?mode=whereused&component=powercalc
The addon slug ha_sentry is consistent across:
- config.json (
"slug": "ha_sentry") - config.yaml (
slug: ha_sentry) - Python code (
ADDON_SLUG = 'ha_sentry')
Bottom Line:
- The
auto_create_dashboardoption has been removed - Access WebUI via sidebar panel labeled "Sentry"
- All functionality is available in the WebUI
- Dashboard auto-creation never worked and is no longer an option
The WebUI provides all features and more than a dashboard would have provided.