Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix vmbdali #115

Merged
merged 2 commits into from
Jul 22, 2024
Merged

Bugfix vmbdali #115

merged 2 commits into from
Jul 22, 2024

Conversation

niobos
Copy link
Collaborator

@niobos niobos commented Jul 22, 2024

WARNING: WORK IN PROGRESS
I haven't tested this on my installation yet

This should fix #114.
It also adds a very basic test that should catch this in the future.

@cereal2nd cereal2nd merged commit d7e7b5f into cereal2nd:master Jul 22, 2024
8 checks passed
@dverhelst
Copy link
Contributor

@niobos , can I be of assistance testing VMBDALI and VMBDALI-20 going forward?

@niobos
Copy link
Collaborator Author

niobos commented Jul 26, 2024

I still need to test the changes on an actual installation that has the VMBDALI modules. Currently, I can't access it, but I should be able to in the next few weeks. If you know how to run Home Assistant with a development version of velbus-aio, you can try it and report back.

@niobos
Copy link
Collaborator Author

niobos commented Jul 30, 2024

I can confirm that these changes fix the VMBDALI (1st version, not -20) in my installation.

What needs to happen next is that @cereal2nd needs to release a new version of this library, and this new release needs to be referenced from the Home Assistant code. This is fairly straight-forward, but requires some manual work.

@cereal2nd
Copy link
Owner

the pull-request has been created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression for VMBDALI starting at 2024.7.0
3 participants