• TL;DR version - too many manual steps / too much work. Standard early-gen issues.

    Then the Fitbit Flex finally arrived. Again I was excited. Especially since it was connected to my Fitbit scale through the app. But then, just like with the UP, I was letdown quickly. It didn’t capture my runs properly so I had to manually input those, I had to tell it that I was at the gym so it knows I was active (like the UP back then as well) and it never knew when I was biking. The last thing I want to do when I pay $100+ is to manually enter data myself. I felt like I was informing them about myself and it wasn’t informing me.**

  • IoT Agency.

  • This is probably simpler than what you’re expecting to see - it’s all in the browser window.

    You can send a notification event with a Javascript call. You’ll still have to tie this somehow to your website (assuming that’s trying to push data) via polling or MQTT or whatever, and the browser window actually has to be running.

    When you receive a notification, you don’t have to write any special code to handle it. A window will appear on your screen. Unfortunately on my Mac Google hasn’t bothered to tie it into native OS X notifications, which is très annoying. You can also trigger Javascript events based on receiving those events.

    There’s a demo here which should make things clear.

  • This is a common result of bad corporate culture. Visionary: “And we’ll make it work with everyone’s stuff!” Pointy-Haired Boss: “How does that make them buy more of our products?”

  • Another “for future reference” post. I’ll be making an IOTDB version of this soon. I’ve been playing with Twilio this after, seems straight forward

  • Tags: SonosAPI

    For future reference.

  • Tim O’Reilly

    Long before we get to fully autonomous devices, there are many “halfway house” applications that are really Internet of Things applications in waiting, which use humans for one or more parts of the entire system. When you understand that the general pattern of #IoTH applications is not just sensor + network + actuator but various combinations of human + network + actuator or sensor + network, you will broaden the possibilities for interfaces and business models.

    …My point is that when you think about the Internet of Things, you should be thinking about the complex system of interaction between humans and things, and asking yourself how sensors, cloud intelligence, and actuators (which may be other humans for now) make it possible to do things differently. It is that creativity in finding the difference that will lead to the breakthrough applications for the Internet of Things and Humans.

  • IOTDB is this cornerstone. If you’re creating or using disparate connected devices, get in touch with me and I’ll hook you up.

    The basis for making IoT happen is the connecting of things: billions of diverse things, from tiny acceleration sensors to video cameras, routers, and cars – or even vacuum cleaners. Connecting one device or devices of the same breed and from the same vendor is easy. But connecting lots of devices or more heterogeneous ones is another story. They need to find the same ‘thing speak’ –a shared abstraction layer to talk to each other. Only by establishing a lingua franca can diverse things be connected to each other, integrated, and managed effectively. This cornerstone has to be laid before we can start talk about new services and in the Internet of Things.

  • Usual IT department fretting about the business getting out their control. BYOD².

  • This is getting into core issues IOTDB is addressing.

    Whether you call it the Internet of Things, Internet of Everything, Industrial Internet, Internet of Services or Internet of FOO, it is inevitable you run into the supposedly BIG question meant to spark a religious war.  Which protocol should the IoT standardize on?  MQTT, that is the way!  Nyet, must use XMPP!  Away with you sir, COAP is it! You shall not pass, IPv6 is the one ring to rule them all!  Excuse me sonny, but websockets are tried and true!   Ok, ok strange character voices debating in my head aside, the question is a legitimate one, but I think the answer is really quite simple: ALL OF THEM.

    …Beyond these examples, the IoT/E needs to embrace the “open” philosophy.  That means supporting multiple embedded platforms, gateways, and third-party services being joined together through a myriad of connecting protocols to create solutions that are exponentially better than the sum of their parts.  No one protocol standard will dictate how a TI chipset is integrated with an iOS based application and Salesforce.com for sales tracking nor should it

  • Get ready for a lot more stories like this over the next few years. This is a point that a lot of Home IoT designers seem to miss - have things happen around your house without you actively triggering them is weird; having them happen for no reason that you can think of is creepy.

    Also note the biggest problem in home automation : meaningful presence detection.

  • It’s not the article I want to draw your attention to but the comments. Peter Waher argues the case for XMPP (over MQTT). I won’t summarize what he said but to me this strikes me like OSI/ISO vs TCP (or even IPv6 v IPv4). I tried to work with XMPP before : it was hard. I had MQTT working exactly as advertised in 5 minutes. Yes, MQTT doesn’t have this or that but I’m sure there’ll be workarounds when they’re needed.

  • There’s no doubt that “dweet" is simple to use : just visit that URL on your smart phone and you’re sharing data using JSON. I assume there’s something deeper going on here, or being planned? That you can share info but additionally you can layer security and/or historical data with it for an additional fee?

    With a new service called Freeboard, Bug Labs is giving people a simple one-click way to publish data from a “thing” to its own Web page (Bug Labs calls this “dweeting”). To get a sense of this, visit Dweet.io with your computer or mobile phone, click “try it now,” and you’ll see raw data from your device itself: its GPS coordinates and even the position of your computer mouse. The data is now on a public Web page and available for analysis and aggregation; another click stops this sharing.

    Freeboard, expected to be launched Tuesday, makes sense of such streams of data. A few more clicks create quick graphical displays of the shared information, such as location, temperature, motor speed, or simply whether a device is on or off. “We are trying to make the Internet of things far simpler, and far more accessible, to anybody,” says Peter Semmelhack, CEO of Bug Labs, a business that initially focused on the development of open-source modular hardware (see “Bug Labs Adds New Modules”), but which now develops software platforms.

  • Tags: Robots

    Micro-robot assembly (video). Full story

  • Jasper has raised $50 million in funding at a valuation of more than $1 billion for software that enables objects of all types—autos, baby pajamas, airplane engines and so on—to communicate in what has lately become known as the Internet of Things.

    …Jasper’s software is now used by more than 1,000 companies from more than 20 industries and is integrated with global mobile operating groups around the world. It delivers, manages and secures connections among things, bringing in applications and services from the Internet. It routes services to customers, meters them, charges for them and shows service providers analytics on how their business is doing.