This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
Failed to connect with the camera (NVR) #302
Comments
|
I upgraded from v22 (which did work, although motion sensors do not update reliably) to v26, and I'm getting this message Logger: custom_components.reolink_dev.base Host 10.0.0.195 error renewing the Reolink subscription |
|
Thanks @MacL3an. There's a reply from @johannbrink in this thread which shows how to get the sensors working via the rest integration (edit configuration.yaml) I tried it on my NVR, which uses the latest 130 firmware, and it works really well! Would be great if the integration could do the same. |
|
@markaggar, fantastic it worked! thanks! When this integration works, does it give any more functionality or does it just automate this setup? Then a question from a HASS beginner: How do I create an automation when a motion is triggered? I assume I use the
|
|
@MacL3an You can literally write "on" (without the quotes) in the to: field. Has to be lower case. The integration (when it works) does let you control various states such as IR mode, push notifications and recording. For me I'm mostly concerned about motion though. I now have smart motion detectors all around the house! |
|
I just figured it out myself by setting the logging level at But thanks for taking the time to write. Since it is a 'binary' sensor I guess on/off makes sense :). States such as IR mode and push can be controlled via the reolink app, so I guess I'm not loosing any functionality then. Thanks again for your help! |
|
You can also go to the developer tools section and see what the current state is for entities. |
|
@MacL3an Can you please enable debug logs and provide them back? logger:
logs:
custom_components.reolink_dev: debug
custom_components.reolink_dev.base.data: warning
reolink: debug
|
|
btw @MacL3an what did you input the boxes? It feels like you didnt "http://HOST" instead of just "HOST" |
When I used the url When I try only |
|
I got it to work! I followed the suggestion I got here and setup the |
|
Yeah, seems I spoke to soon as I now have trouble with unable to renew subscription. I was now able to add the camera and it detects things like person/vehicle detection, but has trouble connecting to these sensors. The UI looks like this: And the logs say: |
|
I am having a similar problem except that it seems like I can see the sensors, but not the camera stream. I get an error opening the stream but I can see the thumbnail image of the camera feed in lovelace. My logs have this: and then when I try to stream: |
|
@MacL3an it clearly states it cannot connect to 10.0.1.15 on port 8000 at the time, did you check that port was open on your camera around the same time (this is used by ONVIF protocol) |
|
All I know is that in the reolink app the port for ONVIF is set to 8000 (the default) in the NVR: I'm not sure if there is any other setting I can play around with or something else I can investigate? I should not need to do any port forwarding/opening on my router, right? |
|
you should try an external RTMP client to check it is working, or use netcat/telnet to check that you are getting a TCP connect |
|
On the NVR, make sure ONVIF is turned on. |
|
I feel like an idiot here, but I cannot find this setting in the Mac or iOS Reolink app. I can set the port, but not enable ONVIF. The only relevant screen is the one I showed above where I can enable UPNP (which I have not enabled). As I wrote in the first post, I have managed to connect HASS to the camera via rtsp via the following config, which works ok: or polling for motion via standard http: |
|
Onvif and Rtsp are 2 different service. Onvif seems to be disabled on yours |
|
@MacL3an - the screen shot I provided is from the monitor that is plugged into the NVR. I can't find this option in the PC or Android app, just the NVR. |
|
I also did this same thing yesterday, I made the changes to the NVR to enable Onvif Protocol, then restarted the NVR Then in HA I already had the cameras added from a previous version v22. I had to remove them all after installing v26, then added each channel using my NVR ip address back in. If I didn't remove them and add them back in the upgrade also didn't work properly, all the motion just showed unavailable. Once I did that the separate motion sensors appeared as devices and are now working
|
|
I finally got it working! I e-mailed Reolink and asked about enabling ONVIF and they told me you can only do it via a screen connected directly to the NVR and also "don't worry if you don't have a monitor, Onvif is enabled by default". However, since I could not connect another ONVIF app to the camera (Security Spy) I went through the hassle of connecting a monitor and there it, of course, turned out that ONVIF was in fact disabled. By the removing the camera and adding it again everything worked like a charm. Thanks again for all the friendly support. Would you guys appreciate a PR where I update the docs to mention things that make sure ONVIF is enabled (not enabled by default and needs a monitor) and that the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I cannot connect to my Reolink NVR.
To Reproduce
I have installed version 2.6 using HACS.
I go Configuration, Integration, Add Integration, Find
Reolink IP Cameraand fill in the IP address of the NVR and use port 80. I get the errorFailed to connect with the camera.The error logs say:
Screenshots
Environment:
Please provide useful information about your environment, like:
Additional context
If I connect directly to the camera via HASS config it works:
The text was updated successfully, but these errors were encountered: