-
Notifications
You must be signed in to change notification settings - Fork 44
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
Auto Discovery and Camera Login #102
Comments
Thank you for reaching out with this finding. It would appear that Dahua may have updated the camera software to improve compliance with the ONVIF login algorithm. This in turn may have triggered a bug in onvif-gui when manually adding a camera. I believe the issue has been resolved and a new version of the program (2.2.9) is available. If you installed via pip, the command to update the program is
|
If you are not able to log into the Dahua camera, please let me know. |
Thank you for your reply and update. It logins fine now after adding manually. However, the camera won't start. Gives this output:
Aspect ratio setting is indeed set to "UNKN" and won't allow changing it. Interesting. |
Indeed an interesting result that could indicate different failure scenarios that may be in play. One possibility is that the authentication has actually failed, but this is not showing up in an error message. The reason I lean towards this possibility is that the first operation upon successful login is to poll the camera for configuration data. This operation will populate the Media, Image and Network tabs at the bottom of the camera panel. If these tabs are empty when the camera is highlighted in the list by clicking on it, that would be a piece of evidence in support of this theory. The message of aspect ratio 0.0 might result from the lack of resolution data from the camera which should have been returned from the poll. There are some gotchas when working with Dahua that might contribute to this condition. The ONVIF interface is not enabled by default. If you are able to log onto the camera using the camera interface in a WEB BROWSER, there are some settings that are required for ONVIF login. At the top right of the interface should be a Setup Tab. For the camera that I have, there is then a selection on the left panel for Network->Port and then a secondary Tab ONVIF with a radio button Authentication On/Off, which needs to be On. There is also a System->Account selection with a Tab for Onvif User. There needs to be a user added to the account for Onvif to be enabled. In my case, the user name is admin and the group is admin. There is also a System->Safety selection and a tab for RTSP authentication, which for me is set to Digest. A successful login will produce a log message similar to below. The data in the second line will only appear if there has been a succesful login.
If these things are present and the Media tab is populated, there are other conditions in effect. If this is the case, some log messages may help shed light on the condition. You could try changing the profile to see if that had any effect. Best Regards and thank you so much for your patience, Stephen |
I did some further research and found a potential cause for what is happening. There is an error in a configuration used for communicating with the camera that is in the Manual Add Camera code. The error involves the device service string in the onvif command which looks like an http post. There was a missing '\r' in the post command that possibly might cause a failure to communicate. I updated the program to fix this issue, since it should corrected regardless. It's worth a try if you are game. If you installed via pip, use the command to get the new version 2.2.10
|
Discovery won't find anything. I have read through the other issues with this and understand that there are many things that might cause this.
I added camera IP manually, and it finds the camera and asks for user and password but its not accepting it, asking for user and password over and over again. ONVIF user and password is 100% correct.
Its a Dahua IP camera.
The text was updated successfully, but these errors were encountered: