**** ** ******** **** ** ***** own '*** ** *** *********'.
****** ********* ** ****' '*** ******', which ** **** *** ********** ***** traditional *** ********. ** ****** *** to * ***** *****, **** *********** **** ** **** *********** *********** ** ******* ***** *** VMS *************.
***, **** *** ******** ******** ******* ** *** ****** *********, ***** **** ** *** ***** problems.
**** *** ****** *** *** ******* to ********* *** **** ** ***** and *** ** ******* **** *********** positioning.
*******
**** **** ***** ****** ***********, ******** SD **** *******, *** ******** **** *** playback ** *****, **** *** *** a ***-*** '*** ** *** ********' that ** **** **** *************. *******, despite *** **** *** ********, ***** the ******** **** ***** ** **** IP *******, ******** ** ***** ** and ** ****** *******, ** ** still ******* **** *********.
**** ****** ********* * ******** * premium ***-*** ********** ** * ******* price, ***** ****** **** **** *** more ***** *********** ****** ******* ***** partners ******* *** ********.
**** ** *** **** **** *** those **** *********** **** ****** *****, ** **** *** *** ******** AVHS ** *** ******* *********** *********, easy ***** ****** ***** ** *** equally ********* *** **** **** **** Camera *********.
Technical *** ********
****** ********* *'* *** ***** ****** ******** worked **** *** **** **** ******* and ******** (**** ******* ** ** network *****), **** ** ****** ***** ********. These ******** ******* ******** *.** *** up, ********* **** ***** (*+ *****) cameras *** ************ ******, ****** ***** may ***** ** ********** *** ****** access ***** **** ********** ** ****.
***** *** ********** *** ******* ** (required *** *****) ** ***/******* ****** apps. No *** ****** ** ****** *** OSX ****** ** *********.
**** ******* *** **** ********* *****-*********, which ******** **** *** ******* ** high ******* ******* ** ***** * second **** *** ****** *** ****** in * ****** ******, *********** **** time ***** ** ******** ********.
*** ******** ** *, *, **, and ** ***** ********** ** ************* **** (thumbnail ******) ******* *** ***** ******* of ******** **** ******** ****** ********* versions, ***** **** **** ** ****** back/forward **********.
Positioning ******
**** *** ******** ** **** ***** access, **** *** ******* ******** ****** Companion's ***********:
*******, ** ***** *** **** *********** not ***** ** ******* *** ********* or **** *** **** ****/**** ***** many ******** ***** *** **** *******:
SD **** ***********
**** ***** ******** ** **** ****** Companion ***** ** **** ****** ********* in **** *****. ** ****** ****, Axis ******** *"************" ** **** ** *********** **** Sandisk. ***** ***** *** ********** ********* and ********* ** ****.
**** **** **** ********** ******** ************ aimed ** ********* ** **** ****/***** failures ** ****** *** ** ******** to ***** ****** ******** ******* ** video *** ****.
** **** ***** ******* ***** ** cards ** *** ******* (*** ****** recording, *** **********), **** ** ****** so ***. ***** ********** *** **** durations *** *** ***** ** **** definite determinations ** ** *******, *** ** will ****** *** ****** ****.
Remote ******
*** **** ******* ***** ******** *.** or ****** *** ********* *** *** cloud ** ****** ******* ****** ****** on ** ****** ********* *************, * single ********. ******** **** *** ******** and ******* ** **** ****** ***********, simply ***** "**** ****** ****** ********", though ***** ** *** **** ** (nor ****** **** ** **** *****) configure ******** ** *** ****** ******.
**** **** ******* *** *** ************* available ** *******, *** ***** *** disable ********** ******* ** **** ** not **** **** ** ** ******** accessible. ******* ***** ******** ***** **** 5.50 *** ***** ** ******** ********, but **** *** **** ** ****** port **********. **** *** ******** ************ on *** ** ******** ****** *********** cameras ******* *** ******** ****** *****. *** **** ** *** ********** behind **, *** **** ****** ****** ****** whitepaper [**** ** ****** *********].
** ***** ** ****** ** ****** access ***** ** *** *****, **** all ********** ******* ****** **********, **** no ***** ********.
Account/Site *****
****** ********* ***** **** *** *** into *** *********** ***** * ****** account (**** ** ******). *** ***** and ******* ******* ** ********* *** then ***** ** **** *******, *** accessible **** ***** ******* ********. **** **** sites ****** ** "******", *.*., ***** users *** *** ****** ** ******* via ***** *****. ***** *** **** to * ****** ****** *******, ****** a ****** ******* *** **** **** sites.
**** **** *** **** ***** ********* roles (*****, ********, ******) ***** *** differentiated **** ** ********. ** ******** is ******** ** ***** ** *** site, **** ********.
** ****** ******** *** ***** ** this *****:
Live **** ************
*** **** ****** ** ****** ********* 3, ***** **** ****** ****** *******, is **** **** ******* *** **** multi-streaming. ******* ****** ** *** ******* **** in ******* "*********" *******, *** ************* switch ** *** **** ****** **** enlarged. *** **** **** ******** **** switching ******* ******** ******* *** **** eliminated.
Search *** ******
*** **** ******* **** **** **** to ******:
This is not good news for those left selling Axis AVHS hosted video, as Axis has now stripped AVHS of its biggest competitive advantage, easy cloud access which is now equally available for free with Axis Camera Companion.
Isn't the advantage of AVHS that the video is stored in the cloud, as opposed to SD cards? So therefore possibly better functionality, performance and reliability?
Did people buy AVHS because port forwarding was too hard?
The most compelling buying point we have seen is easy cloud setup / access. Same reason why Dropcam did well, especially considering 60% of the people who buy them do not buy any storage.
So yes, 'port forwarding was too hard'. However, your question is a little like a carpenter asking "Why would anyone buy a bookshelf at Ikea?"
I thought people who bought AVHS were people who wanted/needed hosted (off-site) video, not people who just wanted to get to their own cameras thru the Internet. Admittedly this was an assumption made because that's the main value I saw in the offering.
Do you expect a significant number of AVHS subscribers to drop the service now that they have an easier way to phone home?
AVHS is sold through partnerships, so the key question is what will they do. The reality is AVHS has been on a slow boat to nowhere for years, so it's not as if things were awesome until this (the most famous one being EMC Dumps Axis VSaaS). However, this hurts AVHS because at least Axis could tell the remaining AVHS partners that at least AVHS was the only offering that provided cloud access. Now that's gone.
Even when Camera Companion first came out, AVHS partners were nervous then. Whoever is left should not be happy about Camera Companion significantly cutting the gap.
Axis more recently emphasized AVHS positioning towards multi-site users, which Camera Companion still does not work for. Of course, there are lots of strong competitive products in that market. Lastly, unless Axis is keeping AVHS developments real quiet, it does not seem like the product / service has gotten much better in the past few years.
All of this is really not very important, in the big picture. Axis still needs something that is a legitimate competitor to Chinese low-cost offerings. These improvements make Camera Companion better, but the high price of Axis camera and the ~$90 price tag for SD cards, makes that cost gap still steep.
I would be nice to see a comparsion between Axis Camera Companion and Hikvision's EZVIZ
A related discussion here: http://ipvm.com/forums/forums/video-surveillance/topics/6562
Do the cameras connected within camera companion have to be on the same subnet? I would like to install this on a PC in our server room so the tech on site could view (not playback, just view) numerous network closets and critical doors at once.
No, they don't. I have a couple of cameras on a different subnet added and it works fine. Network storage may be a bit of an issue, as my standard network shares wouldn't connect across subnets, but local storage works fine, as does live viewing.
Hi I want to add my two cents.
1) First, as mentioned you need first a computer to setup the "site" for the first time, so you need to have a computer. no big deal, but to be clear. It is not possible just using your cellphone's application.
2) In case your customer doesn't have internet, you will NOT able to create/configure the "site". Since its requiere that you logging with a email account, wich will requiere also you to have a email for/from your customer, eather using your customer personal/bussines email to creat an account on Axis.com or you will need to create a separate email in order to create one account at Axis.com for that particular customer.
Even after creating the site, if you want to add another PC or Mobile device to access the cameras, you need internet connection again since the Companion software ask for your email and password to logging the first time. or you could export the site configuration to a .accs file then import in the new pc want to add.
Still is a easy sytem to configure, well designed and good look and feel application and allow outside network access wich this days is a must. and is Free.
We have found that the program automatically reaches out and attempts to upgrade the firmware of all the cameras that it touches. Is there a way to prevent this?
Ross, it updates firmware when you first connect, but it doesn't try to automatically push updates once things are running, correct? This is off the top of my head.
I don't know of a way to stop that, but I'll ask Axis for comment.
Thanks Ethan. Our concern is that if it forces firmware updates it could be an issue with our normal OnGuard VMS. We would like some of our smaller plants/showrooms/stores/etc. to use camera companion and we could log in to each from here in our Ops center. I just don't want to put the program on our Ops center PC's if every time an operator logs in to view something it tries to update firmware on our local cameras that are in OnGuard. Hopefully that makes sense!
About remote access:
"2. Axis solution to remote access Axis Secure Remote Access makes it possible for a smartphone or PC client to access Axis network cameras when the client and the cameras are located on different local networks. Using external mediator servers1 , the client and the camera can find each other and establish a secure peer-to-peer connection. As a fallback the communication is automatically relayed through the mediator servers, when direct communication cannot be established."
From: http://www.axis.com/files/whitepaper/wp_remote_access_63636_en_1504_hi.pdf
