-
Notifications
You must be signed in to change notification settings - Fork 9
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
can't login on config page #21
Comments
You may want to test if you can connect with the xmeye app to confirm the protocol is open and the username and pass are ok. |
yes, i know, they are working fine ... |
I think in icsee you can't add manually without reconfiguring the camera. Alternatively, you can check if the video stream works on go2rtc |
well, not sure, where to post for now ... maybe you want to publish it ... i will explain: how i did it: 2.) on my hass server, if an moton detection with "start" comes into .. then i update the entity .... the rest .... can be done in home assistant to handle this entities on automation ... thats it and working great ... if anyone is interrested to get the code and infos ... let me know ... basically - most of the parts were found on project: "sofiactl" (which is doing "alarm event 2 mqqt" .... but not sure, if that was on github ... cu camel |
Hello,
installed the current version and then i tried to add, but if i enter the
name
host ip
user
password
and then press enter to add, then it conly comes "Failed to connect", and in the logs (set to debug), is nothing visible ...
any ideas ?
having cameras whicha re working fine with icsee or xmeye or xmeye for pc, and supporting ONVIF, RTSP, IPC;
cameras are most of them SV3C (xmeye compatible for sure)
is it not needed to give the port ?
are the icsee working via http on 80 or onvif 8080 port ?
or any hints ?
or is it possible toa d dthe cameras manually ?
funny, theoretical was possible to add my NVR on port 34567, and loaded a lot of functions, but also showing that the integration was not sucessfully loaded ...
any idea are welcome
cu camel
The text was updated successfully, but these errors were encountered: