- Security and Role Based Access Control (RBAC)
- Health checks
- Scheduled and on-demand diagnostics
- Alerts and notifications
- Firmware upgrades
- Remote wipe off
- And more
Once the device manager client is setup on the device, your work is done! Now you can control everything from one platform with just a few clicks. Never worry about checking device health anymore as Mission Control will monitor all the things you care about, and you will get notified if and when anything goes wrong. Controlling a group of devices is as simple as pressing the button. The device manager will fire a command to the group and execute the command on all its members.
Consider the following scenario: You’re running a retail store and have several motion sensors installed around the shop not only for security but to monitor customer traffic flow. By analyzing the data collected, you get a good idea about how many people are entering the store, which entrances they are using, and what items get the most attention. This information significantly helps to decide how to organize items and where to place the promotions.
This set-up is all well and good, but how can you make sure that all the IoT sensors are working properly? What do you do when there’s a software update needed on the sensors? What if you want to change the settings on the sensors? How do you add new IoT sensors to the existing infrastructure? Having a maintenance team manually complete these tasks on each device is one option, albeit a slow and costly one that is not scalable. Manpower can only do so much before technology needs to step in. With RoboMQ in charge of your IoT devices you won’t need to have your workers doing this type of tedious and repetitive work.
RoboMQ devices are built in Docker containers. This means your RoboMQ devices are shipped pre-installed with the Mission Control device manager clients and are ready to work right out of the box. As soon as they are turned on for the first time, devices will register themselves and become part of your trusted device network, after completing the Authentication, Authorization, and Auditing (AAA) process. Think of it like turning on your cell phone, and how it registers with the carrier network. Once the RoboMQ Device manager validates the identity and the ownership, the device will show up on the Mission Control Dashboard. Optionally, a device registration email/SMS notification or a custom business process can be executed when the devices activate on your IoT device network for the first time.
Fig 1: Active devices on your IoT network
Fig 2: Heartbeat and memory check running on set of devices.
Let’s say you want to keep the memory usage on the device lower than 60% to ensure that the device always has enough resources to handle events of motion detection. A simple memory check command can be configured to check devices every 5 seconds.
Due to our Microservices Architecture, data transformation and enrichment is made easy. Upon the collection of data from the devices and IoT sensors, a microservice can be deployed to perform a variety of well-defined tasks, such as limit memory capacity. If a device’s memory usage is higher than 60%, a ticket could be created, and an alert email/SMS could be sent to the maintenance team.
You can optionally define your own handlers to react to such events. Once the memory usage settles back to less than 60%, Mission Control will mark the ticket as “resolved” and send a confirmation email/SMS to the maintenance team. Similarly, a heartbeat check makes sure that the IoT devices are up and running and can take action upon the device re-joining the network or exiting the network.