-
Notifications
You must be signed in to change notification settings - Fork 5
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
Ignoring *.json because it has no messageType #27
Comments
Those first errors are completely normal. As for the failure to connect, does your camera have a different username/password for the RTSP stream and the admin interface? I've encountered cameras that do. |
I have a chinese brand camera that by default is to be connected with this app: https://play.google.com/store/apps/details?id=com.yoosee (which requires some account and allows the camera to be controlled via the Internet, not just LAN, so I don't trust it too much) |
Yeah, it's really hard to tell. None of these cameras perform quite the same, unfortunately. The ONVIF spec leaves a lot to be desired. I've successfully tested 2 cameras, but have definitely had issues with others. It's hard to tell why your camera is misbehaving at the network level. |
Hello,
I am not being able to set up my camera after setting its user/pw (that work for the rtsp stream).
The camera was auto-detected and apart from user/pw all was auto filled.
I'm afraid the issue might start on
I'm using a Raspberry Pi B+ as the host system.
Here are the relevant logs:
The text was updated successfully, but these errors were encountered: