-
Notifications
You must be signed in to change notification settings - Fork 90
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
Yi Dome Guard add support for PTZ RelativeMove with FOV #767
Comments
This is not just a "Space" problem.
So, probably it's a complicated task. But, if you want to try "manually", edit the file
below the </tt:RelativePanTiltTranslationSpace> line. |
I can't get it to work. I give up for now and I will try again with later betas. Thanks anyway |
I'm working on this task. |
Cool, looking forward for it. I reopened the issue because it looks like further development will happen. |
@ErliPan |
@roleoroleo Yi Dome Guard RFUS using r35gb. Some on 9.0.46.00 and a few on 12.1.47.2. |
Here it is: Let me know if it works. |
@roleoroleo I tried the new firmware but after examining through the logs it looks like that ONVIF MoveStatus is also needed. Here's the relevant log snippet. Click here
|
Another try please: |
Unfortunately it still doesn't work, looks like the camera doesn't respond as the Python code expects. Here's the log snippet Click here
and here's the Python scripts that throws the exceptions. Btw happy new year. |
I will try the script. Thanks and Happy New Year to you too. |
I tried to install Frigate as a docker container but it doesn't start properly. |
Mine doesn't load the web ui too after enabling autotracking. I don't know if you have the same issue but I will leave both docker compose and the config.yml here: Here's the docker-composeI'm using the PCIE Coral TPU and Intel QSV hardware accelleration
And here's the config.yml
I got the error log by adding the logger parameters at the end of config.yml and starting the container without the detach parameter. EDIT: I'm currently a bit busy, I need to finish deploying and configure HA + Frigate + Notifications in 2 places and I will soon look into capturing needed network traffic. |
I tested the last release with the fov script and it works.
|
@roleoroleo thanks for the heads up. I'm still unable to test it for now because I'm in another continent but by early march I should be home. I will try to report back the results asap. |
I'm back finalmente, so I took a fresh install of YiHack 0.3.1 and the latest Frigate version. Unfortunately it still crashes on boot. Here's the logs Expand
|
This log is not enough. |
I don't typically do packet captures so I'm sure it this helps but I sent the tcpdump utils binary to the camera and started capturing excluding the ssh stuff. 192.168.1.58 is the camera The http port I changed to 8080 in an attempt to see if anything changes and I didn't revert back yet. Also weird thing. The last time I tried I remember at least managing to get the Frigate PTZ control to work. This time it simply didn't load. I think I'm missing something here. One big suspect is that "http:///onvif/ptz_service" is not giving the right response. I tried opening it from my browser and I got "Empty response" same with wget. Not sure what went wrong |
I need the content of the frames. Use this command with tcpdump: Please, try 0.3.1. There are a lot of new fixes about onvif services.
This is the normal behavior. The service needs to be called with a post request and a specific content. |
So I swapped back to 0.3.1 and captured the content and here's the files: https://mega.nz/file/5klDzQbQ#dPA6VCrz3FsiDQ6HFYayjaa4yJwcoYW33xktX8BjEP8 |
GetStatus request returns "NoStatus" error.
After that, check if the system.sh contains the line In case, the second line is correct one. This is not a problem but fix it and restart. |
So that was the issue as neither of them is in the script
The error is fixed after adding the line but now there's a new error.
Maybe related to this: |
So reading that thread the user mentions a failure of running the test script. I remember being able to run that script so I tried again and it gave the same error. This is the log of Frigate when running 0.2.9
UPDATE: Moving left-right gives me this error:
UPDATE 2: So I guess there's a bug introduced in 0.3.1 Anyway this is the best I can do for now. There's something between 0.3.0 and 0.3.1 that makes the python test script fail and one of the line you mentioned is not present on |
I will try again to install frigate... |
This script https://gist.github.com/hawkeye217/152a1d4ba80760dac95d46e143d37112 runs fine on 0.2.9 and 0.3.0 fails with 0.3.1 giving the same exception as Frigate. I think you should try that. |
I already tested this script and this is the output with my 0.3.1: |
I formatted everything and reinstalled and is the output from 0.3.1 now. I'm so confused
|
Let me check if my cam is really on 0.3.1 |
So with the fresh install i'm not getting the Also my camera is currently connected via Wi-Fi, this evening I will take a ethernet cable to connect the camera and check if anything changes. |
I successfully installed frigate and configured with onvif support. |
Good news it looks like to be working. There's no more errors. I still need to figure out the
|
I'm going to close the issue for now because it looks like it's solved. Still need to figure out why sometimes it turns in the wrong direction but I think it's a config issue. Thank you for the help. Will patiently wait for the stable release. |
Frigate NVR released a new beta with support of autotracking but currently the Yi Dome Guard doesn't support "RelativeMove with FOV" but only "RelativePanTiltTranslationSpace" Script to verify the camera support. Are there any interest to add the feature?
The text was updated successfully, but these errors were encountered: