Overview

Overview

Disclaimer

Use of Ramses Extras is at your own risk. This integration modifies ventilation system behavior and interacts with hardware devices. While extensively tested, users should:

• Understand their ventilation system before enabling automation
• Monitor system behavior after installation
• Have a basic understanding of Home Assistant configuration
• Keep device firmware updated

The authors are not responsible for any damage to equipment, property, or health effects resulting from the use of this software.

What is Ramses Extras?

Ramses Extras is a feature-centric Home Assistant integration that extends the ramses_cc (or Ramses RF) integration with additional entities, automation, and UI components.

The overall goal is to keep functionality modular:

• Features are self-contained.
• The framework provides reusable building blocks.
• The Home Assistant integration layer stays thin.

Core benefits

• Feature-centric design: each feature is self-contained with its own automation, services, entities, and UI.
• Framework foundation: reusable base classes/helpers used by all features.
• Clean HA integration: standard HA platforms and type-safe entities.
• Modular architecture: add new features using established patterns.
• Real-time updates: WebSocket APIs and message listeners for immediate UI updates.

Key concepts

• Features: self-contained modules providing specific functionality.
• Framework: reusable base classes, helpers, and utilities.
• Platforms: Home Assistant integration layer for entities and services.
• Cards: JavaScript-based UI components for Lovelace.
• Config flow: Home Assistant configuration mechanism.

Current features

• Default feature (always enabled)
  • Shared/common entities, diagnostics, and WebSocket endpoints used by other features.
  • Includes shared FAN diagnostics such as sensor.fan_control_mode_{device_id} and binary_sensor.transport_state_{device_id}.
• HVAC Fan Card
  • Advanced Lovelace card for FAN monitoring/control.
  • Supports sticky manual override, control-mode badges, and clear manual-state indicators when automation is overridden.
• Humidity Control (Balance)
  • Humidity-based automation comparing indoor/outdoor absolute humidity.
  • Entities that publish demand to the shared fan-speed arbiter.
• CO2 Control
  • CO2-based automation and entities that publish demand to the shared fan-speed arbiter.
• FAN Configuration (Sensor Control)
  • Central sensor mapping/override system for Humidity Control, CO2 Control, and HVAC Fan Card.
  • Includes zone configuration for multi-room ventilation control with valve actuators.
• Ramses Debugger
  • Debugging tools: traffic analyser, log explorer, packet log explorer.

Next

• Users: Getting Started (Users)
• Developers: Getting Started (Developers)
• Architecture: System Architecture

Back to: Home

Prev: Home Next: Getting Started (Users)