-
Notifications
You must be signed in to change notification settings - Fork 89
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
Username, Password, or Address is wrong. #145
Comments
I have the same problem. When I try to add my XVR5108HS I have the same problem. And now I can't get it to work again. File "/config/custom_components/dahua/client.py", line 657, in get When I go to https://10.11.1.180:443/cgi-bin/magicBox.cgi?action=getMachineName, I get "name=XVR". |
For me it worked after changing the source code from client.py to below (in the custom_components folder). As it appeared my cam only provided that information after authentication and this fixed it: _# self._base = "{0}://{1}:{2}".format(protocol, address, port) |
Thanks, this helps a lot. Can you try this (make sure to revert the code change)... admin:pass@192.168.1.203 |
The option : _self.base = "{0}://{1}:{2}@{3}:{4}".format(protocol, username, password, address, port) did not work for me. For me the solution looks very simple: After deleting and reinstalling the component it works. 👍 |
That was my initial attempt (adding username:passwd to the address field). The result was that my camera got initialised without errors and all but I couldn't get the streams working. Makes sense I guess since the rtsp streams already have username password in it and using this method it would duplicate that. |
I can add camera like this but like intelwolf mentioned stream is not working. |
have you tried:
|
This error originated from a custom integration. Logger: custom_components.dahua Could not connect to Dahua device. For iMou devices see #6 |
you need to verify the user/pass is correct by going to the URL it shows directly in your browser, |
User and pass is correct. When opening http://192.168.88.246/cgi-bin/magicBox.cgi?action=getMachineName it asks for user/pass and then displays camera name=2A01ED7PAA00426 |
As a critical initial step for those new to this, make sure your CGI service is enabled (System->Safety->SystemService->CGI Service). I hadn't done this and could not connect to the camera at all after trying all suggestions in this thread. When I visited this location in browser (http://192.168.1.10/cgi-bin/magicBox.cgi?action=getMachineName) I got a 404. And after trying to add the integration, I would see a 404 error in the integration logs. But after enabling CGI, I was able to successfully add the camera to HA. Tested on Dahua N43AM5Z |
After camera reset I was unable to setup camera in Integration, but while checking suggestion by @nbmi (which was Enabled, btw), I've noticed setting |
After exploring all of the suggestions provided here, I finally just reflashed home assistant and started all over. Once the Dahua integration was installed through HACS I was able to add all of my cameras with no issues. Perhaps this is an issue with Home Assistant? |
i have tried everything mentioned above , but still the same error , indicating error with name password or address , this is the log info Traceback (most recent call last): so , it seams the url fails, but if i test the URL , result is success . |
problem solved , it was port number 443 instead of 80 |
hello, i have the same issue, but i can't find this CGI setting @nbmi is talking about |
Are u using special characters in tbe password? |
no special characters, it's the default password. i also just noticed i cannot access the camera by entering the ip address into the browser |
Have u tried https://THEIP ? |
Did now, still no spark :( |
Version of the custom_component
Configuration
Add your logs here.
Describe the bug
While adding camera to HA i'm getting this error: "Username, Password, or Address is wrong."
Using default username admin/admin
Are these cameras supported?
IPC-HFW1320S
IPC-HFW1300S
IPC-HFW2320R-ZS
Debug log
The text was updated successfully, but these errors were encountered: