Actually the directory ‘/usr/src/homeassistant/homeassistant’ does not exist on my installation.
As for the error itself I am in a process of ‘trying to complete’ my Risco Alarm integration, which is a ‘Partitionless’ Risco (MyElas) iConnect2 (system status arm/ disarm does not show/ function). A project on this is going on in Github https://github.com/home-assistant/core/issues/62927 and https://github.com/OnFreund/pyrisco/pull/2.
From Github I installed 'risco.py patched file in the ‘/pyrisco/’ directory.
Logbook references to line 134 in this file, but the actual code is completely different now from what is stated in the log (log text is the one which was in the previous risco.py file).
So, what does the Traceback represent?
My installation: Home Assistant core-2021.12.7 in Docker container, on Intel NUC, running Debian Buster. Active Python version 3.9.
You mean you overwrote “/usr/local/…/pyrisco/risco.py” inside the docker container, right?
If so, keep in mind that any update/recreation of the container will lose that.
How can I investigate further what you are referring to?
(Note: off course I do understand if I update Home assistant versions the container is replaced. So permanent data, like risco.py, need to be outside the container).
You have issued ls directly in the directory you are dropped in to - which as you can see is already /config
Whereas if you issued - cd / and then ls I think you will find a more typical linux filesystem…
Well, look for /usr/src/homeassistant inside the container. It has its own filesystem, unrelated to the one of host, besides those directories that you explicitly mount inside it, like /config which is mapped somewhere to a host directory.
@mobile.andrew.jones@koying
Thanks guys! You just confirmed my ‘rookie’ status in Docker. I was able to access the different directories and replaced the ‘risco.py’ file within the container. After restart of Home Assistant no more error messages on Risco!
