G-Two
commented
2 months ago It's been a couple years since I've tried/documented the a manual installation process. The contents you list in /.local are all the expected files that would be installed with the subarulink package dependency (i.e. if you were to pip install subarulink). AFAIK, the only control this custom-component has is specifying that subarulink needs to be installed (via the manifest.json file). The files associated with that installation are controlled by the subarulink package, but the ultimate path they are installed to is controlled by the system/script that actually performs the installation.
I was unable to initially install this in a docker image.
I worked around the problem as follows:
note that user 114 is the user ID that home assistant runs as in the container; this might be different for anybody else so beware. Also note that in that command 'homeassistant' is the name I gave to the container. YMMV.
My installation process was exactly what's in the README for manual installation - copy into config/custom_components. After doing the above it works fine.
Something is attempting to write to /.local which as you can see from the path is the root directory (within the container). I suspect that whatever is asking to write there is expecting some kind of prefix in an environment variable or elsewhere.
I am PRETTY sure that whatever this problem is relates to how the homelink plugin is installing its dependency, the main subarulink api. The reason I say that is by examining the contents of /.local (see below). I don't know what's causing it to install its dependency there - I have not encountered this with other custom homeassistant plugins (though I don't use many). I don't really control the installation, it's done by home assistant, and it's not giving me any additional information into what it's doing. There is a good chance that what I'm seeing has not to do with this module specifically and is something weird about the official homeassistant docker container, perhaps something I should have configured. But since I saw the error with this integration, I am reporting it here - I will try to figure this out and if I find it has nothing to do with this module I will come back and close this ticket. In the mean time if anybody has any suggestions on how to figure this out please let me know.