I have 3 x Annke C800 IP cams (rebadged Hikvisions),
They are ONVIF enabled, and they show up in ST when I scan for new devices. When I enter the ONVIF username and password, the cams won’t connect or show video.
Just for curiosity I am able to connect them via ONVIF to a phone app with the username and password, so I know the cams are fine and the credentials are correct.
@dusanhauko what settings are you using for the rlc-820a?
Firmware versions etc…?
@TAustin
I have all rlc-822a/820a and one E! Pro?
They are being discovered fine and work in ONVIF Device Manager, but something possibly in a setting I have somewhere may be different.
rlc-822a’s Build 22041507 Config v3.1.0.0 Firmware v3.1.0.956_22041507
rlc-820a’s Build 22041501 Config v3.1.0.0 Firmware v3.1.0.956_22041501
E1 Pro Build 21112404 Config v3.0.0.0 Firmware v3.0.0.716_21112404
kind of the same issue as @skinnypope
Just a thought if your cams connect to the driver but you are unable to login, and it is a small detail
When entering the username and password, make sure these fields do not use a capital letter to begin with if you have not used one in your camera Onvif settings, the ST app automatically uses a capital letter at the start of username and password
No doubt you guys already know this but it is easy to miss and worth mentioning
And if you do get logged in to your cameras, video will NOT play in the device page, to get video streaming you currently have to hit refresh at the bottom of the devices page, you will then see the info panel expand to show details about your camera.
create a camera group and add the cameras to that group
Thats a good point for others to know if they read all of this.
However, I’m sure mine is a setting somewhere that I’ve overlooked somehow, but haven’t found it yet, that’s why was wanting to know firmwares and models for a good stepping off point.
In your top screencap, if detail is your serial number it might be wise to remove that part !
Upgraded the Annke C800 to latest (Hikvision) 5.6.6 firmware, config page says ONVIF version 18.12 if that helps, still no luck. All usernames and passwords capitalised correctly, and tapping Refresh to connect.
Am still able to access the cams with other iPhone apps over ONVIF so cameras are definitely fine and username/password syntax is confirmed as correct.
Hi @fido
Can you clarify little bit more
I have noticed that ST uses capital letter at the start of user name and password while my entry is small letter still this is changed to capital letter once i hit save
The app takes my actual entry or takes the one with capital letter?
Yup, a very good point and well noticed, IF you enter the username and password with a lower case letter, that is what the connection honours
You are correct that after entering your details an upper case letter is displayed at the start of the fields but that is down to the way the ST app offers text fields, your initial lowercase input IS honoured when logging in
To help resolve your issues can you install the Smartthings CLI ? Details on how are in Tods first post, if you send the log to @TAustin at his email address i am sure he will look into resolving any issues, this is a Beta driver and it is the issues and there resolutions that go towards making a finished item, so your logs are actually really helpful and important
The Smartthings CLI is available at the below thread created by Tod 
All- had a family day all day today so couldn’t work on the driver, but will get back to it tomorrow. So sorry for my delay in responding.
Hi @fido
I have quick question, i have noticed that in CLI logs, the time zone is not correct while I have the smartthings Hub and my pc Time zone both the time zone is correct
is this normal?
Yes, this is ‘normal’. I had posted the question a long while back about how to configure the logging software to display times in local timezone, but never got an answer.
Looking at your log, it appears that even though your cameras were discovered, that they may not have returned the expected information. Can you please delete one of your camera devices in the app and capture a log while you do a Scan Nearby Devices? I want to see exactly what is happening at the time of camera discovery.
Thanks.
What kind of cameras do you have?
Can you install the CLI and capture a log?
How much info being displayed in the Info table is an indication of how far initialization has gotten with your camera. Can you post a screenshot (blur out any info you don’t want to share).
You’ll have to provide me a log so I can really see what may be going on.
Yes, this is an annoying bug in the SmartThings app which has been reported but not fixed. It shows the first character as a capital letter on the Settings screen, but what’s really important is what you actually typed in in the Edit box. The forced capital letter is used for display only and is not passed to the driver.
I have an intelbras im3. The strangest thing is that other people here have the same and found it. I’m on the same wifi network as the hub and app cameras. I will install the CLI and send you the logs
@skinnypope and all others needing the CLI for logs:
My instructions at this link for getting up and running with the CLI might be a little easier to follow: [ST Edge] Breaking boundaries: supporting Blue Iris motion alerts and Shelly wifi Motion Sensors - #43 by TAustin
A quick note on a couple limitations with the current driver I want to make sure everyone understands:
There will be no video stream output on the device control panel itself. Currently there is no way to do that with SmartThings Edge drivers. You must create a camera group, and add your ONVIF Driver cameras to it. If your ONVIF cameras had been successfully initialized in the driver, you should get a live video stream when you open the camera group in the app. Please note this is only going to work when your mobile phone is connected to your home network. Unfortunately video streaming does not work when you are away and connected via a cellular network or even another wifi access point.
You need to make sure that your hub and cameras are on the same subnet. This means if your home network is 192.168.n.xxx that your hub and camera IP address both start with 192.168.n. I do plan to try to address this limitation in a future update, but for now if your cameras are on a separate subnet or VPN, or behind a firewall, you will probably run into problems.
