From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] openwrt or "open" security cams?
Date: Fri, 3 Apr 2020 18:53:55 -0400 (EDT) [thread overview]
Message-ID: <1585954435.95276219@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw5kjqtNQN01kw2aYwe_5vvmODEHu8AtwDjPSDaxwqqzAw@mail.gmail.com>
The ESP32-CAM device (which is under $10 quantity 1 from lots of sources, just google) is a WiFi enabled camera board with lots of functionaliy built in, including a full WiFi (2.4 GHz) and TCP/IP with TLS stack.
I have been playing with a couple, as have my friends. Various folks have 3D printed cases for particular uses, or you can just use any little box with a hole drilled for the camera.
It's programmable with the Arduino tools, or with Micropython, or with an embedded Javascript framework. You need an FTDI usb device to boot it, program it, ...
Folks have used it effectively for security camera applications. The camera that is usually sold with it (a very teeny camera indeed, smaller than a black bean, which I almost lost when I opened the package with the board and camera, the first time).
Easily battery powered. You can find a lot of support from the hacker community.
It does a simple (imperfect) face recognition onboard as an option, and can do single frames or streams, and has a number of GPIO pins you can use to trigger it, if triggering by motion isn't what you want.
On Thursday, April 2, 2020 2:05pm, "Dave Taht" <dave.taht@gmail.com> said:
> I am considering doing a security camera deployment, but am concerned
> about the overall security of
> security cams. Are there any with a reasonably rebuildable set of sources? ipv6?
>
> Anyone have recent experience with zoneminder, jitsi or big blue button?
>
> --
> Make Music, Not War
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
next prev parent reply other threads:[~2020-04-03 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:05 Dave Taht
2020-04-03 22:53 ` David P. Reed [this message]
2020-04-03 23:08 ` Joel Wirāmu Pauling
2020-04-03 23:10 ` Jonathan Morton
2020-04-03 23:15 ` Joel Wirāmu Pauling
2020-04-04 13:37 ` David P. Reed
2020-04-03 23:32 ` Valdis Klētnieks
2020-04-03 23:36 ` Joel Wirāmu Pauling
2020-04-04 0:28 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1585954435.95276219@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox