Since we introduced a ZigBee wireless version, a lot of interesting conversations have ensued including between Mike and I. Why ZigBee, why not Bluetooth?
Along they way I found another interesting and successful project on Kickstarter called the Almond+ that will support ZigBee. Its a router moving into the home automation space and it very low cost and open. I have since contacted them to get an understanding of what profile they intend to support.
Back to ZigBee and Bluetooth Smart (4.0, Low energy).
I'm not going to try and mention all the pros and cons of each wireless technology but I will focus on what decisions we as a device developer have to consider when deciding a direction.
One benefit of ZigBee is inter-operability between controllers if the controllers support the ZigBee Home Automation Public profile. This pretty much guarantees that ANY clogged filter device will work with a controller BUT ONLY IF THE DEVICE IS PUTTING DATA IN THE RIGHT/SAME CLUSTERS. for us, this means we are using the Generic Device simple sensor cluster to alert the user of a clogged filter.
How is this handled on the server side? That is a good question and one of the reasons we don't mind committing to open controllers such as SmartThings, WigWag, and the Almond+. As a GENERIC device, how does the server now what it means when a simple sensor is flagged? It doesn't unless it is 'told' what it means and can display it appropriately to the user. (This is a big deal when a someone like us come up with a NEW sensor).
ZigBee is also a mesh network. This means that we don't need to amplify our transmitter so that the controller can receive our signal. It only needs to get to another device that is acting as a router. This helps keep the cost down and the battery lasting longer. and at the same time increase the range of the device.
Speaking of networks, because the controllers that support ZigBee are connected to WiFi, the user has the ability to view and control the ZigBee network remotely from anywhere in the world (except maybe North Korea). This is an advantage for a lot of things like starting the AC up before you get home, turning light out, and security sensing but for a air filter monitor, it might be questionable.
The cost of the ZigBee device over the Bluetooth device is negligible. In fact, the nice thing for us is that it would be a drop in replacement, SAME PCB.
Bluetooth Smart
Bluetooth Smart has a lot of momentum fueled by mobile phones and tablets. Right now it can only be considered a local solution. That is, you need to be in proximity of the sensor to get the alert. Sounds almost useless considering the sensor will be giving you an audible and visual signal when the filter needs changing. (Unless you turned the signals off).
So are there ANY advantages to Bluetooth at this point in time? Yes.....data.
Inevitably, even our seemingly simple sensor has a lot of data that can be made available to the user which could lead to the user configuring the device differently. We generate data but we also operate based on configuration data. This data is specific to our device and no standard in the world would ever conceive. So while standards are good for competition and inter-operability, it limits the functionality or capabilities that the device can provide.
A well designed sensor will have the ability to be re-flashed over the air and this ability seems to be thought out more carefully in the Bluetooth Smart Ready specifications.
To expose additional data to the user, a custom application would need to written for each platform and this of course means additional support.
Just remember, at some point all the bits and bytes need to be in a place know to the UI that is exposing it to the user.
Please support us at
http://www.kickstarter.com/projects/333435704/filterwatch-low-cost-easy-to-use-air-filter-monito
Cheers John
No comments:
Post a Comment