Fix add-on discovery and bridge communication
This commit is contained in:
+6
-1
@@ -1,5 +1,10 @@
|
||||
# CHANGELOG - Whatsapp Bridge Integration
|
||||
|
||||
## Release 0.3.0 - 2026-08-04
|
||||
- **Fix:** Discover the installed WhatsApp Bridge add-on through the Supervisor API instead of relying exclusively on the old hard-coded repository hostname.
|
||||
- **Fix:** Reuse Home Assistant's asynchronous HTTP session for status checks and message delivery.
|
||||
- **Fix:** Surface HTTP and add-on errors when sending a message instead of reporting failed requests as successful.
|
||||
|
||||
## 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.
|
||||
@@ -25,4 +30,4 @@
|
||||
- **Improved:** The sensor is assigned to the new main device, which significantly simplifies automations (e.g., alert on connection loss).
|
||||
|
||||
## Release 0.1.7
|
||||
- Previous stable version
|
||||
- Previous stable version
|
||||
|
||||
Reference in New Issue
Block a user