GetEvents error / "Events: subscription 8000ffff"

Rolling back might have helped.... no errors in the logs, and I just realised I'd had Auto Tracking disabled in the camera itself as a hang over from testing. Will need to wait til tomorrow now to verify.
 
It is not a BI issue, it is a bug in the Dahua firmware. We went through this when DST went off last Nov.

 
It is not a BI issue, it is a bug in the Dahua firmware. We went through this when DST went off last Nov.


Is that still true for me, who’s in the UK and clocks haven’t yet changed? My camera is set to sync with a local NTP, and no DST config set… There’s no internet access in my setup, so nothing really should be aware of a DST change anywhere… (unless the firmware is really buggy, but I’m running the latest ReoLink firmware from 13th Dec, so I would have assumed any bug would have been fixed?)

Also, the problem seems to be that BlueIris cannot pull/poll/receive ONVIF events, so isn’t the issue there BlueIris, not the camera itself?

Rolling back to a version prior to March 3rd has helped me. I’d be intrigued to see if it helps others…
 
Is that still true for me, who’s in the UK and clocks haven’t yet changed? My camera is set to sync with a local NTP, and no DST config set… There’s no internet access in my setup, so nothing really should be aware of a DST change anywhere… (unless the firmware is really buggy, but I’m running the latest ReoLink firmware from 13th Dec, so I would have assumed any bug would have been fixed?)

Also, the problem seems to be that Blue Iris cannot pull/poll/receive ONVIF events, so isn’t the issue there BlueIris, not the camera itself?

Rolling back to a version prior to March 3rd has helped me. I’d be intrigued to see if it helps others…

Not sure about your Reolink, but you can always use the Onvif viewer to rule out if it is a BI issue. If the Onvif viewer can't connect then the problem lies in the camera. More than likely it is due to a Onvif authentication issue.
 
  • Like
Reactions: looney2ns and Vini
Not sure about your Reolink, but you can always use the Onvif viewer to rule out if it is a BI issue. If the Onvif viewer can't connect then the problem lies in the camera. More than likely it is due to a Onvif authentication issue.

What is "the ONVIF viewer" you refer to? Is there a link?

Edit: I found a copy of ONVIF Device Test Tool v21.12, whilst im not sure what I was looking for. It was able to communicate happily with the camera and pull back camera details and control configuration etc, simply by inputting the IP (no credentials etc).



For what its worth BI 5.8.7.8 has been absolutely fine (for the last ~18 hours now) with the very same ONVIF config with my ReoLink, so something 3rd March definitely changed within BI... Keen to know if other users see benefits from a pre 3rd March version...
 
Last edited:
What is "the ONVIF viewer" you refer to? Is there a link?

Edit: I found a copy of ONVIF Device Test Tool v21.12, whilst im not sure what I was looking for. It was able to communicate happily with the camera and pull back camera details and control configuration etc, simply by inputting the IP (no credentials etc).



For what its worth BI 5.8.7.8 has been absolutely fine (for the last ~18 hours now) with the very same ONVIF config with my ReoLink, so something 3rd March definitely changed within BI... Keen to know if other users see benefits from a pre 3rd March version...
yes, that's it and sounds like you are good to go :)
 
  • Like
Reactions: Vini
Guess we wait for Ken to acknowledge some kind of bug then... until then.... 5.8.7.8..........
 
On the basis rolling back is pretty simple/quick/easy, I took a punt on the latest version 5.8.8.8 (15/03/2024). Seems to be OK/fixed again?

Meaningful/detailed changelogs would be ideal, but I know we've been wanting for years.
 
A little investigation on my system:

T5442TM and T5442T-ZE get continuous Event errors with ONVIF authentication enabled.

T2431T, miniPTZ and 4K 180° are fine with authentication enabled.

I didn't experience the issue at the time switch in March or November of last year.
 
Any news for this issue?
What issue are you facing?

Within 2 weeks/a flurry of releases, my issue was resolved.

My gut is there was a bug in BI that was patched, as nothing on my camera changed/was changed.

If you’re still facing issues, describe what camera, software (BI) and firmware (camera) you’re using and maybe even flag it with BI Support.