Well, that’s a strange one then. It sounds like your RLC-823A is wired directly to your NVR and not available on the network, but if you say it’s not then I believe you!
Could you run an experiment and have the NVR forget the 823A so that it’s not managing it. Reset the camera (or power off and on), then try to discover it with the SmartThings app. This would rule out the NVR connection having anything to do with it.
How about firmware? Is it updated to the latest?
I agree it does sound like RLC-823A is wired directly to NVR, but I definitely have it plugged into the POE switch with nothing connected to the back of the NVR.
I checked all three cameras and they are on the latest firmware.
I turned off the NVR and rebooted each of the cameras. I rebooted the Smartthings hub and I also deleted the two E1 Pro cameras and NVR that the edge driver discovered from the Smartthings app. I then scanned for new devices and this time the edge driver only discovered the two E1 Pro cameras and not the NVR since it was turned off. So with the NVR out of the picture, the RLC-823A was still not discovered, but I do see it in the Reolink app and it works as expected. I turned the NVR back on and did another scan, and the Edge driver discovered it again so now I am back to where I started with the edge driver having added the two E1 Pro and NVR to the Smartthings app.
Not sure where we go from here, but appreciate your help in trying to resolve.
Well thanks for doing all that!
I saw this on a quick internet search of this model and ONVIF:
I just wanted to drop a line and say that I just got a Reolink RLC-823A in. It’s working great with SecuritySpy using the latest firmware (v3.1.0.956_22041511_v1.0.0.30). After upgrading it, I had to go turn ONVIF on in the camera settings. After that, everything works.
Interesting that he mentions turning ONVIF on in the camera settings. Any chance you missed something?
Well thanks for finding this! I am actually on a more recent firmware version. So I have been using the Reolink app on my phone to look for the ONVIF setting and went through it several more times with no success. I started Google searching to see if someone, and even the Reolink site, might tell me where to find this setting. Then it hit me, I downloaded the Reolink client for Win 10 to see what settings it showed and to also get a bigger screen that I did not have to keep scrolling up and down. I found an RTSP setting that was turned off and when I turned it on it revealed the ONVIF on/off switch. Your edge driver immediately discovered the RLC-823A and I have configured it for motion and changed my routine out from IFTTT. Works as advertised. Motion during the day tells Alexa to announce there is motion at my front door and at night if the person keeps coming up my sidewalk within range of my ring doorbell, in addition to the Reolink spot light, my outside front porch light and inside entry light also comes on. Love it when a plan comes together!
Thanks for all you have been doing for the Smartthings community in their new platform space and for taking the time to work through my problem with me!
Don
PS: I saw you have Hill County in your profile. I am a Texan and just got back a few weeks ago from attending our motorcycle club rally held in Kerrville every fall. Beautiful area and great motorcycle roads all through the Hill Country.
Awesome! I need to add a note to the documentation to be sure to use the windows client to check for configuration. I’ve heard that from others before and neglected to ask if you were using it.
I wanted to share the following information. The RLC-823A has three motion types for vehicle, person, and pet (beta). I have mine configured to only report motion for a person within my detection zone and then the camera will auto track that person. I am using your edge driver to have Alexa announce when there is motion at my front door, which she does perfectly in sync with the camera pushing a notification to my phone and the NVR recording that motion. However, after switching over to your driver from IFTTT, Alexa started reporting extra notifications. During these announcements I was not getting a push notification from the camera and the NVR was not capturing a motion event. Finally this morning Alexa announced motion (no push to my phone) when I was able to run to the front door to see if I could find out what was causing it. There was a person walking their dog on the sidewalk just outside my detection zone. So as best as I can tell, it looks like for my Reolink camera, the driver is capturing all motion the camera sees and is not using the camera motion filters I have in place? Changing between the type S and T profiles and main/sub streams does not make a difference. Now that I know what is going on, I can get the driver to report unwanted motion by walking on the sidewalk just outside of my detection zone.
Is this something you can address in a future release, or is it due to the way Reolink has decided to implement their version of ONVIF?
Every camera brand is different in regards to motion detection features and how/if they expose those through their ONVIF interface. I’m happy to work with you to see if there’s anything I can do to address this. You’ll need to get the CLI installed and run logs so I can see exactly what events your camera is sending. As an alternative, you could install the ONVIF Device Manager, which is a free-ware Windows application that may also be able to show us the same thing.
Direct message me if you want to pursue either path.