add V 0.6.0-alpha

This commit is contained in:
2026-01-13 15:38:22 +01:00
committed by GitHub
parent 6a477bc7fe
commit 72d2cf7c5b
13 changed files with 1712 additions and 0 deletions

87
CHANGELOG.md Normal file
View File

@@ -0,0 +1,87 @@
# Changelog
## 0.6.0-alpha
- Extended Node monitoring with additional sensors:
- RAM Total (MB) and RAM Free (MB)
- Swap Used/Total/Free (MB)
- Node Storage (RootFS) Used/Total/Free in GB (3 decimals)
- Kept existing Node sensors: CPU (%), Load (1m), RAM Used (MB), Uptime (d/h/m)
- No changes to VM/CT entities, cleanup logic, or controls
- Add README.md and LICENSE
## 0.5.2-alpha
- Options are now applied live without restart or integration reload
- Changing polling interval updates all coordinators immediately
- Changing IP preference mode/prefix updates all existing guest coordinators immediately
- Triggered refresh after saving options so sensors update quickly
- Renamed integration to "Easy Proxmox (by René Bachmann)"
## 0.5.1-alpha
- Fixed Options Flow crash that caused:
“Config flow could not be loaded: 500 Internal Server Error”
- Fixed incompatibility with Home Assistants `OptionsFlow`:
- Removed illegal assignment to the read-only `config_entry` property
- Now fetching the ConfigEntry safely via `self.context["entry_id"]`
- Restored Options (gear icon) in the integration UI
- Options dialog can now be opened and saved without backend errors
- Improved compatibility with newer Home Assistant core versions
- Stabilized Config Flow import and initialization
## 0.5.0-alpha
- Added Options Flow:
- Configurable polling interval
- Configurable IP preference mode (prefer 192.168.*, private IPs, any, or custom prefix)
- Added Proxmox Node devices:
- One device per Proxmox node
- Sensors for:
- CPU usage (%)
- RAM used (MB) and total RAM (attribute)
- Uptime (days, hours, minutes)
- Load average (1 minute)
- VM/CT devices are now linked to their node device (via_device)
- Existing dynamic VM handling, rename detection and hard cleanup retained
## 0.4.1
- Fixed entity and device cleanup when a VM/CT is deleted:
- Entities are fully removed from Entity Registry
- Devices are fully removed from Device Registry
- No more “unavailable ghost entities”
- Guaranteed hard cleanup for removed guests
## 0.4.0
- Dynamic VM/CT discovery:
- New guests appear automatically without reload
- Removed guests are automatically cleaned up
- Live rename handling:
- Device names and entity names update when VM name changes
- Improved coordinator lifecycle handling
## 0.3.0
- One Home Assistant device per VM/CT
- Power Switch:
- ON → Start
- OFF → Shutdown (soft)
- Buttons:
- Reboot
- Stop (hard)
- Sensors per VM/CT:
- CPU usage (%)
- RAM usage (MB)
- Uptime (days, hours, minutes)
- Network In/Out (MB)
- Preferred IP address + list of all IPs
- VMID added to device and entity names
- Network and memory values converted to MB
- IP selection prioritizes LAN IPs (e.g. 192.168.*)
## 0.2.0
- Start, Stop and Reboot buttons added
- Domain renamed and integration structure stabilized
- Improved error handling and platform loading
## 0.1.0
- Initial Proxmox VE integration
- API token authentication
- Basic connectivity test via Config Flow
- First experimental entities