Hi Jan, Your project sounds awesome - I would be very interested in talking with you further and collaborating. I will open source my stuff. The reason I had not done it yet was that we launched a Kickstarter a while back
http://www.kickstarter.com/projects/daisyworks/internet-your-thing-0 Around the same time, a whole lot of similar / competing ideas sprang up, and I wanted to get something stable and running before I opened it up. The problem I have is that I have a day job + 2 small kids, and it is very difficult for me to find the time to make large leaps of progress. Now, I think I'll just throw a liberal license on it and open it up, since I have no delusions about really building a business out of it -- it is really just for fun, and I'd like to just work with other people to build something out that represents what the larger group / community would like it to be. So, I have a demo server up at http://demo.daisyworks.com -- most of the UI is a placeholder, but it is receiving periodic sensor data from our devices; if you login, you can see the devices that you own, and see their sensor data real-time (you can register one of our devices in the "Register a Daisy" section with the secret key "foo") http://imgur.com/YjocD I use SocketStream for the glue that holds it all together: socket.io for client/server comms, mongoose for orm, redis for pub/sub, jade/stylus for html templates/css, backbone.js for UI micro-architecture, etc. I used flot for the charts, but I'd like to maybe use d3.js. I have some grand ideas on different ways to visualize the data. I also built a prototype visual rule editor here: http://live.daisyworks.com/editor.html -- this is similar to what you describe below -- allows one to visually define rules / actions that run when sensor values are triggered. My goal was to try to make it simple enough for non-tech-savvy people to be able to create a simple rule like "if the temp in my house drops below 55F call my phone" The other interesting thing that we have - is the ability to drive actuators from the browser -- w/o firewall interference. I built a web browser demo that allows you to ping/pong commands from the browser direct to a connected device -- this allows us to chain together complex rules that trigger off one sensor value, and drive an output signal on a GPIO of a completely different device. That rule editor UI was a prototype. I'm now in the process of porting that over into the new Bootstrap-driven UI. If you are interested - or anyone else on the list, for that matter, feel free to contact me @ [email protected] -- I'll add you to the github repo. I'll also slap an OSS license on it, and make it public in a day or two. I've taken a break from it for the last month just b/c I haven't had time to make forward progress, but I aim to get back into it very soon. Regards, Davis On Fri, Aug 10, 2012 at 4:36 AM, Jan Kolkmeier <[email protected]>wrote: > Davis, > > I have been busy with something vaguely related at the side of my Bachelor > Assignment. It's roughly about connecting actuator/sensor nodes (currently > xbee's+arduinos) to the Internet using a "smart gateway" (beaglebone, > raspberry-pi, or just a computer), and let them communicate with each other > with the least possible amount of configuration (ultimately incorporating > NAT traversal techniques). I have no web interface at all and since I had a > very special use case for all of this, my work may not be too reusable in > its current form. See my svd-* repositories at https://github.com/jouz/ > (sorry, > almost no documentation yet... I am just starting to clean it up...). > > > I always wanted to go more into the direction you proposed. Also by > including "soft nodes". These are small "apps" that can run on the > "smart-gateway" that define interaction between the devices. Think of it as > a short JS-script that has the functionality of sensor/actuator nodes > exposed on a high level: > > Microvawe.on("done", function(data) { > HiFi.play("food_ready.mp3"); > }); > > Ultimately, one would be able to compose these "soft nodes" with a > node-based editor. > > > It doesn't sound like you would open-source any of your work? I'd love to > contribute, see what you already have and exchange some ideas... but - to > be honest - also with the hope of being able to learn something for my own > project. > > Best regards, > Jan ( [email protected] ) > > On Friday, June 29, 2012 4:28:38 PM UTC+2, Davis Ford wrote: >> >> Hi all, >> >> I'm working on a single page, real-time webapp that allows users to >> interact with small wi-fi hardware devices that are chock full of sensors >> and controls (e.g. temp, humidity, magnetometer, accelerometer, gpio, etc.) >> -- think Arduino meets a modern webapp with websockets. >> >> The hardware + webapp allows you to do things like: >> >> * Get an sms/email/phone call if a sensor triggers a certain value (e.g. >> temp in my house drops below 55F - alert me, front door to my house was >> opened - SMS me) >> * Control a relay in your house remotely through your browser (e.g. open >> your garage door, turn on/off electric blanket, etc) >> >> The app is already receiving data from our hardware, storing it, and is >> able to be visualized in the webapp using flot charts. There is also a >> visual drag-n-drop rule editor built that I am now porting over to the new >> app (think Yahoo Pipes). I'm just looking for good people to help push it >> to completion faster than I can myself. >> >> This is a passion project. None of us are getting paid (yet). What's in >> it for you? >> >> * You'd get free hardware that would allow you to "sensor-up" your house >> and do cool stuff >> * Fun: this is the most fun I've had building software, and I have ~17 >> years exp. building stuff in embedded/C, Java, .NET, various web >> technologies >> * Hone your chops on all this new tech >> * Part-ownership: we have established a corp.; there are two of us (1 >> hardware guy, 1 software guy) - we aren't making anything yet, but if we >> are able to turn a corner on that, we'd be happy to consider part-ownership >> >> If it sounds intriguing at all, drop me a line off-list. I'll be happy >> to show you more details, demos, code (github). >> > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- http://daisyworks.com -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
