Routing and tips for AIO

Searching for a IoT solutions is simple. But most of them are not really user friendly. IO by ADA fruit was my second choice and useable.

This is there's view:

As a maker, engineer, or designer there are a lot of choices to make. And those choices have a big impact on the cost, size, runtime, and usability of your Thing. Thinking and knowing about your options early on, perhaps even before you open up your IDE or CAD tool, will help you save money, time, and make your product the best it can be.

So here are some notes about it, and I will skip the registration.

Making a connection to the back-end

MQTT is a simple concept and the library uses this routine to link with the backend:

The routine is placed at the end of the program and only needs a wifi connection to run properly. If you get errors, then check you access codes. There's a 5 second delay in the loop.

Prepare a channel for transport or ' Subscribe '

The second MQTT step is 'preparing a downwards channel' from a server:

We are asking for data from the onoffbutton

Setup

You need to place and extra reference in the setup:

Main loop

Will often start with the connect instruction and then hold the usual data exchange from sensors. After that we're ready to start the MQTT exchange:

This command checks the feeds for new data.

The fifth step is reading data from feeds.

After that a routine is used to check if new data came in:

Still in the main loop.

Sending data

Sending or posting data to the server is one step and this command is used:

The library will look at the feeds and send contents to the server with a publish command

/ProgramFiles(x86)/Arduino/Libraries (default)

A P I = Application Programming Interface

AIO uses feeds but other platforms will use a ' topic '

Eclips fase 1 was build on 26 / 12 / 2016
1 januari 2018