Comment Re:A better product is.. (Score 1) 102
It is a Sheevaplug under the covers, but it's not designed to be user customisable product as in the users can login and do things in the OS. It's not using OSGi. It's a standalone appliance (Black box). However, we have designed it to be very flexible. There are several different types of inputs that a user can provide to the box as events
* X10 events from wireless PIRs
* HTTP events as in a user can define button groups and button titles and then we provide a link that will provide the user with a page of buttons on the smart phone that send the events they have defined
* I/O events from a phidgets 8/8/8 interface card, which can be used as physical button events or outputs from an existing alarm system can be fed here for example
* Scheduled events. You can setup events that will fire regularly into the system, as in a calendar
* Network camera input. This is continuously monitored and one of the other events can trigger capture of one or more cameras. The user can specify the capture to start in the past so you can see what happened before the event was triggered. For example, 5 seconds before the user triggers the PIR so that you can see the intruder traverse past the PIR.
the device then provides flexible event processing where you can trigger many output events, along with a lot of qualifiers, such as time of day constraints, the presence of certain "state" (Which can also be added by the event processing engine) and finally it then triggers the output events, these include:
* X10, i.e. switch on/off/dim appliances or trigger the X10 alarm module
* I/O trigger on/off of a port on the phidget 8/8/8 or send a custom defined pulse train
* Send an E-mail event. This contains the name of the event and links to any video that triggered by the event (Viewable as either mjpg or pseudo mjpg which is viewable on Android or Windows 7 phones)
* Send an SMS event, same as an E-mail event, except via SMS
* Sent a custom HTTP event. The user can setup key/value pairs of parameters and a target url and method. This provides a very easy to use gateway facility to your own application.
* Trigger video capture of one or more video streams.
The freaks can be linked together. For example, one freak could send an event to another freak across the net so that the remote freak can turn on a panic light for example. In addition to whatever other output events are triggered locally. They are also linked for video capture, so that one freak can trigger the video that is being captured on a remote freak and we provide a webpage that will provide you with a synchronised and merged view of the video that is captured across a specified "slice" of video cameras you have chosen across your collection of freaks. This is also good for a neighbourhood watch scenario, where you have a PIR sensor at your place, but your neighbour places the camera on their window sill where it can see you place. When someone enters your place, you can an SMS with "guest video" from your neighhour where his camera can clearly see the intruder enter your place. When you combined this with the video buffering you could see the person enter your place even if the sensor was not triggered till several seconds later.
Once a capture period has been captured, the system encodes this into WebM video, which is great for remote viewing of large format video sections, saving events. The video that is captured is instantly playable even as it's still capturing, so you can view the intruder within seconds of the intruder triggering the sensor.
A description just doesn't really do it jusfice, but we will be preparing some video of it's operation that we will put online when we are closer to releasing. That and additional documentation, examples of use etc. Right now we are working hard to try and get it in the shops so to speak within the next two months.