1. Home
  2. TC2.17 - Event Driven IOT Applications, from brokers: Orion, SigFox, etc.

TC2.17 - Event Driven IOT Applications, from brokers: Orion, SigFox, etc.

×

Warning message

  • You can't delete this newsletter because it has not been sent to all its subscribers.
  • You can't delete this newsletter because it has not been sent to all its subscribers.

Test Case Title

TC2.17 - Event Driven IOT Applications, from brokers: Orion, SigFox, etc.

Goal

I can:

Realized event drive solutions, exploiting event drive brokers

make IoT Applications that change status and create notification based on event launched by a sigfox device

Prerequisites

A simple skill for using IOT application.

A Sigfox sensor already registered on the Sigfox site.

Using a PC or Mobile with a web browser.

The following functionalities are available only for specific Snap4city users with specific privileges.

Expected successful result

Check the status of a sigfox sensor and make actions

Steps

 

 

For a more complete overview please read: 

For a minimal example:

  1. When a user uses a sigfox device to register their sensors and send data to the central server, they then want to reuse that data and in the event of a drastic change it is assumed that they want to be notified of that change. This behaviour can also be adopted in the case of sensors in the city and on the basis of which you want to be warned of possible changes.
  2. In the test case TC2.15  IOT Application Creation, using personal devices and exploiting city devices is described how to install a microservices to read a sigfox device:

  1. And send data, for example on a dashboard

 

  1. It is possible to see the data of the sigfox sensor in the dashboard “ClaudioApplication”:

  1. Moreover, for the city user it is possible to reach the same goal (described in the same test case):

  1. Created node

  1. This node can be used to read the data collected by the city sensor.
  2. With the microservices available on nodered, for example the microservice "switch", it is possible to give the value of the sensor returned from previous streams send data via email, telegram or show alerts on dashboards as described in the test case:
    1. TC4.2 Managing Notifications on IOT Application SMS, Telegram, email, Facebook, email, Dashboard events, in Push on other IOT Applications
  • Share
TC2.17 - Event Driven IOT Applications, from brokers: Orion, SigFox, etc. | Snap4City

Error

×

Error message

  • Notice: Trying to get property of non-object in user_is_logged_in() (line 1576 of /var/www/html/drupal/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_is_logged_in() (line 1576 of /var/www/html/drupal/modules/user/user.module).
  • Notice: Trying to get property of non-object in og_field_access() (line 578 of /var/www/html/drupal/sites/default/modules/og/og.module).
  • Notice: Trying to get property of non-object in user_access() (line 806 of /var/www/html/drupal/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_access() (line 818 of /var/www/html/drupal/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_access() (line 819 of /var/www/html/drupal/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_access() (line 825 of /var/www/html/drupal/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_access() (line 828 of /var/www/html/drupal/modules/user/user.module).
  • Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/drupal/includes/common.inc:2791) in drupal_send_headers() (line 1499 of /var/www/html/drupal/includes/bootstrap.inc).
  • Error: __clone method called on non-object in og_user_access_entity() (line 2249 of /var/www/html/drupal/sites/default/modules/og/og.module).
The website encountered an unexpected error. Please try again later.