CastleOS - new home automation software with Kinect voice control

[ChrisCicc]

I'm notoriously bad with release dates. Definately need to work on that! But the good news is it's all caught up and launched now. We're taking the initial feedback we've received, tweaking the messaging a little bit, and will be putting the Kickstarter live in a day or two...

 

[ChrisCicc]

Just a quick update for everyone...
 
CastleHUB Kickstarter
 
Only 5 days left on the CastleHUB Kickstarter! If you haven't reserved yours yet, now is the time! https://www.kickstarter.com/projects/506540480/castlehub-universal-smart-home-intelligence-by-cas
 
New Protocol Support
 
We've promoted TCP Connected devices from the "will support" to the "is supported" category! For those of you trying CastleOS on your home PC while awaiting your CastleHUB, feel free to try out the TCP smart bulbs with CastleOS! (As a personal note, we do find the quality of light the TCP bulbs produce to be on par with other high end bulbs.)
 

 
App Updates
 
We've also released a major update to the CastleOS app's graphic design. This isn't a render - it's in production now and you can download it today. We've replaced static image buttons with interactive and touch sensitive switches.
 

 
The new switches more clearly indicate the current state of the device (on/off), are animated, load faster, and look a lot cooler and more modern, if you ask us! They also work across all your mobile devices, no matter the brand or OS!
 
Amazon Echo
 
Many of you have asked about Amazon Echo support, so we wanted to pass along an update on that.
 
Use it Today
 
Currently, Amazon has released support for Belkin WeMo and Philips Hue devices. You can verbally give the Echo commands that will adjust the state and brightness of the various WeMo and Hue devices. We expect Amazon will soon roll out more support for UPnP smart devices as well. While these commands are not issued to CastleOS directly, CastleOS does monitor all the changes to the status of each device. In other words, CastleOS knows if you've adjusted a device via the Echo, and can act on that information, for instance by using it as an event trigger for a stored event. The benefit of using both together is that CastleOS and the CastleHUB fills the gap between what the Echo provides, and what's need for a full automation system. The Echo is great about translating a speech command to the device, but it does not have an intelligence built into it. It cannot follow up the command with new actions, kick off scenes or events elsewhere in the home, etc. Pairing it with CastleOS accomplishes this. In practice, this means you can use the Echo fully with CastleOS today, however only with WeMo and Hue devices.
 
The Future
 
When Amazon releases the full API for the Echo, we'll be launching support for interfacing with the entire CastleOS system, similar to how we currently do with the Kinect. Until then, feel free to use your Echo with WeMo, Hue, and more!
 
Thanks everyone!!

 

[pete_c]

Yeah here waiting with the Echo still in the box on my desk.  I like the monolith look of the box.
 
When do you think Amazon will release the API?  
 

 

[ChrisCicc]

Yeah here waiting with the Echo still in the box on my desk.  I like the monolith look of the box.
 
When do you think Amazon will release the API?  

 
I'm not even sure they know. 

 

[BobS0327]

Chris,
 
Out of curiosity, does your product support the following?
 
1. Leviton HLC UPB switches
2. DSC hardwired interior motion detectors
3. Optex hardwired exterior motion detectors
 
I currently have a Leviton S&A Omni Pro II controller installed and I'm looking at potential replacement options. My current system does have the above hardware. So, I'd like to retain my substantial hardware investment by being able to migrate most of my hardware to the new platform.
 
I can understand your concern for not using the cloud as to storing sensitive information at a remote location. But that appears to be one small aspect of the cloud. There are other features of the cloud that can be utilized in a smart home environment. For instance, Software As A Service (SAAS) cloud service. An example of SAAS would be CCTV camera facial recognition. Voluminous data would be sent to the cloud from the camera to be processed by a system like MS's Azure which would probably be loaded on remote cluster computers. The heavy duty processing would be done by Azure and the results would be returned locally.
 
Another example would be the use of Platform As A Service (PAAS). I could envison using MS Azure in conjunction with SQL Azure to store and analyze real time medical data (vitals) for a group of senior citizens living in a household. Data would be coming from IOT devices such as implanted devices etc. Data mining could be used to predict serious medical events etc.
 
I honestly cannot understand why anyone would want to send a command to the cloud and back to turn on a kitchen light. But I see a real demand for using the unlimited resources (SAAS, PAAS, IAAS etc.) which will become available to perform beneficial advanced smart home tasks..
 
In spite of the cloud security issues and concerns, I sincerely believe that the cloud is the future of the smart home. I want to be able to utilize the vast cloud resources as a smart home technology user. Thus, cloud access is a very real requirement for me.

 

[wkearney99]

I disagree with the notion that cloud access is 'essential'.  Most of what I've seen thus far has been an attempt to avoid making the devices themselves (the software on them) robust enough to actually work in a disconnected state.  It's a lot 'easier' to make just a dumb client than it is to make a fully implemented set of features in an embedded device.   Witness the recent debacle for Wink devices.  Even with the device being a client they still couldn't properly manage it.
 
I love the idea of being optionally able to use network resources with an automation system.  But I entirely reject the notion that network resources be REQUIRED for even basic functionality. 

 

[pete_c]

Personally I think that cloud access / use will be necessary for those wanting the easy button automation and primarily sleep with their phones at night. 
 
Much yut today do not know what an LP record album is or even a music CD. 
 
Today yut mostly only know what the internet is via their tablets or phone; well its just an easy button spoon feed methodology of automation; works for them.
 
Yesterday I was a chauffeur for my wife.  I took a tablet with me as I had to sit in my automobile for periods of time.  I turned it on, did my doo of what I wanted to do while waiting; then shut off the tablet when I was done with it.  (well too my car pc's are connected to the internet but the HU is smaller than my tablet)  (IE: tablets/portable phones here typically stay in the off mode unless utilized).   
 
The whole idea of spoon feeding automation providing a simple solution without nary a thought about it does nor do they care these days.

 

[wkearney99]

And are you talking 'yut' in the 'My Cousin Vinny' sense?  Heh.
 
It's one thing to have 'external access' to your home automation.  It's another thing entirely for a vendor to do such a shitty job of the software on an embedded device that they HAVE to use network servers to carry their sorry asses.  Calling it the 'cloud' is just bullshit.  Something in your house out to be able to run reliably and standalone while having the option to provide external access.  
 
Now, the next question is ask is what else is the vendor doing with the usage data when forcing you to use a network server?

 

[pete_c]

Yut really was just a pronounciation of youth based on a Brooklyn, New York dialect.  (no disrespect here).
 
I never heard it being used in the midwest until I saw the movie. 
 
Today googling it  (slang?) shows that it means young urban terrorist.  Huh?
 
Unrelating to the "cloud" thing....
 
I personally think this yut coddling has gone too far. 
 
I recall just doing my chores; really not getting much in weekly stipend and never complaining. 
 
Many years ago my son attempted to negociate his chores and lost plain and simply because I was da boss. (well his father).
 
Most parents today do worry about being sued by their children while there is too much coddling going on.  After all it is the easy button solution; why work?
 
Unrelating to eggs (well now added them to my staple of 7 shots of Espresso every morning...)...googling the word coddle...
 
Full Definition of CODDLE -  transitive verb
To treat with extreme or excessive care or kindness :  pamper <accused the court of coddling criminals>
 
Relating to the cloud thing...
 
The whole cloud thing is a win win money maker; after all you do pay for the transport being on 24/7 whatever mechanism it is using and you pay for something that you should be paid for...well how easy is that to do these days.... :blink:
 
Well too relating to the OP; what is the best way to coddle your customers?

 

[ChrisCicc]

You guys are really highlighting the cloud concerns very well! A lot of the startups are going cloud based. There are several reasons for this. First is there is a low barrier to entry with a cloud service. Rent a server, license a wifi module, hire a couple devs, and voila! 
 
The reality though, as many companies especially Wink are learning, is that the cloud brings with it more complexities than immediate benefits, save one: the data.
 
I can say with confidence that the potential value of the data is behind the valuations of half the startups out there. Even companies like Lowe's value the data more than they do the hardware sales, and have no problem publicly stating so (though they are learning real fast of late that without enough customers, the data isn't very valuable). 
 
So how do we manage the balance? As Pete asks, how do we coddle to customers who want the most dead simple setup as possible, while still providing the capability and power of a full, true, home automation system? How do we coddle to investors who want revenue from data, while balancing customers who demand privacy and security? 
 
The first thing customers demand is support for their devices. When a customer has accumulated enough devices, and enough apps to control them all, eventually they'll seek one unified system with a unified app. So the very first thing to do is make sure your system supports every device that is practical. I know Wink has lost more than a couple customers to CastleOS because of lack of device support - they tried to run with the closed ecosystem, and while it works for some customers, it certainly doesn't for all, and I personally believe everyone will eventually outgrow it and demand a more powerful system.
 
The second thing customers demand is for it to be as close to truly plug and play as possible. Most protocols and devices can be auto discovered, and those that can't usually don't need more than a button press for linking. We leverage that as much as possible, along with removing any notion of the "spreadsheet" interface from our UI, to provide a very simple to use system that works with as many devices as possible.

The third major customer demand, though admittedly less so with millennials (though I'd like to see if that changes when they have families and careers), is for data privacy and security. CastleOS is already as good as can be in that regard, our users already own and control all of their data. However, there are uses to bringing some of that data into our cloud that benefits us and our users equally.
 
For instance, one of our primary marketing phrases is we're turning our homes from something we "live in" to something we "live with". To do that requires more than the remote control that is typical of "automation" today, it requires more than even the most automated of automation today. It requires machine understanding of our environment. That's why we're working with Microsoft to leverage their machine learning technology, and other technologies, to take our homes to the next level, and be ready for the sensor-driven future of automation. 

But to do that, we need to suck some data up to the cloud for processing, so customers will have to opt in. All the command and control will still be local, and all your records stored locally, but we'll also be able to process what's happening concurrently, and provide advanced functionality based on that. Likewise, we'll also be able to process the data en masse, anonymize it, and resell it as is useful to industry partners. We have no problem being open and honest about that it, it's a win win for everyone involved. 

It's funny, the home automation industry is probably a good 25-30 years old now. Yet in almost all regards, we're still at the very beginning of what is possible. The next evolution will be lead by powerful, intelligent, software leveraging commodity hardware and sensors, and I plan for CastleOS to lead the charge! 

 

[ChrisCicc]

Chris,
 
Out of curiosity, does your product support the following?
 
1. Leviton HLC UPB switches
2. DSC hardwired interior motion detectors
3. Optex hardwired exterior motion detectors

 
Hey Bob! Your UPB switches should be good to go. The hardwired switches would need to be wired into something like the ELK, or your existing OPII. Both of which are in our dev plan, but not yet complete. Sometime later in 2015 both will be ready to go, with the ELK likely complete first to be honest, sometime this summer. 

Let me know if you have any other questions!

Thanks!!

 

[ChrisCicc]

Since this is the main thread I realized I never posted the announcement about the new freemium model here, so here it is:
 
"We're happy to announce CastleOS v1.3, which includes a new free-to-use tier! This means CastleOS is free for use with up to 10 smart devices. CastleOS can grow with you as you build out your smart home!
 
After ten devices, you can purchase a license at any time to unlock unlimited device support, or upgrade to the CastleHUB. Combined with our expansive protocol and device capabilities, CastleOS can support any size smart home and many commercial installations!
 
In addition, our 30-day unlimited device trial remains for those with existing systems they'd like to test with CastleOS during the trial mode. Whether you're just starting out, or looking for a more capable controller for an existing system, CastleOS is able to support you!"

 

[ChrisCicc]

This is an informal (unlisted) video I recorded last night of the latest Hue voice commands you can give. This is just a sampling...
 
https://www.youtube.com/watch?v=CmNGt4tND64&feature=youtu.be

 

[LarrylLix]

But I like green...ohh sorry...they are Hue bulbs... :rofl:

 

[ChrisCicc]

But I like green...ohh sorry...they are Hue bulbs... :rofl:

 
Want green? We can do green Dark Green. Light Green. Dark Olive Green too. How about sea green, spring green, pale green, or lime green? Let's not forget yellow green, medium sea green, medium spring green, and lawn green, either. Oh and there's always green yellow and forest green, too. 

I think I got them all...