Intel NUCs from the 5th/6th generation are an excellent way to run Blue Iris on the relatively cheap Small form factor computers (well, not compared to the NUC, but you know the half-size towers I'm talking about) chew electricity by about a multiple of at least 3 comparatively. Note, this may be bias, as I'm a NUC fan and moderator at /r/intelnuc, but I sincerely believe this to be helpful advice still: I am still working on integrating it into home assistant and getting notifications working to only alert me on what I want. I am waiting on a google coral to test that too. I have more than that on my house but those two are the ones with a wide view of my yards and streets. The best part I can run it with my nvr and both have been working without issue. I do like the extra features of blue iris though which is why I have tried it, ai cameras, and frigate.įrigate so far I have two cameras integrated. I can't break it because it does have options to. I think honestly I am just to much a tinkerer and that leads to breaking things witch is why I like my nvr. That may change if I start having issues with it but so far. To me with security I don't ever see myself switching from a purpose-built NVR solution for security. No matter how I have tried to avoid issues with crashing and reboots or my own stupidity with PC NVR solutions. I am going to upgrade to POE model soon just to simplify my network wiring though. ![]() Its job is to hold a week's worth of footage and nothing more. I don't need it to do any more than it already does. My NVR has been rock solid for 3 years never an issue. This has reduced the lag to only 2-3 seconds. The streaming lag has also been greatly improved with a recent low latency LL-HLS option to the HASS Stream integration. Both support not just streaming but event handling to capture doorbell presses and motion alerts. The Core Amcrest integration works great with the AD110/AD410, and so does the newer custom Dahua integration. I will say that the AD410 AI human detections is very reliable, and has eliminated all the false positives with objects and shadows triggering motion alerts. I can't answer if there are still issues with its IR that the AD110 has, but I have not seen any reports on the forums saying that it does. I have replaced the AD110 with an AD410, which doesn't even have a PIR sensor. ![]() I really didn't have any issue with it because my porch is brightly lit so the default night vision "auto" mode always kept the IR off - and my doorbell videos at night remained in color. I've reproduced this on 2 different devices at my house and on one I installed at my parents.Ī lot of the grief mentioned here with the AD110 is about the IR illuminations and PIR. But if you use a flashlight to strobe or if your drive way is in front of your cam you can flick your headlights on and off a few times, the IR will crank intensity up and eventually reboot. That will set the intensity with a value from 0-100.Īt a setting of 0 I can get about 18 hours with no issues. cgi bin/configManager.cgi?action=setConfig&=10 cgi-bin/configManager.cgi?action=setConfig&Lighting.Mode=Manual You can adjust the intensity with api calls, but they aren't persistant. If you have a clear/unobstructed view the intensity goes all the way up and will cause reboots. So if you have a column or something on your porch that the IR can reflect off of it will lower the IRs intensity. ![]() The IR will automatically adjust intensity if something comes within the PIR range. OP should be able to strobe a flashlight in front of the camera for a few seconds and it will reboot. No issues from late afternoon until around 11am. My reason for returning mine was that the IR sensor will sometimes go crazy and cause the camera to reboot on its own every few minutes.ĭuring the day my front yard gets a kaleidoscope effect from the sun and my trees. There's some yaml on the last two pages to do the API calls. *Here is a thread on the amcrest forums about the persistent night vision issues. You'll have to have something like nodered make those calls on Tuesday after the reboot or whenever it reboots on its own.** It's possible to use API calls from older documentation to adjust what amcrest calls "SmartLighting" but those settings revert on reboot. ![]() There's some fuckery going on with the IR sensor.You can even see it in OPs pictures where he has both the blue iris overlay as well as the amcrest one. You can't move or remove the timestamp.IR settings are not persistent upon reboot.Unlike other amcrest cams, you have to use their app to setup and make setting changes*.It's in the firmware to auto reboot Tuesdays at 2 am with an un-mutable "Connected to network" audio message.So there are a few issues with this camera that OP didn't touch on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |