Comments on Introducing TalkBack, the New Internet of Things App to Control Things with the ThingSpeak Cloud Hans Scharler is an Internet of Things pioneer. He writes about IoT and ThingSpeak IoT platform features. 2017-04-26T19:23:16Z https://blogs.mathworks.com/iot/2014/01/21/introducing-talkback-the-new-internet-of-things-app-to-control-things-with-the-thingspeak-cloud/feed/atom/ WordPress By: Mikael Patel Mikael Patel https://blogs.mathworks.com/iot/?p=1152#comment-90132 2014-03-08T16:11:55Z 2014-03-08T16:11:55Z In reply to lee.

Hi Lee. Thanks for the swift reply.

My guess is that, for instance, space would not be a very good character to use as the command string is passed in a HTTP POST request.

It would be nice to come to some convention on formatting the command string with and without parameters and possible object reference.

Following the HTTP convention we could use plus(+) as a replacement for space or ampersand(&) and parameter names.

LED+0
LED&state=0

There is also a need for a syntax for commands where there might be several instances and an object reference (or index) is used.

LED3+0
LED+3+0
LED&id=3&state=0

Using an instance references helps reduce the command dispatch. The parameter notation with ampersand might not be a good idea as the whole string is the command to be added. It is actually the add command usecase that need most attention as the execute next command returns the string in the body of the reply.

Cheers!

]]>
By: lee lee https://blogs.mathworks.com/iot/?p=1152#comment-90125 2014-03-08T15:00:03Z 2014-03-08T15:00:03Z In reply to Mikael Patel.

Hi Mikael,

The only restrictions on the syntax of the TalkBack command is that they are UTF8 strings with max length of 255.

lee

]]>
By: Mikael Patel Mikael Patel https://blogs.mathworks.com/iot/?p=1152#comment-90109 2014-03-08T11:21:34Z 2014-03-08T11:21:34Z This is a great extension to the ThingSpeak channel handling. I have implemented support for “get next command” and “add command” in Cosa, an object-oriented platform for Arduino.

Now for a question: I am considering using the command string to identify “object” and also pass parameters. Are there any restrictions on the “syntax” of the command string?

More details on the Cosa issue list;
https://github.com/mikaelpatel/Cosa/issues/133
https://github.com/mikaelpatel/Cosa/issues/134

The demo channels are tagged Cosa.

Cheers!

]]>
By: Hans Hans https://blogs.mathworks.com/iot/?p=1152#comment-89227 2014-02-25T23:21:19Z 2014-02-25T23:21:19Z In reply to Andrew Doodson.

The why might be since the Yun can deploy serial over Wi-Fi and it is waiting for the serial port to be established. Not completely sure though. Glad it works!

]]>
By: Andrew Doodson Andrew Doodson https://blogs.mathworks.com/iot/?p=1152#comment-89211 2014-02-25T16:43:48Z 2014-02-25T16:43:48Z In reply to Hans.

Perfect! Worked as you say, this was the last hurdle of many for me, do you know why: while(!Serial); is used in some sketches but not others in terms of MAKING the code wait for the Serial Monitor? Thanks so much for your help 🙂

]]>
By: Hans Hans https://blogs.mathworks.com/iot/?p=1152#comment-88997 2014-02-21T17:48:12Z 2014-02-21T17:48:12Z In reply to Andrew Doodson.

Try removing line 62 of the sketch: while(!Serial);

(https://github.com/iobridge/ThingSpeak-Arduino-Examples/blob/master/Yun/TalkBack_to_Arduino.ino)

I think this while waits until the serial monitor opens before continuing through the Arduino sketch.

]]>
By: Andrew Doodson Andrew Doodson https://blogs.mathworks.com/iot/?p=1152#comment-88996 2014-02-21T17:43:48Z 2014-02-21T17:43:48Z Hi All,

Has anyone got this working on the Yun when just using Wifi and not tethered to a computer having the serial monitor open, it only seems to work for me when i’ve got the IDE open and the serial monitor open as well, any clues on this one?

]]>
By: Randolph Garrison Randolph Garrison https://blogs.mathworks.com/iot/?p=1152#comment-87178 2014-01-21T21:04:07Z 2014-01-21T21:04:07Z There is a great deal of potential here, especially for people getting older like me. Add cameras and microphones and possibly medical monitors that a family member could securely monitor and communicate.

Security is and always will be the weak point. A strong challenge and response on an independent connection is really needed before I could feel good about this type of setup.

]]>