Not sure if this is the right category so I apologize if it isn’t.
I’m currently running HA in a Docker container, managed by docker-compose. My typical workflow to update HA is:
docker stop home-assistant
docker rm home-assistant
docker-compose pull home-assistant
docker-compose up -d home-assistant
This gets me the latest HA core however the 3rd party Python dependencies listed in the component’s manifest are not updated to the version listed. For example, the August component has a dependency of py-august==0.14.0 however after pulling the latest image, I’m still only at py-august==0.8.1.
Is this expected behavior? The only reason I noticed this is that there was a bug recently fixed in the August component that also required a change in the 3rd party library.
The versions are checked on startup and automatically pulled in on each start of Home Assistant.
So if the manifest.json says py-august==0.14.0 then it should attempted to pip install --upgrade py-august==0.14.0, there is a posibility that your instance may be having issues grabbing it from the internet. This would show up in the syslog.
Thanks for the reply. I’m not seeing anything relevant in syslog. I did manually upgrade by getting a bash shell in the container and running pip3 install --upgrade py-august==0.14.0 and that seemed to work fine. Running a pip3 freeze now shows the updated version.