-
Notifications
You must be signed in to change notification settings - Fork 25
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
Govee integration kills MyVaillant #54
Comments
I have noticed the same behavior. Govee Bluetooth for some H5075 thermometers/hygrometers. They are actually quite useful when fine-tuning a heating system. So the two integrations co-existing would be rather nice. |
There's unfortunately no good fix for that. Govee requires a certain version of a library that seems to have buggy caching which causes this exact error. You could open a issue in Govee's Github and ask them to downgrade, or use the fixed MR konradhalas/dacite#237 |
is it sufficient to disable the bluetooth devices found? edit: disabled the bluetooth HASS integration and continue to use BLE instead |
https://github.com/signalkraft/mypyllant-component/releases/tag/v0.7.4b6 should work better with Govee, since the conflicting requirement is removed. |
Before submitting a new issue
Problem description
Please everyone be warned that Govee integration kills MyVaillant creating duplicated devices at first ( mine is VR 940F, ) and then killing any attempt to read data on the Vaillant's API site.
I'M using 0.6.1 and crashed my head agains the wall before discovering that simply removing the Govee integration fixes the trouble.
It also seems that the "Govee lan" integration can coexist with MyVaillant
Be warned!
Logs follows
Logs
The text was updated successfully, but these errors were encountered: