-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Regression for VMBDALI starting at 2024.7.0 #114
Comments
@sidlgor, @cereal2nd I see two changes in ac557be that I'm trying to understand. I've read the commit message, but that didn't resolve my questions. Can you elaborate on the reasoning behind these changes? I don't want to break the new things you introduced by just rolling these back.
|
Fixes cereal2nd#114
Fixes cereal2nd#114
Fixes cereal2nd#114
Fixes cereal2nd#114
can you make a pull-request out of these commits? |
Sorry, my mistake, overlooked overload for VMBDali (bad excuse: I don't own VmbDali) |
Fixes cereal2nd#114
Type 69 seems to load again with the above commit:
So does VMBDALI-20 (type:90)
|
Hi,
Since version I am 2024.7.0 no longer able to use my 'old' VMBDALI module anymore. In another location an updated VMBDALI-20 seems to load, but is not showing any channels with version >2024.7.0.
Same scan on same version ( and same requirements.txt ) on another location with a VMBDALI-20 seems to work up to module level, but is not loading any channels.
Is module type '69' no longer detected as a VMBDALI and where's the channels?
Please advise, let me know what else I can do to help and thanks in advance!
The text was updated successfully, but these errors were encountered: