After hard resetting them did not fix the issue, I took them all to electronics recycling. I replaced them with TP-Link Tapo 2K cameras which are working fine and also with Blue Iris.
Peter
Not a power supply issue. I keep them in stock and first thing I tried was to swap the power supply. But then I noticed it was ALL 4 of my FI8910W cameras gone south at about the same time on the same date. Almost like they are doing a phone home to something that is no longer responding so...
On October 6th, all 4 of my Foscam FI8910W cameras stopped working. On power-up they work for a minute or two then stop responding. They are ethernet-connected. Once they go wonky they even stop responding to ping requests. They are behind a firewall and not Internet accessible so doubt they...
Picked up a cheap MoonCity camera from Amazon a year or two ago. On install, it looked to be dependent upon custom app (MIPC on ios) and cloud services so I set it it on a shelf where it has sat...
I needed a replacement camera so pulled it out today and set it up for testing. It works fine...
For anybody else experiencng this issue, there is a new update posted today at blueirissoftware.com/updates. This update resolves the dll issue and BI now starts correctly.
I am running BI 4 on a Windows 10 system. Windows is up to date. I install BI updates weekly if avalable and just installed latest last night. This resulted in BI unable to start with following error:
"BlueIris.exe: The program can't start because libfaad2.dll is missing from your computer. Try...
The app seems to have a very tight timeout on the download where it gives up prematurely. It rarely works for me. I can download and run the update file manually from my browser without incident and usually have to.
Peter
Guess I know when to use that option now. Ha ha. Okay. Checked the box to skip monitoring of space on that share. All good now and no red flags on the GUI or IOS apps. Thanks!
Peter
"New" is configured to the default local location of c:\BlueIris\New. The BI use limit is 300GB. It is a 2TB drive with 1.7TB free and, as can be seen from the lower right corner of my prior screenshot, BI reports "C: +1.43TB" so all is well with this one (1.7TB - 1.4TB = the BI requested...
on the left we have two file explorer views - top is the mapped z: drive and bottom is the target network share. On the right we have the Blue Iris log showing z: short 289.9G, properties from the server running BI showing 1.8TB free, and the alert at the bottom inside the BI GUI showing again...
SOLVED: v4 Erroneous Size Errors for Samba Shares used for Clips and Archiving
I am trying to configure BlueIris 4.0.0.12 to use a Samba share on a Linux ClearOS server for the Clips and Archiving "Stored" directory. The share is 2TB with 90% available. I configured BI to use 300GB. BI now...