No problem, I'm happy to share what I've learned! Yeah, connecting to the web can be stressful to a small device, but it's very feasible. A basic OS that handl

No problem, I'm happy to share what I've learned! Yeah, connecting to the web can be stressful to a small device, but it's very feasible. A basic OS that handles timers, a communication stack, a way to abstract tasks and communicate between them, can be quite small. Contiki OS for small devices can run on tiny devices - the amount of RAM and flash and CPU speed isn't much a limiting factor until you start with communication. Then you want RAM to hold queues of packets, neighbor tables, etc. You want flash to hold the code necessary to use the protocols you need. We support a range of devices at Thingsquare, eg the cc1310 with 128kB flash and for that we have space for a full-fledged IPv6 stack and all that's necessary for low-power wireless (ie specific radio duty cycling protocol, routing protocol, etc), our own libraries and abstractions to make it simpler for customers to use the system, with room left for customer application and drivers. Contiki OS is event-based, ie when it is not actively doing something, it simply waits (for something to happen on a physical pin, or radio event, or timer expiry) and can go to sleep. That way, and with lots of hard work to make everything efficient on every level, you save power. Raspberry pi and similar ones makes it simpler (lots of developers know the stuff, linux, etc) but has drawbacks (power, complex system, lack of low-level control and kernel timing requirements might not suffice, cost, IP, in some cases security, licensing, etc). Have a look at these: http://www.thingsquare.com/blog/articles/sensortag-power/ http://www.thingsquare.com/blog/articles/sensortag-power/ and http://www.thingsquare.com/blog/articles/ti-cc1350-power-consumption/ http://www.thingsquare.com/blog/articles/ti-cc1350-power-con...