The Dropcam Echo review unit came in a spartan package. The camera itself was bubble wrapped. There were some mounting aids, a power adapter and an Ethernet cable. Similar to boxed software, the unit was accompanied by a card introducing the Dropcam Echo. The card also had a product key.

I wanted to setup the unit as a non-technical consumer, and decided to follow the directions blindly. Even though my router had a wireless MAC filter, I refrained from adding the Dopcam Echo's wireless MAC ID to the list.

The first direction was to connect the camera to the router using the supplied Ethernet cable. The introduction card directed me to visit as the next step. The key on the card was entered, and after this, the directions on the website were followed.

I was able to start watching the video from the camera on the site soon after entering the key, but the wireless was still left to be configured. Wireless setup was a must as the Dropcam had to be shifted to a different location, away from the router. The setup page presented me with a list of wireless networks within the reach of the camera, and upon selection of my network, prompted me to enter the network password. For a technical person like me, it was unnerving to find these details displayed and requested on a remote non-secure page, but this is the price one has to pay for a solution that is plug and play. After feedback, Dropcam has now moved these pages to a secure server.

After typing in the network password, the page directed me to lookup the status of the wireless connection by observing the nature of the glow around the lens. A full green would have implied that the wireless connection was successful, but I observed blinking red and green in sequence. Upon clicking the appropriate icon in the page, I was informed that the network password entered could have been incorrect. Failing this, I was supposed to contact Dropcam support. Fortunately, I had requested them to let me know where to find the MAC ID earlier. It turned out to be the SN at the back of the unit. With this MAC ID entered in the wireless filter, I entered the password again, and was presented with a successful wireless connection for the camera. After feedback, Dropcam has added a note about wireless MAC filters to the appropriate page.

All said, I was up and running, with the Dropcam far away from the router (still within the wireless reach) within 10 minutes. I have to say that this is probably the shortest time I have ever spent in setting up any sort of networking gadget.

Introduction Analyzing the Dropcam Hardware
Comments Locked


View All Comments

  • MonkeyPaw - Thursday, August 12, 2010 - link

    From my own experience (was burglarized a few months ago in broad daylight), thieves are very bold. They will act like they belong there, and most people won't pay attention, especially if they look official. Unfortunately, all security can be bypassed--even a big dog can be dealt with if someone is determined enough. Your best hope is to make your property less appealing than everyone else's. I don't mean go all ghetto, but smash-and-grab people are pretty lazy, so they will pick the easiest targets first. If only they put their time into productive work, instead of making everyone else's insurance go up every year. >:(
  • jquin6 - Saturday, January 12, 2013 - link

    Criminals taking basic precautions. Did your nanny drop you on your head? Only 40% have some high school or less!
  • mcnabney - Wednesday, August 11, 2010 - link

    The 45GB/mo of upstream should have been mentioned a bit earlier, probably best placed in the cloud section of the article. This product is not really a commercial device and will likely be installed in locations with consumer-grade data connections like cable and DSL (or even wireless like Clear). That type of usage will certainly be noticeable by the ISP. Since this is, as you say, the iPad of IP cameras the likelihood of consumer installs is fairly high and that usage generation will likely come back to bite the customer.

    The cloud usage is really the big drawback, especially when 99.999% of 24/7 data will never ever by viewed. Why pipe it? My first thought was having a two-box solution. One is a camera, the second is small HDD that will store the data. That way the upstream only occurs when requested. It is also easier to haul a little box into court to be used as evidence than to wrangle the cloud. The two box solution could easily be battery backed-up and operate a direct ad-hoc wireless connection.
  • Twoboxer - Wednesday, August 11, 2010 - link

    ^^ Previous comment makes many of the relevant points. Constant streaming is ludicrous.

    The hardware needs to do local motion detection, discriminate between simple lighting changes and real motion, and record only the video from several seconds before the motion detection, through the period of motion, and for several seconds thereafter. The recording should optionally be done to a local device, or to "The Cloud". The choice should be an economic trade-off between owning the local disk hardware, or renting the cloud.

    In either case, real-time remote access needs to be made as easy to implement as their current product apparently is. And a small monthly fee for this service, separate from the above, is reasonable.
  • ganeshts - Wednesday, August 11, 2010 - link

    Twoboxer, The scenario you outline is only one of the possible applications. The solution suggested by you works for that particular scenario.

    When you look at apps like nanny cams (where you keep a watch over the babysitter), constant streaming becomes a necessity, irrespective of motion detection. Agreed, this will not be 24 x 7, as the cam in that particular application can be switched off as soon as the user gets back home.

    Another way to think of this is a webcam without a computer ( though one would definitely hesitate to pay $280 or so for this purpose alone :) )
  • rcc - Thursday, August 12, 2010 - link

    As I mentioned above, the hardware does support local motion detection as you describe. It's a dropcam limitation, most like so they can sell you the various rate plans.
  • andrewbuchanan - Wednesday, August 11, 2010 - link

    I've written several security applications that store video offsite that clients could access anytime through a web browser, one stored mpeg4 clips of motion detection back in 2005, then other one in 2008 stored jpeg images approx every second.

    Neither company really went far with it. The primary technical concern, as somebody else pointed out already, is that most people get 1/2 to 1 Mpbs upload, enough for a couple of cameras max. And that's pinning their upload, in some cases 24x7, something the customer doesn't really want whether they know it or not. And it's bad with dsl/cable providers, worse with cellular or wireless providers. Makes for a nice sales discussion, you either gloss over it but include it in the fine print or scare them with the though of a huge internet bill. Upside is if your house burns down you still have recordings, and in the case of a break in they can't steal the recorder, downside is that your internet connection going down means you lose recordings and that happens all too often.

    My issue personally has always been that the quality of locally stored video can be 30 fps 2MP+ content (these days), or even 30 fps 352x240 (2005), 640x480-2MP by 2008. If it's for security local content just looks way better. I don't think there's enough market for nanny cams to make it worthwhile. Most people don't want cameras in their house, especially ones you can view over the internet.

    And... axis cameras are overpriced, they are nice, but overpriced. But maybe that's why they targeted iphone/apple :-), people who don't mind overpriced.

    Besides the company's I worked with doing this, there were others, so it's not really novel or unique. In most cases I've steered companies to doing something similiar to what I'm doing now, providing local equipment (nvr/dvr) with flash/silverlight/mobile streaming options. Hardware costs are higher, but there's no monthly, it's expandable, flexible, has much better quality, longer recording history, easy on your internet connection, and can still be watched anywhere.

    Downside being it does require someone to actually configure their router which I appreciate is what they are marketing this product as not needing. But is $25/month cheaper than just calling a professional to set up your router for 15-30 minutes?
  • pkoi - Thursday, August 12, 2010 - link

    So in other word that is
    Webcam + h264 compression + nic adapter.
    for ~300$

    In the Cloud ???, Sorry but you inevitably need local storage/server, preferably hidden, with an UPS.
  • ganeshts - Thursday, August 12, 2010 - link

    The review also brings out the USP of the product as the ease of setup and use (even for the non-tech folks).

    Also, the target market is casual monitoring (like nanny cams / looking after pets etc.), not for those really paranoid about security, I guess :)
  • JNo - Monday, August 23, 2010 - link

    It's not the $300 cost of the product that will make them money or not, rather this is like selling printers -the money is in the refills, or in this case the subscriptions.

    "After this, a 7 day recording plan costs $8.95 per month, while the 30 day recording plan costs $24.95 a month."

    At these prices (on par with my mobile phone bill) this is way too expensive for your average jo to be a 'nanny cam'. It is clearly aimed at home security imho. And for most people, a decent holiday is 2 weeks, making the 7 day plan pointless. $25/mth is a lot so the ability to record locally is highly desirable. That's a lot of money for home security based solely on a webcam.

Log in

Don't have an account? Sign up now