Skip to content
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

Connect call failed (again...) #134061

Open
MacL3an opened this issue Dec 26, 2024 · 2 comments
Open

Connect call failed (again...) #134061

MacL3an opened this issue Dec 26, 2024 · 2 comments
Assignees

Comments

@MacL3an
Copy link

MacL3an commented Dec 26, 2024

The problem

The Reolink integration has been working very intermittently for me for several years and after being broken for a couple of months I sat down tonight to update everything to the latest version, but I still can't get it to work.

Here is my setup:
Reolink RLN8-410 (N2MB02) running firmware v3.4.0.293_24010832
Home Assistant upgraded to latest HassOS and Core (core-2024.12.5)

Home Assistant automatically finds my NVR and suggest I add it, but when doing so I get the error "Connect Call Failed":
image

I have tried all the troubleshooting tips and read through all the open and closed issues I could find, which includes:

  1. Disabling and enabling all ports (HTTPs, RTMP, RTSP, ONVIF)
  2. Verifying that if I copy the IP found by Home Assistant into a browser, I can connect and see all the cameras
  3. Adding a new user
  4. Setting a simple password
  5. Setting a static for the Reolink NVR

Does anyone have any suggestions of what I can try?

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

reolink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/reolink

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @starkillerOG, mind taking a look at this issue as it has been labeled with an integration (reolink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of reolink can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign reolink Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


reolink documentation
reolink source
(message by IssueLinks)

@Usti2000
Copy link

Puh….
Hard to determine from remote.
What i can see :
Use of a private class a ip range at home might cause trouble, i use private class c since several years.

second : my cams connect to port 443 by default, not 80, maybe try this if you hav´nt already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants