BWT Perla
dkarv/ha-bwt-perla · vv0.8.5
Custom HA integration for BWT Perla devices
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
sensor | Sensor (temperature, humidity, air quality…) |
What people report
BWT Perla softeners with the local API work; some Silk and older Wi-Fi module units expose no usable local API.
- Works2
- Not working1
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| BWT Perla | Works Local | Works locally; firmware 2.0209 update confirmed fineSaved copyIs it no longer possible to read the data from the BWT Perla? A short information would be great, thanks! Excerpt saved from GitHub on 2026-10-23. | Issue #12 · 2024-08 | |
| BWT Perla Silk | Works Local | Register mapping and firmware version improved; local API on port 80Saved copySummary - Correct and expand Silk `params[]` register names from firmware settings table analysis (fixes several mis-mapped indexes such as hardness units / turbine pulses / regen allow flags / cycle durations). - Expose useful Silk sensors (firmware, avg daily output, salt kg, fill/dwell/brine/backwash/rinse durations) and give leftover `silk_register_*` entities human-readable names instead of \"unknown\". - Read firmware / product metadata from `GET /silk/status` via `bwt_api.get_status()` so device `sw_version` is no longer always `Unknown` (requires bwt_api 1.0.5: … Excerpt saved from GitHub on 2026-10-23. | PR #58 · 2026-09 | |
| BWT Perla Silk YEZA-6XHS (Germany, fw 2.0.18) | Not working Local | No REST API; redirects to VNC on port 6080; ask BWT for firmware upgradeSaved copyWhat happened? Device: BWT Perla Silk (Product Code: YEZA-6XHS) Integration version: v0.7.1 Problem: The integration fails to connect with a `ConnectException: Could not determine BWT model`. The device is reachable on the local network (192.168.178.70) but redirects all HTTP requests to a VNC interface on port 6080 (`/vnc.html?resize=scale&autoconnect=true`). There is no REST API accessible on port 80. Error log: [code] Question: Is the BWT Perla Silk supported? It seems to use a VNC-based interface instead of the HTTP API expected by the integration. Any workaround or planned support would … Excerpt saved from GitHub on 2026-10-23. | Issue #46 · 2026-06 | |
| BWT Perla XL with A6X-WiFi module | Requested | Older module has no local API on port 8080; different hardwareSaved copyGitHub issue [code] bash nc -vz 8080 [code] text connectx to port 8080 (tcp) failed: Connection refused [code] html A6X-wifi Serveur [code] text /cgi-bin/getinfoConnect /cgi-bin/list_ssid /cgi-bin/update1 /cgi-bin/update2 /cgi-bin/update3 [code] bash curl http:// /cgi-bin/getinfoConnect [code] json {"error_connect":"adoucisseur connecté"} ``` ("water softener connected") So there is definitely a local HTTP interface returning JSON, but it appears to be an older API/firmw Excerpt saved from GitHub on 2026-10-23. | Issue #62 · 2026-10 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Details
| Installs (analytics) | 191 (0.03%) |
|---|---|
| GitHub stars | 51 |
| Latest version | v0.8.5 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @dkarv |
| License | MIT |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/dkarv/ha-bwt-perla/blob/main/README.md
- Source code: https://github.com/dkarv/ha-bwt-perla
- Issues: https://github.com/dkarv/ha-bwt-perla/issues
- HACS: https://hacs.xyz
