3 Commits

Author SHA1 Message Date
f0e17bf90a Update version to 0.7.4 in manifest.json 2026-01-14 07:40:38 +01:00
c374740503 Add diagnostics export instructions to README
Added a diagnostics section to README for issue reporting.
2026-01-14 07:39:23 +01:00
d4cbf1d303 Add Home Assistant Diagnostics support
Added support for Home Assistant Diagnostics, including a new feature to download diagnostics for each Easy Proxmox config entry. Diagnostics include sanitized config entry data, runtime client information, and more, with sensitive data redacted.
2026-01-14 07:38:27 +01:00
3 changed files with 38 additions and 17 deletions

View File

@@ -1,19 +1,30 @@
# Changelog # Changelog
## 0.7.3 ## 0.7.4
- Fixed service execution when using device targets in automations and scripts - Added Home Assistant Diagnostics support
- Services now work correctly on Home Assistant versions where `ServiceCall.target` is not available - New “Download diagnostics” feature for each Easy Proxmox config entry
- Improved target resolution: - Diagnostics include:
- Supports `device_id` passed via UI targets and via service data - Config entry data and options (sanitized)
- Supports `entity_id` targets and automatically resolves them to the corresponding device - Runtime client information
- Accepts both `str` and `list[str]` formats for target identifiers - Coordinator states (last update success, exceptions, update interval)
- Fixed issue where service calls were accepted but no Proxmox action was executed - Safe previews of nodes and guests
- Improved compatibility with the Home Assistant automation editor and mobile UI - Sensitive data such as API tokens and credentials are automatically redacted
- Diagnostics are fully JSON-serializable and suitable for GitHub issue attachments
## 0.7.2
- Fixed service validation for device targets: ## 0.7.3
- Home Assistant may pass `device_id` as a list (target/data wrapper) - Fixed service execution when using device targets in automations and scripts
- Services now accept both `str` and `list[str]` for `device_id` - Services now work correctly on Home Assistant versions where `ServiceCall.target` is not available
- Improved target resolution:
- Supports `device_id` passed via UI targets and via service data
- Supports `entity_id` targets and automatically resolves them to the corresponding device
- Accepts both `str` and `list[str]` formats for target identifiers
- Fixed issue where service calls were accepted but no Proxmox action was executed
- Improved compatibility with the Home Assistant automation editor and mobile UI
## 0.7.2
- Fixed service validation for device targets:
- Home Assistant may pass `device_id` as a list (target/data wrapper)
- Services now accept both `str` and `list[str]` for `device_id`
- Improved device target parsing for UI and script wrappers - Improved device target parsing for UI and script wrappers
## 0.7.1 ## 0.7.1
@@ -138,3 +149,4 @@

View File

@@ -329,6 +329,14 @@ The API token has admin rights. Treat it like a root password:
| Buttons dont work | Check Proxmox permissions (PVEAdmin role) | | Buttons dont work | Check Proxmox permissions (PVEAdmin role) |
| Old devices remain | Fully cleaned up automatically since version 0.4.1 | | Old devices remain | Fully cleaned up automatically since version 0.4.1 |
### Diagnostics
If you open an issue on GitHub, please attach a diagnostics export:
Settings → Devices & Services → Easy Proxmox → (⋮) → Download diagnostics
This export is automatically sanitized (API token is redacted).
--- ---
## Support & Contributing ## Support & Contributing

View File

@@ -1,7 +1,7 @@
{ {
"domain": "proxmox_pve", "domain": "proxmox_pve",
"name": "Easy Proxmox (by René Bachmann)", "name": "Easy Proxmox (by René Bachmann)",
"version": "0.7.3", "version": "0.7.4",
"documentation": "https://github.com/bahmcloud/easy_proxmox ", "documentation": "https://github.com/bahmcloud/easy_proxmox ",
"requirements": ["aiohttp>=3.9.0"], "requirements": ["aiohttp>=3.9.0"],
"codeowners": ["@BAHMCLOUD"], "codeowners": ["@BAHMCLOUD"],
@@ -9,3 +9,4 @@
"iot_class": "local_polling", "iot_class": "local_polling",
"integration_type": "service" "integration_type": "service"
} }