-
Notifications
You must be signed in to change notification settings - Fork 28
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
Pyvlx broken when garage door is in KLF200 #45
Comments
Hi @Julius2342, I just saw your PR, you are so fast ! I modified the I have now another message in logs and the garage door is not discovered in HA.
I already had the LIGHT_ON_OFF message before. |
The improvement is, that is no longer an exception :) Is it possible that you had Do you know the difference? We might just treat And the same applies to |
For sure ! Appreciate that ;)
I don't know how to check the hex code and I don't know the difference. I think it controls the light of the motor. I can do what you say and test.
I think it behave the same. It's a garage door (DEXXO SMART IO https://www.youtube.com/watch?v=V2VsOD4dLvo) I will try and tell you. |
Hello, My different tries didn't really work. As i'm not familiar with python, maybe I did things wrong. Your fix does not seems to be included in latest HA release. Regards, |
I just released a new version of pyvlx. make a pr to hass to bump the version. |
Hello,
I have a velux cover that works fine (KLF200 -> pyvlx -> HA).
I also have a garage door that produce an error in pyvlx when present in KLF200.
Here are the logs :
378 is x17A in hex. The API doc for that type says the following:
Can you add the 0x017A to the “enum” items in
NodeTypewithSubtype()
?Here is the discussion in HA community :
https://community.home-assistant.io/t/velux-component-for-klf-200-doesnt-support-the-new-api-with-firmware-2-0-0-71/75641/119
Many thanks !
The text was updated successfully, but these errors were encountered: