-
-
Notifications
You must be signed in to change notification settings - Fork 68
HA Entity state not updating #45
Comments
I'm running HASS Deepstack face on docker on windows PC and I have the same problem. |
You have installed deepstack version 1.0, which means you have it installed
on raspberry. I personally encountered this when I tried to install it on
a raspberry. Deepstack has dropped support for raspberry. You need to
install the latest version, and this is version 2 and it is already
activated
Вы установили deepstack версии 1.0, а значит у вас это установлено на
raspberry. Сам лично сталкивался с этим, когда пытался установить на
raspberry. Deepstack прекратил поддержку для raspberry. Нужно ставить
последнюю версию, а это версия 2 и она уже активированная
пн, 17 мая 2021 г., 9:01 Andrius ***@***.***>:
… Also when I start deepstack it says "visit local host to activate
Deepstack". Maybe it needs some kind of activation to work? Unfortunately
cant find any info on activation.. If I enter random key it says "Can't
reach activation server".
[image: Screenshot 2021-05-17 at 08 57 11]
<https://user-images.githubusercontent.com/54658863/118439285-55a0b800-b6ee-11eb-859f-dbd5ba2e6195.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/API7ECFJQSQOWZQ3MLGTO7TTOCWLPANCNFSM446GSVWA>
.
|
Hi, Thanks for info. Is version 2 even available for PI? |
Unfortunately for raspberry, images are no longer made. At the moment
there is only this deepstack v 1.0 image that requires activation. You can
install deepstack v 2 on windows, linux, docker
К сожалению для raspberry больше не
делают образы. На данный момент есть только этот образ deepstack v 1.0
который требует активации. Вы можете установить deepstack v 2 на windows,
linux, docker
пн, 17 мая 2021 г., 10:08 Andrius ***@***.***>:
… You have installed deepstack version 1.0, which means you have it
installed on raspberry. I personally encountered this when I tried to
install it on a raspberry. Deepstack has dropped support for raspberry. You
need to install the latest version, and this is version 2 and it is already
activated Вы установили deepstack версии 1.0, а значит у вас это
установлено на raspberry. Сам лично сталкивался с этим, когда пытался
установить на raspberry. Deepstack прекратил поддержку для raspberry. Нужно
ставить последнюю версию, а это версия 2 и она уже активированная пн, 17
мая 2021 г., 9:01 Andrius *@*.***>:
… <#m_-8814452699590874688_>
Hi, Thanks for info. Is version 2 even available for PI?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/API7ECFJ2I2TMYCKDEV6LCDTOC6GDANCNFSM446GSVWA>
.
|
I am running docker on same rpi4. Also tried installing deepstack docker container, but there was some issues running it.. Only this method with image was working. Maybe need to check it again. For installation I used this script:
|
I was unable to run docker on the PI. I have successfully launched only on synology and on vmware with Hass OS with portainer integration Read on the forum deepstack The answer of the author himself is that pi will no longer be supported and they go completely to docker |
Is this still an issue on latest deepstack image? |
stale closing |
Hi, I am trying to run deepstack face recognition on my HA.
HASS is running on rpi4, and deepstack is running on another rpi4. Issue what I am facing at the moment is that I dont get any recognition update on entity inside HA. State of this entity always stays Unknown. However if I check deepstack on another rpi4 I can see my recognition request from HA, so not sure what is wrong. Are there any log files on HA or on deepstack side?
So ether recognition is not accuring or recognition result is not geting back to HA.
I am also running frigate container together with deepstack on same rpi4, not sure if it can have some effect.
HA config:
The text was updated successfully, but these errors were encountered: