The user with Log ID (-1193106576, the error there is a bit more confusing as it show: getSystemDateAndTime error (192.168.2.156):ONVIF SOAP Fault An error was discovered processing the wsse:Security header.:
I have no idea why there should be an issue with the security header in that request as it doesn’t have one. Basically, the app has to call that function to get the date and time so it can be used to create the security header for further requests.
I have double checked login and password. No luck. Error: discovery error. Undefined.
Strange this cause on my TV via Tinycam Pro it is working great on ONVIF.
As for motion, have you turned it on in the Homey device (big button with a man walking). A lot of users think this is the alarm status, but it is an option to turn motion detection on and off.
Hi Adrian, i’m 100% sure the login credentials are correct. To investigate this further i installed the application called ‘ONVIF device manger’ on my pc. With the same creditentials i can login to the NVR and see all settings, cams, events and what so on…
I don’t now very much about all of this, but when I scroll through the log file I think i can read out it is connecting with the NVR, because it read outs the time and date, firmware version and a lot of more information. but in the end it all stops with
Failed to connect to camera, Unrecognized configuration.
So I honestly don’t think there is an issue with the login credentials.
Motion is working. For all 3 cameras. Like you said, it was a RTFM problem
For the screenshot. I can get a screenshot for any camera using ONVIF Device Manager. But I can’t find the right URL there neither.
Just wanted to highlight a thing with my Reolinks which sends person detected motion events.
It’s just that the camera capability for Person detection seems not to be presented after a while( a day or two) on the Device.
That also seemingly makes the related flowcard to be missing with ?Card Unavailabe notification.
But it still works anyway!?
Why would this capability be removed from device when it’s actually is there all along?
I’m not sure either way, but glad it’s working.
The main change was to create my own connection routine that called the same stages as the library version but using promisified calls to individual functions instead of nested callbacks. That gave me much better control over handling errors and skipping parts that were unnecessary. Maybe that was the solution but I didn’t expect it to change your situation.
Ok, it’s progress
Could you set the log to Detailed Information, switch the motion detection option on so I can see if it is enabling correctly and then try to trigger motion finally send the log. then send the log.