TO ALL USERS/TESTERS OF THE EDGE ONVIF DRIVER:
A change by SmartThings has broken the motion event on/off switch in the driver. Some of you may have not noticed yet, but you may now have a broken cloud icon in place of the switch, or the switch may not be behaving correctly. Even if you don’t usually touch that switch, its on/off value is no longer working as before no matter what state you left it in. So if your driver restarts for whatever reason, your motion event subscription may not get restarted. If you have found that your motion events mysteriously stopped working, this is probably why.
To fix this, I have to release a NEW driver (existing devices can’t be fixed), and you will have to re-discover and re-configure your camera devices with this new driver.
On the other hand, if you are lucky, and things seems to still be working OK for you, then no immediate action is required, however I would recommend that at some point when it’s convenient, to go ahead and transition to the new driver, since all future updates will be made to that version.
I’ve made a couple other improvements to this driver to address some issues found. For example: there are typically two video configuration profiles returned by most cameras: one for mainstream, and a second one for substream. However if a camera returns more than two video profiles, then code has been added to scan them all to find a low resolution profile to use for substream.
These are the recommended steps for when you are ready to move to the new driver:
- Take note of the device configuration settings you have set for each of your cameras, as well as routines you’ve created
- Delete all of your camera devices (excluding any virtual camera devices you had in camera groups)
- Uninstall the driver from your hub (use my test channel link or CLI)
- Install the new driver from the same test channel: ONVIF Video Camera V1.1, version 2022-07-05T18:39:13.098340457)
- In mobile device: Add device / Scan for nearby devices
- Reconfigure each of your discovered cameras and recreate your routines
The new driver will not discover your cameras unless you have deleted your current camera devices and removed the former driver, so it’s important you follow the sequence above.
Believe me, I know what a pain this is, but I did warn in the beginning that this could happen - not only as this driver was being developed, but as long as Edge is still in beta.
I appreciate everyone’s patience!
MANUAL Camera Device Discovery Option
If you are having problems getting an ONVIF camera found during the discovery process, there is an alternative way to get your camera device created in SmartThings using my manual ONVIF device creator. This is a separate driver and is available on the same test channel as ONVIF Manual Device Creator V1.1. Instructions for use are as follows:
Once this manual creation driver has been installed to your hub , do a Scan for nearby devices and you should find a new device called Manual ONVIF Cam Discovery V1.1 in your ‘No room assigned’ room.
Open the new device and enter an IP address of your camera (NOT one already running under the main ONVIF driver) and then tap the Create new device button. If all goes well, the Status field should go from ‘Responding’ then to ‘Transfer to ONVIF Driver’, and a new device should be created. If you get a ‘Not responding’ message, then the camera is not answering at the given IP address.
Do not try to update any device Settings at this point (such as userid and password).
Make sure you have the updated version of the main ONVIF V1.1 driver (version ** 2022-07-05T18:39:13.098340457**) before you do the next step.
Now you can transfer your manually-created camera device over to the ONVIF Video Camera V1.1 driver. Note: Sometimes it might take a minute or so for the Driver option to appear on the device menu since it’s a brand new device, so if it’s not there, just wait a bit and it should eventually appear. Then go ahead and transfer it.
At this point, you can now set your user and password in Settings, tap Refresh to initialize, and the camera device should now be operating normally.