v0.7.0 pre release (please read release notes before updating)

[sfstar]

The problem

This is an issue that will be used as a thread to index what issues are found with the new register set added in the 0.7.0-beta release.

Link to release notes:
https://github.com/sfstar/hass-victron/releases/tag/v0.7.0-beta

Lowest compatible victron venus os version v3.54
Lowest tested ha core version (by maintainer) ha 2025.08.3 on haos

Installed devices during testing:

• grid meter
• vebus
• settings
• pvinverter

Further device behaviour feedback on this pre-release is appreciated.
Please note that support might be a bit slow so only upgrade if you feel comfortable enough to rollback based on instructions in release notes.
Don't upgrade if you want a more stable experience

Environment

• Home Assistant Core release with the issue:
• Last working Home Assistant Core release (if known):
• Integration version causing this issue:

Problem-relevant configuration dialog

Traceback/Error logs

In case of unit ID issue, missing devices or non-updating devices

Additional information

[kucerazdenek]

cerbo gx venus os version v3.55
HA container (Synology) - 2025.7.2
3-phase system (3x 25A), Fronius 8.2.3-M, 3x Victron Multiplus II/3000, 6x Pylontech US5000
I have seen battery device on ID 225 in v0.6.1, all entities were available.
After upgrade to 0.7.0 all entities under ID 225 got unavailable.
After rescan, device ID 225 disappeared as such

PS: when reverted back to 0.6.1, ID 225 battery appeared again

[sfstar]

Thank you for testing, due to upcoming breaking changes in the new 2025.9 release as discovered by @jacauc in #361 I will revert the changes made by the beta release in order to release an hotfix without these changes included.
Once done, the changes will be re-applied and 0.7.0-beta re-released.
Please note that the battery detection issue as of yet hasn't been resolved

[sfstar]

#366 will reintroduce the 0.7.0 functionality and will be remerged at 9th of september the earliest.
To allow for any other issues with the upcoming 2025.9 release to be addressed before these breaking changes are reintroduced.

[kucerazdenek]

#366 will reintroduce the 0.7.0 functionality and will be remerged at 9th of september the earliest. To allow for any other issues with the upcoming 2025.9 release to be addressed before these breaking changes are reintroduced.

@sfstar I really appreciate the hard work you do for all of us. May I ask you if there is some schedule/estimate, when version working with Venus OS/Cerbo GX 3.60+ will be released? In 3.60, Victron improved DynamicESS algorithm and this functionality finally become usable, but because of changes to modbus registers I cannot upgrade to this version and still stuck on 3.55. Thanks.

[VibroAxe]

#366 will reintroduce the 0.7.0 functionality and will be remerged at 9th of september the earliest. To allow for any other issues with the upcoming 2025.9 release to be addressed before these breaking changes are reintroduced.

@sfstar I really appreciate the hard work you do for all of us. May I ask you if there is some schedule/estimate, when version working with Venus OS/Cerbo GX 3.60+ will be released? In 3.60, Victron improved DynamicESS algorithm and this functionality finally become usable, but because of changes to modbus registers I cannot upgrade to this version and still stuck on 3.55. Thanks.

I just hit the same problem that my cerbo is on 3.70 and home assistant is on 2025.9 causing this integration to get stuck in the middle as the upgraded register set doesn't exist

[kucerazdenek]

Seem there is no activity about support of newer version of Venus OS. I found v0.7.0-beta-2 was released few days ago without any notice in this thread, but has warning "Note that in order for this integration to guarantee to work you need victron venus os v3.54 and < 3.60 installed" which makes it unusable. 3.60 was released in June, recent one is 3.66, so kind of late to the party...

[kucerazdenek]

Still same error on 0.7.0-beta-2 with Pylontech on ID 225 as decribed at beginning of this thread.

[kucerazdenek]

Still same error on 0.7.0-beta-2 with Pylontech on ID 225 as decribed at beginning of this thread.

After upgrade of Venus OS from version 3.55 to 3.66, ID 225 battery reappeared.

[kucerazdenek]

following entities become unavailable after upgrade Venus OS to 3.66.

[sfstar]

Thank you for your feedback,
I released a new beta v0.7.0-beta-3 with all register changes until that version according to the victron xlsx.
Since, its beta it might not fully work but it should at least find the new registers added until 3.66.

Edit small bug in v0.7.0-beta-3 has now been solved and v0.7.0-beta-4 is out now

[kucerazdenek]

Thanks, so far so good, at least for my configuration.
HA container (Synology) - 2025.10.4
Venus OS - 3.66
3-phase system (3x 25A)
3x Victron Multiplus II/3000
ID 20 - Fronius 8.2.3-M
ID 30 - grid meter
ID 100 - system
ID 225 - 6x Pylontech US5000
ID 227 - vebus

Only unavailable entity is victron_battery_mode

[sfstar]

#391 should introduce more of the new registers upon rescan.
Currently testing in my env.
Expect a beta bump this workweek.

[sfstar]

v0.7.0-beta-5 has been made (currently running on my production instance without issue)