<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Instathings - Medium]]></title>
        <description><![CDATA[Instathings is pioneering Low-Code IoT Integration. Our mission is to make it incredibly easy and cost-effective to monitor and control environments and machineries. Visit instathings.io to learn more. - Medium]]></description>
        <link>https://medium.com/instathings?source=rss----504f1399fb38---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Instathings - Medium</title>
            <link>https://medium.com/instathings?source=rss----504f1399fb38---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:06:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/instathings" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Integrate Modbus with MQTT, the free, easy way.]]></title>
            <link>https://medium.com/instathings/integrate-modbus-with-mqtt-the-free-easy-way-4edc8f1f2990?source=rss----504f1399fb38---4</link>
            <guid isPermaLink="false">https://medium.com/p/4edc8f1f2990</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[modbus]]></category>
            <category><![CDATA[mqtt]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Claudio Petrini]]></dc:creator>
            <pubDate>Mon, 20 Apr 2020 13:37:43 GMT</pubDate>
            <atom:updated>2020-04-23T08:07:57.357Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROVEGUq1iOaej41HMVcElw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cbpsc1">Clint Patterson</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>Machineries and hardware devices can be connected to a network using many different protocols that require a specific knowledge to be used and integrated. Instathings’ mission is to convert these protocols into a simple API that any developer can consume with little or no knowledge of the technology stack that is used to deploy and manage hardware.</p><p>Instathings has two main components:</p><ul><li>a gateway (based on Docker and Node.js) that manages different automation protocols and convert them to MQTT;</li><li>a cloud service, that is used to:<br>1) manage the gateway and the devices connected to it; <br>2) collect the data from the gateway via MQTT and make them available via REST API or websocket.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*VHqceDKCPPvxSBKfTcUrYA.png" /><figcaption>Architectural overview</figcaption></figure><p>Using Instathings, the integration of any hardware device becomes seamless and fast. While I’m writing this post, we support two different automation protocols: Zigbee and Modbus. In both cases, we use a bridge to translate the protocols to MQTT.</p><p>In this post, I will show you:</p><ol><li>how to create a driver that describes a Modbus device contributing to Instathings open source catalogue of drivers;</li><li>test the driver via API using a Raspberry Pi, a <a href="https://www.amazon.it/DSD-TECH-SH-U10-Convertitore-Compatibile/dp/B078X5H8H7/ref=sr_1_1">Modbus USB dongle DSD TECH SH-U10</a> and Instathings Cloud.</li></ol><h3>Requirements</h3><p>To write the driver you’ll need:</p><ul><li>a Modbus device (check if it’s already in the <a href="https://docs.instathings.io/docs/all-devices.html">supported devices list</a>);</li><li>the device datasheet or proper documentation regarding the Modbus protocol on the device;</li><li>Git.</li></ul><p>To test the driver you’ll need:</p><ul><li>a Raspberry Pi and a Modbus dongle (or any equivalent Linux based hardware that can be connected to a device via Modbus);</li><li>an <a href="https://editor.instathings.io/">Instathings</a> account (or an MQTT server).</li></ul><p>In this tutorial I’ll show how to add support for the Eastron SDM120 energy meter. You can download the <a href="http://www.eastroneurope.com/media/_system/tech_specs/3914/SDM120%20PROTOCOL.pdf">technical documentation</a> of the device as a PDF file from the manufacturer’s website.</p><h3>Modbus2MQTT</h3><p><a href="https://github.com/Instathings/modbus2mqtt">Modbus2MQTT</a> is an open source bridge that we created to manage the communication between a Modbus device and an MQTT broker.</p><p>The bridge depends on <a href="https://github.com/Instathings/modbus-herdsman-converters">modbus-herdsman-converters</a>, which is the actual library of drivers. Anyone can contribute.</p><p>To support a specific device, you need to:</p><ol><li>write a descriptor;</li><li>contribute with a pull request.</li></ol><h3>Create a Modbus driver</h3><p>The driver is a Javascript object, for most of the devices you can think it as a JSON descriptor (an example).</p><p>For our example let’s define the structure of our new driver:</p><pre>{<br> &quot;model&quot;: &quot;SDM120&quot;,<br> &quot;vendor&quot;: &quot;Eastron&quot;,<br> &quot;supports&quot;: &quot;&quot;,<br> &quot;description&quot;: &quot;Energy meter&quot;,<br> &quot;fromModbus&quot;: {<br>  &quot;input&quot;: {},<br>  &quot;keep&quot;: {}<br> },<br> &quot;toModbus&quot;: {}<br>}</pre><p>Required keys:</p><ul><li><strong>model </strong>(string): this is by far the most important key, it describes the device model and you can think it like a device id</li><li><strong>vendor </strong>(string): the device vendor</li><li><strong>supports</strong> (string): a small but readable description of the data that the device will read. This is only used for documentation.</li><li><strong>description </strong>(string): a concise description of the device</li><li><strong>fromModbus </strong>(object): an object that contains 2 keys <strong>input</strong>, <strong>keep. <br></strong>Those keys will describe the device addresses to read in order to retrieve data, we’ll dig into this in a bit</li><li><strong>toModbus </strong>(object): unused so far.</li></ul><p>Now let’s populate the <strong>input</strong> key. <br>From the device document we read that:</p><ul><li>we can read Voltage at address 30001</li><li>we can read Current at address 30007</li><li>etc.</li></ul><p>Our descriptor will become:</p><pre>{<br> &quot;model&quot;: &quot;SDM120&quot;,<br> &quot;vendor&quot;: &quot;Eastron&quot;,<br> &quot;supports&quot;: &quot;&quot;,<br> &quot;description&quot;: &quot;Energy meter&quot;,<br> &quot;fromModbus&quot;: {<br>  &quot;input&quot;: {<br>   &quot;voltage&quot;: {<br>    &quot;address&quot;: 30001<br>   },<br>   &quot;current&quot;: {<br>    &quot;address&quot;: 30007<br>   }<br>  },<br>  &quot;keep&quot;: {}<br> },<br> &quot;toModbus&quot;: {}<br>}</pre><p>If this were the complete driver, then Modbus2MQTT would publish a JSON message like the following:</p><pre>{<br> &quot;voltage&quot;: &lt; value read at address 30001 &gt; ,<br> &quot;current&quot;: &lt; value read at address 30007 &gt;<br>}</pre><p>We’re using the key as a key of the output object and the address as an actual address to read the data from.</p><p>The descriptor supports additional parameters which, for the sake of this tutorial, are not described here (for instance you can post process data read before it gets published).<br>The complete descriptor is available <a href="https://github.com/Instathings/modbus-herdsman-converters/blob/development/devices/SDM120.js">here</a>.</p><p>Note: So far we read from the input registers only but we’ll improve this :)</p><h4>Make a pull request</h4><p>After your descriptor is ready make a pull request to the <a href="https://github.com/Instathings/modbus-herdsman-converters">modbus-herdsman-converter repo</a> or contact us at <a href="https://www.instathings.io/">Instathings</a>.</p><h3>Testing the device</h3><p>Once your pull request has been accepted, you’ll be able to use Instathings to read data from the device seamlessly.</p><p>First, set up the Gateway in order to connect it to the Instathings Cloud. <br><a href="https://docs.instathings.io/docs/guides/gateway-setup.html">Here</a>’s a detailed step by step guide on how to do this.</p><p>When the Gateway is connected you’ll see something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-MCwxzv0iFjPAFHcgXF9hQ.png" /><figcaption>Gateway correctly connected</figcaption></figure><p>You can now plug in the USB Modbus adapter and click on the “Install” button in the “Protocols” section.<br>When the protocol is correctly installed the Protocols section will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bggz_rFCQw1_y5loIlJ8bg.png" /><figcaption>Modbus software support installed successfully</figcaption></figure><p>We can now add your device to the Gateway; to do so go to the “Devices” tab and select the device from the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBsg8PaH1U7qcFhDZVcuCg.png" /></figure><p>Just click on Create.</p><p>We now need to “Pair” the Modbus device; this case requires only to specify the Modbus Id of the device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LEpv2Sbqj73RQGWsWJEJIg.png" /></figure><p>Again, just click “Pair”.<br>If everything went well, you’ll see a success message and the Instathings Editor will report the device as “Paired”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mo17TTH58KPjw7-4s9gG_g.png" /></figure><p>From now on, the Instathings Gateway will poll every 10s the device in order to report data to the Cloud.<br>You’ll see data flowing in the “Data” section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OSJScLa0t7Hf3dvXDEPRBA.png" /></figure><p>You can access this data via API as well, check out <a href="https://docs.instathings.io/docs/guides/api-access.html">this</a> detailed guide about how to enable API access.</p><h3>Using Modbus2MQTT without Instathings</h3><p>After your contribution wait for a new release that includes your descriptor and then just use the Modbus2MQTT bridge.</p><p>In order to pair the bridge with the device you’ll need to publish a message to:</p><pre>modbus2mqtt/configure/set</pre><p>With the following payload:</p><pre>{<br> &quot;id&quot;: &quot;uniqueidentifier&quot;,<br> &quot;modbus_id&quot;: &quot;the modbus id of the device&quot;,<br> &quot;baud_rate&quot;: &quot;the baud rate to use&quot;,<br> &quot;interval&quot;: 10000, // in ms the polling interval<br> &quot;model&quot;: &quot;SDM120&quot; // this must be the same model of the descriptor <br>}</pre><p>You’ll receive an ACK message here:</p><pre>modbus2mqtt/bridge/log</pre><p>Then you’ll need to subscribe to the topic with the format:</p><pre>modbus2mqtt/&lt;id&gt; </pre><p>where in this case id = uniqueidentifier and you’ll see data flowing :)</p><h3>Conclusions</h3><p>In this article, I introduced Modbus2MQTT and illustrated how to add and test a driver to the library of supported devices using Instathings.</p><p>Finally, I showed how to use Modbus2MQTT as a stand alone library to translate Modbus to MQTT (viceversa coming soon).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4edc8f1f2990" width="1" height="1" alt=""><hr><p><a href="https://medium.com/instathings/integrate-modbus-with-mqtt-the-free-easy-way-4edc8f1f2990">Integrate Modbus with MQTT, the free, easy way.</a> was originally published in <a href="https://medium.com/instathings">Instathings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT? It is still too hard and expensive to connect things to the Internet.]]></title>
            <link>https://medium.com/instathings/iot-it-is-still-too-hard-and-expensive-to-connect-things-to-the-internet-8def99764605?source=rss----504f1399fb38---4</link>
            <guid isPermaLink="false">https://medium.com/p/8def99764605</guid>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Nicola Mattina]]></dc:creator>
            <pubDate>Wed, 15 Apr 2020 22:33:14 GMT</pubDate>
            <atom:updated>2020-04-15T22:39:35.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MxzGbDoZ8WAp67PjIbpqaw.jpeg" /><figcaption><em>Photo by </em><a href="https://unsplash.com/@hackcapital?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Hack Capital</em></a><em> on </em><a href="https://unsplash.com/s/photos/software?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a><em>.</em></figcaption></figure><p>During the past 25 years, I’ve regularly worked closely with software engineers in various roles: as an analyst, UX designer, product manager, and a customer. Most of the times, we worked together really well. Other times it was extremely frustrating. More than once, I quarrelled furiously with them…</p><p>Over time, I have tried to better understand the dynamics of software design, development and management. And I realized that many misunderstandings between clients and developers depends on a different perception of the many activities that we normally expect from a developer (and give for granted): understand all requirements on the fly, make forward-thinking technical decisions, grind out lines of code, continually learn new things to solve a broad range of complex problems, test what they’ve produced, debug, put into production, manage software in production, and… participate in many meetings.</p><p>The result is that developers often work under pressure because clients (especially those who know little about software) expect that they deliver the perfect software at lightning speed and possibly with a ridiculous budget.</p><h3>The origin of Stamplay</h3><p>I was one of those clients. Until I decided that I wanted to design a tool to create apps using a <a href="https://en.wikipedia.org/wiki/Mashup_(web_application_hybrid)">mashup</a> approach, or combining and orchestrating various specialized Softwares as a Service (SaaS). I saw this opportunity because ten years ago companies, especially small and medium businesses, started to move their information systems to the cloud to embrace digital transformation without spending a fortune. At the same time, services like <a href="https://zapier.com/">Zapier</a> (founded in 2011) became more and more popular to automatically sync data between the various SaaS instead of using spreadsheets.</p><p>I wanted to make it easier to use SaaS as building bricks to create brand new apps, because <a href="https://en.wikipedia.org/wiki/Cloud-based_integration">cloud-based integration</a> was still a complex and time consuming activity that required a lot of coding.</p><p>In 2013, I co-founded <strong>Stamplay </strong>with <a href="https://www.linkedin.com/in/giulianoiacobelli/">Giuliano Iacobelli</a>, with a vague idea to create a sort of Zapier on steroids, a platform that could be used by professional and citizen developers to create complex applications in the cloud connecting existing services. In its first version, it was a mix of pre-made components and connectors to SaaS and social network platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*zvAvbJtsy5EE78PD5kQMXw.png" /><figcaption>An early version of Stamplay.</figcaption></figure><p>After some iterations, we abandoned the idea to provide tools to create applications from start to finish because it was too ambitious for a small team with little economical resources and we focused on back-end integrations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*QQoSikhf_hicnffUMmRWxA.png" /><figcaption>A late version of Stamplay.</figcaption></figure><p>In 2019, after a tortuous journey, we sold Stamplay to Claris (a subsidiary of Apple). My former co-founder Giuliano moved to California and is now product manager of <a href="https://www.claris.com/connect/">Claris Connect</a>.</p><p>Claris new low-code development platform plus integrations provided by Stamplay is a vague approximation of my initial idea of mashup applications. The road to democratizing software development is still long and I need to have the patience to build it one piece at a time. 🧘</p><h3>From Stamplay to Instathings</h3><p>Cloud-based integration is a commoditized market: <a href="https://en.wikipedia.org/wiki/Low-code_development_platform">low-code and no-code platforms</a> are adding integrations and automations functionalities as a feature of their platforms both acquiring startups (IE. Claris acquired Stamplay, Quickbase acquired Cloudpipes) or developing them from scratch. For me, this is not an exciting field of exploration anymore.</p><p>So, what’s next? There are many opportunities to streamline software development and, probably, in 2020 the most obvious choice to create a new startup would have been to consider artificial intelligence. This is exactly what I did, at first, but the more I was looking at the sector and the more there was a problem popping out. All data scientists that I interviewed were complaining about the fact that it was hard and expensive to collect data from the field. In fact, even thought many machineries are controlled electronically and can be connected to a network, it is very likely that they are using a technology stack based on <a href="https://en.wikipedia.org/wiki/List_of_automation_protocols">automation protocols</a> and some old fashioned software that is not easy to integrate.</p><p>Not being an expert of Internet of Things, I was quite surprised by the fact the — despite there are hundreds of IoT platforms and solutions — it requires a lot of effort to connect a device to an application.</p><p>Let me explain my point with a very simple example: let say that I need to monitor the temperature of a meeting room. Obviously, I need a temperature sensor. Which one? Since it is an office, I could use a smart home device. After a quick search, I find many inexpensive wireless devices by companies like Samsung, Fibaro, Xiaomi. They seem easy to deploy and to manage. Bingo! Unfortunately, my enthusiasm doesn’t last long: what is Zigbee or Z-wave? How do I connect the sensor to the Internet? Can I consume the data via API? Maybe IFTTT? If you approached home automation, you know what I mean: too many standards, too many options, closed systems. It is very far from the API ecosystem that every developer has learned to master.</p><p>It is surprising how difficult it is for a web developer to integrate even a simple consumer product like a wireless temperature sensor that costs less than 20 dollars. It is even more complicated if you need to collect data from a machine that uses an old industrial automation protocols like Modbus.</p><p>Despite the hype around Internet on Things in the last decade, there is still a chasm that separates <a href="https://en.wikipedia.org/wiki/Operational_Technology">operational technologies</a> (OT) and <a href="https://en.wikipedia.org/wiki/Information_technology">information technologies</a> (IT).</p><p>After many interviews and analysis, I came to the conclusion that there is an opportunity to help software developers to monitor and control machineries and environments, creating a <strong>low-code solution that translates any automation protocol into an API that is easy to integrate in any web and mobile application</strong>.</p><h3>Always be a co-founder</h3><p>As I wrote, I’m not a software developer and I can’t code. But I’m lucky, because <a href="https://medium.com/u/3d8cbafe19ae">Claudio Petrini</a> decided to join me in this adventure. We worked together at Stamplay for 5 years and he is one of the most talented and disciplined software engineers that I know.</p><p>When I presented him the idea, last July, he was working on a project to integrate some hardware and he was stuck because he needed to study how to connect to the device.</p><p>We shared the vision, Claudio has the competence and a unique experience in API integration and… that is how <a href="https://www.instathings.io/"><strong>Instathings</strong></a> was born. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8def99764605" width="1" height="1" alt=""><hr><p><a href="https://medium.com/instathings/iot-it-is-still-too-hard-and-expensive-to-connect-things-to-the-internet-8def99764605">IoT? It is still too hard and expensive to connect things to the Internet.</a> was originally published in <a href="https://medium.com/instathings">Instathings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>