Releases: moehrem/DiveraControl
v2.0.0-beta.1
Beta release - bug infested!
This is a beta release which comes with bugs and errors. This is not meant to be used in a productive environment. Do not install, unless you are willing to supply feedback! Thank you!
Known bugs
- timeouts requesting data from Divera
- missing and wrong text elements
- poor performance upon integrating multiple users
New featues
- multi user support
- each Divera unit will be shown as hum of devices
- each user will be shown as device within its hub
- new entity: status selector, which enabels user to select the personal status
- new entity: last alarm, which shows the latest alarm details
- new entity: personal details, which show all user cluster relation details
- changed entity: unit details, which show cluster number
- removed: webhook support - this is available in standard HA already
- reduced: configuration flow, which works mostly with user credentials now and will ask for AP-keys in very special cases only
- new service: set user status, which can be used in automations per device or in frontend panels
What's Changed
- update readme links by @moehrem in #123
- upgrade by @moehrem in #124
- v2.0.0-beta.1 by @moehrem in #125
Full Changelog: v1.4.1...v2.0.0-beta.1
Contributors
Assets 3
v1.4.1 - Permission handling
v1.4.1 - Permission handling
This is a minor less fancy patch to fix some long standing bugs with the permission handling. The most obvious thing: No more "permission data not available" errors upon initializing the integration.
Permission data is now cached in the API instance itself. They will be updated with any data call from Divera. As single point of truth all persmission requests are handled by a new dedicated class.
What's Changed
- bugfix: workflow release.yml with wrong path by @moehrem in #118
- fixing security issues in workflows by @moehrem in #119
- implemented permission handling by @moehrem in #122
Full Changelog: v1.4.0...v1.4.1
Contributors
Assets 3
v1.4.0
DiveraControl v1.4.0 - webhooks incoming!
With this update we proudly present webhook support!
You are now able to configure a unit specific API-enpoint to be used as webhook address within Divera 24/7. Divera will call that endpoint upon any new alert, thus reducing response times of DiveraControl to an abolute minimum.
New users just use the new option while setting up the integration. Existing users may activate webhook support by reconfiguring existing units.
🚀 Highlights
- Added optional webhook support alongside polling.
- Expanded and stabilized the configuration and reconfiguration flows.
- Improved diagnostics with integration-specific in-memory log output.
- Fixed multiple issues around URL resolution, update interval behavior, and translations.
✨ New
- Implemented webhook endpoint handling to trigger targeted coordinator refreshes.
- Added config flow steps for webhook setup, including info and error screens.
- Extended reconfigure flow to update:
- API key
- Update intervals
- Base API URL
- Webhook usage
- Refactored form schemas into a dedicated structure for better maintainability.
🛠 Improvements
- Webhook URL generation now prefers Home Assistant Cloud URL, then external URL fallback.
- Added explicit error handling when no external/cloud URL is available.
- Optimized duplicate detection in config flow to avoid duplicate cluster entries.
- Reworked dynamic update interval switching (alarm vs. normal state).
- Expanded DE/EN translations for webhook, reconfigure, and error messaging.
- Improved diagnostics output with recent in-memory integration logs.
🐞 Fixes
- Fixed webhook URL generation for non-internal/cloud scenarios.
- Corrected translation placeholders and language string issues.
- Fixed diagnostics/log-handler integration issues.
- Applied follow-up fixes for update interval logic and related tests.
✅ Tests, CI, and Release Automation
- Added/updated tests for webhook handling, diagnostics, data normalization, and config flow.
- Consolidated CI testing to Python 3.13.
- Updated test dependencies for aiodns/pycares compatibility on Python 3.13.
- Added release workflow to build and upload ZIP release assets.
📚 Docs and Maintenance
- Updated German and English README documentation.
- Standardized license files to Apache 2.0 naming/layout.
- Removed committed coverage/build artifact files from the repository.
Upgrade notes
- Existing installations are migrated forward; new config fields (such as webhook usage) are added automatically.
- Webhooks require a publicly reachable Home Assistant URL (Cloud or external URL).
- If enabling webhooks, verify the generated webhook URL in setup and update it in Divera as needed.
- Reconfigure changes (API key, URL, intervals, webhook mode) trigger entry reload behavior.
Known limitations
- If no external or cloud URL is configured, webhook mode cannot be enabled; polling remains the fallback.
- Diagnostics redact API/access keys, but may still contain operational cluster/alarm context and should be handled as sensitive.
- After translation/diagnostics updates, UI text consistency may require a reload/restart depending on local cache state.
What's Changed
- v1.4.0-beta.1 Webhooks incoming by @moehrem in #108
- bugfix: set external or cloud url by @moehrem in #109
- bugfix: fix webhook URL generation for non-internal or cloud access by @moehrem in #110
- updated url generation to cloud first, then external, and added error… by @moehrem in #111
- [WIP] Update to address feedback on config flow refactor by @Copilot in #113
- Use TextSelectorType.PASSWORD enum instead of raw string in TextSelectorConfig by @Copilot in #114
- Use TextSelectorType.PASSWORD enum instead of string literal in schemas.py by @Copilot in #115
- Hoist
existing_ucr_idscomputation out of loop in config flow by @Copilot in #116 - refactored config flow: by @moehrem in #112
- workflow, bugfixes by @moehrem in #117
New Contributors
- @Copilot made their first contribution in #113
Full Changelog: v1.3.2...v1.4.0
Contributors
Assets 3
v1.4.0-beta.3 -- Webhooks incoming!
Bugfixes and Refactoring
Its still a Beta for the new webhooks feature. And still I would be happy about any tests and feedback.
- support existing webhook id
- added a new schema file for config flow
- updated translations
- added a new webhook handler file to handle the webhook logic and preparation of the webhook entry data
- optimized existing cluster check in config flow to prevent multiple iterations over existing entries
- changed requirements to fix aiodns/pycares issue with Python 3.13
- updated config flow to handle reconfiguration
- added translations for new messages
- reworked readme to reflect new features and changes
What's Changed
- [WIP] Update to address feedback on config flow refactor by @Copilot in #113
- Use TextSelectorType.PASSWORD enum instead of raw string in TextSelectorConfig by @Copilot in #114
- Use TextSelectorType.PASSWORD enum instead of string literal in schemas.py by @Copilot in #115
- Hoist
existing_ucr_idscomputation out of loop in config flow by @Copilot in #116 - refactored config flow: by @moehrem in #112
New Contributors
- @Copilot made their first contribution in #113
Full Changelog: v1.4.0-beta.2...v1.4.0-beta.3
Contributors
Assets 2
v1.4.0-beta.2 -- Webhooks incoming!
Prerelease Beta for v1.4.0 - Webhooks
Attention!
This is a prerelease. I need it to further test the new webhook functionality. I do not recommend to use it yet, but would be happy about any test feedback.
New Functions
Implemented webhook support. The integration will offer to create an url and endpoint to use as webhook-address in Divera. Existing implementions can use the "reconfigure" option to enable webhook.
The endpoint, once called, will trigger an immediate data update request from Divera. Thus reaction times are heavily reduced.
What's Changed
Full Changelog: v1.3.2...v1.4.0-beta.1
Contributors
Assets 2
v1.4.0-beta.1 -- Webhooks incoming!
Prerelease Beta for v1.4.0 - Webhooks
Attention!
This is a prerelease. I need it to further test the new webhook functionality. I do not recommend to use it yet, but would be happy about any test feedback.
New Functions
Implemented webhook support. The integration will offer to create an url and endpoint to use as webhook-address in Divera. Existing implementions can use the "reconfigure" option to enable webhook.
The endpoint, once called, will trigger an immediate data update request from Divera. Thus reaction times are heavily reduced.
What's Changed
Full Changelog: v1.3.2...v1.4.0-beta.1
Contributors
Assets 2
v1.3.2: Bugfix for "vehicle status"
v1.3.2
Bugfix:
In some cases the "vehicle status" from the related service was handled as list of strings - which raised an error in Divera API.
What's Changed
Full Changelog: v1.3.1...v1.3.2
Contributors
Assets 2
v1.3.1: Update intervals
Ist just a minor change: The new minimum interval is now 5 seconds. Before it was 30s.
The settings can be changed for units that are already integrated by reconfiguring them via the context menu for the unit.
What's Changed
Full Changelog: v1.3.0...v1.3.1
Contributors
Assets 2
v1.3.0
v1.3.0
💡 What's Changed
This release brings improved configurability for advanced users, enhanced security by redacting sensitive data in error messages, and optimized CI/CD workflows. The services definitions have been updated to comply with current Home Assistant standards.
✨ Features
- Custom base API URL config: Added support for configurable base API URL with reconfig option
- Configuration flow: improved navigation for better readability
🐛 Bug Fixes
- Security: API key in API ClientError message is now properly redacted
- CI/CD: Fixed workflows being triggered too often
📝 Updates
- Redefined
services.yamlto match Home Assistant standards - Updated tests to work with configurable base URL
Full Changelog: v1.2.0...v1.2.1
Contributors
Assets 2
v1.2.0
This release brings a major internal overhaul and full UI integration into Home Assistant’s automation and action tools.
It focuses on usability, reliability, and deeper frontend integration.
💥 Breaking Changes
Reworked service data handling – action calls now require updated mandatory parameters!
Good news: You no longer need to add a “cluster ID.” You can now directly reference all your calls to a unit (device).
Bad news: Old service calls and scripts will no longer work. Please review and reconfigure all your implementations as needed.
Upgrade procedure:
- Install update
- Restart Home Assistant or clear its cache to apply entity structure changes
- Review and update existing automations and service calls to match new data requirements
- If you encounter issues, please fully remove the integration, restart HA and add DiveraControl again
- If you still face issues: please open a GitHub issue with relevant log details
✨ New Features
-
Automations UI support
DiveraControl services and actions are now fully available in the automation editor.
Just select a device, and all available actions (based on permissions) will appear.
Input fields now include dropdowns, checkboxes, and sliders — each offering the correct input type automatically. -
Frontend Action UI support
Similar to automations, any selected device in a Lovelace UI card now exposes its available services with proper data input fields. -
Developer Tools – Actions UI support
You can now use DiveraControl actions directly from the Developer Tools in “UI mode.”
Where supported, data fields will automatically provide structured input. -
Expanded Action Fields
Several services now support additional fields and parameters for finer control.
🔧 Under the Hood
- Biggest bug killed: with multiple units news are distributed to wrong unit. Thanks @ricman01 for showing up with the issue!
- Major entity handling overhaul for improved stability and performance
- Numerous bug fixes and internal optimizations
- Added automated tests to ensure safer and more reliable future development
- Introduced full translations in both German and English
What's Changed
Full Changelog: v1.1.5...v1.2.0
