5 ms·
So... A problem here - there's a lot of startup in the home automation space right now. I've been using MiCasaVerde for over a year now and it's awesome. Ful
by windexh8er 14y ago
So... A problem here - there's a lot of startup in the home automation space right now. I've been using MiCasaVerde for over a year now and it's awesome. Fully controllable and configurable via the MiOS GUI, or hack it to your heart's content via Lua scripts. The awesome thing is there's plenty of devices you can buy OTS right now whether Z-Wave (built-in) or Insteon (add-on USB adapter). What confuses me about what NinjaBlocks is trying to do is - they don't cater to anyone who already HAS home automation... Meaning: I'd buy it for $200, but they don't say what I can integrate with. I'm not going to spend another grand on switches, dimmers, motion detectors, locks, etc. if I don't know I can reuse my investment. That's a big part of why Spark is not a good option IMHO (http://www.sparkdevices.com/ http://www.sparkdevices.com/) - because they're using 802.11 WiFi (I don't want my home automation components on Wifi for a variety of reasons, but the first two are: 1) WiFi doesn't have a low-power advantage like ZigBee, Z-Wave, Insteon, etc. and 2) WiFi doesn't automagically create a mesh network for auto-routing and network extension).
Then you have a startup like SmartThings (http://smartthings.com/ http://smartthings.com/) that's just reinventing the wheel, creating a pretty iOS interface, and then trying to charge an outrageous amount for a monthly service - something MiCasaVerde doesn't do. So, at the end of the day would I use SmartThings? I'd like to - but I won't because I don't want to pay $120 a year for something I can run better in my own infrastructure. I don't want you selling my energy usage data or knowing if I'm home, with something like MiCasaVerde - I can choose not to use their cloud proxy to control my home.
If anyone is listening who's designing home automation and wants to cater to people who are looking at building a service to deploy these types of automation to the masses you need to do it right. Baby Boomers, at least the majority of them, will think all of the above are too complicated, so they're going to want someone to install and maintain this for them. There's a huge middleground that needs to be solved here and unless SmartThings and others are going to provide a service, that $10/month is not going to be justified.
Back to NinjaBlocks, please answer the following:
1) Monthly fee if I use your cloud proxy to hit the controller? If so - how much?
2) If #1 is true - is the API directly accessible on the controller - or are you locking me in?
3) Low power integration (i.e. ZigBee, Z-Wave, Insteon, etc.)? Answered my own Q: No... From (http://help.ninjablocks.com/customer/portal/articles/692139-what-rf-devices-can-my-ninja-block-talk-to- http://help.ninjablocks.com/customer/portal/articles/692139-...): "The original Ninja Block comes with a RF 433.92 Mhz (433) dongle and future Ninja Blocks will have this baked in. 433 is awesome because you will find it in all sorts of low-cost battery powered devices, its range is pretty good too. That said, its not all sunshine and lollipops - there are good reasons its considered "low-tech" - only one device can "talk" at a time, labelling is appalling, all protocols are proprietary. So not everything will work out of the box, but a lot of stuff will. " <<<<<----- Sorry, but this sucks, I'm out. You need to have a real and baked solution besides this 433Mhz junk that's not mesh, and has zero security baked in. There's no way I'll pay $200 for this with zero long term scalability or security in mind.
Again, another pretty solution that's just a toy. For my money I'd go with SmartThings - but for the long term I'm sticking with my MiCasaVerde (http://micasaverde.com http://micasaverde.com) setup - cost feasible and fully in my control and no monthly costs. Until someone can come to the table with that I'm better off building my own interface.
- onethumb 14y agoLots of good questions here, but I think the critical question is whether it's compatible with any of the other emerging standards like Z-Wave. Can someone from Ninja Blocks weigh in on this? There are a ton of Z-Wave components I'd love to mix in here.
- windexh8er 14y agoIt's not (see second to last paragraph - Q #3, and answer follows from the NinjaBlocks site). Z-Wave and Insteon are the defacto standard, if it doesn't support it - it's not going to fly. I'm guessing they didn't want to deal with licensing. And, Z-Wave isn't emerging - it's been around for quite a while. It's not perfect (most low power mesh wireless networking standards have their flaws), but what NinjaBlocks has chosen to implement is not something you want in a system you depend on. Insteon has the advantage of wireless plus being able to operate over powerline (i.e. your home power distribution).
- onethumb 14y agoThat page appears to be a few months old and they hadn't actually built / shipped any "new" Ninja Blocks, so I'm hoping things have changed. :)
- windexh8er 14y agoThat page is also linked from the OPs original post under "Where can I get additional sensors?" - so I'm guessing that information is correct. Since it's the only information available, I'll treat it as such until they provide more details otherwise. It's a bummer - I've gotten my hopes up for a few platforms as of late, all have been let-downs in their own way.
- askpete 14y agoHey @windexh8er, from the sounds of it you are already well automated! I'm not sure how much NB offers you today, however ... Ninja is ultimately (read: not yet) a meta-platform for connecting stuff. As you point out, there are plenty of different approaches and technology with advantages/disadvantages. We think the thing what is really missing in the landscape today is interoperability. Say you want to give access to your security system's motion detectors to a third-party app that helps you save energy, that is nigh on impossible with an OTS offering. That kind of thing is exactly what we enable (albeit a little crippled) today. Its early days and we have a metric-shiton of stuff to do, some of which includes: * making the webservice fully or partially optional - current cloud driven architecture is for expedience * supporting lots more sidebands than just 433 - again chosen for expedience and cost. Z-wave is better, no doubt, but its not really justified in the mega premium per device i.e. $70 for z-wave PIR vs ~$15 for 433. BTW we have proof-of-concept support for Zigbee Light Link via a USB dongle on a block. * publishing a public repository of local modules to make it easy to wrap (and share wrappers) for proprietary/lan based offerings (think wemo, philips hue, etc) Another thing to note is that we are a hardware company by necessity not choice. You can run our (node.js) client on an RPi, beagle bone, media centre pc, etc. Anyhoo, I digressed. We hope to have something that you can get excited about one day in the not too distant future ;)