https://github.com/emmeoerre/ave_dominaplus
Home assistant integration to control AVE Dominaplus systems. Completely local, completely push
https://github.com/emmeoerre/ave_dominaplus
domotics hacs hacs-integration home-assistant home-assistant-integration websocket
Last synced: 2 months ago
JSON representation
Home assistant integration to control AVE Dominaplus systems. Completely local, completely push
- Host: GitHub
- URL: https://github.com/emmeoerre/ave_dominaplus
- Owner: emmeoerre
- License: mit
- Created: 2025-05-09T06:59:47.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2026-04-13T13:15:57.000Z (2 months ago)
- Last Synced: 2026-04-13T13:28:24.553Z (2 months ago)
- Topics: domotics, hacs, hacs-integration, home-assistant, home-assistant-integration, websocket
- Language: Python
- Homepage:
- Size: 119 KB
- Stars: 5
- Watchers: 1
- Forks: 3
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# 🌟 AVE Dominaplus Integration for Home Assistant
Control your AVE Dominaplus home automation system directly from Home Assistant! This integration uses WebSocket communication with the AVE webserver for a **completely asynchronous** and **100% local** setup.
---
## 📋 Requirements
- An **AVE webserver device** installed and accessible from your Home Assistant instance.
- Only tested with the **"autologin" setting** enabled in the webserver.
- **AVE Cloud configuration is NOT required**.
- **Alarm units** connected to the webserver (required for motion sensors and alarm zones).
---
## 🚀 Installation
1. Install the integration via HACS (recommended) or manually copy the files to your `custom_components` directory.
2. At this point Home Assistant may autodiscover the AVE webserver and show a configuration prompt. If you see it, open that prompt and continue from there.
3. If no autodiscovery prompt appears go to **Settings → Devices & Services → Add Integration**. Search for **"AVE Dominaplus"** and select it manually.
4. In the configuration prompt provide the webserver IP address and configure additional settings as needed.
---
## 🛠️ Supported Devices
### ✅ Switches
- **Fully supported**: Discovered at startup, with names.
- Synced with the **"Get lights"** flag.
- Supports turning on, off, and toggling.
### ✅ Alarm Areas
- **Supported**: Discovered at startup, with names.
- Synced with the **"Get antitheft sensor areas"** flag.
- Provides motion sensor functionality.
- Includes **"Last cleared"** and **"Last revealed"** timestamps as attributes.
- *Note: "Armed" and "Triggered" states are not yet exposed as entities.*
### ✅ Individual Alarm Sensors
- **Supported**: Discovered when the first event is triggered.
- Synced with the **"Get individual antitheft sensors"** flag.
- The system does not provide names, so sensors are auto-named. It is recommended to set custom
names after discovery.
- These sensors are sensitive and may trigger quickly; configure accordingly.
### ✅ Thermostats
- **Supported** when **"Get thermostats"** is enabled in the config flow.
- For each thermostat the integration creates two entities:
* a **climate** entity representing the controller
* a **number** entity showing the current temperature offset of the device (–5 °C..+5 °C)
#### Climate entity behaviour
- `Mode` controls the combination of season and on/off state:
* `Cool` for summer mode
* `Heat` for winter mode
* `Off` if the thermostat is powered off (support depends on the device)
- `Preset` is either `Schedule` (follow the schedule on the webserver)
or `Manual` (immediate changes from Home Assistant). Changing the
target temperature from HA will automatically switch the preset to
`Manual`, mimicking the vendor app behaviour.
- `Fan mode` reflects the fancoil speed reported by the zone; it is **read‑only**.
#### Offset sensor
- A read‑only number sensor is created for each thermostat exposing the
device’s current offset.
- The offset **cannot be modified from Home Assistant**; it must be set on the
physical thermostat itself. The sensor simply mirrors the value reported
by the device.
---
## 🔜 Not yet supported (contributors welcome!)
Other devices are not yet supported either for lack of time or lack of devices at hand
- **Dimmers**: Work in progress
- **Scenarios**: Backend discovery is ready; no entity is exposed
- **Areas**: Feel free to come with a plan to add AVE areas and device area assignments without clashing with the HA areas
- **Economizers**: Not yet supported
- **Shutters**: Not yet supported
---
## 🏷️ About Device Names
The integration supports two naming strategies:
1. **Names from Webserver** (Recommended):
- Entity IDs like: `switch.normalized_ave_name`.
- Names are fetched from the Dominaplus configuration.
- Changes are fetched at every restart.
2. **Generated Names**:
- Entity IDs like: `switch._`.
- Names are automatically generated.
**Tip**: If you plan to customize entity names:
The integration tries its best to not override your custom names even if they are changed in the AVE apps. But for better measure:
- First, enable **"Get entities names from webserver"** to discover all entities.
- Then, disable this option before setting custom names to prevent overwriting.
---
## ❓ Frequently asked questions
### I don’t see certain device types after installation
First verify the device type is listed under “Supported Devices” above. If
it is supported and still not visible, reconfigure the integration in Home
Assistant (Settings → Devices & Services → your AVE entry → ⋮ menu →
Reconfigure). Items added in a newer version may not appear until the entry
has been re‑configured.
## ⚠️ Known Issues
### Multiple Webservers for Different Plants
- Currently, multiple webservers for different plants are **not supported**. Multiple controllers for the same plant are supported, but separate plant setups may cause device ID clashes. Support for multi-plant setups is being explored.
### Individual sensor alarm states after power outage
- After a webserver or alarm unit reboot, a brief arm/disarm cycle may be needed for sensors to start reporting state updates. This behavior is due to the alarm system firmware, not the integration.
## 🆘 How to ask for help
Before opening an issue:
* Make sure the integration is up to date.
* Check the **FAQ** and **Known Issues** sections above; your question may already be answered.
When creating a GitHub issue:
* Search for an existing issue describing the same problem and add additional information there instead
of opening a duplicate.
* Do **not** post on unrelated issues; off-topic comments may be removed.
* Provide as much relevant information as you can:
- integration version,
- Home Assistant version,
- webserver firmware version,
- model of the affected device(s),
- log output with the `ave_dominaplus` domain set to `debug` (capture the messages
emitted when the integration starts).
---
## 🤝 Contributing & developing
Contributions are welcome! If you encounter issues or have feature requests, feel free to open an issue or submit a pull request on GitHub.
You can join our [discord server](https://discord.gg/PQ52jwV6BX)
Development setup and debugging guide (VS Code on Windows + WSL): [docs/development/vscode-windows.md](docs/development/vscode-windows.md)
---
## 📜 License
This project is licensed under the **MIT License**. See the `LICENSE` file for more details.