<?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[Stories by Guido Bellomo on Medium]]></title>
        <description><![CDATA[Stories by Guido Bellomo on Medium]]></description>
        <link>https://medium.com/@javascriptjedi?source=rss-5c1f127e83d5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*k-0TIcb0i4Jq0Z9Z.jpg</url>
            <title>Stories by Guido Bellomo on Medium</title>
            <link>https://medium.com/@javascriptjedi?source=rss-5c1f127e83d5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:42:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@javascriptjedi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[RedBot: sviluppare chatbot con Node-RED]]></title>
            <link>https://medium.com/convcomp2016/redbot-sviluppare-chatbot-con-node-red-d3783306459f?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3783306459f</guid>
            <category><![CDATA[tecnologia]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Mon, 12 Nov 2018 17:11:54 GMT</pubDate>
            <atom:updated>2018-11-12T17:11:54.874Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L5zv7FlYyhws7s-KLOzQAA.png" /><figcaption>Esempio di chatbot sviluppato con RedBot/Node-RED</figcaption></figure><p><a href="http://red-bot.io/">RedBot</a> è una piattaforma open source per creare chatbot per <strong>Telegram</strong>, <strong>Slack</strong>, <strong>Viber</strong>, <strong>Twilio</strong> e <strong>Facebook</strong>.</p><p>Come spesso capita con i progetti open source, <strong>RedBot</strong> è nato per soddisfare un’esigenze personale: mi ero messo in testa di controllare tutti i device di casa (termostato, valvole dei caloriferi, security cam, etc) da un’unico punto tramite le rispettive API. Non volevo creare un’altra app mobile, mi serviva qualcosa con un interfaccia minimale. Un chatbot era il candidato ideale: la maggior parte delle piattaforme di chat infatti supporta elementi grafici quali bottoni, immagini, link, etc.</p><p>Dopo un pò di test vari mi ero fatto un’idea piuttosto precisa sui requisiti della piattaforma di cui avevo bisogno:</p><ul><li><strong>open-source</strong>: un chatbot che non comunica con l’esterno (CRM, IoT, etc) e’ un chatbot inutile, per cui la capacità di interfacciarsi con l’esterno è una delle caratteristiche più importanti. <br>Molte piattaforme permettono di interfacciarsi con l’esterno tramite chiamate <em>http</em>, non sempre però è possibile parametrizzarle (ad esempio inserendo dati presi dalla conversazione corrente). Nessuna piattaforma permette di ricevere chiamate con la conseguente impossibilità di iniziare una conversazione partendo da uno stimolo esterno. <br>Un sistema chiuso impone restrizioni sull’implementazione della bussiness logic del chatbot che prima o poi pesano su qualunque progetto.</li><li><strong>visuale</strong>: un chatbot complesso presenta flussi di conversazione di cui non è facile avere una panoramica guardando il solo codice. Inoltre lo sviluppo di un chatbot spesso procede per numerosi piccoli aggiustamenti che è sicuramente più facile eseguire su interfacce semplici piuttosto che sul puro codice. Non da ultimo, è probabile che sul chatbot debbano lavorare prefessionalità diverse da un programmatore, che non possono o non vogliono mettere le mani al codice (si pensi ad un traduttore, un copywriter, etc).</li><li><strong>multi-platform</strong>: la stessa implementazione deve poter funzionare su piattaforme diverse (almeno <strong>Telegram</strong>, <strong>Facebook</strong> e <strong>Slack </strong>e assistenti vocali quali <strong>Alexa</strong> e <strong>Google Assistant</strong>).</li></ul><p>La frustrazione di non riucire a trovare qualcosa che fosse sufficientemente aperto e allo stesso tempo visuale mi ha spinto a creare qualcosa di nuovo.</p><p>Fortunatamente non sono dovuto partire da zero, esisteva già <a href="https://nodered.org/">Node-RED</a>: un tool open source di programmazione <em>flow-based</em> con cui si possono creare programmi semplicemente connettendo più blocchi funzionali, il tutto in maniera visuale.</p><p>I blocchi di base sono molti: da quelli logici e per il controllo di flusso (<em>if</em>, <em>switch</em>, etc) ad altri più operativi (manipolazione di files, ricevere e rispondere a chiamate <em>http</em>, etc) ed ovviamente è possibile creare nuovi <em>nodi</em> in <em>JavaScript</em>: sono più di <a href="https://flows.nodered.org/?num_pages=1">1000 nodi custom</a> disponibili.</p><p>Poichè la conversazione con un chatbot è facilmente assimilabile ad un flusso di eventi, ho iniziato a creare <em>nodi</em> con cui estendere <strong>Node-RED</strong>: da quelli specifici per inviare e ricevere messaggi per le piattaforme supportate a quelli per costruire i veri e propri <em>blocchi</em> della conversazione con il chatbot.</p><p>Ad esempio, il flusso del più semplice dei chatbot (<em>“Hello world!”</em>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqVIr1yd4Gid2tnMa95Gpg.png" /><figcaption>Hello World chatbot</figcaption></figure><p>Ogni messaggio ricevuto dal chatbot viene replicato sull’uscita del nodo <em>receiver</em>. Per rispondere alla conversazione è sufficiente inserire un blocco <em>text</em> e inviarlo al nodo <em>sender</em>.<br>Ogni nodo è configurabile tramite tramite l’interfaccia di <strong>Node-RED</strong>, in questo modo la maggior parte delle operazioni sul chatbot avvengono senza toccare il codice:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*B_7rV6xZd44Z8G_zKcFUEA.png" /></figure><p>Sono disponibili diversi blocchi di conversazione: per inviare immagini, file, video, codici QR, messaggi vocali, etc. quasi tutti cross-platform: il medesimo flusso sarà riutilizzabile, piazzando gli opportuni <em>senders</em>/<em>receivers,</em> per tutte le altre piattaforme supportate.</p><p>In particolare, nel caso di <strong>Telegram,</strong> il set-up è particolarmente semplice, per cui bastano pochi click per mettere in piedi un chatbot funzionante.</p><p>Vi sono inoltre una serie di nodi per eseguire l’analisi del testo (<strong>Natural Language Processing</strong>) dai più semplici basati su librerie di terze parti come <a href="https://www.rivescript.com/">RiveScript</a> e <a href="https://github.com/spencermountain/compromise">Compromise</a> a quelli più complessi che si appoggiano a servizi esterni come <a href="http://www.dialogflow.com/">Dialogflow</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NVAEmInrUluvIN_W07ELg.png" /><figcaption>Controllo di flusso sull’intent rilevato da Dialogflow</figcaption></figure><p>A completamento del tutto vi sono alcuni nodi per controllare di flusso in modo da instradare la conversazione verso un particolare sotto-flusso in base a parametri come la lingua, l’intent rilevato, il valore di una variabile, etc. i quali, in accoppiata con il nodo <em>function</em> di <strong>Node-RED</strong> (in cui è possibile eseguire direttamente codice <em>JavaScript</em>), permettono di districarsi in qualunque bussiness logic ci si ritrovi a dover implementare.</p><p><strong>RedBot</strong> permette inoltre di semplificare operazioni molto comuni quando si sviluppano chatbot, come ad esempio proseguire la conversazione (<em>follow-up</em>) con l’utente e salvare dati in uno spazio di memoria (<em>chat-context</em>): ad esempio un semplice flusso per chiedere l’indirizzo email dell’utente:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*JGcVNT91D3f-ZDKBi6clQg.png" /><figcaption>Follow-up di una conversazione</figcaption></figure><p>Il primo messaggio testuale pone la domanda all’utente (<em>“Qual è il tuo indirizzo email?”</em>), l’eventuale risposta dell’utente arriverà direttamente sull’uscita del primo <em>sender</em> e fatta passare attraverso il nodo <em>parser </em>che cercherà di estrarre una mail valida, in caso positivo il flusso proseguirà sulla prima uscita e il valore trovato verrà salvato nello spazio di memoria relativo all’utente corrente (che può essere quindi utilizzato per salvare lo stato della discussione in atto).<br>I valori salvati nel <em>chat-context</em> possono essere utilizzati nei nodi <em>function </em>(<em>JavaScript</em>), sia più semplicemente nei messaggi con semplici placeholders: <em>“Grazie per la tua email: {{email}}”</em>.</p><p>GitHub: <a href="https://github.com/guidone/node-red-contrib-chatbot">RedBot</a>/<a href="https://github.com/node-red/node-red">Node-RED</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3783306459f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/convcomp2016/redbot-sviluppare-chatbot-con-node-red-d3783306459f">RedBot: sviluppare chatbot con Node-RED</a> was originally published in <a href="https://medium.com/convcomp2016">ConvComp.it</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RedBot Analytics]]></title>
            <link>https://medium.com/javascriptjedi/redbot-analytics-8ada0f63669?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ada0f63669</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[telegram]]></category>
            <category><![CDATA[redbot]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Fri, 26 May 2017 07:18:59 GMT</pubDate>
            <atom:updated>2017-05-26T07:22:44.679Z</atom:updated>
            <content:encoded><![CDATA[<p>With <strong>RedBot</strong> is not possible to track conversation with an external analytics platform like <a href="http://dashbot.io/">Dashbot.io</a>:</p><figure><img alt="Analytics node" src="https://cdn-images-1.medium.com/proxy/1*Ap5IuNtA4uFHNGQiukx_hg.png" /><figcaption>Analytics node</figcaption></figure><p>Just place the Analytics Node after a receiver node (like the Telegram Receiver Node) and just before a sender node (like the Telegram Sender Node), it will track the message to the analytics platform and pass through the message to the output node (it will handle correctly inbound and outbound messages automatically)</p><figure><img alt="Dashbot.io dashboard" src="https://cdn-images-1.medium.com/proxy/1*8oGKRVmc3c9GX4CbW5rQkg.png" /><figcaption>Dashbot.io dashboard</figcaption></figure><p>The analytics feature is not embedded in the sender/receiver nodes, in this way with a simple Switch Node it&#39;s possible to filter out messages that don’t have to be tracked, for example messages with sensible information (like password, etc.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ada0f63669" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/redbot-analytics-8ada0f63669">RedBot Analytics</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logging conversations with RedBot]]></title>
            <link>https://medium.com/javascriptjedi/logging-conversations-with-redbot-f3873f850afd?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3873f850afd</guid>
            <category><![CDATA[node-red]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[logs]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Wed, 05 Oct 2016 17:17:59 GMT</pubDate>
            <atom:updated>2017-04-11T08:09:00.209Z</atom:updated>
            <content:encoded><![CDATA[<p>Running a chat bot requires some caring, in particular you’re never done training it.</p><p>A good habit is to inspect the chat bot log searching for user sentences that were not recognized by the bot and then the parsers (Listen Node, RiveScript Node, etc) in order to support it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/0*ec9okJSQ70qqkMQj.png" /><figcaption>Log filename</figcaption></figure><p>In <a href="https://github.com/guidone/node-red-contrib-chatbot">RedBot</a> every platform receiver can log the conversation to a file, it looks like</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a598c39872d1aefd0c8462ae72184ad8/href">https://medium.com/media/a598c39872d1aefd0c8462ae72184ad8/href</a></iframe><p>The first string is the <em>chatId</em> followed by the name (if available). Then the symbol <strong>&gt;</strong> means it’s an inbound message (from user to the chat bot).</p><p>There is also the Log Node that produces a log string for every message that can be manipulated inside <strong>Node-RED</strong> (in case for example the log string should be sent to an external service).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3873f850afd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/logging-conversations-with-redbot-f3873f850afd">Logging conversations with RedBot</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Store user response in RedBot]]></title>
            <link>https://medium.com/javascriptjedi/store-user-response-in-redbot-4f8eb08618cc?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f8eb08618cc</guid>
            <category><![CDATA[email]]></category>
            <category><![CDATA[node-red]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Fri, 16 Sep 2016 13:38:44 GMT</pubDate>
            <atom:updated>2017-04-10T09:30:28.610Z</atom:updated>
            <content:encoded><![CDATA[<p>Working with chatbots it’s sometimes useful to parse and store the user response somewhere.</p><p>In <a href="https://github.com/guidone/node-red-contrib-chatbot">RedBot</a> there’s the <em>chat context</em>, it’s a volatile memory space where it’s possible to store variables related to the current chat user, for example consider this flow in which we ask the user to type in his email</p><figure><img alt="parse-email" src="https://cdn-images-1.medium.com/max/1024/0*_RL2ygZdYGx5bolN.png" /></figure><p>The first <strong>Message node</strong> just sends out the question to the user <em>“What is your email?”</em> (always use a conversational tone with a chatbot and not cold robotic sentences like <em>“Type your email”</em>).</p><p>Note that the <strong>Telegram Sender node</strong> has the <strong>track</strong> option enabled, that means that the chat flows will re-start from here: any answer from the chat user will be redirected to the output pin following the rest of the flow.</p><p>The <strong>Parse node</strong> analyze the incoming message and cab be configure to search for a pattern, it could be email, image, location, etc.<br>In that case it searches for a valid email: if the content of the incoming messages matches the pattern, the value is stored in the chat context and the output is redirected to the first output, otherwise the second output.</p><p>If the user’s input doesn’t match a valid email, a warning message is sent to the user and the flow restart from the node asking for the email.</p><p>If a valid email is found, it’s stored in the chat context (the name of the variable can be configured in the <strong>Parse node</strong> panel) and it’s available in the rest of the flow.</p><p>For example we can use it in the final <strong>Message node</strong> with a handlebars-like syntax with the text: <em>“Thanks, from now on I’ll use {{myemail}} as your email”</em>.</p><p>Or we can use it in a <strong>Function node</strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a97cc9d8e279640cb70583a35585aa8d/href">https://medium.com/media/a97cc9d8e279640cb70583a35585aa8d/href</a></iframe><p>To setup a Telegram bot, follow the <a href="http://javascript-jedi.com/simple-telegram-chatbot-with-redbot/">tutorial</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f8eb08618cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/store-user-response-in-redbot-4f8eb08618cc">Store user response in RedBot</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup a development chatbot for Facebok and RedBot]]></title>
            <link>https://medium.com/javascriptjedi/setup-a-development-chatbot-for-facebok-and-redbot-d0ad6254ad96?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0ad6254ad96</guid>
            <category><![CDATA[facebook-messenger]]></category>
            <category><![CDATA[node-red]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Thu, 01 Sep 2016 11:45:10 GMT</pubDate>
            <atom:updated>2017-04-10T12:06:35.836Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a quick tutorial to setup a very simple chatbot with <strong>Facebook Messenger</strong> and <a href="https://github.com/guidone/node-red-contrib-chatbot">RedBot</a>.</p><p>First of all install <a href="http://nodered.org/docs/getting-started/installation">Node-RED</a></p><pre>sudo npm install -g node-red</pre><p>Then open the user data directory <em>$HOME/.node-red</em> and install the package</p><pre>cd $HOME/.node-red<br>npm install node-red-contrib-chatbot</pre><p>Then run</p><pre>node-red</pre><p>Setting up a <strong>Facebook Messenger</strong> is quite tricky since <strong>Facebook API</strong> talks to <strong>Red-Node</strong> via a https callback (a self signed certificate is not enough). It also requires a verify token that makes the whole process non linear and confusing.</p><p>We’ll use <strong>ngrok</strong> to create a https tunnel for our local Node-RED instance. <a href="https://ngrok.com/download">Install it</a>, then open a shell window and run</p><pre>ngrok http 127.0.0.1:1088</pre><p>Grab the https address you get, something like <a href="https://123123.ngrok.io,/"><strong>https://123123.ngrok.io</strong>,</a> this is the base url of the Facebook callback (<strong>update:</strong> now the Facebook web hook is mounted on the same address/port of <strong>Node-Red</strong>),</p><figure><img alt="fb-tutorial-2.png" src="https://cdn-images-1.medium.com/max/682/0*jxpJJ-4bKopGLFEX.png" /></figure><p>The callback is</p><pre><a href="http://youraddress.ngrok.io/redbot/facebook">http://<strong>youraddress.ngrok.io</strong>/redbot/facebook</a></pre><p>Replace the hostname in bold with what you got above.<a href="https://developers.facebook.com/"><br>Start here</a> create a new Facebook app</p><figure><img alt="fb-tutorial-1.png" src="https://cdn-images-1.medium.com/max/751/0*ueP957K_Jbqfd0zp.png" /></figure><p>Then click on <em>“get started with Messenger”</em>. Your Facebook app must be connected to a Facebook page, select one from the drop down menu (or create one if you don’t have any) and confirm, that will create a new <strong>access token</strong></p><figure><img alt="fb-tutorial-3" src="https://cdn-images-1.medium.com/max/808/0*3nwny4NeaNYOjoTP.png" /></figure><p>Copy this value as well as the <strong>app secret</strong> that you find in the <em>“dashboard”</em> section. Don’t close this page yet and open <strong>Node-Red</strong>.</p><p>Add a new Facebook Receiver Node, then open the configuration of the node and fill up form with the <strong>access token</strong> and <strong>app secret</strong> you got before, then give a name to this configuration for your convenience and specify the <strong>verify token</strong>: this is an arbitrary string, you can put here whatever you like, just remember it you’ll need in the next step.</p><figure><img alt="fb-tutorial-5" src="https://cdn-images-1.medium.com/max/1024/0*30Bj9l4UUfffuXeJ.png" /></figure><p>Save your node and switch back to the <strong>Facebook App</strong> configuration page, click on <em>“Setup webhooks”</em></p><figure><img alt="fb-tutorial-4" src="https://cdn-images-1.medium.com/max/1024/0*p68cqtR2skKrN7qE.png" /></figure><p>Copy the callback url you got before and the arbitrary verify token you put in <strong>Node-RED</strong>, don’t forget to check <em>“messages”</em>.</p><p>Click on <em>“Verify and Save”</em>, if you don’t get any error means Facebook is able to contact your <strong>Node-RED</strong> instance and everything is ok.<br>If you get an error means that you have used wrong parameters (access token, app secret, etc) or, for some reason, Facebook APIs cannot reach the your callback url.<br>To exclude the second option and be sure that your <strong>Node-RED</strong> instance works correctly, grab your <strong>ngrok</strong> url and open this address</p><pre><a href="http://youraddress.ngrok.io/redbot/facebook/_status">http://youraddress.ngrok.io/redbot/facebook/<strong>_status</strong></a></pre><p>If you get an <em>“ok”</em> then <strong>Node-RED</strong> is up and running.</p><p>The most is done, let’s test if it works: connect a Debug Node to the Facebook Receiver Node, then open the <strong>Facebook</strong> page selected with the drop down (when the access token was generated), click on the <em>“Message”</em> button and type anything.</p><p>Something should be visible in the console. From now on everything is similar to what explained in the <a href="http://javascript-jedi.com/simple-telegram-chatbot-with-redbot/">Telegram chat bot tutorial</a> (most of the nodes in <strong>RedBot</strong> can be used for all platforms Telegram, Facebook, Slack so there’s no need to create platform specific flows).</p><p>Happy chatboting!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0ad6254ad96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/setup-a-development-chatbot-for-facebok-and-redbot-d0ad6254ad96">Setup a development chatbot for Facebok and RedBot</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NetAtmo dashboard for Node-RED]]></title>
            <link>https://medium.com/javascriptjedi/netatmo-dashboard-for-node-red-71e70b679681?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/71e70b679681</guid>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[netatmo]]></category>
            <category><![CDATA[node-red]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Mon, 29 Aug 2016 19:00:01 GMT</pubDate>
            <atom:updated>2017-04-10T12:13:40.178Z</atom:updated>
            <content:encoded><![CDATA[<p>There are few <a href="http://nodered.org/">Node-RED</a> nodes for the <a href="https://www.netatmo.com/">NetAtmo</a> weather station, most of them return data of the sensors as time series.</p><p>I needed something simpler for my <a href="https://telegram.me/guidone_bot">chatbot</a>, a way to get fetch all current values from all sensors, something like this</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/436d9544d1510f85d7a12bba3ac2763f/href">https://medium.com/media/436d9544d1510f85d7a12bba3ac2763f/href</a></iframe><p>So I created this <a href="http://node-red-contrib-netatmo-dashboard/">node-red-contrib-netatmo-dashboard</a>.</p><p>To install</p><pre>cd $HOME/.node-red<br>npm install  node-red-contrib-netatmo-dashboard</pre><p>See <a href="https://dev.netatmo.com/">Netatmo Connect</a> to get an API key.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71e70b679681" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/netatmo-dashboard-for-node-red-71e70b679681">NetAtmo dashboard for Node-RED</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup a simple Telegram chatbot with RedBot]]></title>
            <link>https://medium.com/javascriptjedi/setup-a-simple-telegram-chatbot-with-redbot-84c2f8ac1024?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/84c2f8ac1024</guid>
            <category><![CDATA[setup]]></category>
            <category><![CDATA[telegram]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[redbot]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Thu, 25 Aug 2016 22:07:08 GMT</pubDate>
            <atom:updated>2017-04-10T12:18:44.450Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a quick tutorial to setup a very simple chatbot with <strong>Telegram</strong> and <a href="https://github.com/guidone/node-red-contrib-chatbot">RedBot</a>.</p><p>First of all install <a href="http://nodered.org/docs/getting-started/installation">Node-RED</a></p><pre>sudo npm install -g node-red</pre><p>Then open the user data directory <em>$HOME/.node-red</em> and install the package</p><pre>cd $HOME/.node-red<br>npm install node-red-contrib-chatbot</pre><p>Then run</p><pre>node-red</pre><p>The next step is to create a chat bot, I reccomend to use <strong>Telegram</strong> since the setup it’s easier ( <strong>Telegram</strong> allows polling to receive messages, <strong>Facebook</strong> requires a https callback and a valid https certificate).<br><strong>Telegram</strong> is really coherent and you have to use a chat bot to create a chatbot. Connect to <strong>@BotFather</strong> and type /newbot, then in the next two steps give the bot a name and username (this will be the real unique address of your chatbot), you’ll get something like this for <strong>@my_new_chat_bot</strong></p><figure><img alt="telegram-token" src="https://cdn-images-1.medium.com/max/1023/0*0wrljAbA4L4lk05z.png" /></figure><p>Copy and paste the access <strong>token</strong>. For more information <a href="https://core.telegram.org/bots#botfather">read here</a>.</p><p>Then open your <strong>Node-RED</strong> and add a Telegram Receiver, in the configuration panel, add a new bot and paste the <strong>token</strong></p><figure><img alt="example-telegram-receiver.png" src="https://cdn-images-1.medium.com/max/1024/0*DaWrRGgBRaBlbHRA.png" /></figure><p>Now add a Message Node and connect to the Telegram Receiver</p><figure><img alt="example-simple-message.png" src="https://cdn-images-1.medium.com/max/1024/0*QcLv9APpSwxtko1-.png" /></figure><p>Finally add a Telegram Sender Node, don’t forget to select in the configuration panel the same bot of the Telegram Receiver, this should be the final layout</p><figure><img alt="example-simple.png" src="https://cdn-images-1.medium.com/max/1024/0*O6MFyzHW00kT1wkX.png" /></figure><p>Now you have a useful bot that answers <strong>“Hi there!”</strong> to any received message.</p><p>Receving the same answers is not very useful, we can introduce Command Node: it will pass through the output only if the input message is <em>“hi”</em>:</p><figure><img alt="telegram-command" src="https://cdn-images-1.medium.com/max/773/0*-Di5hBoUH-X_VBMi.png" /></figure><p>In this way it’s possible to trigger different actions with different commands, read more about <strong>Telegram</strong> commands <a href="https://core.telegram.org/bots#commands">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84c2f8ac1024" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/setup-a-simple-telegram-chatbot-with-redbot-84c2f8ac1024">Setup a simple Telegram chatbot with RedBot</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RedBot, a chatbot framework for Node-RED]]></title>
            <link>https://medium.com/javascriptjedi/redbot-a-chatbot-framework-for-node-red-7746f8815427?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7746f8815427</guid>
            <category><![CDATA[redbot]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Tue, 23 Aug 2016 20:59:39 GMT</pubDate>
            <atom:updated>2017-04-11T08:35:54.489Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="RedBot_logo" src="https://cdn-images-1.medium.com/max/807/0*K1JNejqpXYdKHOat.png" /></figure><h4>RedBot is a Node-RED framework to create chatbots for Telegram, Facebook and Slack. Almost no coding skills required.</h4><blockquote>Node-RED is a tool for wiring together hardware devices, APIs and online services in new and interesting ways.</blockquote><p>With <strong>RedBot</strong> it’s possible to easily create chatbots just wiring together basic blocks like <em>message</em>, <em>audio</em>, <em>location</em>, etc. and interact with the Node-RED <a href="http://flows.nodered.org/">ecosystem</a>. If you have particular need, you can do it by yourself in NodeJS, it’s all open source!</p><p><strong>RedBot</strong> is able to understand user’s input using a simple token-based detector or more advanced language interaction like <a href="https://www.rivescript.com/">RiveScript</a>.</p><figure><img alt="RedBot node palette" src="https://cdn-images-1.medium.com/max/1024/0*ziab_4My1StijzEI.png" /></figure><p>The <a href="https://github.com/guidone/node-red-contrib-chatbot">GitHub repository</a> and a <a href="https://github.com/guidone/node-red-contrib-chatbot#getting-started">quick tutorial to setup a Telegram chat bot</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7746f8815427" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/redbot-a-chatbot-framework-for-node-red-7746f8815427">RedBot, a chatbot framework for Node-RED</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guidone]]></title>
            <link>https://medium.com/@javascriptjedi/guidone-c92307c9364c?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c92307c9364c</guid>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Fri, 27 Dec 2013 13:25:16 GMT</pubDate>
            <atom:updated>2013-12-27T13:25:16.082Z</atom:updated>
            <content:encoded><![CDATA[<h4>Javascript Jedi</h4><h3>Just a title</h3><p>So what happens?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c92307c9364c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you a compulsive reloader?]]></title>
            <link>https://medium.com/javascriptjedi/are-you-a-compulsive-reloader-d3abaf03b121?source=rss-5c1f127e83d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3abaf03b121</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[reload]]></category>
            <category><![CDATA[titanium]]></category>
            <category><![CDATA[compile]]></category>
            <dc:creator><![CDATA[Guido Bellomo]]></dc:creator>
            <pubDate>Tue, 16 Jul 2013 14:32:32 GMT</pubDate>
            <atom:updated>2017-04-10T09:24:04.821Z</atom:updated>
            <content:encoded><![CDATA[<p>Several months ago I started working on <strong>Appcelerator Titanium</strong>, mainly in <strong>Javascript</strong>, the same language as the previous position but with a little difference: the IDE now takes 1–2 minutes to compile while on the web re-starting the project is just a matter of hitting the reload button.<br>I realized that I was compulsively hitting that button even for small changes.<br>When re-starting the project is a cost in terms of time — like in Titanium (consider the compilation and the time needed to navigate to the right feature) — it’s mandatory to write more code between reloads.<br><strong>It turned out that now I write better code.<br>How many lines of code do you write on average between a reload?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3abaf03b121" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascriptjedi/are-you-a-compulsive-reloader-d3abaf03b121">Are you a compulsive reloader?</a> was originally published in <a href="https://medium.com/javascriptjedi">JavascriptJedi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>