Chris Cicchitelli Administrator Posts: 3390
1/3/2013
|
This is an open thread for suggestions of new devices and protocols for CastleOS to support. Please add your suggestions with a reply below, we'll continually update this post with a running tally of all suggestions. Suggestions thus far:
Device Suggestions: Radio Thermostats GlobalCache IR Controller
Protocol Suggestions: Z-Wave ZigBee
|
|
+1
link
|
Jason L. Posts: 4
1/29/2013
|
Chris Cicchitelli wrote: This is an open thread for suggestions of new devices and protocols for CastleOS to support. Please add your suggestions with a reply below, we'll continually update this post with a running tally of all suggestions. Suggestions thus far:
Device Suggestions: Radio Thermostats GlobalCache IR Controller
Protocol Suggestions: Z-Wave ZigBee I want to add support for the z-wave suggestion (hopefully helping bump up its priority?). While I have the kinect and server hardware needed already, z-wave integration/full support is a MUST for any HA purchase (CastleOS for example) I make going forward.
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
1/29/2013
|
Jason L. wrote: I want to add support for the z-wave suggestion (hopefully helping bump up its priority?). While I have the kinect and server hardware needed already, z-wave integration/full support is a MUST for any HA purchase (CastleOS for example) I make going forward. It's our top priority! We just have to finish the beta process with X10 and Insteon, and next up will be finishing Z-Wave integration! We're hoping to have it complete in February.
|
|
+1
link
|
Aaron Romine Posts: 3
2/4/2013
|
Support the Smartlinc 9761 port.
I don't know if I speak for a lot of people, but I know my gateway drug to Insteon was the starter kit at Best Buy (includes a Lamplinc, range extender, and Smartlinc 2412n). Since I started with the Smartlinc, i've been trying to get a more intelligent system to automate. One of the things about the smartlinc is it includes an undocumented port on 9761 which is basically a TCP enabled PLM interface. I have used a virtual COM port to use this port for communication using houselinc and even been trying CastleOS (although after a few hours it appears to stop working). I know a few other products (including Power-Home, and QWHomeAutomation support this interface)
For those who want to investigate your software, having support of a 'starter kit' can really help kickstart adoption. I know a PLM is only about $80, however for many who want to 'try' home automation, this could be the killer app. I am going to continue to hack around with my smartlinc and see if I can get a stable connection via virtual COM port driver or write my own client-proxy (I'm a .NET dev).
Having solid support with the Smartlinc would make me feel a lot better about investing in an Xbox Kinect to try this system (I do not own an xbox). Otherwise I'm still about $160 away from just communication with my devices (PLM + Kinect). Think of it this way: if you want people to get started having $90 Kinect + $100 Insteon starter kit - it allows users to get up and running with 'Computer - Lights on' for under $200.
Cheers! edited by aarondr on 2/4/2013
|
|
+1
link
|
Mack McDowell Posts: 27
7/10/2013
|
Support for Security systems like DSC or ELK.
Almost all of the Home Automation software available on the market has some way to interface to home security systems whether the feature/capability is integrated, by plug-in or virtual device doesn't matter, but having the ability to do it one way or another does. Thanks Mack
|
|
+1
link
|
Bryan Gauvin Posts: 1
7/19/2013
|
iaqualink pool controll. Would love to switch to SPA mode when I launch a scene.
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
7/19/2013
|
Bryan Gauvin wrote: iaqualink pool controll. Would love to switch to SPA mode when I launch a scene. Thank you for the suggestion! We'll take a look at iaqualink! Pool control is on the roadmap. Thanks again for your interest!
|
|
+1
link
|
Alexis Zenios Posts: 1
7/23/2013
|
Any update on Z Wave support?
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
7/24/2013
|
Alexis Zenios wrote: Any update on Z Wave support? Will arrive in the beginning of August!
|
|
+1
link
|
Maninder Singh Posts: 1
7/28/2013
|
Are you looking at adding http support so that we can trigger other IP based devices?
Thanks
|
|
+1
link
|
Joseph Brandenburg Posts: 1
9/3/2013
|
When Zwave support is finalized will you be requiring a Zwave dongle on the server? I already have a Veralite.
Also, per our brief discussion months ago, is there an option yet to allow simple http get or post commands to be sent by issuing voice commands? This should actually be much easier to do than most of what CastleOS already does, but I don't see the option yet.
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
9/3/2013
|
Joseph Brandenburg wrote: When Zwave support is finalized will you be requiring a Zwave dongle on the server? I already have a Veralite.
Also, per our brief discussion months ago, is there an option yet to allow simple http get or post commands to be sent by issuing voice commands? This should actually be much easier to do than most of what CastleOS already does, but I don't see the option yet. Yes and yes! Both should be available this month.
|
|
+1
link
|
Lawrence Morrisson Posts: 7
9/10/2013
|
I'd like to see support for accessing and controlling the Nest thermostat please.
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
9/10/2013
|
Lawrence Morrisson wrote: I'd like to see support for accessing and controlling the Nest thermostat please. Unfortunately we cannot do that. Technically, we could code it up in a few hours. But as soon as we launched it Nest would have their lawyers instruct us to stop doing so. Nest has already done this to others in the industry, including the largest players. Sorry about that! Maybe send Nest an email, encourage them to change their mind?
|
|
+1
link
|
Lawrence Morrisson Posts: 7
9/11/2013
|
Chris Cicchitelli wrote: Lawrence Morrisson wrote:
I'd like to see support for accessing and controlling the Nest thermostat please.
Unfortunately we cannot do that. Technically, we could code it up in a few hours. But as soon as we launched it Nest would have their lawyers instruct us to stop doing so. Nest has already done this to others in the industry, including the largest players. Sorry about that! Maybe send Nest an email, encourage them to change their mind?  Well that sucks  I might email them. Could you not provide a way in your product to allow third-party enthusiasts to write plug-ins themselves? Include some sort of framework or API? This would protect against those sort of lawsuits. Mi Casa seems to have a system such as that and I notice it does already have a Nest app that somebody has written (though I have no idea how well it works). I did read somewhere else in your site or blog that you had decided against that at some point, but I figured I'd raise it again to see if you had thought or would think more about it. One of the counter arguments to doing it was to ensure everything remained smooth/easy/cohesive in the interface and worked perfectly in order to retain a good user experience. This is certainly a worthy goal but I am sure you could think up a way to keep that. It could be governed by the capabilities of the API. Perhaps the module could be a separate service or component that was accessed in a slightly different way but could hook into the core services with a finite and tightly controlled set of instructions. Of course, I can certainly understand and agree that it might pose certain challenges but I am sure with the coding ability you have already shown, there could be a sweet spot that both you and your customer base would be happy with. I am quite sure making something like that open that people could plug into would really accelerate the interest and fame of this product. edited by lozman on 9/12/2013
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
9/20/2013
|
Lawrence Morrisson wrote: Chris Cicchitelli wrote:
Lawrence Morrisson wrote:
I'd like to see support for accessing and controlling the Nest thermostat please.
Unfortunately we cannot do that. Technically, we could code it up in a few hours. But as soon as we launched it Nest would have their lawyers instruct us to stop doing so. Nest has already done this to others in the industry, including the largest players. Sorry about that! Maybe send Nest an email, encourage them to change their mind? 
Well that sucks I might email them.
Could you not provide a way in your product to allow third-party enthusiasts to write plug-ins themselves? Include some sort of framework or API? This would protect against those sort of lawsuits. Mi Casa seems to have a system such as that and I notice it does already have a Nest app that somebody has written (though I have no idea how well it works).
I did read somewhere else in your site or blog that you had decided against that at some point, but I figured I'd raise it again to see if you had thought or would think more about it.
One of the counter arguments to doing it was to ensure everything remained smooth/easy/cohesive in the interface and worked perfectly in order to retain a good user experience. This is certainly a worthy goal but I am sure you could think up a way to keep that. It could be governed by the capabilities of the API. Perhaps the module could be a separate service or component that was accessed in a slightly different way but could hook into the core services with a finite and tightly controlled set of instructions.
Of course, I can certainly understand and agree that it might pose certain challenges but I am sure with the coding ability you have already shown, there could be a sweet spot that both you and your customer base would be happy with.
I am quite sure making something like that open that people could plug into would really accelerate the interest and fame of this product. edited by lozman on 9/12/2013 We do plan the ability for custom plugins to be written. Right now we're prioritizing adding centralized features, but we'll get to it! Stay tuned!
|
|
+1
link
|
B Posts: 79
9/20/2013
|
|
|
+1
link
|
Chris Cicchitelli Administrator Posts: 3390
9/20/2013
|
Brian Klavetter wrote: Hello,
Would it be possible to add DIRECTV SHEF protocol to CastleOS so that directv receivers could operate by voice? Noticed that Indigo has a plug-in for it. http://www.perceptiveautomation.com/wiki/doku.php?id=plugins:directvdvrcontrol Hmm, that's interesting. I'm not immediately familiar with SHEF, but at first glance it doesn't look too complicated. I'll get back to you, thanks for the suggestion!
|
|
+2
link
|
Frank Dracman Posts: 194
9/22/2013
|
Hi, is support for the Samsung smart tv on the road map?
|
|
+1
link
|
oneklakes Posts: 30
10/4/2013
|
Hi Chris,
I'm requesting support for the Insteon Smoke Bridge. This is the device made by Smarthome that connects First Alert smoke detectors to the insteon network so alerts can be sent via SMS & email when the detectors are triggered. I'm hoping this will not take a lot of work since this should be similar to the Insteon leak detector which you already support.
Thanks again for an awesome product.
oneklakes
|
|
+1
link
|