Paul Jobson created a repository named Experiments and Notes for Onion Omega2+. You will find several notes good to know. Try it.
I added a SparkFun MicroView display to the Omega2+ to show temperature and humidity from Weather Underground. The display text here is in German but can changed.
The MicroView USB programmer serves as programmer for the Arduino inside MicroView and as serial interface between Omega2+ USB and MicroView TX/RX.
The Arduino program SerialDisplay.ino waits for a telegram containing a start character, the temperature as floating point number, and the humidity as integer.
To control the serial interface /dev/ttyUSB0 at Omega2+ we have to install stty by opkg install coreutils-stty. The Shell script oled.sh sends the data from Omega2+ to MicroView.
During serial communication MicroView is controlled by DTR (The bootloader will be activated). Therefore, DTR must be disabled in this case. I did not find a solution by stty. A simple way is to connect TX, RX, GND and VCC between MicroView and MicroView programmer only. This way the RST line is not affected during serial communication.
All script including the Arduino sketch are saved at Github as usual.
If you test a new IoT node (or a Linux device in general) it is important to get some information whether the node runs stable or have problems.
The command uptime returns the time elapsed since last boot and some other information.
root@Omega-B2BB:/home# uptime 23:34:53 up 4 days, 13:56, load average: 0.00, 0.00, 0.00
The uptime command gives a one line display of the following information.
- The current time (23:34:53)
- How long the system has been running (up 4 days)
- The system load averages for the past 1, 5, and 15 minutes (0.00, 0.00, 0.00)
Here the Omega2+ has not a lot to do.
It’s not allways possible to contact that node directly for monitoring. To send the uptime result as a message is a good way to get this info.
My preferred way is to use Pushover messages but I had problem with sending the data by cURL. I have to wait for an answer from Onion’s community because this worked with an older firmware version.
But, to get this info yet I use Twitter direct messages. IFTTT acts as a gateway to twitter.
I use the Maker event to trigger sending a direct message to myself.
The configuration is quite simple. The event is named Uptime, what else?
After that we can specify the message content. I will send only one value with the complete uptime message inside.
To send the message from Omega2+ (or any other Linux device) I use a POST web request sent by cURL. The complete Shell script monitoring_update.sh looks as follows:
#!/bin/sh uptime > UPT MSG=`cat UPT` echo -n Uptime: echo "$MSG" # Send data as Twitter direct message via IFTTT curl --data "value1=$MSG" \ https://maker.ifttt.com/trigger/Uptime/with/key/dy0QeH-N3Ezfa4Ilst-r4F
You can find the script at Github.
I placed the script in a crontab for calling it each hour. There is a second script which calls weather data each 15 minutes.
root@Omega-B2BB:/home# crontab -l
0 */1 * * * /home/monitoring_uptime.sh
*/15 * * * * /home/weather.sh
You can see the direct messages sent from my Omega2+ on my mobile phone.
After installing Mosquitto on Omega2+ in the blog post Using MQTT on Onion Omega2+ the subscription of messages was shown. Here I will send data to the MQTT broker to subscribe and access them from anywhere in the world.
For data generation I use the script wunderweather.phy again. The script mqtt.sh reads the requested data (temperature & humidity) and publishes these to my MQTT broker. Look for the files at Github.
#!/bin/sh #MQTT BROKER="m20.cloudmqtt.com" BRUSER="rawyjpid" BRPASSW="ah52k3gjd8JS" BRPORT=12394 TEMPTOP="OMEGA2/WU/temperature" HUMITOP="OMEGA2/WU/humidity" echo "Send data to MQTT Broker" DATE="$(date +"%d-%m-%Y")" read TEMP < /home/TEMP echo "Temperature = $TEMP *C" read HUMI < /home/HUMI echo "Rel. Humidity = $HUMI %" mosquitto_pub -h $BROKER -u $BRUSER -P $BRPASSW -p $BRPORT -t $TEMPTOP -m $TEMP mosquitto_pub -h $BROKER -u $BRUSER -P $BRPASSW -p $BRPORT -t $HUMITOP -m $HUMI
The screenshot of my MQTT client MyMQTT shows messages from two publishers. WU labels the data received from Weather Underground requestet here and ASH2200 is a sensor placed outside of my house. The difference between the measured values is due to different measuring locations.
If you have no own weather station but are interested in local weather data then weather data from Weather Underground (wunderground) can help to close this gap.
I built three small scripts to ask wunderground for data, send the to the thingspeak server for visualization and cover both scripts. You will find them on Github for download.
wunderweather.py asks Wunderground for locale weather data. Local means here Altendorf in Switzerland.
#!/usr/bin/python # Reading weather data from wunderground network import urllib2 import json f = urllib2.urlopen('http://api.wunderground.com/api/a50aba1a6119706f/geolookup/conditions/q/Switzerland/Altendorf.json') json_string = f.read() parsed_json = json.loads(json_string) location = parsed_json['location']['city'] temp_c = parsed_json['current_observation']['temp_c'] rel_hum = parsed_json['current_observation']['relative_humidity'] weather = parsed_json['current_observation']['weather'] station = parsed_json['current_observation']['station_id'] updated = parsed_json['current_observation']['observation_time_rfc822'] print("Current temperature in %s is: %s *C" % (location, temp_c)) print("Current relative humidity is: %s %%" % (rel_hum)) print("Weather is %s " % (weather)) print("Weather station is %s" % (station)) print("Last updated: %s" % (updated)) f.close() f = open("TEMP","w") f.write(str(temp_c)) f.close() f = open("HUMI","w") f.write(str(rel_hum)) f.close()
thingspeak.sh sends temperature und humidity to the Thingspeak server:
#!/bin/sh echo "Send data to Thingspeak Server" #Thingspeak api_key='CRPX6X538QZ1DZHY' DATE=date read TEMP < /home/TEMP echo "Temperature = $TEMP *C" read HUMI < /home/HUMI echo "Rel. Humidity = $HUMI %" curl --data \ "api_key=$api_key&field1=$TEMP&field2=$HUMI&field3=$DATE" \ https://api.thingspeak.com/update > log 2>&1
As you can see from both scripts you need access data for the APIs. Therefore you have to register on both services.
The last script weather.sh covers both calls. That’s all:
#!/bin/sh /home/wunderweather.py /home/thingspeak.sh echo "Done."
Push messages can help to get status info of IoT nodes which can not always connected directly. There are different services that are suitable for sending push messages. A very simple way to integrate the sending of push messages into an application program is pushover (https://pushover.net/). You have to create an account there and register your application. After that you will get credentials for connecting to the Pushover server.
For Android devices receiving the Pushover messages you will find a Pushover Client in Google Play Store. After installation and login with the Pushover credentials you can register this client on server side too
After starting with Onion Omega2+ I want to get some information of the uptime of the system to check stability. For this purpose I installed cURL and Pushover and call a Shell script as cronjob.
Here are the steps to follow after registration at Pushover:
opkg update opkg install curl
The following script sends a message to the Pushover server and the server prepares the messages to the registered devices.
$ curl –s \ --form-string "token=<APP_TOKEN> \ --form-string "user=<USER_TOKEN> \ --form-string "message=<MESSAGE> \ https://api.pushover.net/1/messages.json
This command I embedded into a further Shell script OmegaPushover.sh which can send messages in the following format:
$ ./OmegaPushover.sh "This is a message"
To include into the crontab I wrote a further script monitoring_uptime.sh.
#!/bin/sh uptime > UPT MSG=`cat UPT` echo -n Uptime: echo "$MSG" ./OmegaPushover.sh "$MSG"
Both scripts you will find in my Onion Omega repository.
Here is a screenshot of a received Pushover message from my Android phone.
MQTT is an important protocol for data exchange in IoT networks.The communication between the producer of data (publisher) and the consumer of that data (subscriber) goes over an MQTT Broker always.
There are some free MQTT Broker around. I use CloudMQTT of the Swedish company 84codes AB for my applications. CloudMQTT are Mosquitto server in the cloud.
Whats’s to do on Onion Omega2+ side after creating an MQTT account?
We have to install Mosquitto.
opkg update opkg install mosquitto mosquitto-client libmosquitto
I have here several temperature sensors in a controller network that send temperature and humidity data to the CloudMQTT broker.
To subscribe these data the follwoing subscribe command is needed on Onion Omega2+:
mosquitto_sub -h m20.cloudmqtt.com -u "ra.....id" -P "ah.....8JS" -p 12394 -t "DHT11/+/#" -v
You must change the user (-u), password (-P), and port (-p) to the login data of your broker account.
As you can see from the following screenshot it’s winter in Switzerland with around 2°C and 80 % rel. Humidity.