thechairman wrote: ↑Mon Aug 14, 2023 3:31 pm
***UPDATE***
So things are working exactly as they should be. I have not made any other changes to settings since posting and now I am suddenly receiving notifications again.
To follow up my previous and fairly abstract post of last evening, the issue does seem cyclical as said to be happening approximately every 30 days or so. If this can be pinned down as indeed being the case, I would certainly look at anything within my particular ecosystem on a similar schedule that could possibly be the cause. But that's about the only clue provided to aid in any type of methodical investigation of the issue. And maybe cyclical, maybe coincidence...
So a few practical angles to consider checking into;
First, T-Mobile
does have a fairly good troubleshooting list available that includes quite a few practical tips -- some that may not necessarily occur to a user as even being related to their particular problem, but may well be nonetheless. So if it hasn't been referred to already...
https://www.t-mobile.com/support/device ... leshooting
Otherwise;
1. Stay away from Blue Iris updates if you have a version that works and serves your needs. Run Blue Iris on a dedicated and well maintained machine not running anything else.
2. Schedule Windows updates to occur on a monthly basis under your control and observation. Shut down Blue Iris first. I personally follow up with my own additional maintenance routine with a free system utility that quite nicely cleans the residual crap left over including orphan registry items. I have the Windows defrag utility disabled and only do an occasional analysis of my SSD using third party software. The results are usually green all the way. The spinners are left to the Blue Iris database maintenance routine since that's all that's on them. Point is, I'll pretty much know these bases are already covered if having to troubleshoot anything.
3. Be aware of other device's updates and upgrades. Inspect device configurations and reboot on a practical schedule, but not excessively.
4. As mentioned in the T-Mobile tips, time/date synchronization among devices (and networks) can be critical for optimum performance and smooth integration of services.
5. Know the limitations imposed by the carrier relative to your actual usage. Monitor your usage at both the carrier and device levels to ensure compliance with the carrier policy.
6. Multiple instances of the same alerts can (and eventually will) be problematic at the mail server and carrier gateway when not responsibly monitored and regulated. Stay on top of your triggers and alert configurations and behavior. Some services are more stringent than others about excessive message repetition before imposing restrictions. Gmail is among the more forgiving email providers both from what I've read and in my own experience. They are also one of the most respected and dependable regardless of what the Google naysayers like to claim.
7. Know your cameras, their configurations and primary purpose. Be aware that seasonal changes can (and usually do) affect a camera's triggers, thereby its alerts. Review and re-tune your triggers from time to time anyway just to account for little stuff possibly affecting the performance..., e.g., leaves fall, the road is now exposed with 500 cars a day triggering excessive alerts.
There is obviously more, but the bottom line is the equipment and systems basically perform as they are configured (or mis-configured) to perform by the end user. Yes, changes can obviously occur beyond the end user's control, but it is the end user's responsibility to cover what they
can control before jumping to conclusions. The time you spend on hold with a service provider help desk screener may well be better spent investigating your own system thoroughly beforehand.
Just my $.02. I'm by no means anything more than a Blue Iris user with only moderate personal experience on what I would consider a very practical level. Keeping it simple and going from there is what has worked for me and is just how I roll.