Mobile alerting with tracking & escalation for Google IoT Core
Google IoT Core provides a scalable, rapid solution development platform, made up of tightly integrated components that can be customized to help you solve your business challenges. Whether you are collecting data from a Raspberry Pi or industrial machines, the platformcan help you manage your IoT devices in real time. Pairing this powerful IoT platform with SIGNL4 can enhance your daily operations with an extension to your mobile team in the field or on the shop floor.
How it Works
SIGNL4 integrates with Google IoT Core using a simple MQTT flow on the Google Cloud platform.
Service engineers alerted via mobile push, text and voice
Uses Email configuration to connect to your SIGNL4 team
Staff can acknowledge tickets and take ownership
Alerts are escalated in case of no response
Two-way integration to interact or set the device state
On-call scheduling to alert the right people at the right time
IoT Service Alerting
IoT Device Management
Manufacturing, Utility, Oil and Gas, Agriculture, etc.
Tickets and Incidents are sent to SIGNL4
Event categorization, routing and automated delivery
Persistent Notifications by push, text and voice call with Tracking, Escalation and Confirmation to Staff on Duty
HOW TO INTEGRATE
Gathering events from IoT devices and sending team alerts in case of critical incidents is a broad field. Systems can involve simple prototypes using a Raspberry Pi and can expand into industrial IoT scenarios, machine data or distributed systems in the field.
The following example demonstrates the flow of an event captured on a device through to notification of an engineer using SIGNL4 and Google IoT Core together.
SIGNL4 is a mobile alert notification app for powerful alerting, alert management and mobile assignment of work items. Get the app at https://www.signl4.com.
Cloud IoT Core is a fully managed service that allows you to easily and securely manage and connect your IoT devices. The integration with SIGNL4 is straightforward. In the following we will show an example on how to send alert notifications using SIGNL4 in case of MQTT events coming from devices in the field.
Therefore, we will focus on the Cloud Function part that is used to send the SIGNL4 alert and only briefly mention the other steps.
Prepare the Google IoT Cloud and Pub/Sub
In Google Cloud IoT Core first create a registry. Then a gateway and a device.
In Google IoT Cloud under Pub/Sub create a Topic and a Subscription.
Prepare your Raspberry Pi
A great device for IoT prototyping is the Raspberry Pi. We will use this one as our device and connect it to Google IoT core. As a protocol for sending event data we use MQTT. This is quite an undertaking, however, luckily there is a great sample available already at GitHub:
This sample included a Python file that can be used as is or you can modify it to match your needs. By default it sends a bunch MQTT messages. You might want to modify the code to send an MQTT messages in case a sensor detects something or a button is clicked.
In order for the Python script to work you need RSA keys you can create it with the following command directly on your Raspberry Pi:
Now you can test it by sending an MQTT message from your Raspberry Pi as described above. You should then receive an alert on your SIGNL4 app.
ALERT OPTIMIZATION SIGNL4 can further increase the visibility of alerts through its Signals and Services section. Augmenting the color and icon of alerts will provide more relevant information at a glance without having to open the alert.
Change alert color and override title + text
Override text, colors and titles are triggered by keywords set within the mobile app.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.