Bump vallox_websocket_api to 4.0.2

[slovdahl]

Proposed change

Changelog: yozik04/vallox_websocket_api@3.3.0...4.0.2

Attempts to fix #99294.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Vallox data handling #99294
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @andre-richter, @viiru-, mind taking a look at this pull request as it has been labeled with an integration (vallox) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vallox can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign vallox Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[slovdahl]

@yozik04 it looks like the UUID of the Vallox unit changes with the update 🤔 This means that a new device and entities are added and all the old entities are made unavailable after the upgrade, which is a bit annoying.

In my dev instance my Vallox unit got UUID 83f56834-6639-41c0-b727-b896b7633bbd before, and now 83f56834-6639-41c0-b727-b896b7630024. So only the last 4 characters have changed, 3bbd -> 0024. Any idea what could cause it?

[yozik04]

It can be that previous was just wrong :) can you validate it somehow?

[slovdahl]

What does this return for you on 3.3.0 vs 4.0.0?

import asyncio
from vallox_websocket_api import Vallox

client = Vallox('ip.address')

async def run():
    info = await client.get_info()
    print(f"client.get_info(): {info}")

asyncio.new_event_loop().run_until_complete(run())

With 3.3.0:

$ python test.py 
client.get_info(): {'model': 'Vallox 110 MV', 'sw_version': '2.0.2', 'uuid': UUID('83f56834-6639-41c0-b727-b896b7633bbd')}

With 4.0.0:

$ python test.py 
client.get_info(): {'model': 'Vallox 110 MV', 'sw_version': '2.0.2', 'uuid': UUID('83f56834-6639-41c0-b727-b896b7630024')}

[slovdahl]

Ah, the Vallox web UI actually lists it too. It says the same as on version 3.3.0 of vallox_websocket_api.

[yozik04]

Reproduced. Will investigate.

[yozik04]

Fixed in 4.0.2

[slovdahl]

Fixed in 4.0.2

Thank you, confirmed in HA that upgrading does not add a second device now and that the test.py script gives the same UUID 👍🙇

Need to dig into the test failures now then.. 🤔

[bdraco]

Thanks @slovdahl @yozik04