Wrong notification image

Freightdog · Post by **Freightdog** » Fri Feb 03, 2023 6:49 pm

Hi all. I've been using BI5 for a couple of years with no major problems, but there is one that crops up now and again. When I get a push notification to my android phone BI is sending the image from the previous motion alert. So like today, I had a delivery at the front door, phone pinged, glanced at the image, carried on my day. Then several hours later a car headlight triggers the camera and I get a ping on my phone, only this time the image is from the delivery several hours before?? Now this has happened before but it cured itself somehow.

Does anyone know why this happens?

I'm running a new Windows PC, have pretty good broadband, and the phone was connected to the wifi at the time.

IAmATeaf · Post by **IAmATeaf** » Fri Feb 03, 2023 9:23 pm

You’re lucky you’re getting an image, mine was on/off for a while and then in the last year I’ve never had an image come through with an alert.

IAmATeaf · Post by **IAmATeaf** » Fri Feb 03, 2023 9:56 pm

And having said/typed the above I’ve just checked my latest alert and would you believe it there is an image, DOH! And the image is spot on.

PaulDaisy · Post by **PaulDaisy** » Fri Feb 03, 2023 10:08 pm

Check your log. Did a DB repair take place between the off image and the fix? I suspect that the DB image counter is off by one due to minor corruption.

Freightdog · Post by **Freightdog** » Fri Feb 03, 2023 10:11 pm

PaulDaisy wrote: ↑Fri Feb 03, 2023 10:08 pm Check your log. Did a DB repair take place between the off image and the fix? I suspect that the DB image counter is off by one due to minor corruption.

Ah i didn't know that would have an effect. i'll check that and see. Thx

PaulDaisy · Post by **PaulDaisy** » Fri Feb 03, 2023 10:27 pm

I suspect that it may. Your BI installation is probably set up to automatically repair and rebuild the DB at least once every two days (default), so that could cause it to fix itself. You could set it to rebuild more frequently if the issue persists. Some releases appear more prone to DB corruption (the log will even tell you that the DB is corrupted).