home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.09k stars 31.1k forks source link

mycroftapi has overly strict version lock, creates dependency conflict for websocket-client #84164

Closed jorhett closed 1 year ago

jorhett commented 1 year ago

The problem

(venv) homeassistant$ pip3 install -r requirements_all.txt
...
ERROR: Cannot install -r requirements_all.txt (line 1029), -r requirements_all.txt (line 1137), -r requirements_all.txt (line 588), -r requirements_all.txt (line 897), -r requirements_all.txt (line 927) and -r requirements_all.txt (line 978) because these package versions have conflicting dependencies.

The conflict is caused by:
    devolo-home-control-api 0.18.2 depends on websocket-client>=0.58.0
    homematicip 1.0.11 depends on websocket-client>=1.0.0
    ibm-watson 5.2.2 depends on websocket-client==1.1.0
    jellyfin-apiclient-python 1.9.2 depends on websocket-client
    libsoundtouch 0.8.0 depends on websocket-client>=0.40.0
    mycroftapi 2.0 depends on websocket-client==0.44.0

What version of Home Assistant Core has the issue?

dev branch

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

mycroftapi

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.