Dependency conflict with core `nam`, `gios` and `brother` integrations

[bieniu]

Version of the custom_component

Configuration

Add your logs here.

Describe the bug

The core nam, gios and brother integrations use backend libraries which use dacite>=1.7.0 package. Govee integration causes dependency conflict because it forces dacite version 1.6.0 to be installed.

Debug log

Add your logs here.

[pejotigrek]

+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" :)

[ch3funio]

I've got the same conflict with nam and govee dependencies

[KitHubek]

the same here

[lazyjai]

+1 conflicts with Roborock as well. Update Govee to the newest dacite would be ideal.

[GitMeTender]

+1 please fix :)

[GitMeTender]

+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" :)

could you please make a short tut for this? would help a lot of people! 💯

[sugarfunk]

+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" :)

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

[DataBitz]

+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.