Skip to content

Advanced Settings

devin edited this page Oct 21, 2026 · 2 revisions

Advanced Settings

Configure integration-level debug settings.

Frontend log level controls browser console logging for Ramses Extras cards/editors. Log level controls the backend Python logging level for the Ramses Extras integration.

Integration Advanced Settings

Access these via:

  • Settings → Devices & Services → Ramses Extras
  • Click Configure → Advanced Settings

Available Settings

Frontend Log Level

Controls browser console logging for Ramses Extras frontend components:

  • Debug - Verbose logging for development
  • Info - General information messages
  • Warning - Only warnings and errors
  • Error - Only error messages

Log Level (Backend)

Controls Python logging level for the Ramses Extras integration:

  • Debug - Verbose logging for development and troubleshooting
  • Info - General operational information
  • Warning - Only warnings and errors
  • Error - Only critical errors

When to Use Debug Settings

Enable debug logging when:

  • Troubleshooting entity creation issues
  • Debugging automation behavior
  • Investigating WebSocket communication problems
  • Developing custom features
  • Reporting issues to maintainers

Debug Output Locations

Frontend Logs

  • Browser Developer Tools → Console tab
  • Shows card/editor initialization, WebSocket messages, UI events
  • Filter by ramses_extras to see relevant messages

Backend Logs

  • Home Assistant → Settings → Logs
  • Shows feature initialization, service calls, automation logic
  • Filter by custom_components.ramses_extras

Performance Considerations

Debug logging can impact performance:

  • Frontend Debug - Increases browser console output
  • Backend Debug - Increases Home Assistant log size
  • Recommendation - Use debug level only when actively troubleshooting
  • Production - Use Info or Warning level for normal operation

Configuration Export/Import

Ramses Extras stores all configuration in a structured model that can be exported to YAML for backup, sharing, and migration purposes.

Export Configuration

You can export configuration using either method:

Method 1: WebSocket Command

{
  "type": "ramses_extras/ramses_debugger/config/export"
}

The export is returned as YAML content in the WebSocket response.

Method 2: UI Copy/Paste (Recommended)

  • Open Ramses Debugger card
  • Click Export Configuration
  • Copy the YAML from the text field
  • Paste into your preferred text editor or file

The UI method is easier for most users and provides a simple copy/paste workflow.

What Gets Exported

  • Feature enablement per device
  • Sensor mappings and calibrations
  • Zone configurations
  • Area sensor settings
  • Debug settings (excluding sensitive data)

What's Excluded

For security and privacy, the export excludes:

  • Passwords and credentials
  • API keys
  • Transient runtime data
  • Sensitive personal information

Import Configuration

You can import configuration using either method:

Method 1: WebSocket Command

{
  "type": "ramses_extras/ramses_debugger/config/import",
  "config": "<yaml_content>"
}

Method 2: UI Copy/Paste (Recommended)

  • Open Ramses Debugger card
  • Click Import Configuration
  • Paste your YAML configuration into the text field
  • Click Import to apply the configuration

The UI method is easier for most users and provides validation before applying changes.

Important: Import validates against schema and checks constraints before applying changes.

Safe Import Workflow

Using the UI method (recommended):

  1. Open Ramses Debugger card
  2. Click Import Configuration
  3. Paste your YAML configuration
  4. Review any validation errors shown
  5. Click Import to apply changes
  6. Verify configuration in the UI

Using WebSocket method:

  1. Always start with dry_run: true to validate
  2. Review validation errors
  3. Fix any missing entities or issues
  4. Import with dry_run: false
  5. Verify configuration in the UI

Use Cases

  • Backup - Save your complete configuration
  • Support - Share setup when asking for help
  • Migration - Move settings between Home Assistant instances
  • Version Control - Track configuration changes over time

Related Documentation


Back to: Home | Prev: Fan Control | Next: System Architecture

Clone this wiki locally