Open bieniu opened 1 year ago
+1 from me - had some problems with core nam
integration too.
after forceing govee
to install dacite
1.7.0 everything works smoothly, so it would be nice to have it "out of the box" :)
I've got the same conflict with nam and govee dependencies
the same here
+1 conflicts with Roborock as well. Update Govee to the newest dacite would be ideal.
+1 please fix :)
+1 from me - had some problems with core
nam
integration too. after forceinggovee
to installdacite
1.7.0 everything works smoothly, so it would be nice to have it "out of the box" :)
could you please make a short tut for this? would help a lot of people! 💯
+1 from me - had some problems with core
nam
integration too. after forceinggovee
to installdacite
1.7.0 everything works smoothly, so it would be nice to have it "out of the box" :)could you please make a short tut for this? would help a lot of people! 💯
1) Change the dependency in the manifest
2) Reload the integration
3) Reboot/restart
+1 conflicts with Roborock as well. Update Govee to the newest dacite would be ideal.
I could not use the HA core Roborock integration for months and finally found Govee was the cause. Had to switch to the govee2mqtt addon and remove this addon because of it.
Version of the custom_component
Configuration
Describe the bug
The core
nam
,gios
andbrother
integrations use backend libraries which usedacite>=1.7.0
package. Govee integration causes dependency conflict because it forcesdacite
version1.6.0
to be installed.Debug log