Leaving 2014...

As a token of my appreciation, you'll be entered into a drawing for a jReCo (Jubito Remote Control) once you...

• Like Jubito on social networks (facebook, twitter, google+, facebook jaNET Framework)
• Post a comment
• Spread it through your website/blog and publish the link to any of the above

What you'll get is an Arduino Nano, RF Receiver + Transmitter modules, soldered, with full support and software implementation as seen in this tutorial.

I select this project because it was my first flirt with Arduino and because everybody, or almost everybody start with controlling lights, which is a good starting point for home automation.

So, from back then, with a little bit of research, I ended up from this...

to that...

I hope to find it as amusing as I, and give you a boost of encouragement to start developing your own "things".

This "contest" will close at January 30th and the winner will be announced in this post and at the social networks.

I wish you a creative 2015, good luck!

4th Annual Internet of Things Awards

UPDATE: Jubito is been selected! Vote for it!

Postscapes 4th Annual Internet of Things Awards - 2014/15. A showcase of the year’s best #IoT products and companies.

Everyone is invited to vote for their favorite IoT Award winners.

Nominate Jubito :)

The power of reflection

In this post we've explained a scenario that consisted by a number (3) of alternative responses. Someone might consider, what if I want to use the response or some other action, like evaluation, to another activity? Should I make duplicates or a number of responses for each one of them? The answer is no. This can be solved by creating the response or some action as a launcher. A launcher creates two instances. One that holds the action and the other the reflection. The reflection is indicated by asterisk symbol.

For example, if I create a new launcher 'demo_launcher' that holds 'Hello %user%' as action, then the system will create:

1. *demo_launcher: Hello %user%
2. demo_launcher: *demo_launcher

When 'demo_launcher' is called the response will look like this...

Hello john (where john the system login. Check Built-in functions and API for more info)

Now, from a different Instruction Set that returns for example the user status, *demo_launcher can be invoked like this..

get_user_stat: *demo_launcher. Your status is set to %whereami%.

which will return...
Hello john, your status is set to present.

I think it's a very straightforward methodology and will become a standard in the future versions.

Screenshots are from the development version which is not yet available. However the functionality remains.

Of course these actions can be applied to any system object, such the evaluator.

Chain reaction behind the scenes.

Launchers are extremely versatile. You can combine anything that supported from the framework in a single action.
So, the verdict is that if you want a complex Instruction Set it is wise first to create launcher components and then mixed in a single one.

You can review a complex AppConfig.xml configuration file.

Jubito at MobiHealth 2014

Jubito was proudly presented at the 4th International Conference on Wireless Mobile Communication and Healthcare by Kostas Giokas, Senior Researcher, Leader of the Applied Informatics in mHealth (AiM) research team, of the Biomedical Engineering Laboratory, Institute of Communications and Computer Systems, National Technical University of Athens.

JUBITO: An interoperable platform for wellness, was presented at the 4th International Conference on Wireless Mobile Communication and Healthcare, MobiHealth, on the 4th of Novermber, held in Athens, Greece.

http://www.biomed.ntua.gr
http://www.ntua.gr
http://www.iccs.gr