jeatheak / Mitsubishi-WF-RAC-Integration

WF-RAC homeassistant integration
MIT License
101 stars 19 forks source link

Bump aenum requirement from aenum==3.1.11 to aenum>=3.1.11 or aenum==3.1.12 #50

Closed Veda82 closed 1 year ago

Veda82 commented 1 year ago

I'm using Home Assistant in a docker environment with this image:

https://hub.docker.com/r/linuxserver/homeassistant

In this image, aenum has been updated to version 3.1.12; the integration requires version 3.1.11.

Unfortunately, due to some permission issues, Home Assistant cannot downgrade the package in this docker image, see:

https://github.com/linuxserver/docker-homeassistant/issues/74

There is a solution using a docker mod:

https://github.com/linuxserver/docker-mods/tree/universal-package-install

but it would be easier / neater if the integration requirement could be changed in:

aenum>=3.1.11

or

aenum==3.1.12

tismij commented 1 year ago

have the same issue, how did you fix this until req changed ? nvm went back a version until fixed.

Veda82 commented 1 year ago

@tismij if you're using the same Docker image, you can use:

https://github.com/linuxserver/docker-mods

Basically, you should add these environment variables to your container configuration:

DOCKER_MODS=linuxserver/mods:universal-package-install INSTALL_PIP_PACKAGES=aenum==3.1.11

tismij commented 1 year ago

noticed in manifest.json it says: "requirements": ["aenum==3.1.11"] When I have more time will try changing in here and seeing if that is enough. Edit: manifest.json in the custom_components\mitsubishi_wf_rac folder in my docker environment.

jeatheak commented 1 year ago

Hey @Veda82 @tismij I changed the requirements to >= 3.1.11 hopefully it will fi the issue for you.

Veda82 commented 1 year ago

Great! I will test and let you know!

Veda82 commented 1 year ago

Just tested the update, everything seems fine to me...

Thanks for the support!