Repository navigation
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.
Access these via:
- Settings → Devices & Services → Ramses Extras
- Click Configure → Advanced Settings
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
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
Enable debug logging when:
- Troubleshooting entity creation issues
- Debugging automation behavior
- Investigating WebSocket communication problems
- Developing custom features
- Reporting issues to maintainers
- Browser Developer Tools → Console tab
- Shows card/editor initialization, WebSocket messages, UI events
- Filter by
ramses_extrasto see relevant messages
- Home Assistant → Settings → Logs
- Shows feature initialization, service calls, automation logic
- Filter by
custom_components.ramses_extras
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
Ramses Extras stores all configuration in a structured model that can be exported to YAML for backup, sharing, and migration purposes.
You can export configuration using either method:
{
"type": "ramses_extras/ramses_debugger/config/export"
}The export is returned as YAML content in the WebSocket response.
- 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.
- Feature enablement per device
- Sensor mappings and calibrations
- Zone configurations
- Area sensor settings
- Debug settings (excluding sensitive data)
For security and privacy, the export excludes:
- Passwords and credentials
- API keys
- Transient runtime data
- Sensitive personal information
You can import configuration using either method:
{
"type": "ramses_extras/ramses_debugger/config/import",
"config": "<yaml_content>"
}- 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.
Using the UI method (recommended):
- Open Ramses Debugger card
- Click Import Configuration
- Paste your YAML configuration
- Review any validation errors shown
- Click Import to apply changes
- Verify configuration in the UI
Using WebSocket method:
- Always start with
dry_run: trueto validate - Review validation errors
- Fix any missing entities or issues
- Import with
dry_run: false - Verify configuration in the UI
- 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
- Debugging and Troubleshooting - Comprehensive troubleshooting guide
- Ramses Debugger - Advanced debugging tools
- Development Guide - For developers
Back to: Home | Prev: Fan Control | Next: System Architecture
- Feature Catalog
- CO2 Control
- Humidity Control (Balance)
- Temp Control (Bypass)
- FAN Configuration (Sensor Control)
- HVAC Fan Card
- Floorplan Helper
- Ramses Debugger
-
Device Simulator -
⚠️ Use only on dedicated system/container - Default Feature
- Hello World (Developer Example)