XMPP-IoTJekyll v3.3.1//www.xmpp-iot.org/apple-touch-icon-precomposed.pngHow XMPP can solve the IoT puzzle2017-03-05T22:06:41+00:00//www.xmpp-iot.org/Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.seJava smack tutorial2017-02-05T00:00:00+00:00//www.xmpp-iot.org/tutorials/java-tutorialJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>This tutorial will be created during the Google summer of code 2017. You who starts with the teaser tasks are encouraged to help out in finishing this tutorial in how to get smack up and running togheter with the extensions. TIP you could use the other tutorials as inputs or outputs</p>
<p>#Preparations</p>
<ul>
<li>start with the smack XMPP library</li>
<li>look at the other tutorials</li>
<li>create two clients that reads and writes values to eachother</li>
</ul>
<h1 id="read-a-value">Read a value</h1>
<p>To be added</p>
<h1 id="write-a-value">Write a value</h1>
<p>To be added</p>
Read and Write to Devices With Converse.js2015-08-20T17:59:14+00:00//www.xmpp-iot.org/tutorials/read-and-write-to-devices-with-converse-jsJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>This tutorial is regarding using Converse.Js to read values and write values to devices, and also retrieve history of fields.</p>
<h2 id="getting-started">Getting Started</h2>
<p>Follow the instructions given <a href="https://conversejs.org/docs/html/quickstart.html">here</a></p>
<p>Use this <a href="https://github.com/adhish20/converse.js/blob/dev_iot/builds/converse.js">converse.js file</a> instead of the one given in above link.</p>
<h2 id="start-with-logging-into-an-xmpp-account">Start with logging into an XMPP account</h2>
<ul>
<li>
<p>Log into your xmpp account.</p>
</li>
<li>
<p>Contacts will be displayed with an Icon to their left.</p>
</li>
<li>
<p>These icons determine the type of contacts (Sensor Devices, Control Devices or Contacts)</p>
</li>
<li>
<p>Open a Chatbox with a Device.</p>
</li>
<li>
<p>We have used <a href="https://conversejs.org/docs/html/features.html#commands">Command Feature</a> to implement the functions.</p>
</li>
</ul>
<h2 id="reading-values-from-a-device">Reading Values from a Device</h2>
<ul>
<li>
<p>It works for Sensor as well as Control Devices.</p>
</li>
<li>
<p>The command for reading a value is ‘/read’.</p>
</li>
<li>
<p>It will display the fields stored in the device along with their present values. Like this :</p>
</li>
</ul>
<p><img src="/images/read.png" alt="Read Requests" /></p>
<h2 id="writing-value-to-a-field">Writing Value to a Field</h2>
<ul>
<li>
<p>It works for Control Devices.</p>
</li>
<li>
<p>First perform a Read to know the FieldNames.</p>
</li>
<li>
<p>The command for writing a Value to a FieldName is ‘/write FieldName Value’.</p>
</li>
<li>
<p>Now you can again perform a Read to check if the Value for that FieldName is changed. Like this :</p>
</li>
</ul>
<p><img src="/images/write1.png" alt="Write Requests Step-1" />
<img src="/images/write2.png" alt="Write Requests Step-2" />
<img src="/images/write3.png" alt="Write Requests Step-3" /></p>
<h2 id="history-retrieval-for-a-field">History Retrieval for a Field</h2>
<ul>
<li>
<p>It works for Sensor as well as Control Devices for Fields that store their History.</p>
</li>
<li>
<p>The command to retrieve Hisotry of a FieldName is ‘/history day/week/month/year FieldName’.</p>
</li>
<li>
<p>Output for the same looks like this:</p>
</li>
</ul>
<p><img src="/images/history1.png" alt="History Requests Step-1" />
<img src="/images/history2.png" alt="History Requests Step-2" />
<img src="/images/history3.png" alt="History Requests Step-3" /></p>
<p>Hope you like playing around with it :)</p>
IEA Cordova Application2015-08-20T06:08:53+00:00//www.xmpp-iot.org/tutorials/iea-cordova-applicationJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>This tutorial is regarding using IEA Cordova Mobile Application, which can be used to read values and write values to devices, and also retrieve history of fields.</p>
<h2 id="getting-started">Getting Started</h2>
<ul>
<li>You need to install the application to your android device using latest apk file.</li>
<li>Home page looks like this :</li>
</ul>
<p><img src="/images/login2.png" alt="Login View" width="360" /></p>
<h2 id="start-with-logging-into-an-xmpp-account">Start with logging into an XMPP account</h2>
<ul>
<li>Login with any xmpp account. Online contacts along with the details of device, will be displayed for the contacts like this:</li>
</ul>
<p><img src="/images/contacts2.png" alt="Retrieved Contacts VCard Display" width="360" /></p>
<h2 id="reading-values-from-a-device">Reading Values from a Device</h2>
<ul>
<li>Clicking on a device contact will perform a Read Operation, the fields stored in the device along with their value will appear as a drop down for the contact:</li>
</ul>
<p><img src="/images/read-mobile1.png" alt="Read Values of a Device" width="360" /></p>
<h2 id="writing-value-to-a-field">Writing Value to a Field</h2>
<ul>
<li>If a field is writable, we can edit its value and tap the ‘write’ button, to send a write to a field request to the device:</li>
</ul>
<p><img src="/images/write-mobile1.png" alt="Write for App" width="360" /></p>
<h2 id="history-retrieval-for-a-field">History Retrieval for a Field</h2>
<ul>
<li>If a field stores history of its values, tapping on the ‘fieldname’ will generate a graph based on the history of its values:</li>
</ul>
<p><img src="/images/history-mobile2.png" alt="History Graph 1" width="360" />
<img src="/images/history-mobile1.png" alt="History Graph 2" width="360" /></p>
<p>Hope you like playing around with it :)</p>
Week 122015-08-19T13:46:36+00:00//www.xmpp-iot.org/gsoc/week-12Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="history-logger-for-sensor-devices">History Logger for Sensor Devices</h4>
<p>##Abstract</p>
<p>Storing momentary data for Sensor Devices by a node that sends back History data stored by the Logger.</p>
<p>##Work</p>
<ul>
<li>Implementing IoT_Logger.py for SleekXMPP, which is basically an API for storing and Rerieving of Momentary Data collected from other resource of same device.</li>
<li>Implementing IoT_HistoryLogger.py for SleekXMPP:
<ul>
<li>It registers a new resource of the same device whose data is to be stored.</li>
<li>Sends a read request to the original device at regular intervals and stores the values using above mentioned API.</li>
<li>Recieves messages and respond back with history on receiving a history request by getting back data using the above mentioned API.</li>
</ul>
</li>
<li>Also did a few changes to XEP-0323 Plugin of SleekXMPP for History Messages.</li>
</ul>
<p>##Results
<img src="/images/logger.png" alt="Logger" width="900" /></p>
<h2 id="gsoc-final-evaluation">GSoC Final Evaluation</h2>
<p>With this I conclude the modules made in ‘Prototyping IoT Tools’ Project for GSoC 2015. Will focus a little on Code Clean up and tutorials for the same.</p>
Week 112015-08-12T14:29:03+00:00//www.xmpp-iot.org/gsoc/week-11Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="client-device-logger">Client-Device Logger</h4>
<p>##Abstract</p>
<p>Logging momentary Data of a Sensor device using another resource of the same Jid.</p>
<p>##Work</p>
<ul>
<li>2 resources of same device can interact with each other, without any subscription.</li>
<li>So basic idea is to write a Logging Python Script for SleekXMPP that runs with same Jid as some Sensor Device which keeps asking for its Momentary Data at particular intervals from the Device and stores it locally or in some Database ( InfluxDb ).</li>
<li>So that when asked for history, the actual resource gives momentary data, while the resource of Logger Script gives History Data.</li>
</ul>
<p>##Road Ahead</p>
<ul>
<li>Complete this module and implement XEP-0326.</li>
<li>Write Tutorials for all Modules in this Project, made during GSoC 2015.</li>
</ul>
Week 102015-08-05T13:57:49+00:00//www.xmpp-iot.org/gsoc/week-10Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="write-and-history-for-mobile-application">Write and History for Mobile Application</h4>
<p>##Abstract</p>
<p>Implementation of Write for Control Devices and History Retrieval for a Sensor Device.</p>
<p>##Work</p>
<ul>
<li>Implemented Write for numerical Fields.</li>
<li>Implemented History using Chart.js for Sensor devices which stores history.</li>
<li>History for a field is displayed as Graph on top of the Contacts.</li>
</ul>
<p>##Problems Faced</p>
<ul>
<li>Setting up Proxy Settings for Gradle (Solved) : Gradle needs proxy settings in order to use maven for building Android Application.</li>
</ul>
<p>##Final Output</p>
<p><img src="/images/write-mobile1.png" alt="Write for App" width="360" />
<img src="/images/history-mobile2.png" alt="History Graph 1" width="360" />
<img src="/images/history-mobile1.png" alt="History Graph 2" width="360" /></p>
<p>##Road Ahead</p>
<ul>
<li>Implementing History Retrieval for SleekXMPP.</li>
</ul>
Week 92015-07-29T08:13:56+00:00//www.xmpp-iot.org/gsoc/week-9Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="vcard-css-changes-and-read-implementation-for-mobile-application">VCard, CSS Changes and Read Implementation for Mobile Application</h4>
<p>##Abstract</p>
<p>VCard stores the information of a User which is retrieved at the time when the roster is recieved. And Implement Read for Sensor Devices.</p>
<p>##Work</p>
<ul>
<li>We use the NickName and Image from the VCard for the Contacts View.</li>
<li>Bug Fix for Login Form Removal after the connection has been established.</li>
<li>CSS Changes for the Views.</li>
<li>Add Dynamic Event Listener for Tap on Contacts to send a Read Request.</li>
<li>Display Read Values as a Dropdown to the Device in the Contacts View.</li>
</ul>
<p>##Problems Faced</p>
<ul>
<li>(Solved) Dynamic Event Handler was not working when using jQuery on(‘tap’) function. The problem was with the older version of jQuery, replacing it with the latest version solved the problem.</li>
</ul>
<p>##Final Output</p>
<p><img src="/images/login2.png" alt="Login View" width="360" />
<img src="/images/contacts2.png" alt="Retrieved Contacts VCard Display" width="360" />
<img src="/images/read-mobile1.png" alt="Read Values of a Device" width="360" /></p>
<p>##Road Ahead</p>
<ul>
<li>Implement Write and History using a Graph Library.</li>
<li>CSS changes for Read Values.</li>
<li>Some functionality changes for adding contacts to Contacts View.</li>
</ul>
Week 82015-07-22T08:13:48+00:00//www.xmpp-iot.org/gsoc/week-8Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="login-and-contact-retrieval-using-strophe-for-mobile-application">Login and Contact Retrieval using Strophe for Mobile Application</h4>
<p>##Abstract</p>
<p>Implementation of Mobile Application (Login, Roster and Presence).</p>
<p>##Work</p>
<ul>
<li>Related Info : https://github.com/alexstrat/PhoneGap-XMPPplugin-Android/</li>
<li>Tested Strophe Login using a hardcoded Script to connect to the BOSH Server with fixed Login Details.</li>
<li>Made a View for Login to enter Username and Password.</li>
<li>Problem : Login Form does not remove after Login is Successful.</li>
<li>Contacts Retrieved are displayed as Jid under the login Form.</li>
</ul>
<p>##Problems Faced and Bugs</p>
<ul>
<li>Bug : Login Form not removing.</li>
<li>Presence only received for one Device (Solved) : Occupied with this problem for quiet some time. Realized later that Handler needs to return true, otherwise they work only once.</li>
</ul>
<p>##Final Output</p>
<p><img src="/images/login1.png" alt="Login View" width="360" />
<img src="/images/contacts1.png" alt="Retrieved Contacts Display" width="360" /></p>
<p>##Road Ahead</p>
<ul>
<li>Retrieve VCard, Bug Fixes, Implement Read, CSS Changes.</li>
</ul>
Week 72015-07-15T06:56:41+00:00//www.xmpp-iot.org/gsoc/week-7Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="learning-cordova-with-examples">Learning Cordova with Examples</h4>
<p>##Abstract</p>
<p><a href="https://cordova.apache.org/">Apache Cordova</a> is a platform for building cross-platform applications using HTML, CSS and JavaScript.</p>
<p>This week I have tried various examples in order to have a better understanding of Cordova for the purpose of making an IoT Client application for Android and Apple iOS.</p>
<p>##Work</p>
<ul>
<li>Made a starting application that shows a alert message on starting.</li>
<li>Directory Application that stores the information locally and implement search on it.</li>
<li>Learn View Routing on Cordova.</li>
<li>Understand how to use Location, Contacts and Camera APIs using Cordova.</li>
</ul>
<p>##Images from Example Application</p>
<p><img src="/images/directory.png" alt="Directory" width="360" />
<img src="/images/employee.png" alt="Employee View" width="360" /></p>
<p>##Road Ahead</p>
<ul>
<li>Start with implementation of Application(Login, Strophe Connection, Retrieve Contacts).</li>
</ul>
Week 62015-07-08T14:52:43+00:00//www.xmpp-iot.org/gsoc/week-6Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="history-request-and-its-visualization-using-chartjs">History Request and its Visualization using ChartJs</h4>
<p>##Abstract</p>
<p>History Request is sent to a Device with a FieldName so as to read its values over a period of time. Visualizing these Values can be usefull in many ways, like predicting Temperature Change based on the Previous Values of Temperature.</p>
<p>This Week we will use History to get Values of a Field over a period of time from a Device and Display them in the form of a Line Graph.</p>
<p>##Work</p>
<ul>
<li>Send a hardcoded History Query to a Device and get Values of Field over a particular period of Time.</li>
<li>Extend sending History Query from hardcoded to a command ‘/history day/week/month/year FieldName’ that can be sent to a device using ChatBox.</li>
<li>Parse the Message to Data of ChartJs Line Graph.</li>
<li>Display Graph as a message in the ChatBox.</li>
</ul>
<p>##Problems Faced and Work Arounds</p>
<p>####History Command not receiving any messages.</p>
<ul>
<li>As this was a part of last week work, It was resolved by sending ‘SEQNR’ as a part of the History Query which is Unique Reference Number for the IQ to identify messages related to that IQ.</li>
</ul>
<p>##Final Output
<img src="/images/history1.png" alt="History Requests Step-1" />
<img src="/images/history2.png" alt="History Requests Step-2" />
<img src="/images/history3.png" alt="History Requests Step-3" /></p>
<p>##GSOC MID-EVALUATION WEEK</p>
<p>So this is the time when the First GSOC Evaluation takes place. We have completed 90% of what was mentioned as part of Project Timeline. Also the Features Added to Converse can be tested by cloning dev_iot branch from here “https://github.com/adhish20/converse.js/tree/dev_iot” and setting up an Development Environment for it.</p>
<p>##Road Ahead</p>
<ul>
<li>Making a Mobile Application of an IoT Client using Apache Cordova.</li>
</ul>
Week 52015-07-08T14:06:10+00:00//www.xmpp-iot.org/gsoc/week-5Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="write-and-history-requests">Write and History Requests</h4>
<p>##Abstract</p>
<p>Write Request is sent to a Device JID to set a Field to a particular Numeric Value , for instance Relay of a Device, or “hue” of Philips Hue can be changed through a write command.</p>
<p>History Request is sent to a Device with a FieldName so as to read its values over a period of time.</p>
<p>This Week we will use Write to set numeric values to Device Fields and History to get Values of a Field over a period of time from a Device.</p>
<p>##Work</p>
<ul>
<li>Send a hardcoded Write Query to a Device and set a Field Value to a particular Value.</li>
<li>Extend sending Write Query from hardcoded to a command ‘/write FieldName Value’ that can be sent to a device using ChatBox.</li>
<li>Send a hardcoded History Query to a Device and get Values of Field over a particular period of Time.</li>
</ul>
<p>##Problems Faced and Work Arounds</p>
<p>####History Command not receiving any messages.</p>
<ul>
<li>We tried sending various hardcoded History Queries to the Devices but they were not responding to the History Request.</li>
</ul>
<p>##Final Output
<img src="/images/write1.png" alt="Write Requests Step-1" />
<img src="/images/write2.png" alt="Write Requests Step-2" />
<img src="/images/write3.png" alt="Write Requests Step-3" /></p>
<p>##Road Ahead</p>
<ul>
<li>We will complete implementing History and use ChartJs to Visualize the History in the form of a Line Graph.</li>
</ul>
Week 42015-06-23T22:02:34+00:00//www.xmpp-iot.org/gsoc/week-4Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="read-requests">Read Requests</h4>
<p>##Abstract</p>
<p>Read Request is sent to a Device JID to retrieve Numeric Values from them, for instance Temperature related Values from a Temperature Sensor Device. This Week we will use it to retrieve numeric values from Devices and get them displayed in ChatBoxes.</p>
<p>##Work</p>
<ul>
<li>Send a hardcoded Read Query to a Device and retrieve its values in the console.</li>
<li>Extend sending Read Query from hardcoded to a command ‘/read’ that can be sent to a device using ChatBox.</li>
<li>Parse the message coming back from the Device to Display the Name and Value of Device in ChatBox.</li>
</ul>
<p>##Problems Faced and Work Arounds</p>
<p>####Inputs for Read Request</p>
<ul>
<li>There was a similar problem to that of Disco Query, we were not sending resources when we began, and the device sent back an Error IQ which was resolved as soon as we figured out the same for Disco Query.</li>
</ul>
<p>##Final Output</p>
<p><img src="/images/read.png" alt="Read Requests" /></p>
<p>##Road Ahead</p>
<ul>
<li>We will implement Write and write an API for Raspberry Pi 2 in JavaScript for next week.</li>
</ul>
Week 32015-06-18T20:47:42+00:00//www.xmpp-iot.org/gsoc/week-3Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="disco-requests">Disco Requests</h4>
<p>##Abstract</p>
<p>Disco Query is sent to a JID to check for features related to the JID. This Week we will use it to identify Devices and the IoT Features that they support.</p>
<p>##Work</p>
<ul>
<li>Send Disco Query to all contacts as soon as a JID logs in.</li>
<li>Based on the features received from the contacts set ‘support_0323’ and ‘support_0325’ vars in the Contact Data Structure.</li>
<li>Set some Viewable Difference so as to Differentiate between Contacts and Devices Visually.</li>
</ul>
<p>##Problems Faced and Work Arounds</p>
<p>####Inputs for Disco Query</p>
<ul>
<li>Initially we faced problem with Disco Query that was, We were not able to retrieve features for Devices, while it was working good with normal JIDs.</li>
<li>Disco not working for Devices.</li>
</ul>
<p><img src="/images/disco_1.png" alt="Disco not working for Devices" /></p>
<ul>
<li>Disco working for JIDs.</li>
</ul>
<p><img src="/images/disco_2.png" alt="Disco working for JIDs" /></p>
<ul>
<li>We figured out that the problem faced was because we were sending the Disco Query to Bare_JID instead of sending it to JID/resource.</li>
<li>Disco working for Devices after using Resources.</li>
</ul>
<p><img src="/images/disco_3.png" alt="Disco working for Devices" /></p>
<p>####Visual Difference between Contacts and Devices</p>
<ul>
<li>We started with the Idea of having a different Tabs and Views for IoT Devices, which we were unable to do because of Contact Rendering Issues.</li>
<li>Then we had 2 ideas to replace the above which were to have a different Group for IoT Devices or have a Different Icon for Devices.</li>
<li>We settled down on having a Different Icon for Devices and that is a ‘Wrench’ Icon.</li>
<li>Successful Disco Request and View.</li>
</ul>
<p><img src="/images/disco.png" alt="Successful Disco Request and View" /></p>
<p>##Road Ahead</p>
<ul>
<li>For next week we will implement Read and Write for Devices.</li>
</ul>
Week 22015-06-10T13:46:07+00:00//www.xmpp-iot.org/gsoc/week-2Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="identifying-devices-and-extending-client-to-all-webpages">Identifying Devices and Extending Client to all WebPages</h4>
<p>##Abstract</p>
<p>ConverseJs is a Chat Client that uses XMPP standards. We need to extend its support to <a href="http://xmpp.org/extensions/xep-0323.html">XEP-0323</a> and <a href="http://xmpp.org/extensions/xep-0325.html">XEP-0325</a> standards, so that the client can distinguish between friends and devices.</p>
<p>##Work</p>
<ul>
<li>Extended Chat Client to all Pages.</li>
<li>Instantiated our own BOSH Server at ‘http://jabber.sust.se/xmpp-httpbind/’.</li>
<li>Made a Script that uses XEP-0323 and XEP-0325 to distinguish between devices by sending a Disco Query.</li>
<li>This is the Sequence Diagram for a Successful IoT-Sensor Data Request.
<img src="/images/xep-0323_success.png" alt="Successful IoT-Sensor Data Request" /></li>
</ul>
<p>##Road Ahead</p>
<ul>
<li>Set up a Different Tab for Devices which can read and write values to it.</li>
<li>Creating IoT Device APIs for Devices like intel edison, intel galileo, raspberry PI 2, beagle bone black, etc.</li>
</ul>
Week 12015-06-06T07:12:14+00:00//www.xmpp-iot.org/gsoc/week-1Joachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>#Objective</p>
<h4 id="create-an-interactive-user-interface-for-web-visualisation-client">Create an Interactive user interface for Web Visualisation Client</h4>
<p>##Abstract</p>
<p>For the devices to interact with our website we need a chat client that uses XMPP Protocol.</p>
<p>##Work</p>
<ul>
<li>Used Converse.js to implement a single page Chat Client on the homepage of <a href="http://xmpp-iot.org/">XMPP-IoT</a> Website.</li>
<li>We have used the official <a href="https://bind.jappix.com/">Jappix binding (or BOSH) server</a>.</li>
</ul>
<p>##Road Ahead</p>
<ul>
<li>Extend Chat Client to all Pages.</li>
<li>Instantiate our own BOSH Server.</li>
<li>Differentiate between Friends and Devices.</li>
</ul>
Timeline2015-05-25T23:32:27+00:00//www.xmpp-iot.org/gsoc/timelineJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<html>
<body>
<iframe src="../../timeline.html" width="100%" height="650" frameborder="0"></iframe>
</body>
</html>
Prototyping Tools for IoT - Project Proposal2015-05-11T11:20:57+00:00//www.xmpp-iot.org/gsoc/project-proposalJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>##Abstract</p>
<p>Internet of Things(IoT) is expected to offer advanced connectivity of devices, systems, and services that goes beyond machine-to-machine communications (M2M) and covers a variety of protocols, domains, and applications. We aim at making Tools and create a binding between SleekXMPP and various Devices like Netatmo,intel edison, intel galileo, raspberry PI 2, beagle bone black, etc. which can be controlled by means of Client Applications. Also to check compatibility between Devices, i.e. if they can Talk(exchange Data) between each other.</p>
<p>##Description and Research</p>
<p>The Project contains mainly 6 deliverables, those are:</p>
<ol>
<li>A web html/javascript based client that is used to visualise and control the devices created.</li>
<li>Python scripts toolkit to be run on different devices like raspberry pi, Netatmo etc.</li>
<li>An Access Rights Manager that manages what devices can talk to each other.</li>
<li>Adding Tutorials to xmpp-iot.org site for showing the wrking of above mentioned.</li>
<li>Client-Device Logger that Logs the data of the Device.</li>
<li>Implement a first version of the <a href="http://xmpp.org/extensions/xep-0326.html">XEP-0326</a></li>
</ol>
<p>####1. Web Visualization Client</p>
<p>The web client is a html, javascript xmpp client implemented using Strophe that connect to the xmpp network and through the roster it retrieves its friendship subscriptions that it uses to access xmpp endpoints that is devices.</p>
<p>The Javascript is a web Client used to:</p>
<ul>
<li>Visualize data with graphs.</li>
<li>Reading values on demand.</li>
<li>Sending control commands to change values in the devices.</li>
</ul>
<p>Use of <a href="http://cordova.apache.org/">Cordova</a> in combination makes it possible to deliver the client as an native mobile application.</p>
<p>It runs programs and access data that is stored on the server. Since we are working with Internet of Things(IoT), The device would act as a server for the Client Application where the Client would ask for values from the Device and can also receive Events from the Device.</p>
<p>####2. Python Scripts Toolkit for different Devices</p>
<p>Develop Binding between SleekXMPP and Devices for IoT with easy to use example scripts that serves as the Prototyping Tools. When somebody starts to create a device, they can use these scripts as the base for their devices.</p>
<p>Functions needed by an IoT Device are :</p>
<ul>
<li>Local Storage for Storage of Data and Values.</li>
<li>Easy Configurable I/O Management.</li>
<li>Type Conversions.</li>
<li>Access Security who can retrieve what Information.</li>
</ul>
<p>####3. Access Rights Manager</p>
<p>An application that would check for compatibility between Devices and making the exchange of Data more Secure, i.e. who can access what in which device is managed by this application. All this is according to Provisioning Things as in <a href="http://xmpp.org/extensions/xep-0324.html">XEP-0324</a>.</p>
<p>####4. Tutorials</p>
<p>This would generally consist of Videos or Walkthroughs that can guide users on how to work with the Products that are being made as a part of the Project. which will be put on the <a href="http://xmpp-iot.github.io/">XMPP-IoT</a> site.</p>
<p>####5. Client-Device Logs</p>
<p>A Network Storage that stores logs for “If you make friend with some client it will start logging data for your device”.</p>
<p>####6. First Implementation of XEP-0326</p>
<p>First Implementation of Hiding legacy systems through Concentrators as given in <a href="http://xmpp.org/extensions/xep-0326.html">XEP-0326</a>.</p>
<p>##Approach</p>
<p>My initial work would deal with going through XEP-0323, XEP-0325, XEP-0324 and XEP-0326 which explains how Reading of Things, Writing of Things, Provisioning of Things and Hiding Legacy systems through Concentrators respectively is done. That would form the basis of how the interaction between the devices work. The most complex task would be to create a good user interface that can be a base for others to build on and therefore i will provide more time to this. This would be my methodology of approaching the Project by learning more and more about it and making it the basis of my Implementation.</p>
<p>There might be need of few external Libraries and APIs like for the Client we need Apache Cordova and Strophe and for Device Toolkits, I need to make API of devices that might include some external library depending upon its functionality.</p>
<p>##Timeline</p>
<p>#####Community Bonding Period</p>
<p>Work on necessary documentation for understanding the Architectural and Functional requirements and design of the Deliverables and Come up with a definitive list of Devices. A primary list of Devices consists of intel edison, intel galileo, raspberry PI 2, beagle bone black.</p>
<p>#####Week 1-2( 25 May - 7 June )</p>
<p>Create an Interactive user interface for Web Visualisation Client using HTML, CSS.</p>
<p>#####Week 3( 8 June - 14 June )</p>
<p>Graph Visualiser for Web Client and extending Teaser Tasks(Relay and Make Friend Features) to the Web View.</p>
<p>#####Week 4( 15 June - 21 June )</p>
<p>Extending existing examples to other hardware platforms like for intel edison, intel galileo, raspberry PI 2, beagle bone black, etc.</p>
<p>#####Week 5( 22 June - 28 June )</p>
<p>Come up with a working HTML Client for devices and Access Rights Manager.</p>
<p>#####Week 6( 29 June - 5 July )</p>
<p>Catch Up for Mid Term Evaluation.</p>
<p>#####Week 7-8( 6 July - 19 July )</p>
<p>Make Web Client as Mobile Application using Cordova.</p>
<p>#####Week 9( 20 July - 26 July )</p>
<p>Create a Client-Device Logger that would log data for a device.</p>
<p>#####Week 10-11( 27 July - 8 August )</p>
<p>Make Tutorials and Implement XEP-0326.</p>
<p>#####Week 12( 10 August - 16 August )</p>
<p>Catch Up Week for all Deliverables.</p>
<p>#####Week 13( 17 August - 23 August )</p>
<p>Pencils Down Week, Improve Documentation for all the Products.</p>
<p>##Project Blog</p>
<p>All related stuff and Updates can be found at the <a href="http://xmpp-iot.github.io/gsoc/">XMPP IoT-GSoC Blog</a>.</p>
Project Ideas2015-05-11T09:32:23+00:00//www.xmpp-iot.org/gsoc/project-ideasJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>The XMPP community is part of the Google summer of Code 2015 and for XMPP-IoT we have several projects</p>
<p>#What is this XMPP-IoT
There are many solutions how to connect Internet of Things (IoT) devices to internet, to create services and interesting applications. on this site you find an introduction to how we mimic the world of people chatting to enable <strong>any device to any device</strong> interoperability. Supporting all usecases that IoT needs. Especially the possibility to be a way for companies to interact through federation.</p>
<p>The projects are:</p>
<ul>
<li><a href="http://wiki.xmpp.org/web/Summer_of_Code_2015#Prototyping_tools.2C_for_Internet_of_Things_Using_SleekXMPP_and_Web">prototyping tools with python and javascript</a></li>
<li><a href="http://wiki.xmpp.org/web/Summer_of_Code_2015#Adding_XMPP-IoT_to_the_openHAB_smarthome_project_using_Smack">Adding XMPP-iot to openHAB using java SMACK</a></li>
</ul>
<p>The third IoT realted project is maintained by Process one</p>
<ul>
<li><a href="http://wiki.xmpp.org/web/Summer_of_Code_2015#Provisioning_and_registry_of_Things_.28IoT.29_for_ejabberd">Provisioning and registry of Things for Ejabberd</a></li>
</ul>
<p>You can also propose others if you have an idea. post it to the chat room or mailing list</p>
<p>#Talk to us!</p>
<ul>
<li>We’d really like to talk with you a bit, so please come by the XSF’s GSoC MUC room at gsoc@muc.xmpp.org and have a chat. <a href="http://logs.xmpp.org/gsoc">you find the logs here</a></li>
<li><a href="http://mail.jabber.org/mailman/listinfo/gsoc">Join the gsoc maillist</a></li>
<li>there is also a twitter handle <a href="https://twitter.com/XMPPIoT">@XMPPIoT to be used</a></li>
</ul>
<p>##Teaser tasks for prototyping tools</p>
<p>To be able to quickly startup any project you need to have prototyping tools. Using python and javascript in combination gives you a very quick start on almost any device</p>
<ul>
<li>Run the sample scripts under the <a href="http://xmpp-iot.github.io/tutorials/">Tutorials</a> And propose better ones to understand the concepts.</li>
<li>Create a python script “makingfriends” to manage friendship subscriptions between devices when you need several JID’s to be able to talk to each other.</li>
<li>Build a one to many chat room example of a device sending values to many devices in a MUC chatroom using XEP323 message stanzas</li>
<li>Look at the scripts avaliable in the <a href="https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325/examples/IoT">SleekXMPP IoT examples</a> especially the PhilipsHue. Create a mapping to another open API for a device.</li>
</ul>
<p>##Teaser tasks for openHAB</p>
<p><a href="http://openhab.org/">OpenHAB</a> is an opensoruce project acting as a control environment for a smart home bridging between many different physical protocols.</p>
<ul>
<li>
<p>start an OpenHAB instance and trigger the XMPP module to send a plain chat message <strong>ex “Toggle”</strong> or <strong>“relay=True”</strong>. This can be sent to another OpenHAB instance recieving the message and acting on it’s local variables. It can also be sent to the <a href="http://xmpp-iot.github.io/tutorials/python-tutorial/">python script in the tutorial</a> triggering a relay to “Toggle”.</p>
</li>
<li>
<p>Implement a first SMACK-extension for the <a href="http://xmpp.org/extensions/xep-0323.html">XEP323 basic stanzas</a>. First a read request. <a href="https://github.com/igniterealtime/Smack/tree/master/smack-extensions">Smack extensions</a> some more info <a href="https://www.igniterealtime.org/builds/smack/docs/latest/documentation/extensions/index.html">Smack docs</a></p>
</li>
</ul>
<p>This is maintained by <a href="http://lsys.se/">Joachim Lindborg</a> member of the <a href="http://xmpp.org/about-xmpp/xsf/xsf-member-list/">XMPP Extensions Foundation</a></p>
Being friend with Philips Hue lights2015-01-29T00:00:00+00:00//www.xmpp-iot.org/tutorials/python-philiphshueJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>This tutorial runs a python script on a raspberry, or the like, and
publishes a XMPP JID that you be friend with and then use both <a href="http://xmpp.org/extensions/xep-0323.html">XEP 323</a> read
and <a href="http://xmpp.org/extensions/xep-0325.html">XEP 325</a> control. But you can also use plain chat to interact with
the lamp through simple chat.</p>
<p>#Preparations
you need an environment that can run python scripts.</p>
<h2 id="a-jid-for-each-lamp">A JID for each lamp</h2>
<p>You need one Jabber ID or JID for short. First setup these accounts
for each lamp on your favourite XMPP site for example [jabber.se] or
find one on any of the <a href="https://xmpp.net/directory.php">free public and secure XMPP sites</a></p>
<p>##Get the python code</p>
<p>Clone the philipshue api and SleekXMPP code from github</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span>git clone https://github.com/studioimaginaire/phue.git
Cloning into <span class="s1">'phue'</span>...
<span class="gp">>$ </span>git clone -b xep_0323_325 https://github.com/joachimlindborg/SleekXMPP.git
Cloning into <span class="s1">'SleekXMPP'</span>...</code></pre></figure>
<h2 id="start-the-hue-api-client">start the Hue Api client</h2>
<p>The script will try to connect to the local HUE gateway. If it cannot
get access the script will ask you to push the connect button. If It
is able to connect it will log on to the gateway. It uses the central
Philips Hue service to find the IP adress for the gateway</p>
<ul>
<li>Each lamp is known as “individual” so you start one script for each lamp.</li>
<li>If you don’t provide an individual you will adress the whole group
of lamps connected to the hue gateway</li>
</ul>
<p>when the script starts the first time you need to press the button on
the Philipshue gateway to open access to it. Use a - - debug to get
more information</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span><span class="nb">cd </span>SleekXMPP/examples/IoT/
<span class="gp">>$ </span>python IoT_PhilipsHueApi.py -j john@your.domain.com -p password -n “John” --individual 1
INFO Negotiating TLS
INFO Using SSL version: 3
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate COULD NOT BE VERIFIED.
INFO JID <span class="nb">set </span>to: john@your.domain.com/544301500141697366520183
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate
expiration COULD NOT BE VERIFIED.</code></pre></figure>
<p>you can now start chatting with the lamp by sending <strong>hi</strong> or <strong>?</strong> in
the chat window.</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span><span class="nb">cd </span>SleekXMPP/examples/IoT/
<span class="gp">>$ </span>python IoT_PhilipsHueApi.py -j john@your.domain.com -p password -n “John” --individual 1
INFO Negotiating TLS
INFO Using SSL version: 3
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate COULD NOT BE VERIFIED.
INFO JID <span class="nb">set </span>to: john@your.domain.com/544301500141697366520183
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate
expiration COULD NOT BE VERIFIED.</code></pre></figure>
<p>giving a debug flag would give more information</p>
<h1 id="reading-a-value-from-a-device">Reading a value from a device</h1>
<p>We now start a script that continiously reads values from the first.</p>
<h1 id="writing-a-value-to-a-device">Writing a value to a device</h1>
<p>keep the two scripts above running ans start a third one changing values in the sever device.</p>
Friendship between peers2014-11-24T00:00:00+00:00//www.xmpp-iot.org/basics/being-friendsJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>The most basic concept of using XMPP is the notion of
friends. To exchange data between two endpoints they need to be
friends. The friendship is in reality to peers subscribing to one and
eachothers precense<sup id="fnref:precense"><a href="#fn:precense" class="footnote">1</a></sup> updates.</p>
<p>##Friend request</p>
<p>The friending process starts with one end point asking another for a
“precense subscription” <a href="http://im.about.com/od/imfornewusers/ss/pidgin-account-adding-contacts.htm">Pidgin example</a>
The two enpoints can be in any domains <strong>my-thing@my-domain.com/resource_id</strong> makes a request to <strong>your-thing@your-domain.com/</strong></p>
<p>##Confirm request</p>
<p>The enpoint confirms the request so now we have a single sided
subscription <em>my-thing</em> will recieve precense updates from
<em>your-thing</em>. <em>your-thing</em> now sends a “precense subscription”
back to <em>my-thing</em> which inturn confirms the request.</p>
<p>##Dual subscription</p>
<p>The two enpoints now have a dual subscription in talking to each other
so they can now send read and write. The information is stored on the
servers in the peer’s rosters<sup id="fnref:roster"><a href="#fn:roster" class="footnote">2</a></sup></p>
<p>new session the first thing you recieve is your roster, containing the
state of al your friend relations.</p>
<p>##Having a Parent, Adding security</p>
<p>The usage of friendship is very good if you are a human that can take your own descisions. But if we are a temp sensor we must talk to a trusted friend to ask for permissions.</p>
<p>Every device can have a “best friend” or “parent” which is the trusted party that takes the descisions regarding the device possibilities to respond to friendship requests and access to specific fields.</p>
<p>Using this way of endpoint security creates endless possibilities with
changing the ownership of devcices during first
commissioning[^commission] It can even support the usecase of
thirdparty delivering unnamed Things that you can buy in any store and then transfer them to be your own property</p>
<p>[^commission] The process when a Thing recieves it first configuration.</p>
<p class="notice-inverse"><code class="highlighter-rouge">JID (jabber id):</code> Every account in the XMPP network have an identity that looks like an email adress it is a uniqe identifier in the domain this is called the Jabber ID or <strong>JID</strong>.</p>
<p class="notice-inverse"><code class="highlighter-rouge">Resource:</code> For every login to a server a client will recive a <strong>Resource</strong> this id is used to distinguish between the different session. For example you being logged in to the same account from your <em>ipad</em>, <em>phone</em>, <em>computer</em> etc.
When working with Things it is seldom a Thing has several logins and resources but you should be aware of the possibility.</p>
<div class="footnotes">
<ol>
<li id="fn:precense">
<p>Your state being <em>online</em>, <em>offline</em>, <em>available</em> etc <a href="#fnref:precense" class="reversefootnote">↩</a></p>
</li>
<li id="fn:roster">
<p>The storage of all your friends when you login and start a <a href="#fnref:roster" class="reversefootnote">↩</a></p>
</li>
</ol>
</div>
Hiding legacy systems2014-11-22T00:00:00+00:00//www.xmpp-iot.org/basics/hiding-legacyJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>When talking to a peer you can assume it is a device or thing with node’s and fields. But behind that device there could be a whole legacy system. What if the peer you are talking <em>metering@utility.com</em> is a big system of thousands of devices with many fields.</p>
<p>XMPP-IoT give you the possibility to model your world in different ways we have talked of <strong>Nodes</strong> and <strong>Fields</strong> and that a device can have a flat level with many nodes with fields.</p>
<p>The XMPP-IoT extension <a href="http://xmpp.org/extensions/xep-0326.html">XEP-326 Concentrators</a> makes it possible to extend this with the possibility to describe any hiearchy physical and or logical.</p>
<p>This makes it possible for a peer to investigate another peer and learn about the hiearchy of nodes and fields.</p>
<p>##example hiding a legacy modbus system</p>
<p>Modbus is a communication bus used in many industrial systems.</p>
<p><em>pic on the setup</em></p>
<p>We now model every device on the Modbus bus as a separate Node with Fields under a Datasource called Modbus</p>
Datamodel of things2014-11-20T00:00:00+00:00//www.xmpp-iot.org/basics/Thing-datamodelJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>In XMPP-IoT we have restricted a device to have a flat model consisting of one or many <strong>Node</strong> and each Node can have several <strong>Fields</strong>. Each field conforms to a readable or writable value with an SI unit.</p>
<p>If you would like to create a more complex device with recursive defintions of nodes you should describe them as a concentrator wich also is used to hide legacy systems.</p>
<h2 id="node">Node</h2>
<p>A node is a logical group of field with a unique name in the</p>
<h2 id="field">Field</h2>
Glossary2014-11-19T00:00:00+00:00//www.xmpp-iot.org/basics/GlossaryJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.sePython Read and Write2014-11-16T00:00:00+00:00//www.xmpp-iot.org/tutorials/python-tutorialJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>This tutorial is very simple we start two sripts mimicing two devices
talking to each other one acting as a device with two values a PIR
motion sensor and a RELAY that can toggle “true” “false”.</p>
<figure>
<a href="../../images/Script_to_script.png"><img src="../../images/Script_to_script.png" /></a>
<figcaption>Two scripts talking</figcaption>
</figure>
<h1 id="preparations">Preparations</h1>
<p>you need an environment that can run python scripts.</p>
<h2 id="two-friending-jids">Two friending JID’s</h2>
<p>Setup two accounts on your favourite XMPP site for example
jabber.se. Use any jabber client to test the accounts and make sure
they are friends.</p>
<h2 id="get-the-python-code">Get the python code</h2>
<p>Clone the code from github. Soon released through SleekXMPP</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span>git clone -b xep_0323_325 https://github.com/joachimlindborg/SleekXMPP.git </code></pre></figure>
<h2 id="start-the-server-device">start the server device</h2>
<p>go down to the IoT example catalog. And start one script</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span><span class="nb">cd </span>SleekXMPP/examples/IoT
<span class="gp">>$ </span>python IoT_TestDevice.py -j yourthing@jabber.se -p passwd -n <span class="nb">test
</span>INFO Negotiating TLS
INFO Using SSL version: 3
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate COULD NOT BE VERIFIED.
INFO JID <span class="nb">set </span>to: yourthing@jabber.se/544301500141697366520183
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate expiration COULD NOT BE VERIFIED.</code></pre></figure>
<p>giving a - - debug flag would give more information</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span>python IoT_TestDevice.py -j yourthing@jabber.se -p passwd -n <span class="nb">test</span> --debug
DEBUG Loaded Plugin: RFC 6120: Stream Feature: STARTTLS
DEBUG Loaded Plugin: RFC 6120: Stream Feature: Resource Binding
DEBUG Loaded Plugin: RFC 3920: Stream Feature: Start Session
DEBUG Loaded Plugin: RFC 6121: Stream Feature: Roster Versioning
DEBUG Loaded Plugin: RFC 6121: Stream Feature: Subscription Pre-Approval
DEBUG Loaded Plugin: RFC 6120: Stream Feature: SASL
DEBUG Loaded Plugin: XEP-0030: Service Discovery
DEBUG Loaded Plugin: XEP-0323 Internet of Things - Sensor Data
DEBUG Loaded Plugin: XEP-0325 Internet of Things - Control
DEBUG Loaded Plugin: XEP-0199: XMPP Ping
DEBUG Device object started nodeId <span class="nb">test
</span>DEBUG fields<span class="o">{</span><span class="s1">'Counter'</span>: <span class="o">{</span><span class="s1">'dataType'</span>: None, <span class="s1">'type'</span>: <span class="s1">'numeric'</span>, <span class="s1">'unit'</span>: <span class="s1">'Count'</span><span class="o">}</span>, <span class="s1">'Relay'</span>: <span class="o">{</span><span class="s1">'dataType'</span>: None, <span class="s1">'type'</span>: <span class="s1">'numeric'</span>, <span class="s1">'unit'</span>: <span class="s1">'Bool'</span><span class="o">}}</span>
DEBUG momentary<span class="o">{}</span>
DEBUG momentary updated<span class="o">{</span><span class="s1">'Counter'</span>: <span class="o">{</span><span class="s1">'flags'</span>: <span class="o">{</span><span class="s1">'momentary'</span>: <span class="s1">'true'</span>, <span class="s1">'automaticReadout'</span>: <span class="s1">'true'</span><span class="o">}</span>, <span class="s1">'value'</span>: <span class="s1">'0'</span><span class="o">}}</span>
DEBUG fields<span class="o">{</span><span class="s1">'Counter'</span>: <span class="o">{</span><span class="s1">'dataType'</span>: None, <span class="s1">'type'</span>: <span class="s1">'numeric'</span>, <span class="s1">'unit'</span>: <span class="s1">'Count'</span><span class="o">}</span>, <span class="s1">'Relay'</span>: <span class="o">{</span><span class="s1">'dataType'</span>: None, <span class="s1">'type'</span>: <span class="s1">'numeric'</span>, <span class="s1">'unit'</span>: <span class="s1">'Bool'</span><span class="o">}}</span>
DEBUG momentary<span class="o">{</span><span class="s1">'Counter'</span>: <span class="o">{</span><span class="s1">'flags'</span>: <span class="o">{</span><span class="s1">'momentary'</span>: <span class="s1">'true'</span>, <span class="s1">'automaticReadout'</span>: <span class="s1">'true'</span><span class="o">}</span>, <span class="s1">'value'</span>: <span class="s1">'0'</span><span class="o">}}</span>
DEBUG momentary updated<span class="o">{</span><span class="s1">'Counter'</span>: <span class="o">{</span><span class="s1">'flags'</span>: <span class="o">{</span><span class="s1">'momentary'</span>: <span class="s1">'true'</span>, <span class="s1">'automaticReadout'</span>: <span class="s1">'true'</span><span class="o">}</span>, <span class="s1">'value'</span>: <span class="s1">'0'</span><span class="o">}</span>, <span class="s1">'Relay'</span>: <span class="o">{</span><span class="s1">'flags'</span>: <span class="o">{</span><span class="s1">'writable'</span>: <span class="s1">'true'</span>, <span class="s1">'momentary'</span>: <span class="s1">'true'</span>, <span class="s1">'automaticReadout'</span>: <span class="s1">'true'</span><span class="o">}</span>, <span class="s1">'value'</span>: <span class="s1">'0'</span><span class="o">}}</span></code></pre></figure>
<h1 id="reading-a-value-from-a-device">Reading a value from a device</h1>
<p>We now start a script that every 6th seconde reads all values from the first.</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span><span class="nb">cd </span>SleekXMPP/examples/IoT
<span class="gp">>$ </span>python IoT_TestDevice.py -j anotherthing@jabber.se -p passwd -g
yourthing@jabber.se --delay 6
INFO Negotiating TLS
INFO Using SSL version: 3
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate COULD NOT BE VERIFIED.
INFO JID <span class="nb">set </span>to: anotherthing@jabber.se/28
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate
expiration COULD NOT BE VERIFIED.
INFO IoT SEND 323 REQ <iq <span class="nv">to</span><span class="o">=</span><span class="s2">"yourthing@jabber.se/98"</span> <span class="nv">from</span><span class="o">=</span><span class="s2">"anotherthing@jabber.se/28"</span> <span class="nv">id</span><span class="o">=</span><span class="s2">"2"</span> <span class="nb">type</span><span class="o">=</span><span class="s2">"get"</span>><req <span class="nv">xmlns</span><span class="o">=</span><span class="s2">"urn:xmpp:iot:sensordata"</span> <span class="nv">seqnr</span><span class="o">=</span><span class="s2">"2"</span> <span class="nv">momentary</span><span class="o">=</span><span class="s2">"true"</span> /></iq>
INFO IoT RECIEVE <message <span class="nv">to</span><span class="o">=</span><span class="s2">"anotherthing@jabber.se/28"</span> <span class="nv">from</span><span class="o">=</span><span class="s2">"yourthing@jabber.se/28"</span> xml:lang<span class="o">=</span><span class="s2">"en"</span>><fields <span class="nv">xmlns</span><span class="o">=</span><span class="s2">"urn:xmpp:iot:sensordata"</span> <span class="nv">seqnr</span><span class="o">=</span><span class="s2">"2"</span> <span class="k">done</span><span class="o">=</span><span class="s2">"true"</span>><node <span class="nv">nodeId</span><span class="o">=</span><span class="s2">"test"</span>><timestamp <span class="nv">value</span><span class="o">=</span><span class="s2">"2015-02-10T03:26:26"</span>><numeric <span class="nv">unit</span><span class="o">=</span><span class="s2">"Count"</span> <span class="nv">automaticReadout</span><span class="o">=</span><span class="s2">"true"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"Counter"</span> <span class="nv">value</span><span class="o">=</span><span class="s2">"3"</span> <span class="nv">momentary</span><span class="o">=</span><span class="s2">"true"</span> /><boolean <span class="nv">writable</span><span class="o">=</span><span class="s2">"true"</span> <span class="nv">automaticReadout</span><span class="o">=</span><span class="s2">"true"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"relay"</span> <span class="nv">value</span><span class="o">=</span><span class="s2">"False"</span> <span class="nv">momentary</span><span class="o">=</span><span class="s2">"true"</span> /></timestamp></node></fields></message>
INFO we got fields from yourthing@jabber.se/28 on node <span class="nb">test
</span>INFO <span class="o">(</span><span class="nb">test </span>Counter 3<span class="o">)</span> Count <span class="o">[</span>momentary,automaticReadout,]
INFO <span class="o">(</span><span class="nb">test </span>relay False<span class="o">)</span> <span class="o">[</span>writable,momentary,automaticReadout,]</code></pre></figure>
<h1 id="writing-a-value-to-a-device">Writing a value to a device</h1>
<p>keep the two scripts above running and start a third one sending a
value change True on the “Toggle” field every 10th second</p>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="gp">>$ </span><span class="nb">cd </span>SleekXMPP/examples/IoT
<span class="gp">>$ </span>python IoT_TestDevice.py -j anotherthing@jabber.se -p passwd -c
yourthing@jabber.se --field <span class="s2">"Toggle"</span> --value <span class="s2">"True"</span> --delay 10
INFO Negotiating TLS
INFO Using SSL version: 3
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate COULD NOT BE VERIFIED.
INFO JID <span class="nb">set </span>to: anotherthing@jabber.se/28
WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate
expiration COULD NOT BE VERIFIED.
INFO IoT will <span class="nb">set </span>Toggle to True on to <span class="o">{</span>u<span class="s1">'28'</span>: <span class="o">{</span><span class="s1">'status'</span>: u<span class="s1">''</span>,
<span class="s1">'priority'</span>: 0, <span class="s1">'show'</span>: u<span class="s1">''</span><span class="o">}}</span>
INFO Control callback from yourthing@jabber.se/98 result OK error None
INFO IoT will <span class="nb">set </span>Toggle to True on to <span class="o">{</span>u<span class="s1">'28'</span>: <span class="o">{</span><span class="s1">'status'</span>: u<span class="s1">''</span>,
<span class="s1">'priority'</span>: 0, <span class="s1">'show'</span>: u<span class="s1">''</span><span class="o">}}</span>
INFO Control callback from yourthing@jabber.se/98 result OK error None</code></pre></figure>
<p>You now see the value of the relay changing once in a while in script
reading values from the first instance.</p>
<h1 id="what-have-you-done">What have you done?</h1>
<p>You have now sent standardized calls between to endpoints that can be on
any federated xmpp server on internet there are several
https://xmpp.net/directory.php. Just imagin how devices now can talk
between companies in a defined way.</p>
Javascript Read and Write2014-11-16T00:00:00+00:00//www.xmpp-iot.org/tutorials/javascript-tutorialJoachim Lindborg//www.xmpp-iot.org/joachim.lindborg@lsys.se
<p>This tutorial shows how to make a web client that can read and write values to XMPP-IoT devices it is based on the Strophe.js package and node.js</p>
<p>#Preparations
you need to have a device running somewhere supporting xmpp-iot-xep-323 read and xmpp-iot-xep-325</p>
<p>if you haven’t one available by your self open a window towards the <a href="http://sust.se/iot-lab.html">Sustainable Innovation IoT lab</a></p>
<h1 id="read-a-value">Read a value</h1>
<h1 id="write-a-value">Write a value</h1>