-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any chance for 1.2 as home assistant Addon? #1218
Comments
+1. There's the one in this repo but it's stuck at 1.1 and seems like the owner of that repo isn't maintaining it. Would probably be best if you provided it yourselves, assuming that's something you can take on naturally. |
That's fine. I forced myself and finally installed in a docker! |
I am not sure if this has done it, but I simply updated config.json and Dockerfile from jakowenko's repo to point to v1.2.0, and it seems it's working. The main reason I wanted to move away from v1.1.0 was the huge amount of memory the addon was using, apparently due to memory leaks in that version. However, with v1.2.0, I am seeing an even higher memory usage at a constant 4GB. Before, it was around 2.7GB. @pospielov do you mind sharing some insight in this regard? Is this amount of memory usage normal, or is the way I am creating v1.2.0 of the addon wrong? |
There was this advise when 1.1.0 came out. I'm using it on a GTX1650 with only 4GB VRAM I'm running this on Unraid using docker compose with the following:
I haven't tried updating any of the individual modules to 1.2.0 yet. Also it looks like that addon uses a single container version. So I'm not sure how you would split it like compose. Edit: |
Thanks. There is no .env file for the addon. I am not sure where to put those configs. I am running Home Assistant on an Intel NUC with an integrated GPU. I also have a Google Coral attached, but I don't think CompreFace supports it. |
Any chance for 1.2 as home assistant Addon? Currently on 1.1 since last year....
The text was updated successfully, but these errors were encountered: