Search results

  1. N

    AI motion detection with BlueIris: an alternate approach

    I'm not super familiar with Telegram, but I believe different chats will be different people. I don't think there's a way you can have different chats for each camera since the system only supports a single bot.
  2. N

    AI motion detection with BlueIris: an alternate approach

    No, it has to wait for the annotation to complete before it can proceed to sending all the triggers. Honestly the annotations are just a novelty and not particularly useful once you have the system up and running: you can tell by looking at the photo what triggered it (car, person) with your own...
  3. N

    [tool] [tutorial] Free AI Person Detection for Blue Iris

    That's how it should work. BlueIris is sending a broader set of images over than actually contain the objects you care about. The AI system evaluates what BlueIris sends and ignores things that don't actually have what you're looking for in it.
  4. N

    AI motion detection with BlueIris: an alternate approach

    Version 5.2.0 is now available: * The original image that caused a trigger to fire is now stored temporarily and available for use via the built-in web server. The images are available in the /originals folder with the original filename. To update run docker-compose pull then docker-compose...
  5. N

    AI motion detection with BlueIris: an alternate approach

    Version 5.1.2 is now available. This release patches a low severity security vulnerability in a 3rd party library. There are no functional changes in this release. To update run docker-compose pull then docker-compose up to restart.
  6. N

    AI motion detection with BlueIris: an alternate approach

    When cool down is set it waits for the 20 seconds to expire before looking at another image, regardless of whether something was detected.
  7. N

    AI motion detection with BlueIris: an alternate approach

    Someone would have to try it by pointing the "Deepstack" URI in the configuration to a Yolo URI instead.
  8. N

    AI motion detection with BlueIris: an alternate approach

    This system only works with Deepstack. Unless Yolo has exactly the same request and response format as Deepstack it won't work.
  9. N

    AI motion detection with BlueIris: an alternate approach

    Awesome! Glad you got it working!
  10. N

    AI motion detection with BlueIris: an alternate approach

    There is some information on setting up with Portainer in the open issue to document how to do it: Document how to set this up with Portainer · Issue #184 · danecreekphotography/node-deepstackai-trigger. I've never used Portainer before however so my ability to assist is limited. As in other...
  11. N

    AI motion detection with BlueIris: an alternate approach

    There's a ton of logging already produced by the system to see where the delay is. What I suggest doing is just walking outside to trigger one of your cameras and then checking the logs in Docker to see when the image is received by the system, when it is processed for detection, and when the...
  12. N

    AI motion detection with BlueIris: an alternate approach

    Please open a support request over on GitHub for assistance with this. It's very likely because you are on Docker Toolbox and you'll have to change parts of the compose file to not use secrets. When opening the support request make sure to include the complete docker-compose.yaml file and the...
  13. N

    AI motion detection with BlueIris: an alternate approach

    Are you running docker-compose up from within the folder that has all three files (docker-compose.yaml, triggers.json, and settings.json) in it?
  14. N

    AI motion detection with BlueIris: an alternate approach

    Your mount point is incorrect. Post your entire docker-compose.yaml so we can see what you have.
  15. N

    AI motion detection with BlueIris: an alternate approach

    You're using Docker Toolbox instead of Docker Desktop. Don't use Docker Toolbox. From Docker's website: Install Docker Desktop instead.
  16. N

    AI motion detection with BlueIris: an alternate approach

    Release 5.1.1 is now available: - Relax the test for valid watchObject folders at startup. If the path has globs in it a warning will still get thrown but system startup will proceed. Resolves issue 342. There are no breaking changes in this release. To update pull the latest image from Docker...
  17. N

    AI motion detection with BlueIris: an alternate approach

    It's shown in the table on the defining triggers page in the example column. It's an array and supports as many rectangular areas as you like. The property name is "masks" not "mask". If you are having trouble getting this working open a support request over at github and include your...
  18. N

    AI motion detection with BlueIris: an alternate approach

    Glad it worked well! Documentation for Pushover handlers is on the wiki. You need to specify the UserKey in the trigger so the system knows what user to send the notification to. In your case it's probably the same as your UserKey in settings.json, but if you wanted to send to someone else...
  19. N

    AI motion detection with BlueIris: an alternate approach

    Yeah, looks like it doesn't work. I gave it a try and had the same problem. I'd look at the camera configuration options to see if you can disable that folder structure and have it just write a flat list of images. Alternatively you might be able to get /aiinput/overview/OverviewPTZ to work as...
  20. N

    AI motion detection with BlueIris: an alternate approach

    That's how I have my machine configured. It auto-logs in on reboot and then Docker starts up fine and the system comes up.
  21. N

    AI motion detection with BlueIris: an alternate approach

    Assuming you've mounted the ftp folder to /aiinput in Docker then something like this will probably work for the watch pattern: /aiinput/overview/OverviewPTZ/**/*.jpg. The watchPattern supports globs, but I've never tried with it so you may have to play around with it a bit.
  22. N

    AI motion detection with BlueIris: an alternate approach

    See the troubleshooting page for help. If that still doesn't fix it open a GitHub support issue with the requested information. You definitely do not want the snapshotUri feature. It's only useful for a very specific scenario and I'm confident that's not your scenario :)
  23. N

    AI motion detection with BlueIris: an alternate approach

    See danecreekphotography/node-deepstackai-trigger for how to resolve this.
  24. N

    AI motion detection with BlueIris: an alternate approach

    Version 5.1.0 is out: Warnings are now shown when annotateImage is true for a trigger handler but enableAnnotations wasn't set to true in the settings.json file. Log messages are printed on startup to help confirm the image folder was mounted correctly with Docker. Web server now shuts down...
  25. N

    AI motion detection with BlueIris: an alternate approach

    I just tried with v5.0.0 and v4.0.0 and don't see any difference in CPU usage. It hovers between 6-8% for "vmmem". I also tried with MQTT off (since that's where the substantial changes were in v5.0.0) and didn't see any difference.
  26. N

    AI motion detection with BlueIris: an alternate approach

    I don't actually have any dashboard set up in HA that looks at the statistics. I don't care about them at all :D Can you please open a support request in GitHub for the MQTT issue? Make sure you include the exact sequence of steps you take that lead to it (which services are rebooting, in what...
  27. N

    AI motion detection with BlueIris: an alternate approach

    Version 5.0.0 is out! Breaking changes statusTopic can no longer be set on the mqtt configuration in settings.json. Overall status messages are always sent to the node-deepstackai-trigger/status topic. This change aligns the status topic messages with the new MQTT messages that the system...
  28. N

    AI motion detection with BlueIris: an alternate approach

    Please open a support request over on GitHub so I can look into this a bit. Make sure to include all the information requested in the support template. For reference, I have 5 cameras and only 80 images currently in my input folder and CPU usage is only 33% (from BlueIris).