v0.3.0

This release contains several bug fixes, improvements and a breaking change.

Users that have a device with modbus id 0 connected should perform a rescan after installing this update.
This will seperate the modbus device with id 0 into it's seperate dedicated device.
Unfortunately historical data for the entities, when the device was placed under unit id 100, will not be transfered.
All other entities and devices should remain unaffected.

Breaking changes

• Split device with unit id 0 into a dedicated device instead of grouping under device 100 #21, #47, #96, #138, #161, #191

Bugfix

• Add unit id 101 as valid unit id for temp sensors #45
• Add unit id 36 to allow for the detection of more pvinverters #200
• Decode ess_mode values more accurately #44
• Scale startervoltage of alternator by 10 instead of 100 #27

New features

• Allow users to change the host IP when migrating subnets/ip's by reconfiguring the integration #121
• Add solarcharge state "WAKE-UP" as a decodable value #178
• Add tank status "ERROR" as decodable value #102

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.2.0..v0.3.0

v0.2.0

This release contains several bug fixes and fixes that improve the integrations stability.
Users that have devices not being detected by this integration should perform a rescan after upgrading.
Furthermore, the stability of handling victron non-documented output has been improved.
Previously returning undocumented values had the unfortunate effect of stopping entities from being updating.
Starting from this release the integration will now log an error and set the state of the entity as "nondecodeable".

Please note that also starting from this release the integration will allow some community sourced register decodings that are not properly documented by victron to be added. This entails a parting ways from the rigid approach of if it's not documented it's not added.

Breaking changes

None

Bugfix

• PV-inverters, solarchargers and grid meters with modbus id 35 or 36 are now correctly detected #36, #129, #137, #182
• State of charge is now correctly displayed for battery entities #130
• Improved resilliency to unsupported values being returned by the gx device #189

New features

• Unit id range introduced by gx release 3.20 is now supported #8, #157, #179, #192
• Ruuvi battery state low is now a supported decodeable value #186

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.7..v0.2.0

v0.1.7

"BREAKING CHANGE"
Victron has released an new modbus register XLSX file.
In this file the registers for:
sensor.victron_pvinverter_power_max_capacity
sensor.victron_pvinverter_power_total
sensor.victron_ gps_altitude

Have been marked with new unit of measurements reflecting the actual value being reported.
Users that have an pvinverter and/or an GPS device connected to the GX device will have to manually "fix" the entities after updating the integration.

This can be done by pressing the "Fix Issue" button on the page "developer tools" -> "statistics"
You can also use this button to navigate to the page (if you have my homeassistant configured):

Ensure that you choose the "Update the unit of the historic statistic values from '' to 'W', without converting." option.

Please note that if you downgrade from v0.1.7 to an earlier version you will need to perform the "Fix Issue" flow again (after downgrading) to revert the statistics unit of measurement back to the value used in those releases.

Users that don't follow the "Fix Issue" flow will experience no statistics data being compiled for these entities.

Breaking changes

• This release changes the unit of measurement for pvinverter_max_capacity, pvinverter_power_total #133 #142 #159 #169 based on victronenergy/dbus_modbustcp#30
• This release changes the unit of measurement for gps_altitude #28 based on victronenergy/dbus_modbustcp#31

Bugfix

None

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.6..v0.1.7

v0.1.6

This release contains fixes contributed by @ChristophCaina to resolve warnings related to deprecated constants that will be removed in HA 2025.1 #154

Breaking changes

None

Bugfix

None

New features

Prepared this integration for ha constants deprecations slated for 2025.1

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.5..v0.1.6

v0.1.5

"BREAKING CHANGE"
Homeassistant has released homeassistant core 2023.9.1.
This release bumps the pymodbus library version to match the one used by the core modbus integration in ha core 2023.9.1 (home-assistant/core#99940).
This library version contains a breaking change in the naming scheme for decoding constants that are also used by this integration.

Users running both the core modbus integration and this integration should upgrade both in the same cycle.
If you upgrade either this integration or HA core without upgrading the other then you will get errors on startup and this integration might not function.

Furthermore, please check if you are using any other integrations that rely on the pymodbus library and update them to a patched version in the same patch round.

Breaking changes

This and any further releases of this integration will now only support HA core 2023.9.1 and newer. (For older ha core versions use previous releases) #122

Bugfix

None

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.4..v0.1.5

v0.1.4

This release changes the behaviour of this integration regarding the modbus library that is also used by the core modbus integration.
Due to multiple breaking changes (for core modbus integration) being introduced in the last couple of ha core releases a lot of users that also use the core modbus integration were experiencing issues when this integration was activated due to it's strict version constraint conflicting with the ha core required version.
By loosening the version constraint to a greater than pymodbus version, this integration should clash less with the ha core version constraint and should make it compatible again with ha core 2023.7.0 until 2023.9.0 (for 2023.9.1 and newer check v0.1.5).

This will however come at the cost of this integration being quicker to break upon HA core version upgrades.
If the working of this integration is mission critical to you then please be slower to upgrade and check for reported issues before eventually bumping versions.

Breaking changes

None

Bugfix

• Loosening of the pymodbus library version constraint should most likely address several of the following issues #115, #112, #105, #97 and #103

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.3..v0.1.4

v0.1.3

This is a compatibility release that bumps the pymodbus library version used by this integration to align to the version used by ha core 2023.8

Breaking changes

None

Bugfix

None

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.2..v0.1.3

v0.1.2

This is a "bugfix" release that adresses the way this integration handles updating entities when the connection to the modbus service is lost. Although this doesn't adress all connection issues it should reduce the amount of scenario's that cause the entities to no longer update.

Breaking changes

None

Bugfix

• Ensure that only coordinator data pushes are used to update entity state instead of also polling it from the entity side.

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.1..v0.1.2

v0.1.1

This is a "bugfix" release that will allow this integration to work with home assistant 2023.6 (and python 3.11 by extension)

Breaking changes

None

Bugfix

• Ensure that no deprecated properties are being set on victron number entities to prevent the integration not working with homeassistant 2023.10
• Ensure that no non-default properties are being set after properties that have a default set #81

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.1.0..v0.1.1

v0.1.0

This is a "breaking change" release that is intended to improve multiphase support and granular sliders #67, #57, #52 and #15

Breaking changes

This release introduces a first attempt at better supporting split and three phase systems by simplifying the configuration flow for these systems.
Furthermore this release also introduces a configureable option to have either "slider" or "box" based number entities so that users have the ability to (via typing) set (for example ess_powersetpoint) to more granular values.

Please note that this release introduces new configuration options that will result in errors when the integration is restarted without an config update.
The easiest way to trigger this update is to remove the configuration under "Settings" -> "Devices & services" (by clicking on the "hamburger menu" next to the victron entry and following the "delete" flow).
After which you can re-add the integration by folllowing the configuration wizard to re-add the integration to your home assistant instance.
Statistics and automations won't be affected by this action since the integration will re-add the entities with the same unique_id and entity_id's.

Bugfix

None

New features

None

Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.0.10..v0.1.0