Releases: sfstar/hass-victron
v0.0.10
This is a "Bugfix" release that is required in order to use the integration with homeassistant 2023.5.x and higher.
Thanks to @nijel for opening pr's that address issue #22 and the proper decoding of string based entities.
Breaking changes
None
Bugfix
- Ensure proper decoding of string based entities #59
- Ensure that non numeric entities don't have an device_class, state_class, unit_of_measurement or suggested_display_precision #58, #22
New features
None
Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.0.9..v0.0.10
Contributors
Assets 2
v0.0.9
This is a "Bugfix" release
Thanks to @ChristophPech for opening (and michaelkuty for testing) a pr that adresses issues #48 and #18
Breaking changes
None
Bugfix
- Fixed writing to number.victron_settings_ess_maxdischargepower. For more detail see #48
- Introduce static step definition for registers like number. victron_settings_ess_batterylife_minimumsoc that only support values that are a multiple of x (in the example case 5) #18
New features
None
Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.0.8..v0.0.9
Contributors
Assets 2
v0.0.8
This is a "bugfix" release
Breaking changes
None
Bugfix
- Do not assign device class to text based entities that shouldn't have a device class.
This resolves issues #22, #25, #32, #42, #43.
These issues were caused by the conditional statement for device class checking empty entity unit types to the unit type "voltage"
This string to string comparison always returned true with an empty string since the check was setup to see if "" was contained in "voltage".
Instead of checking whether "" fully matched "voltage".
By fixing this check the text based entities with no unit type should now no longer be assigned "voltage" as device class.
New features
None
Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.0.5..v0.0.6
v0.0.7
This is a "bugfix" release
Breaking changes
None
Bugfix
None
New features
- Core modbus integration compatibility
Starting from homeassistant core version 2023.2.x the built-in modbus integration now uses pymodbus version 3.1.1.
Version 0.0.7 (and up) of this integration will also use the 3.1.1 pymodbus version.
This ensures that this integration and the built-in modbus integration will be able to be run in parallel.
Which allows users to try out this integration without having to remove the built-in modbus yaml configuration.
It also facilitates a slower less destructive migration path by allowing users to switch over lovelace, yaml and automations entity references in due time.
Disclaimer:
Although core version >= 2023.2 and previous versions of this integration should be compatible it is recommended that all users update both core and this integration in the same patch round.
Since having multiple library version requirements might cause the built-in 3.1.1 library to be overwritten by 3.0.2 reference of versions 0.0.6 and earlier.
This could cause issues if you are using specific configuration options of the built-in modbus integration that weren't working with pymodbus 3.0.2 and were fixed in 3.1.1
Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.0.5..v0.0.6
v0.0.6
This is a "bugfix" release
Breaking changes
None
Bugfix
- Fixes #11 "Retrying setup: division by zero"
This bug prevented a successful setup of the integration and occurred whenever an user has a system with a generator.
It was missed when issue #7 was fixed in release v0.0.4
New features
None
Full Changelog: https://github.com/sfstar/hass-victron/compare/v0.0.5..v0.0.6
v0.0.5
This is a "bugfix" release with breaking changes
Breaking changes
- Change behaviour of ve.can 0 device.
The VE.CAN 0 device is offered under the unit 100 (system / settings) registers by victron.
Since the unit id is used to determine under which device the entities are grouped this caused the VE.CAN 0 device to be included in the overall system settings.
In order to change this an condition has been added that checks if the registers aren't of type system/settings for unit 100
If so the actual id of 0 is used to trigger these entities to automatically group in (for example) an solarcharger device.
This is the behaviour for all other devices but wasn't yet applied to the special unit 100 case.
For users that are upgrading it's important to know that the VE.CAN entities currently under settings will become permanently unavailable when upgrading.
Please update your dashboard, automation etc references to this change and manually remove these entities. (Or you could delete and add the integration again to cleanup the unavailable entities).
While at the same time a new device will be created for the new VE.CAN 0 entities. (essentially the old entity_id but with _0 appended to the end like all other slaves that are not 100 or 225
Bugfix
- See breaking changes section
New features
- None
Full Changelog: v0.0.4...v0.0.5
v0.0.4
This is a "bugfix" release
Bugfixes
- Revert assumed multiply behaviour introduced in v0.0.3 (see #7).
In version v0.0.3 an change was introduced that multiplied the register data that was returned by 10 if the scalefactor is 0.
However, it turned out that there aren't any scalefactor 0 registers in the victron documentation.
These 0 values were in fact 0.1 or 0.01 entries that weren't correctly displayed in numbers on mac.
This bugfix removes treating 0 scalefactor as a special case in total.
As well as introduces the correct scale factor in the register ledger entries of this integration
New features
- Initial attempt at supporting gracefull unavailable state.
This is an initial attempt at supporting the unavailable state when an (partial) update of the entities failes.
It also changes the failure from an error to an warning with basic resolve instruction.
Full Changelog: v0.0.3...v0.0.4
v0.0.3
v0.0.2
This is a "bugfix" release
Bugfixes
- Assign old data as parsed data if an update failes
This bugfix enhances the integration resilience to partial data request failures.
The downside is that no entities will be updated until the next completely successfull update interval
The upside being that a single register set not updating will no longer crash the integration (requiring a manual restart for the entities to update again).
New features
- None
Full Changelog: v0.0.1...v0.0.2
v0.0.1
This release is the first acceptance release for the hass-victron integration.
It includes support for:
- Discovering victron GX connected devices on setup
- Rescan option to update list of connected devices
- Reading all registers of victron energy gx device into sensors and binary_sensors
- (if write support enabled) Exposing sliders, buttons, switches and selects for writeable registers
- Configurable update interval
- Limiting sliders etc based on user system limits (voltage/amperage of DC / AC circuit)
- Changing from write to read (and vice versa) without having to re-add integration
- Expose all entities with correct device class, state_class and unit of measurement if applicable
- Grouping the entities in logical devices (please note that devices that are assigned another role like grid meters will generate a new device name based on that role)
Known limitations
- This version will only work if the built-in modbus integration is not enabled.
Due to a major version mismatch in the used pymodbus library version.
In december 2022 the maintainer of pymodbus is expected to release 3.1.0 after which the built-in modbus integration will be updated to include 3.1.0 as the version used.
When that occurs the release version of home assistant that contains the 3.1.0 change will become the mimum recommended version for this integration (The ha version is expected to be 2022.12 or 20223.01)
- The entities exposed won't be marked unavailable on a connection loss
The entities exposed by this integration currently won't update while the connection is lost to the GX device.
This could cause an end user to incorrectly think that the integration is still working correctly.
This behaviour will be addressed in a future release.