As I mentioned last month we are going through a process of creating designs for an update Eclipse logo. We had some great ideas submitted through our crowd source project and now it is time to test out some of the better ones. Starting today we are going to display some of the news designs on eclipse.org. Visitors to the web site will have an opportunity to +1, 0, or -1 on the design and provide comments. We are going to rotate through each design for 1-2 weeks to collect feedback from the community. I hope you enjoy the new designs.
1. Wunderbar - looks like an interesting kit of hardware and software for IoT applications. They seem to be using MQTT for the message protocol.
2. Comparing bandwidth consumption between MQTT, AMQP and TCP – perfect illustration on why an IoT protocol like MQTT is needed.
3. New MQTT-SN (Sensor Networks) specification published – for really small devices with no TCP
4. Lots of analyst predictions about IoT in 2014 – not a big believer in the `Year of`meme but 2014 is going to be a fun year to be in IoT
Interesting links for the IoT and M2M Industry.
1. Axeda support for new SalesForce1 platform
- SalesForce had their huge Dreamforce conference last week and a major theme was IoT. Axeda, a partner in Eclipse M2M, nailed it on the importance of machine data.
2. Amazon announced Kinesis service
- It looks like Amazon is getting into the IoT industry with its recently announce Kinesis service that will support for the real-time processing of data streams. I wonder if it has MQTT support?
3. Makers and developers are important for IoT
- If you are in London or can easily get to London for Dec. 2-3 I would suggest attending the Thingmonk event. It has a great line-up of speakers from the IoT industry and there is a ton of IoT innovation happening in London. I will be there.
IoT and M2M industry desperately needs to have open protocols that promote interoperability between different solutions and applications. The current state of the industry is a set of proprietary or best vertical oriented protocols that lead to silos of technology, not a network.
MQTT is gaining a lot of interest as a messaging protocol to fit this need. It is being standardized at Oasis. We have great open source implementations available at Eclipse Paho, Eclipse Mosquito and other places. There are many vendors providing MQTT support. However, like any good standard, testing is how you prove that it actually works.
The time has come to test the promise of MQTT interoperability. To do so, we are organizing the first MQTT Interoperability Testing Day on March 17 at the Hyatt Regency San Francisco Airport (This is the location for the EclipseCon conference). We would like to invite the many different MQTT based products, open source projects and solutions to participate. You do not have to be using Paho or Mosquito. The goal is to test as many different clients and servers to prove MQTT interoperability.
Some interesting links from the IoT and M2M industry.
1. Adding OAuth to MQTT
A couple of blog post from people thinking of adding OAuth to MQTT. Identity and authentication are issues that really have not been suitable addressed in IoT. It is great to see people talking about it. Next we need an open source identity framework for IoT at Eclispe.
OAuth binding for MQTT from Paul Madsen
Using OAuth 2.0 with MQTT from Paul Fremantle
2. M2M Platforms
-Bosch has written article to define what an M2M/ IoT platform should feature
- M2Mi is a new M2M platform vendor that I have not come across before. They look interesting…
The OASIS MQTT TC has published their draft 15 spec.
4. Bonus Link – My rant about Telco missing out on developers.
Over the last 2 months, I have had the opportunity to attend three M2M events: M2M Summit, M2M World Congress and the ETSI M2M Workshop. All of these events had a significant participation by the big European telcos. In Europe and the US, the telcos are pumping a large amount of money, at least marketing dollars, into the M2M industry.
A lot of speakers at these events were senior people from the telco industry presenting their M2M and IoT strategies. After hearing enough of these presentations you start to get a feel for their priorities and perspective. One thing you never hear in these presentations is developers, open hardware or open source. The only time any of these were mentioned was when I or someone from Sierra Wireless was presenting.
It was almost as if developers did not exist. One would think the Telcos would have learnt from the smartphone industry where Apple and Google have dominated due to the incredibly successful developer programs. Based on what I have heard that would not seem to be the case.
It feels like the Telcos are stuck in a closed walled garden cathedral-like strategy. They have a strong focus on partner programs which they seem to believe makes them open. Ironically one presenter bragged they had improved their partner program so it now only took weeks to join, not months. They seem to think innovation needs to be under their control so they can show a ROI. The concept of a bazaar where innovation happens everywhere seems to a foreign concept. Given the success of the Google and Apple appstore I find this surprising.
Open source would also appear to still be a ‘scary’ concept. At the ETSI event, one panelist proclaimed [paraphrased] ‘he was worried open source was causing fragmentation in the M2M industry’. In fairness, he was conflating open source with the maker and hacker movement around open hardware but it still shows a lack of appreciation for how developers innovate.
These comments about open source are consistent with my interactions I have had with telcos. Some individuals within these organizations certainly get open source. However, the overall organization still seems to view open source as a scary idea, not a driver for innovation or pervasive adoption of technology.
If Telcos are going to succeed in M2M and IoT they need to embrace developers. My recommendation to any Telco executive is as follows:
- Innovation will happen outside your walled garden. Don’t expect developers to join your partner program. They don’t have the time or money. Imagine having 100,000’s developers active in your community not just 50-100 companies. Learn how to nurture and promote this innovation but don’t expect an ROI on each engagement.
- Developers are using open hardware, like Arduino and BeagleBone, to experiment and innovate. You need to support open hardware and include it in your strategy.
- Open source software will lower the barriers of adoption for your platform. Developers love to use open source since they don’t have to ask permission,they can learn from the code and it is typically great software. The Internet is run on open source software. It is an intricate part of the entire software industry. Embrace open source, learn how to benefit from it, it is not scary.
- If you still don’t understand, read ‘The New Kingmakers’. Developers certainly are the new kingmakers and you are missing out.
As a bonus recommendation, I am speaking at an IoT event that speaks to developers and industry, called Thingmonk. If you really want to understand how innovation is happening in IoT, you need to attend.
The Eclipse logo has been in existence for over 10 years. It has served the community well but it is time for a bit of an update. To help create an updated logo I have started a design competition on designonclick. If you are a graphic designer or know of a graphic designer, we welcome your ideas.
For those astute community members, you may remember I tried to update the logo a couple of years ago. It is time to try again.
Links for the past week in the IoT and M2M industry.
Interesting list of companies, especially since I have not heard of some of them, ex Schneider and Grundfos. The list is also missing some important companies, like GE, but all top 10 list of this problem.
Nice to see Intel making some heavy investment in IoT.
Really good article from Stefan Ferber at Bosch about the IoT inflection point.
4. ETSI M2M Workshop presentations
Last week I attended the ETSI M2M Workshop. Some interesting presentations that for the most part did not have a lot of vendor product pitches. All for the presentations are availalbe at http://docbox.etsi.org/Workshop/2013/201311_M2MWORKSHOP/
James Governor recently blogged about his desire to have a good gender balance for his upcoming Thingmonk conference. This is something that I would like to see at our EclipseCon conferences. At the most recent EclipseCon Europe event we had only 27 women out of 589 attendees. Not very good; actually pretty pathetic.
I don’t know of any silver bullet to address this imbalance. I like to think, at least hope, EclipseCon is a welcoming event for women. At past conferences, most women attendees I have spoken with seem to enjoy the conference. If this is not the case, I would invite people to please let me know what we can do to make it so.We will be putting a code of conduct in place but we need to do more. If you have suggestions please leave a comment or send me an email (ian dot skerrett at eclipse.org)
One thing I would like to encourage is more speaking proposals from women. We have had some great women speakers in the past but they are unfortunately female speakers are always a minority. The Call for Papers is now open so the timing is good. If you are a women or know a women that would be a great EclipseCon speaker please submit a proposal. I am happy to report that we will have our first female keynote speaker. We will be announcing all the keynotes in a couple of weeks but I know she is going to be awesome.
Some IoT / M2M links from last week.
1. New Eclipse Project Proposal: Krikkit.
Project proposal from Cisco about making edge devices smarter about IoT data.
2. New SmartHome Consortium including ABB, Bosch, Cisco and LG
These companies should really look at Eclipse SmartHome. It would appear to help solve a lot of the goals they mention in their press release.
Looks like Blackberry is integrating with MQTT.
4. M2M Goodness at EclipseCon Europe
Last week there were a number of M2M presentations at EclipseCon Europe. Alex Blewitt blogged about some of the highlights on InfoQ.