Events : subscription 00002efd

pemmel

n3wb
Joined
Oct 23, 2016
Messages
8
Reaction score
0
One of my Reolink cams is getting this on the BI Status screen. I looked in the BI help file but got no hits.

Anybody know what this is about ?
Pete
 

Jared

Young grasshopper
Joined
Apr 3, 2017
Messages
66
Reaction score
8
So, I had this error occur today on all 31 cameras or most of them anyway. its not doing it now, just did it around 1:30 pm or so. i dont see where pull point subscription is even an option to uncheck. Im sure im just missing it. Can anyone help me with this?
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
So, I had this error occur today on all 31 cameras or most of them anyway. its not doing it now, just did it around 1:30 pm or so. i dont see where pull point subscription is even an option to uncheck. Im sure im just missing it. Can anyone help me with this?
video>configure
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
Hi Gary here you helped out with an answer about subscriptions 00002efd problem can you tell me where this needs to be fixed in Blue-iris please thanks
its in the video configuration tab of each camera in BI settings.
 

phototimez

n3wb
Joined
Jun 25, 2017
Messages
2
Reaction score
0
Hi Gary here you helped out with an answer about subscriptions 00002efd problem can you tell me where this needs to be fixed in Blue-iris please thanks
Your the man. been trying to find it for ages. all good now no notifications anymore thank you
 

ExTechjunkie

Young grasshopper
Joined
Oct 21, 2020
Messages
41
Reaction score
18
Location
New York
I've just found this old thread by searching for an "Events: subscription" log entry issue that I'm experiencing in a newer version of Blue Iris, which does not have a "pull point subscription" checkbox (although I suspect it has just been renamed to "Get ONVIF Trigger Events" since this thread began)...

I'm using Blue Iris 5.4.0.1 and my log is filling up with "Events: subscription" entries from three cameras, several every second. What is odd to me is that "Backdoor" and Mailbox" are the same make, model, firmware version and settings as 8 other cameras in my system. On just these two cameras, camera-based motion events are never received by Blue Iris. The other 8 work perfectly in BI - camera-based motion detection works and the log does not fill with subscription events from those other 8 cams. What's more perplexing is that on my NVR, ALL 10 work perfectly/identically, camera-based motion detection included.

I can't understand why just these two are not functioning correctly in BI with regard to motion events and these numerous subscription events in the log.

The Doorbell is a completely different story. While it continues to generate the subscription events, camera based motion detection does work in Blue Iris. I suspect that my be due either to its additional PIR motion sensor and/or to its different (Amcrest) video configuration profile.

On a perhaps related note, two other Amcrest cams that I have do not ever report motion events to BI although they too work fine with my NVR. They use the IP2M-841 profile and lack a secondary/PIR motion sensor.

Disabling "Get ONVIF Trigger Events" on the video config screen stops generating the events below, but then camera-based motion is not received by Blue Iris for sure.

As a workaround, I've opted to deselect "Get ONVIF Trigger Events" for the cams where camera-based motion is non-operational in BI and go with BI's native motion detection instead. I would prefer to resolve the issue though and would also like to stop filling the BI log with the subscription events from the Doorbell. Suggestions welcome.
1 4/5/2021 4:49:12.495 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:12.600 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:12.651 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:15.541 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:15.681 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:17.647 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:18.691 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:18.934 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:21.701 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:21.980 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:22.686 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:24.713 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:25.205 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:27.723 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:27.726 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:28.265 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:30.734 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:31.649 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:32.772 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:33.752 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:34.763 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:36.765 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:37.790 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:37.824 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:39.774 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:40.815 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:42.784 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:42.871 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:43.841 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:45.795 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:46.919 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:47.922 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:48.805 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:49.947 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:51.819 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:52.961 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:53.193 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:54.827 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:56.232 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:49:57.834 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:49:58.009 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:49:59.265 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:50:01.006 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:50:02.348 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:50:03.087 PM BackDoor Events: subscription 00002efd
1 4/5/2021 4:50:04.021 PM Mailbox Events: subscription 00000190
1 4/5/2021 4:50:05.397 PM Doorbell Events: subscription 00000194
1 4/5/2021 4:50:07.034 PM Mailbox Events: subscription 00000190
 
Joined
Apr 12, 2021
Messages
13
Reaction score
2
Location
Planet Earth
I've only been in the BI ecosystem for a few weeks (though I have a good ~5 years of deploying various enterprise CCTV systems under the old belt), but I was having the same problem. I have been searching far and wide for a solution but it appears there isn't really a good one, except to just turn off "Get ONVIF Trigger Events" in the video config screen of the camera.

For what it's worth, I don't think I'd ever want it to use the camera's motion detection with BI; I have a whole collection of different cameras around my property from different manufacturers including Hik and Amcrest and Unifi , pretty much all leftovers from small deployments, and most of them have onboard motion detection but frankly it's pretty bad compared to BI's native motion detection. Most of my camera units require hours of calibration in their native environments and even then don't pick up motion reliably (or, far too easily); in BI it took me about 20 minutes flat to get them calibrated darn near perfect. Just had to turn off object detection because that was pretty flaky. Unless you have some really sick $800 motorized unit with crazy sensors I really don't think you can beat the quality and customizability of the BI detection. Not that that helps folks who do need it for edge cases.
 

ExTechjunkie

Young grasshopper
Joined
Oct 21, 2020
Messages
41
Reaction score
18
Location
New York
Yeah, no argument there about BI motion detection being better than what the cameras have built in. Rain and fog cause false motion alerts from the cameras all the time. I just wanted to start with BI as a drop-in replacement for everything my NVR is currently doing. When I couldn’t find a motion zone grid in BI like the ones I set for each camera in the NVR, I figured I’d begin with camera based motion and figure out how to define the zones in BI later. Then this weirdness tripped me up.
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,430
Reaction score
47,552
Location
USA
Yeah, no argument there about BI motion detection being better than what the cameras have built in. Rain and fog cause false motion alerts from the cameras all the time. I just wanted to start with BI as a drop-in replacement for everything my NVR is currently doing. When I couldn’t find a motion zone grid in BI like the ones I set for each camera in the NVR, I figured I’d begin with camera based motion and figure out how to define the zones in BI later. Then this weirdness tripped me up.
Motion detection certainly depends on the camera. Many of us with Dahua AI cams find it to be extremely accurate with no false alerts even in snow and rain. As always YMMV.

Let BI run with that ONVIF subscription for a day or two and see if it resolves itself. Whenever I added a camera and got that subscription log, it resolved itself over a day or so.

 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,430
Reaction score
47,552
Location
USA
Have you tried rolling back to a stable version?

There is nothing wrong being on the bleeding edge, but BI does push out updates quickly and of course no two systems are the same, so it may be fine on my system and not yours.

BI will not know it is a bug unless you email them per the link in BI.

BI is basically a one man show and this is not his forum and he doesn't visit it.

Have you tried deleting the camera and re-add it? Doing find/inspect? Is motion detection and smart motion detection off within the camera itself?
 

looney2ns

IPCT Contributor
Joined
Sep 25, 2016
Messages
15,521
Reaction score
22,657
Location
Evansville, In. USA
Thanks you for the suggestions. Since this bug has been reported over several months(above) on different BI release levels as well as on different camera it's
obviously a bug in BI software. I don't care to spend my time looking for a band aid or debuging unless they want my help. I just want something that works
reasonably well.

Given all the BI discussion and users here, it's a sad commentary that BI does not monitor here in an effort to improve their product as well as customer relations.
I and many many others are not having the problems you are talking about.
He apparently knows what is successful, since he's been doing BlueIris for over 20yrs.
What firmware version do you have on the 5442.
I have 6 of them working fine with BI, and not getting errors like you report.
 
Top