Skip to content

4.0.7: Multi-split (VRF) setups: find every indoor unit, one device per unit, no bounce-back

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Sep 20:12
· 10 commits to master since this release
4.0.7
c60969d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release makes multi-split (VRF) setups work properly. One Gree WiFi gateway (for example a GR-Gcloud) that fronts several indoor units is now discovered completely, each indoor unit becomes its own Home Assistant device, and the UI no longer bounces back to the old value after a command.

  • Discovery finds all indoor units. The sub-unit list is fetched after the scan instead of inside it, for all gateways at the same time. The integration asks for it in each form that different module firmwares answer, and merges the results. A gateway with a single indoor unit is expanded too. (#507)
  • One device per indoor unit. All indoor units used to share one device, so they could not be put in different rooms. They now each get their own device. (#454)
  • No more bounce-back. A VRF gateway can report its old cached state for a few seconds after a command. The integration now keeps the value you set until the unit confirms it, for at most 8 seconds, and refreshes about 2 seconds after each command. (#508)
  • Unsupported switches are hidden. Switches for features an indoor unit does not have (it reports an empty value) are now shown as unavailable. (#508)

If you already have a VRF setup: after the update you will see an old shared device with no entities left. Delete it under Settings > Devices & services > Devices. The switch entities also get new unique IDs, so the old switch entities stay behind and the new ones may get a _2 suffix in their entity ID. Update automations that use them.

For all users: switches now show as unavailable while the unit is offline. The change also carries #520, which starts the upcoming 5.0 integration when it is installed next to this one, so the move to 5.0 later happens without extra steps.

Tested on my own dev instance against my standalone test unit (no change for single units, same entity IDs) and against a fake VRF gateway harness that reproduces the stale read-back and the different sub-unit list forms. The VRF behaviour itself was tested on real gateways by the contributors.

Thanks to @meirlo and @ItayGo for the contributions.

What's Changed

  • Start the 5.0 integration when it is installed next to 4.x by @RobHofmann in #520
  • Fix VRF sub-device discovery: defer + concurrent subList, robust parsing by @meirlo in #507
  • fix: complete VRF device_info fix started in #338 — sub-units still share one HA device by @ItayGo in #454
  • Hold VRF sub-unit UI state until gateway catches up; hide unsupported switches by @meirlo in #508
  • Release 4.0.7 by @github-actions[bot] in #521

New Contributors

Full Changelog: 4.0.6...4.0.7

Contributors

RobHofmann, meirlo, and ItayGo
Assets 2
Loading