Dahua impossible to reconnect

Configuration
1

Hi,

my camera didn’t work anymore without doing anything,
HA Onvif tell me the authentification expired and ask me to reconnect, when i do so i’ve this message:
“Wsse authorized time check failed. (code:s:Sender) (subcodes:{http://www.onvif.org/ver10/error}NotAuthorized)”

the time of the camera is the same as internet clock
can someone help me out.

2

Hi, welcome to the forum!

What happens if you connect with a browser to that cam and is the HA clock correct?

1 Like
3

Which Dahua model does the error occur on?

I don’t have a precise explanation as to why this happens with the HA Onvif integration, but I know it happens with my Imou (Dahua OEM) DB61i, where the error also occurs every three to four months. In this case, simply rebooting the DB61i helps me. If you then restart HA, the DB61i is recognized by the HA Onvif integration again without this (alleged) authorization error.

Note: I have 5 Dahua and 2 Imou cameras in use and the problem only occurs with the DB61i.

4

hi thanks for your answers,

it happens with a dahua vto2202 and dahua IPC-HDW2849T-S-IL, i’ve already tried to reboot the devices and HA, synchronize the time several times, i’ve the access and see live in a browser for both.

5

OK, if restarting the device doesn’t solve the problem, I’m afraid I have no other ideas. With my DB61i, where the problem happened again yesterday, that was and still is the solution. You can also try playing around with the DTS settings. Enabling or disabling DTS.

As I already wrote, this problem only occurs with the DB61i and not with any other Dahua cameras or the Dahua NVR. The NVR only has this Onvif issue,

Logger: homeassistant.components.onvif
Quelle: components/onvif/device.py:315
Integration: ONVIF (Dokumentation, Probleme)
Erstmals aufgetreten: 18. Mai 2025 um 15:05:06 (2 Vorkommnisse)
Zuletzt protokolliert: 18. Mai 2025 um 15:05:06

The date/time on NVR (UTC) is '2025-05-18 13:04:30+00:00', which is different from the system '2025-05-18 13:05:06.291348+00:00', this could lead to authentication issues

but it’s been around for about 2-3 years, and there doesn’t seem to be a real solution. The problem went away for a while, and then reappeared after some HA Core update. :rofl: However, nothing has been changed to the NVR firmware in the meantime. Despite the problem, the NVR is (so far) functioning normally, so I can/must live with it.

1 Like