[ST Edge] ONVIF-compliant IP Camera Motion Detection & Video Streaming - Testers Wanted!

Oh, I didn’t realize that there more steps. There is only one cam, so I guess I need the instructions for setting up a virtual camera device. Is there a guide somewhere, already written up on how to do this?

Edit: Nevermind, I found the vEdge Creator thread and followed your instructions. I’ve created a vEdge Videocam dummy but the ST (v1.7.94.21) app doesn’t give me an option to ‘Add camera group’.

Others have reported that their add camera group option has disappeared. I’m not sure what is going on - it appears to be some kind of app issue. For some it randomly reappears again, so keep your multiple camera devices and see if it eventually shows up.

Ah, too bad. OK, I’ll leave it alone for a while and hopefully the option will appear. Thanks.

Just installed the edge drivers and discovered my Reolink cameras. I have these models - E1 Outdoor, RLC-810A, RLC-811A, RLC-823A, and TrackMix PoE. In total I have 9 camera’s. The only camera that was not detected after installing the v1.3 ONVIF driver was the RLC-811A. I ran the scan routine numerous times for it to detect the other 8. Not being able to have the RLC-811A auto detect I went ahead and installed the OVNIF manual driver. Once installed the scan detected the Manual ONVIF driver. Then without putting in the fixed IP address for the RLC-811A, I went ahead and had Smartthings scan for a device. This time it found the RLC-811A and I was able to enter the User/Password and set up the camera. I found this a little odd.

All of the cameras are now setup and I can see the video feeds in camera groups. What I have not been able to do is get motion to work. All of the Reolink camreas are of profile type T, so I set the motion rule to - RuleEngine/CellMontionDetector. I have had these cameras for about 1 year and with the Reolink software they detect motion and record events without issue. The only way I was able to get Smartthings to register motion was if I turned on Events while motion was being detected by the camera. However, when I did this the camera would never go back to no-motion. Thus, the edge driver seems to be detection the state of motion when Events is turned on, but it I can’t seem to get it to update the state of motion.

Attached is a screen shot of one of the camera’s settings.

Hi there - For motion, what exactly happens when you turn the Events switch on? Does is stay on and status field says ‘Subscribed to events’, or does it just revert back to off?

RuleEngine/CellMotionDetector usually works for Reolink cameras, so that’s unusual it doesn’t work. Have you tried the other option: VideoSource/MotionAlarm?

Can you install the SmartThings CLI so we can get some logs of what is happening?

Starting with Events off, status is “Unsubcribed to events.” Then when I turn Events On, it stays on, turns blue, and the status shows “Subscribed to events” for about 10 seconds and then Status goes to Responding, and stays that way. I have tried both RuleEngine/CellMotionDectector and VideoSource/MotionAlarm to the same thing as described above happens.

Here is the log
“”“connecting… connected
2023-02-11T22:08:12.185043128+00:00 TRACE ONVIF Video Camera V1.3 Received event with handler discovery
2023-02-11T22:08:12.213181378+00:00 DEBUG ONVIF Video Camera V1.3 Discovery handler invoked
2023-02-11T22:08:12.219018878+00:00 INFO ONVIF Video Camera V1.3 Starting Discovery cycle #1
2023-02-11T22:08:12.409615253+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.42
2023-02-11T22:08:12.411588545+00:00 DEBUG ONVIF Video Camera V1.3 ProbeMatch table: 0x23e1bf0
2023-02-11T22:08:12.414136336+00:00 DEBUG ONVIF Video Camera V1.3 Scopes onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/location/country/china onvif://www.onvif.org/type/network_video_transmitter onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/Profile/T onvif://www.onvif.org/name/IPC-BO onvif://www.onvif.org/hardware/RLC-823A onvif://www.onvif.org/name/IPC
2023-02-11T22:08:12.427876753+00:00 DEBUG ONVIF Video Camera V1.3 Types tds:Device tdn:NetworkVideoTransmitter
2023-02-11T22:08:12.428342086+00:00 DEBUG ONVIF Video Camera V1.3 MetadataVersion 1
2023-02-11T22:08:12.428984670+00:00 DEBUG ONVIF Video Camera V1.3 XAddrs http://192.168.1.42:8000/onvif/device_service
2023-02-11T22:08:12.429738086+00:00 DEBUG ONVIF Video Camera V1.3 EndpointReference table: 0x2293788
2023-02-11T22:08:12.430565836+00:00 DEBUG ONVIF Video Camera V1.3 Address urn:uuid:2419d68a-2dd2-21b2-a205-ec:71:db:8b:73:af
2023-02-11T22:08:12.431225420+00:00 DEBUG ONVIF Video Camera V1.3 Discovered device was already known
2023-02-11T22:08:12.443253336+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.39
2023-02-11T22:08:12.444867836+00:00 DEBUG ONVIF Video Camera V1.3 ProbeMatch table: 0x22a2850
2023-02-11T22:08:12.450691753+00:00 DEBUG ONVIF Video Camera V1.3 Scopes onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/location/country/china onvif://www.onvif.org/type/network_video_transmitter onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/Profile/T onvif://www.onvif.org/name/IPC-BO onvif://www.onvif.org/hardware/E1Outdoor onvif://www.onvif.org/name/IPC
2023-02-11T22:08:12.451467920+00:00 DEBUG ONVIF Video Camera V1.3 Types tds:Device tdn:NetworkVideoTransmitter
2023-02-11T22:08:12.452146045+00:00 DEBUG ONVIF Video Camera V1.3 MetadataVersion 1
2023-02-11T22:08:12.452779753+00:00 DEBUG ONVIF Video Camera V1.3 XAddrs http://192.168.1.39:8000/onvif/device_service
2023-02-11T22:08:12.453403503+00:00 DEBUG ONVIF Video Camera V1.3 EndpointReference table: 0x22a28c8
2023-02-11T22:08:12.454024378+00:00 DEBUG ONVIF Video Camera V1.3 Address urn:uuid:2419d68a-2dd2-21b2-a205-ec:71:db:a7:86:e1
2023-02-11T22:08:12.454642795+00:00 DEBUG ONVIF Video Camera V1.3 Discovered device was already known
2023-02-11T22:08:12.544756961+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.545312795+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:12.689495420+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.690050628+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:12.737670128+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:12.746276212+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.747392628+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.747823753+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:12.757050878+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:12.758666128+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.891364962+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.891925670+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:12.904789837+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:12.905230545+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:12.941413337+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:12.943043378+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.396698383+00:00 INFO ONVIF Video Camera V1.3 Starting Discovery cycle #2
2023-02-11T22:08:23.547865258+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.42
2023-02-11T22:08:23.557163508+00:00 DEBUG ONVIF Video Camera V1.3 ProbeMatch table: 0x2468888
2023-02-11T22:08:23.557650550+00:00 DEBUG ONVIF Video Camera V1.3 Scopes onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/location/country/china onvif://www.onvif.org/type/network_video_transmitter onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/Profile/T onvif://www.onvif.org/name/IPC-BO onvif://www.onvif.org/hardware/RLC-823A onvif://www.onvif.org/name/IPC
2023-02-11T22:08:23.558342258+00:00 DEBUG ONVIF Video Camera V1.3 Types tds:Device tdn:NetworkVideoTransmitter
2023-02-11T22:08:23.558972550+00:00 DEBUG ONVIF Video Camera V1.3 MetadataVersion 1
2023-02-11T22:08:23.559596383+00:00 DEBUG ONVIF Video Camera V1.3 XAddrs http://192.168.1.42:8000/onvif/device_service
2023-02-11T22:08:23.560502342+00:00 DEBUG ONVIF Video Camera V1.3 EndpointReference table: 0x246e058
2023-02-11T22:08:23.561179008+00:00 DEBUG ONVIF Video Camera V1.3 Address urn:uuid:2419d68a-2dd2-21b2-a205-ec:71:db:8b:73:af
2023-02-11T22:08:23.561803467+00:00 DEBUG ONVIF Video Camera V1.3 Discovered device was already known
2023-02-11T22:08:23.577185092+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.37
2023-02-11T22:08:23.578819550+00:00 DEBUG ONVIF Video Camera V1.3 ProbeMatch table: 0x23f74c0
2023-02-11T22:08:23.584485675+00:00 DEBUG ONVIF Video Camera V1.3 Scopes onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/location/country/china onvif://www.onvif.org/type/network_video_transmitter onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/Profile/T onvif://www.onvif.org/name/IPC-BO onvif://www.onvif.org/hardware/E1Outdoor onvif://www.onvif.org/name/IPC
2023-02-11T22:08:23.585269550+00:00 DEBUG ONVIF Video Camera V1.3 Types tds:Device tdn:NetworkVideoTransmitter
2023-02-11T22:08:23.586061092+00:00 DEBUG ONVIF Video Camera V1.3 MetadataVersion 1
2023-02-11T22:08:23.586692633+00:00 DEBUG ONVIF Video Camera V1.3 XAddrs http://192.168.1.37:8000/onvif/device_service
2023-02-11T22:08:23.587309717+00:00 DEBUG ONVIF Video Camera V1.3 EndpointReference table: 0x23f7538
2023-02-11T22:08:23.587930592+00:00 DEBUG ONVIF Video Camera V1.3 Address urn:uuid:2419d68a-2dd2-21b2-a205-ec:71:db:7b:3b:06
2023-02-11T22:08:23.588550800+00:00 DEBUG ONVIF Video Camera V1.3 Discovered device was already known
2023-02-11T22:08:23.601740467+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.602183717+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:23.664241425+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:23.665930300+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.714273342+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.714716008+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:23.728507258+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:23.730147467+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.816883383+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.817336383+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.31
2023-02-11T22:08:23.936377050+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:23.936929717+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:24.188808842+00:00 DEBUG ONVIF Video Camera V1.3 Discovery response from: 192.168.1.30
2023-02-11T22:08:24.190804009+00:00 WARN ONVIF Video Camera V1.3 Discovery response missing ProbMatch.Types element; ignored
2023-02-11T22:08:33.294558263+00:00 TRACE ONVIF Video Camera V1.3 Received event with handler discovery
2023-02-11T22:08:34.529779805+00:00 INFO ONVIF Video Camera V1.3 Exiting discovery
2023-02-11T22:08:34.531541722+00:00 DEBUG ONVIF Video Camera V1.3 discovery device thread event handled”“”

Let’s focus on the Motion event problem for now. Since you said you got most of your devices already discovered, can you choose one and capture a log of when you tap the refresh button and then turning ON the events switch?

Please send me the log in a direct message, and also begin and end the log text with triple back-ticks (```) to ensure readable formatting. It looks like you tried using quotes above; check to make sure you are using the single back-ticks (sometimes to the left of the ‘1’ key on a computer keyboard, or in a mobile app, you can usually select the specific quote/back-tick type.

p.s. Do you know what the devices are at 192.168.1.30 and 192.168.1.31 ? They are responding, but with an unexpected message format.

@Dennis be prepared to wait if you open a support ticket. I am also missing the camera group. I have many cameras added to the Smartthings app but can’t get the Create Camera Group option. I have tried uninstalling, clearing data. Nothing seems to solve the issue. I would be interested in knowing who got it to appear after a while and what they may have tried. Since my support case is about 1.5 months old and I am no closer to getting a resolution. I have heard nothing from the engineer and the support person keeps telling me they are still waiting for an update from the development team. I even asked if they can escalate the issue based on the age of the case. They say it is escalated. Very slow process

Thanks for sharing, that’s useful insight about the resolution progress. I have not yet opened a support ticket because I didn’t think it would yield much result; ergo, based on personal observation, ST devs tend to address problems which are based on internal priorities. However I had wondered if adding another real camera, instead of virtual, would fix it but it doesn’t seem likely from what you’ve said.

Seems to have been an update by ST on device rotation, previously rotating a device with a camera on screen failed to rotate and resize the camera image

Now device rotation successfully rotates and re sizes the on screen camera feed

Icing on the cake would be to allow LAN cameras to display stream on there own device page and subsequently to display on a capable Samsung Tv, i continue to hope

That’s a good sign!

It does show a commitment to retain camera integration and offer some fixes

FOR ANYONE WHO HAS BEEN UNABLE TO CREATE A CAMERA GROUP:

The latest version of my API Browser+ web app adds a new feature to create a camera group. So if this ability has disappeared from your SmartThings app, try using this tool so you can get your camera group created. Note that you will need at least two camera devices to create a group. If needed, you can create a virtual camera device using my vEdge driver, and include it in your group.

4 Likes

There are ST oddities still remaining when adding a camera

For whatever reason one if my cams was using test driver and not reporting movement at all, i deleted it and re added using the current driver, the camera was found and movement is now functioning perhaps a bit too well but thats for another day and probably my settings

But, the freshly added camera could not get added to an existing camera group, the camera add part of the camera group could not see the camera existed, it took about an hour before the camera became available to add to a group

Hi Tod, Tod would it be possible to disable some of the settings in a camera config, perhaps with an on off button on the device page

My cams handle all the settings such as motion timeout and revert after, i find adding your settings into the mix ontop of the cameras own settings unnessaraily complicated, perhaps even a parameter value on each setting that disables a setting, perhaps typing the word off in a value or 100

Disabling a setting in the camera driver would then leave the camera in full control

Is it something that could be added ?

Hi guys,

Someone else with this issue:

All cams is off to stream but it was responding normally.

@TAustin could you help?

In device settings:

  1. You can disable the motion auto-revert
  2. You can effectively disable the minimum motion/linecross/tamper intervals by setting those values to 0

@nayelyz - Please see @Dienzora’s post above.

I’ve just started getting this too. Looks like SmartThings may have disabled video streaming in the app. The driver is not getting any request for the streaming URL. Can you look into this please?

Hoping this is just a temporary issue… :unamused:

Thanks for the tip on setting zero values Tod

So far, i see no disruption to video streaming, region issue perhaps ?

Thanks for reporting that - maybe video streaming is down on just some servers.