@TAustin 4 event log emailed to you. I hope this gets this to the finishline for Reolink AI cameras.
*Update…I found the problem and am still sorting 1 camera out. I would still like for the logs to be useful, for further development and possible refinement.
Well, Done!
Reolink rlc-822a and rlc-820a
(E1Pro included as functioning camera)
Thanks to @TAustin they are working now with this.
After scanning nearby and inputting user/pass the cameras where “responding,” however once motion was toggled on it would get stuck and end up with server/network error.
After a few attempts of refresh with each camera (4 total on this install) and having network errors. I closed the app for few minutes and after a reattempt on each camera individually. I was closing app after network errors and refreshes (essentially giving ST and Driver a break.) Two of the cameras installed and subscribed to events successfully with just closing/reopening app.
*DISCLAIMER:Read Reolink Cams with Smart AI Detection
If you think your cameras are set perfect for the use case, you are using them for (myself included). These settings are probably not going to work. I would highly suggest putting the cameras at a really high sensitivity (High), including all smart detection (High), beta pet detection (OFF), and minimum/maximum size detection (Remove).
If you have delays built into your detections, be aware that if you have motion detection ON in ST the cameras still follow the same rules in Reolink, so adjust ST detection times and auto-reverts to mimic.
I would also suggest if they’re inside your home tie a quick automation turning a light On, with 5 second auto Off, to adjust individual cameras back to useable motion levels.
*Do this when no one else is moving around or home.
If you have motion detection zones in Reolink they are the same in ST, again adjust accordingly.
To sum this up at the time of this writing "Dumb your smart cameras down and turn all extra features off. Then reverse engineer them back to acceptable settings for your needs.
*Suggestion
Don’t install if you don’t have time planned out because even a minor change in Reolink upsets the motion detection in ST.
Huge Hats Off to @TAustin
Hi, thank you for your work. I have dahua ip camera (Model: HDW4231EMP-AS-S4). my camera supports onvif. I added this driver, searched for new devices. Added both of my onvif webcams almost instantly.Configured user/pass and hit refresh. Updated info appeared an i was able to not enable motion detect. They are not showing video.
can you help me?
not working
@TAustin
Do you have any control over the font size in the info panel ? If possible can it be increased, my poor old eyes struggle to read it at present
Hi there - and welcome to the community! I think it was you that sent me the email with the additional information, so I will study that and get back to you.
It can be increased, and I have tried that, but unfortunately it messes up the formatting of the table. I know it’s very small! The reason for that font size is to keep the text for each record in one line. But I will experiment some more to see what I can do.
Yes, it is me. Thank you
Wanted to let you all know that I just got a firmware update to my hub today and it seems to have killed the ONVIF driver (and other LAN drivers). In other words, it did not restart successfully when the hub reloaded all my drivers. Symptoms are that no video will stream and no motion events are being processed, and you may see only the initial discovery line items in the info table (IP address thru URN)
Hitting refresh does not work as all LAN communication attempts result in immediate socket timeouts. It seems something has changed in the underlying platform that is causing this and if anyone gets this firmware update (Version 000.043.00003), you will likely experience the same issues. I’m going to have to report this to SmartThings and see if there is a recommended workaround.
Stay tuned…
Is your hub fw beta Tod or St official rollout ?
Not seen any update announcements ?
You know, I’m not even sure anymore. I was on the Edge Alpha a year ago and since then I seem to get firmware updates prior to most others. Hopefully they will hold off any further distribution of this until this problem is fixed. This is breaking several of my drivers.
Normaly… there is an announcement, i have seen nothing but then i cant see large parts of the forum, i think the web dev guys are on holiday
And disappointingly Nayalez reports ST unwilling to help with expediting a fix for the camera stream issues, which stops some of biggest camera companies creating there own offical integrations with Lan
So much for fully supporting LAN… very annoying
@TAustin Wow! Thats rough, hopefully it doesn’t turn into a complete nightmare for you. Atleast we know to be on the lookout if some of the other drivers go down also.
Quick update - the problem with the new firmware is solved. It’s good that I got this update early, so I could catch the problem before it affected everyone else.
So the next driver update I push (probably later today) will contain the fix. 
I wish they would fix the forum as quick as you fix driver issues Tod
Hikvision DS-2CD2347G2-LU
Firmware V 5.7.2
Video streaming - confirmed
Audio streaming - confirmed
Motion detecting - tba
I know you all must be awfully bored not having a new driver update to cause you headaches, so I’m about to change that…
New driver version has been pushed out: 2022-05-14T01:45:17.37677
This has some important changes:
fixes the problem I mentioned earlier regarding the new hub firmware (however most don’t even have the new firmware yet, anyway)
pretty substantial change in motion event setup: Now that I’ve seen the variations in the way various cameras might be configured for motion detection, I wanted to provide a bit more flexibility to accommodate different scenarios. To that end, there is now a new device Settings option that allows you to choose between two different motion alert rules:
– CellMotionDetection: this is the rule that the driver has been using as it is the most common motion detection method available across cameras, and supported by cameras with both Profile S (Streaming) and Profile T. If your motion events are working now, this is the method being used.
– MotionAlarm: this event should be available on all cameras supporting Profile T; it typically is not available on cameras supporting only Profile S. I have added the option to use this as an alternative because I’ve learned that not all cameras might have the CellMotionDetection rule available. MotionAlarm is part of a more sophisticated suite of event rules available with Profile T cameras, that might allow things like field or line detectors, people/pet/car detection and other options. Some camera software seems to have some pretty extensive ability to build custom rules as well. I am still figuring out exact behavior, but what I believe is that a MotionAlarm event will be generated any time there is a state change for ANY-motion related rule (people/pet/custom/etc.), so I think it could work well for the purposes of this driver where Profile T is available and you don’t want to undo your current custom rules just to get the camera to integrate with SmartThings.
You may or may not see the new Setting (‘Motion Rule Selection’) in your existing devices once the driver has been updated on your hub. It showed up for me in my existing devices (I’m on iOS), so hopefully it will dynamically update for everyone. If not, you may need to delete your camera devices and re-discover to see/use it.
This update is one of those that may very well break things, since it has some pretty extensive changes in the way it initializes and uses motion events. Unfortunately I don’t have a Profile T camera, so could not test much of the new logic. If after the driver update, everything continues to work for you and you don’t want to mess around with it, that’s great. You really don’t have to take any further action; CellMotionDetector is the default and if it was working for you before, hopefully it will continue to do so. And you never need to touch the new device Setting.
For the more adventurous - and especially those with Profile T devices (@fido, @K_White I’m looking at you ), I’d love for you to try switching to the MotionAlarm motion rule and seeing if it works. REMEMBER TO HIT REFRESH AFTER CHANGING IT IN SETTINGS. And as always, when things go wrong, logs of Refresh, enabling Motion events, and actual motion events will be much appreciated!
@TAustin Of course, I’m going to hit that settings change button…why wouldn’t I. Don’t tell me you got a new toy for me to play with and not touch it. JK
I updated it in the cli, so just changed to Motion Alarm and refreshed. Found that it made it quicker for the setting to update to “subscribed to events” by closing the app after refreshing instead staring at it waiting to see if it happened.
I don’t know if it was the update but now I can see my Foscam R2 live! I’m going to test the motion alert soon.
I’m looking for anyone besides @Sakari that has a TP-Link camera - model C100 would be ideal, but not mandatory. We’re having some difficulty getting events to work and it would be good to see if this is camera specific, or a problem in general with TP-Link.