Releases: custom-components/zaptec
v0.7.2
🎉 What's in this release
This release is an improvement release of the Zaptec integration. It contains a lot of stability fixes, especially for the amount of logging and how API errors are handled. It adds a couple of new entities that have been requested such as cable locking and status light brightness setting. As the first non-English translation, Dutch translation has been added (shout-out to @c0mplex1 ). See below for the full list of features and fixes.
Any issues, proposals, improvements can be added by creating an issue here.
What's Changed
- Add sensors and service call by @sveinse in #81
- Adding info regarding the load balancing blueprint by @svenakela in #92
- More about load balancing, better formatting. by @svenakela in #93
- Fix HA warning on TEMP_CELSIUS and state class entity warning by @danielkihlgren in #100
- Delete stale/old Zaptec devices by @sveinse in #104
- Fix excessive API logging by @sveinse in #110
- Add binary sensor for online charger by @sveinse in #115
- Add missing translations by @sveinse in #118
- Ignore updates with chargerid 0000...0000 by @sveinse in #119
- Remove excessive data in sensor attributes by @sveinse in #120
- Added support for cable locking by @sveinse in #127
- Add retry on API error code 500 by @sveinse in #111
- Fix redaction of username and password in logs by @sveinse in #132
- Dutch language translation by @c0mplex1 in #135
- Add HMI brightness entity by @sveinse in #136
New Contributors
- @svenakela made their first contribution in #92
- @c0mplex1 made their first contribution in #135
Full Changelog: v0.7.1...v0.7.2
ℹ️ Known issues
Contributors
Assets 2
v0.7.2 BETA 1
A preliminary beta release for testing. Please report any bugs at https://github.com/custom-components/zaptec/issues
What's Changed
- Add sensors and service call by @sveinse in #81
- Adding info regarding the load balancing blueprint by @svenakela in #92
- More about load balancing, better formatting. by @svenakela in #93
- Fix #85 and #87 by @danielkihlgren in #100
- Fix stale devices (#89) and total (#87) by @sveinse in #104
- Fix API logging (#90) by @sveinse in #110
- Add binary sensor for online charger (#114) by @sveinse in #115
- Add missing translations to entities with state by @sveinse in #118
- Ignore updates with chargerid 0000...0000 by @sveinse in #119
- Remove excessive data in sensor attributes by @sveinse in #120
- Added support for cable locking by @sveinse in #127
- Retry on API error code 500 (#90) by @sveinse in #111
- Add documentation about usage of undocumentet API usage by @sveinse in #128
- Fix redaction of username and password in logs by @sveinse in #132
New Contributors
- @svenakela made their first contribution in #92
Full Changelog: v0.7.1...v0.7.2b1
Contributors
Assets 2
v0.7.1
⚠️ IMPORTANT ⚠️
If running version < 0.7.0: This release contains breaking changes! Entities and device names have changed significantly. You will have to update your automations after installation. It can prove easier to uninstall the zaptec integration before installing 0.7.1 to ensure all entity names gets properly updated.
What's Changed
- Fixed issue with multiple chargers (data leaking over)
- Added new charger sensors. "Humidity", "Temperature (internal)",
"Allocated charge current", "Authentication Type" - Added new installation sensor "Max Current"
- Added statistics support for each entity that measures values
- Cleanup of translations, more consistent usage of "Authorization"
- Change "Authorization Required" switch to binary sensor. It is better to
use Zaptec Portal for these types of adjustments - Fixed issues and improved diagnostics download
- API request cleanups
- Cleanup of debug output
- Increase poll update delay slightly to ensure Zaptec Cloud data is updated
by the time the next poll is run - Change Circuit to use "active" (was "is_active")
Changelog: CHANGELOG.md
Commit changelog: v0.7.0...v0.7.1
v0.7.0
What's Changed
- Major refactor of the integration, #56
- Added entities for data-points. No need for using attrs and templates
- Using device names as defined in Zaptec portal
- Added support to select which charger to use (handy in large installs)
- Fixed charging current adjustment, either all or individual three phase adjustment
- Support for Zaptec native authorization and deauthorization
- Support integration with the HA energy panel
Contributors
- @sveinse has been leading this refactor and testing
- @Gyran fixed dev container implementation
- @Hellowlol for supporting on reviews
Changelog: CHANGELOG.md
Commit changelog: 0.0.6b2...v0.7.0
Contributors
Assets 2
0.0.6b2
Full Changelog: 0.0.6b1...0.0.6b2
0.0.6 - beta
What's Changed
- Fix github url in help message by @miksen in #27
- Update API data example with latest changes in API by @danielkihlgren in #31
- Phasechange by @gustafssone in #23
New Contributors
- @miksen made their first contribution in #27
- @danielkihlgren made their first contribution in #31
- @gustafssone made their first contribution in #23
Full Changelog: 0.0.5...0.0.6b1
Contributors
Assets 2
0.0.5
What's Changed
- Remove chardet import by @Olen in #16
- Added support for chargers that are not reachable as installations by @mrfrostfire in #20
New Contributors
- @Olen made their first contribution in #16
- @mrfrostfire made their first contribution in #20
Full Changelog: 0.0.3...0.0.5
Contributors
Assets 2
Add 0.0.3
Breaking changes in 0.0.2
New:
- This integration now uses config flow.
- We now use a combination of push and pull to get live updates. This needs to be enabled in zapcloud. See the attached image.
- Added multiple services
Removed:
- Support for yaml configuration. Remove this from your yaml file(s).