IPCamera - Clock Not Sync'd

Add-ons Bindings
1

@matt1,

I’ve been getting these errors (only during startup of OH) below since 4.3.0, was wondering if this is just a one off. Both DVR and Pi4 have correct time based on NTP.

2025-05-08 12:27:53.966 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:27:57.537 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:27:57.768 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:28:07.882 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:28:12.904 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:28:18.529 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:28:18.882 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other
2025-05-08 12:28:20.408 [WARN ] [ab.binding.ipcamera.internal.onvif.OnvifConnection] - ONVIF time in camera does not match openHAB's time, this can cause authentication issues as ONVIF requires the time to be close to each other

Best, Jay

2

I had the same warn message after updating to 4.3.?.
Setting a different ntp server on the cam solved it, although the time was correct before.

3

Just changed it to time.google.com and it’s still happening. Which one are you using?

Best, Jay

4

0.de.pool.ntp.org
… which I guess does not make much sense if you are in the US.

5

A couple of comments.

Most brands do not care if the time is out, the binding does and still does not care even though it will warn you in the logs. I have seen a brand that does care, hence why this was changed in the binding around 4.3…The ONVIF spec states that the times need to be within X amount of time otherwise device can ignore the requests as it could be old traffic getting replayed as a form of attack.

I have been considering making the binding have the option to set the time and date on the cameras from the openHABs time. If I did this then all cameras would be in sync even if you block the cameras from reaching NTP directly as this ability is in the ONVIF spec. However from testing a lot of cameras dont bother to implement their end of what is needed for that to work.

If you enable DEBUG level I believe it will tell you the times and what the offset is between them. I have seen some cameras need to have the timezone set to the wrong setting for the UTC time to be correct. Report that to the camera manufacturer if you see it after updating firmware.