As @K_White had pointed out, if you camera is hardwired directly to the NVR, then it’s not available or visible on your home network so it won’t be available to this driver.
Camera groups require at least 2 cameras, so you are going to have to install my virtual camera driver (available from same channel) so you can add a second ‘dummy’ camera to successfully create a camera group. See this post for more information.
Once you have at least two camera devices, tap the big ‘+’ in the upper right corner of the main screen in your mobile app. Besides the option to add a new device, there are also 2 other options, and one of them is to create a camera group. You’ll give it a name, what room to put it in, and then select the cameras you want to add to it. Choose your camera device and the virtual camera device.
@TAustin I’m not sure the dummy camera will work for what I’m saying below. My knowledge on using a Reolink Kit with ONVIF Device Manager is zero, but it would most likely be just utilizing the NVR IP address and the user sees the available channels…not sure on this. You need more info from him on that.
I asked @gmanor77 if it was a kit for a very specific reason and he didn’t reply. Reolink “Kits” come with multiple of the “same” model # cameras. These cameras will not connect to the router/network (only NVR) they cannot be run standalone because they are hardcoded to the NVR which provides them a subnet IP address from the NVR and if I remember correctly they don’t have UUID’s.
Correct me if I’m wrong here @TAustin and @fido
Thats exactly what i would expect, the nvr creates its own subnet for the cams, standard fare really so Tods driver will not expose the cameras connected to the NVR as it cannot see them, only the IP address of the NVR
Not sure if there is a way to see an NVR subnet its not something i have given much thought too or tested, however if the cameras have an onvif option something might be do able but Tod is the whizz and he will know for definate
Here he is saying that he DOES have another IP camera that is available on his network and was found by my driver. So I thought he was asking how he would get that one up and running in a camera group. And that’s why I pointed out the need for the virtual camera so that he would have at least 2 to add to the group.
I wasn’t implying that the other camera directly connected to his NVR could be solved in any way.
@TAustin Yes, I knew what you were implying, but I didn’t want @gmanor77 to think the dummy camera would magically discover the other (NVR connected) cameras, but yes it will allow the creation of the camera group for the network connected camera.
Apologies if I made that sound a different way then how I meant.
The cameras that are supplied with the NVR have no idependant UI or control ?
Im not familiar with them at all,
Is there any literature on them and there specs
Just taken a quick look at the Reolink website, from my brief scout through, the cameras do appear to have a web browser available UI and a network option, the screenshot i have seen does not show what options are available in the network section though
If this screenshot is the same as the option in the Reolink 520 then yes it will work with Tods driver, there appears to be an onvif option
@fido yeah, thats why I had said zero knowledge with the ONVIF for that setup, but since we havent heard back not sure.
I did some looking earlier too, but what I think maybe the case is the nvr assigns IP addresses to the cameras (not sure on this) in a subnet then they are viewed by channels that you assign them too.
My setup is I can view either way, I can view with IP Addresses on my network or go to my nvr and view cameras according to the assigned channels I’ve given them. The later is similar to a kit setup, but cameras I dont believe have a UID in the kit case.
Hi @TAustin, first of all thanks you!
I have 2 camera Vstarcam C24S, Smartthings recognise it immediatly but the status is always “Not repsonding”.
The camera works with onvif
I send to you my log by email, it’s seams that the problem is “2022-05-20T19:43:09.073552949+00:00 ERROR ONVIF Video Camera V1 Failed to get date/time from http://192.168.1.11:10080/onvif/device_service (IPCam #2 (configure!))”
Indeed, the date/time request is failing because the camera is expecting authentication. This isn’t supposed to be required for this request according to the specification, but as I’m learning the hard way, many manufacturers seem to want to do their own thing!
This can be addressed with some simple code changes I’ll need to make. I should have an update for you sometime this weekend.
OK, Thanks for reporting. Do you know if they are supposed to be ONVIF compliant?
Because there have been a couple cases where the auto discovery is not finding some cameras that definitely ARE supposed to be ONVIF compliant, I am soon going to have available a way to try and create them manually by their IP address, so stay tuned…
Sorry, the driver does not support that at the moment. It could probably support triggering recording in a future update, but there is no capability in SmartThings to view it (only live video) or send it.
The driver as it currently exists supports only live streaming and motion alerts.
Hi - I believe I have the solution to your date/time request fail problem. I’m working on a couple other issues that I want to get sorted before I push out the new driver to everyone, but I should have it out in the next day or two.
