Open kirangp opened 11 months ago
Same here!
I have the same problem. Hoping for a solution!
Pretty much all the sungrow addons have this problem atm. Tried pinning some different versions but no luck.
Same issue for me
+1
+1
Yup ditto - same issue here. Just freshly installed Home Assistant OS, running in VM.
k, so it does not look like the: pycryptodomex==3.11.0 Is in the main requirements, however I am cautious this is inside the Docker container... just need to work out how to get inside that and the wrapping here, as a blunt hammer may try: pycryptodomex~=3.11.0 for requirements.txt, that should install anything compatible with 3.11 code stream...
found it in Dockerfile: COPY requirements.txt ./ RUN apk add --no-cache python3-dev py3-pip g++ RUN pip install --upgrade pycryptodomex==3.11.0 --no-cache-dir -r requirements.txt
Changing to: COPY requirements.txt ./ RUN apk add --no-cache python3-dev py3-pip g++ RUN pip install --upgrade pycryptodomex~=3.11.0 --no-cache-dir -r requirements.txt
... let's see what goes boom.
pull request created, not sure if someone needs to approve here, will dig a little further around repo
same here. Also freshly installed Home Assistant OS running in a VM. @loucksg I'm not sure, how to understand your last answer: what exactly was the outcome and is there a workaround at the moment? I tried Part 2 from here and it seems to work: https://gist.github.com/Paraphraser/cad3b0aa6428c58ee87bc835ac12ed37
@ltw001 Link seems broken?
@loucksg Is there any way I can install this addon with your pull request in HA? Looks like the pull request has not been approved/merged.
@loucksg Is there any way I can install this addon with your pull request in HA? Looks like the pull request has not been approved/merged.
I'm guessing we could fork https://github.com/MatterVN/HassioAddon and this repo and fix it on that fork? I've tried that but I'm rather new to Home Assistant add-ons and can't seem to get the reference from the HassioAddon repo to the submodule to work.
Same problem here. I try to install the addon following the instructions but still does not work.
is it possible to upload with the fix ?
+1 same issue here when attempting to install
@ltw001 Link seems broken?
I think it's this - https://gist.github.com/Paraphraser/cad3b0aa6428c58ee87bc835ac12ed37#part-2--using-patched-images-in-homeassistant
but seems to be referencing gosungrow not modbustcp2mqtt
same here totally fresh here - how to fix this? - please help
same here totally fresh here - how to fix this? - please help
Hi @RafAustralia, this was fixed in a fork over at https://github.com/DisreputableCode/HassioAddons Been using it from r about a month or 2 without any problems.
Hey Benborra.
Firstly huge thank you for replying. It means a lot.
Secondly please note I am so new to home assistant that I would barely know how to apply this fix. I just read through It and it has the fixes I saw people mention online like the docker file etc etc. But it is no longer pressing an install button stuff. It needs knowledge of code. Im getting better by the minute but my code is minimal. Been doing it for 3 days. Lol. Sorry.
Hencewhy its a bit of babysitting stuff
Raf Sent from Nam Concept’s iPhone
On 3 May 2024, at 11:39 PM, benborra @.***> wrote:
same here totally fresh here - how to fix this? - please help
Hi @RafAustraliahttps://github.com/RafAustralia, this was fixed in a fork over at https://github.com/DisreputableCode/HassioAddons Been using it from r about a month or 2 without any problems.
— Reply to this email directly, view it on GitHubhttps://github.com/MatterVN/ModbusTCP2MQTT/issues/72#issuecomment-2093042813, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIGQNNDAU2YIC5PQCLDJTM3ZAOHO5AVCNFSM6AAAAABARKRKEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGA2DEOBRGM. You are receiving this because you were mentioned.Message ID: @.***>
Hey!
It actually worked… I was able to install it, but by the time I got there some of my sensors were so messed up that I decided to start over… but I just wanted to say huge thank you for being so kind and showing me the fix for it. 😊
Thank you.
Raf
From: benborra @.> Sent: Friday, May 3, 2024 11:39 PM To: MatterVN/ModbusTCP2MQTT @.> Cc: Rafal Tomaszewski @.>; Mention @.> Subject: Re: [MatterVN/ModbusTCP2MQTT] Unable to install the addon (Issue #72)
same here totally fresh here - how to fix this? - please help
Hi @RafAustraliahttps://github.com/RafAustralia, this was fixed in a fork over at https://github.com/DisreputableCode/HassioAddons Been using it from r about a month or 2 without any problems.
— Reply to this email directly, view it on GitHubhttps://github.com/MatterVN/ModbusTCP2MQTT/issues/72#issuecomment-2093042813, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIGQNNDAU2YIC5PQCLDJTM3ZAOHO5AVCNFSM6AAAAABARKRKEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGA2DEOBRGM. You are receiving this because you were mentioned.Message ID: @.**@.>>
No worries, was one of the most complex things I've done so far in home assistant as well. I unfortunately don't recall which guide I followed but I also had some issues fetching the data from my sungrow converter because I was polling to frequently. Couldn't even reach it directly by IP anymore myself.
I also had to add the MQTT to my Integrations.
And there I needed to add my parameters.
I had to reinstall the addon and now whenever I try to install, I always get the below error.
Thanks
Log
Logger: homeassistant.components.hassio Source: components/hassio/websocket_api.py:138 Integration: Home Assistant Supervisor (documentation, issues) First occurred: 21:38:00 (4 occurrences) Last logged: 22:46:33
Failed to to call /addons/eeb054de_modbus_inverter/install - The command '/bin/ash -o pipefail -c pip install --upgrade pycryptodomex==3.11.0 --no-cache-dir -r requirements.txt' returned a non-zero code: 1 Failed to to call /store/repositories - Can't add https://github.com/MatterVN/HassioAddon, already in the store
Managed to dig up more and see this in Supervisor Logs
23-12-12 23:08:15 INFO (MainThread) [supervisor.host.apparmor] Adding/updating AppArmor profile: eeb054de_modbus_inverter 23-12-12 23:08:15 INFO (MainThread) [supervisor.docker.addon] Starting build for eeb054de/aarch64-addon-modbus_inverter:0.3.8 23-12-12 23:08:25 ERROR (MainThread) [supervisor.docker.addon] Can't build eeb054de/aarch64-addon-modbus_inverter:0.3.8: The command '/bin/ash -o pipefail -c pip install --upgrade pycryptodomex==3.11.0 --no-cache-dir -r requirements.txt' returned a non-zero code: 1 23-12-12 23:08:25 ERROR (MainThread) [supervisor.docker.addon] Build log: Step 1/23 : ARG BUILD_FROM
Step 2/23 : FROM $BUILD_FROM
---> d524bbcac2d5
Step 3/23 : ENV LANG C.UTF-8
---> Using cache
---> 680ba6cc0009
Step 4/23 : ARG BUILD_VERSION
---> Using cache
---> 1ec1d5293eda
Step 5/23 : ARG BUILD_ARCH
---> Using cache
---> 95be34e1f31a
Step 6/23 : COPY requirements.txt ./
---> Using cache
---> f0adae72b86c
Step 7/23 : RUN apk add --no-cache python3-dev py3-pip g++
---> Using cache
---> 6fd6012fbf33
Step 8/23 : RUN pip install --upgrade pycryptodomex==3.11.0 --no-cache-dir -r requirements.txt
---> Running in e32d095d6563
error: externally-managed-environment
× This environment is externally managed ╰─> The system-wide python installation should be maintained using the system package manager (apk) only.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification.
Removing intermediate container e32d095d6563