Sponsored Content
Top Forums Programming Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App Post 303043645 by Neo on Sunday 2nd of February 2020 11:52:53 PM
Old 02-03-2020
I see folks on FB are starting to show interest in this app, so here are the steps to get started, for those who do not want login:

(1) Download and install the IoT-OnOff app. Basic use is free and that is all you need. Note, I am not the creator of this app and have no relationship with the creator at all.

Configure the app as follows.

(2) Go to settings:

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App-img_0465ajpg


(3) Then go to MQTT Broker and add the IP address of the MQTT server / service (and make sure all the other settings are the exact same as in the photo):

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App-img_450213596df6-1jpeg


(3) Then go to the Authentication screen and add the user name and password to the broker service:
  • The user name is: <contact me, or reply back asking for user name>
  • The password is: <contact me, or reply back asking for password>

There is no "hidden meaning" to the user name and password, I just used them at random when I first installed and tested the MQTT message broker Smilie

Make sure you turn on "authentication" at the bottom of that screen:

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App-img_52044ea2d923-1jpeg


(4) Next you configure your dashboard (just take a few minutes, see next post):
 

5 More Discussions You Might Find Interesting

1. Solaris

luminis app

The guys at SunGard want to charge a lot of $$$$ for installing Luminis and we are trying to see if this can be done without them. Their installation guide provided page #53 ( http://www.luminis.nocccd.edu/documents/Luminis%20IV/lp40000in.pdf ) doesn't really tell you much. All they say is that... (4 Replies)
Discussion started by: ceci1
4 Replies

2. Solaris

Problem with /app

Hi folks, i have a problem with my /app directory on solaris 10.It is mounted under rpool root and sometimes it increase dimension bringing root out of space.I want to mount /app under different position, maybe under secondary hardisk for which i have created a mount point with zfs pool...How... (10 Replies)
Discussion started by: mattpunk
10 Replies

3. OS X (Apple)

Can a ios app be developed on a windows or ipad?

hi, i want to start developing an ios app that can be used on iphone and ipad. can anyone guide me how to start? i saw that it can be developed only on a mac system.. but i dont have a mac system. i have an ipad 4 and a laptop with windows os? can i use one of these to start developing ios app??... (4 Replies)
Discussion started by: Little
4 Replies

4. Programming

Arduino Project: iPhone to HM-10 BLE to NB-IoT Shield to NB-IoT Network to Internet to Linux Server

This post describes a "work in progress" project I started today. Here is the High Level Overview: Currently, this project sits on my desk as an Arduino UNO (on the bottom), an NB-IoT Shield (sandwiched in the middle), a Sensor Shield (on top) with a HM-10 BLE Module (in the little... (13 Replies)
Discussion started by: Neo
13 Replies

5. Programming

Wuhan Coronavirus Status for China - Rapid Prototype Blynk App with ESP8266

Here is a rapid prototype app I just put together which might be of interest to some people. Basically, I have parsed the data from a Chinese web site which is tracking the Wuhan coronavirus, and cache that data every minute via a local cron file and make a simple API available to a Blink app. ... (6 Replies)
Discussion started by: Neo
6 Replies
App::Info::Handler::Carp(3pm)				User Contributed Perl Documentation			     App::Info::Handler::Carp(3pm)

NAME
App::Info::Handler::Carp - Use Carp to handle App::Info events SYNOPSIS
use App::Info::Category::FooApp; use App::Info::Handler::Carp; my $carp = App::Info::Handler::Carp->new('carp'); my $app = App::Info::Category::FooApp->new( on_info => $carp ); # Or... my $app = App::Info::Category::FooApp->new( on_error => 'croak' ); DESCRIPTION
App::Info::Handler::Carp objects handle App::Info events by passing their messages to Carp functions. This means that if you want errors to croak or info messages to carp, you can easily do that. You'll find, however, that App::Info::Handler::Carp is most effective for info and error events; unknown and prompt events are better handled by event handlers that know how to prompt users for data. See App::Info::Handler::Prompt for an example of that functionality. Upon loading, App::Info::Handler::Carp registers itself with App::Info::Handler, setting up a number of strings that can be passed to an App::Info concrete subclass constructor. These strings are shortcuts that tell App::Info how to create the proper App::Info::Handler::Carp object for handling events. The registered strings are: carp Passes the event message to "Carp::carp()". warn An alias for "carp". croak Passes the event message to "Carp::croak()". die An alias for "croak". cluck Passes the event message to "Carp::cluck()". confess Passes the event message to "Carp::confess()". INTERFACE
Constructor new my $carp_handler = App::Info::Handler::Carp->new; $carp_handler = App::Info::Handler::Carp->new( level => 'carp' ); my $croak_handler = App::Info::Handler::Carp->new( level => 'croak' ); Constructs a new App::Info::Handler::Carp object and returns it. It can take a single parameterized argument, "level", which can be any one of the following values: carp Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::carp()". warn An alias for "carp". croak Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::croak()". die An alias for "croak". cluck Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::cluck()". confess Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::confess()". If the "level" parameter is not passed, "new()" will default to creating an App::Info::Handler::Carp object that passes App::Info event messages to "Carp::carp()". BUGS
Please send bug reports to <bug-app-info@rt.cpan.org> or file them at <http://rt.cpan.org/NoAuth/Bugs.html?Dist=App-Info>. AUTHOR
David Wheeler <david@justatheory.com> SEE ALSO
App::Info documents the event handling interface. Carp of documents the functions used by this class. App::Info::Handler::Print handles events by printing their messages to a file handle. App::Info::Handler::Prompt offers event handling more appropriate for unknown and confirm events. App::Info::Handler describes how to implement custom App::Info event handlers. COPYRIGHT AND LICENSE
Copyright (c) 2002-2008, David Wheeler. Some Rights Reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2011-03-15 App::Info::Handler::Carp(3pm)
All times are GMT -4. The time now is 12:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy