Skip to content

Bug Fix: PVS5 Setup Failure

Choose a tag to compare

View all tags
@smcneece smcneece released this 23 Mar 20:31
v2026.03.4
1f8a57d

Release Date: March 23 2026
Type: Bug fix

What's Fixed

PVS5 systems could not be added to Home Assistant

PVS5 firmware does not include a standalone BUILD field in its supervisor/info response. Instead, the build number is embedded in the SWVER string (for example "2025.11, Build 5412"). The integration was looking only for a standalone BUILD field, found nothing, and fell back to legacy mode. Legacy mode returned a 403 error because PVS5 new firmware requires authentication. Setup failed entirely with no clear error message.

Three issues were corrected:

  1. The integration now falls back to parsing the SWVER field when no standalone BUILD field is present. The build number parser already handled this format; it just was not being called with SWVER as input.

  2. PVS5 is now correctly identified as new firmware (varserver) regardless of build number. The 61840 build threshold applies only to PVS6 hardware. Any PVS5 with a detected build is treated as new firmware and uses the varserver authentication path.

  3. The 60-second polling minimum intended for old PVS6 firmware no longer applies to PVS5. PVS5 with new firmware follows the standard 10-second minimum.

Who Is Affected

PVS5 hardware owners who have not been able to add the integration. PVS6 users are not affected.

Upgrade Notes

  • Standard HACS update or manual file copy, restart Home Assistant
  • No configuration changes required
  • PVS5 users who previously could not set up the integration should now be able to add it normally
Assets 2
Loading