Releases: sfstar/hass-victron
v0.6.3
Changes
Patch release based on v0.6.2 to backport ha core config flow incompatibility fix from beta v0.7.0-x release to v0.6.x for the new ha core 2025.12 release which will be released this evening.
Upgrades from from ha core 2025.11 to 2025.12 with this release installed were verified to work.
🚨 Breaking changes
None
🐛 Bug fixes
✨ New features
None
🚀 Enhancements
Special thanks to @RobMeerwijk this release!
Contributors
Assets 8
v0.7.0-beta-5
Changes
🚨 Breaking changes
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
🐛 Bug fixes
- Disable ess strategy for single register for now due to garbage retur… @sfstar (#387)
- split smart battery registers to solve battery becoming unavailable f… @sfstar (#391)
- remove 3 of the new registers since they seem to report garbage values @sfstar (#393)
✨ New features
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
- Feature add registers until 3 66 @iRateD1703, @sfstar (#386)
- Fix 2025.12 deprecation of config flow entries @sfstar (#394)
🚀 Enhancements
- Feature add registers until 3 66 @iRateD1703, @sfstar (#386)
Special thanks to @iRateD1703 for this release!
Contributors
Assets 8
v0.7.0-beta-4
Changes
🚨 Breaking changes
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
🐛 Bug fixes
✨ New features
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
- Feature add registers until 3 66 @iRateD1703, @sfstar (#386)
🚀 Enhancements
- Feature add registers until 3 66 @iRateD1703, @sfstar (#386)
Special thanks to @iRateD1703 for this release!
Contributors
Assets 8
v0.7.0-beta-3
Changes
🚨 Breaking changes
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
✨ New features
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
- Feature add registers until 3 66 @iRateD1703, @sfstar (#386)
🚀 Enhancements
- Feature add registers until 3 66 @iRateD1703, @sfstar (#386)
Special thanks to @iRateD1703 for this release!
Contributors
Assets 8
v0.7.0-beta-2
Changes
This is a beta release only install it in case you want to try the new release and are up to some work to revert to 0.6.2 in case this release doesn't work as expected. (If you want to upgrade when this release has matured a little please wait until this message is gone from the release notes).
🚨 Breaking changes
Note that in order for this integration to guarantee to work you need victron venus os v3.54 and < 3.60 installed.
After upgrading please perform a rescan off devices in case you want additional register sets to be discovered.
How to revert in case you want to go back to second latest release:
- install previous release via hacs
- perform rescan of devices
- remove the entities that were made for this release but werent present in 0.6.2
Current known issues are reported here #360
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
🐛 Bug fixes
None
✨ New features
- Revert "Revert "Feature/add all registers that were added to venus since integration inception"" @sfstar (#366)
Special thanks to No contributors for this release!
Contributors
Assets 8
v0.6.2
Changes
🚨 Breaking changes
This release bumps the minimum required ha core version to 2025.9.
Furthermore, it contains breaking changes that require all other modbus integrations installed via hacs to be upgraded at the same time as ha core is bumped to 2025.9.
If you are running any other modbus integrations please don't upgrade to 2025.9 until you are sure that all integrations are compatible.
If not, upgrade to this release and bump homeassistant core to 2025.9 at the same time since otherwise the built-in modbus integration or this integration might stop working.
Thanks to @jacauc for bringing the upcoming breaking change to my attention and proposing a pr to address the issue.
Furthermore, my apologies for putting a breaking change in a patch release.
Due to incompatible upcoming breaking changes for additional modbus registers in the 0.7.0-beta release I was unable to make a minor bump at this time.
- Feature/add all registers that were added to venus since integration inception @sfstar (#274)
- Revert "Feature/add all registers that were added to venus since integration inception" @sfstar (#364)
🐛 Bug fixes
- Feature/add all registers that were added to venus since integration inception @sfstar (#274)
- Revert "Feature/add all registers that were added to venus since integration inception" @sfstar (#364)
- Update hub.py to be compatible with PyModbus >=3.10 and HA 2025.9 @jacauc (#362)
✨ New features
🚀 Enhancements
⬆️ Dependency updates
Special thanks to @jacauc for this release!
Contributors
Assets 8
v0.7.0-beta
Changes
This is a beta release only install it in case you want to try the new release and are up to some work to revert to 0.6.1 in case this release doesn't work as expected. (If you want to upgrade when this release has matured a little please wait until this message is gone from the release notes).
🚨 Breaking changes
Note that in order for this integration to guarantee to work you need victron venus os v3.54 or higher installed.
After upgrading please perform a rescan off devices in case you want additional register sets to be discovered.
How to revert in case you want to go back to second latest release:
- install previous release via hacs
- perform rescan of devices
- remove the entities that were made for this release but werent present in 0.6.1
🐛 Bug fixes
✨ New features
Special thanks to No contributors for this release!
Contributors
Assets 8
v0.6.1
Changes
🚨🚨🚨 Please read this before upgrading 🚨🚨🚨:
It is recommended to upgrade this integration before upgrading homeassistant core.
So that you can revert to a working release of hass-victron and report any issues you encountered.
Normally this isn't necessary, but in this case the release was put through an quick test and some small issues might have been missed.
Note that issues found after upgrading will be investigated but a quick fix isn't guaranteed.
Therefore, each user should follow the upgrade path in accordance with their tollerance to risk / non functional state.
🐛 Bug fixes
Special thanks to No contributors for this release!