3 Commits
0.2.3 ... 0.2.4

3 changed files with 10 additions and 4 deletions

View File

@@ -1,5 +1,9 @@
# CHANGELOG - Whatsapp Bridge Integration # CHANGELOG - Whatsapp Bridge Integration
## Release 0.2.4 - 2026-06-15
- **Fix:** Resolved a `TypeError` in `async_get_or_create()` caused by stricter Home Assistant Core requirements demanding a `config_entry_id` for all device registry entries.
- **Architecture Refinement:** The global "WhatsApp Bridge Hub" now utilizes a shared multi-entry architecture. It dynamically links to active configurations under a static identifier, ensuring the hub remains a single, non-duplicated entity that survives individual account deletions.
## Release 0.2.3 - 2026-06-15 ## Release 0.2.3 - 2026-06-15
- **New (Orphaned Devices Cleaner):** Added an automatic database cleanup utility. On startup, the integration now automatically identifies and removes orphaned or "ghost" devices left behind by previous configuration changes or older versions. - **New (Orphaned Devices Cleaner):** Added an automatic database cleanup utility. On startup, the integration now automatically identifies and removes orphaned or "ghost" devices left behind by previous configuration changes or older versions.
- **Fix:** Decoupled the central "WhatsApp Bridge Hub" device from specific config entry bindings. The Hub is now persistent and indestructible, preventing global entities (Broadcast and Live Status) from disappearing when individual user profiles are deleted or re-added. - **Fix:** Decoupled the central "WhatsApp Bridge Hub" device from specific config entry bindings. The Hub is now persistent and indestructible, preventing global entities (Broadcast and Live Status) from disappearing when individual user profiles are deleted or re-added.

View File

@@ -40,16 +40,18 @@ async def async_setup_entry(hass: HomeAssistant, entry):
name=f"WhatsApp {entry.title}", name=f"WhatsApp {entry.title}",
manufacturer="Bahmcloud", manufacturer="Bahmcloud",
model="Kontakt-Endpunkt", model="Kontakt-Endpunkt",
sw_version="0.2.3", sw_version="0.2.4",
) )
# 3. Zentralen System-Hub VOLLKOMMEN UNABHÄNGIG anlegen (ohne feste config_entry_id Bindung) # 3. Zentralen System-Hub anlegen mit erzwungener config_entry_id Bindung (HA Core Anforderung)
# Nutzt Multi-Entry-Zusammenführung über den fixen "global_bridge_hub" Identifier.
device_registry.async_get_or_create( device_registry.async_get_or_create(
config_entry_id=entry.entry_id,
identifiers={(DOMAIN, "global_bridge_hub")}, identifiers={(DOMAIN, "global_bridge_hub")},
name="WhatsApp Bridge Hub", name="WhatsApp Bridge Hub",
manufacturer="Bahmcloud", manufacturer="Bahmcloud",
model="Bridge Server", model="Bridge Server",
sw_version="0.2.3", sw_version="0.2.4",
) )
# Forward the setup to the sensor platform to create entities # Forward the setup to the sensor platform to create entities

View File

@@ -4,7 +4,7 @@
"documentation": "https://git.bahmcloud.de/bahmcloud/Whatsapp-Bridge-Integration", "documentation": "https://git.bahmcloud.de/bahmcloud/Whatsapp-Bridge-Integration",
"dependencies": [], "dependencies": [],
"codeowners": ["@bahmcloud"], "codeowners": ["@bahmcloud"],
"version": "0.2.3", "version": "0.2.4",
"iot_class": "local_polling", "iot_class": "local_polling",
"config_flow": true "config_flow": true
} }