MQTT Broker integration using REST API

MQTT Broker integration using REST API

In today’s world, the enterprise application system is incomplete without providing a way to integrate with other systems. Ergo,MQTT Broker integration with your application is very crucial for any process / production management application in Industrial and Customer implementation. To make such implementation feasible, MQTTRoute supports many integrations which include Relational DB, Data storage, Queue integration, Application integration, Social integration & finally Application/Mobile integration using REST APIs. Bevywise MQTT broker was built with options to store data into any back end data storage via the custom data store. You can visualize the data by storing the data into the storage. In addition, You can use the ready to use plugin to store data to Elastic and MongoDB. In addition to this, our recent update on MQTT Broker comes up with an extension to store the data in any of the big data engine for powerful analysis & Data hooks for any custom integration.

We are still working hard to make the MQTT Broker work more seamlessly with any of your application. Hence, we support the availability of APIs in our MQTT Broker with some additional interactions through which your IoT Application can manage your edge devices via the MQTT Broker.

Need of REST API Integration

In the digital world, the huge number of cloud / mobile applications & IoT devices keep on rising and hence the businesses are trying to find a beneficial use for these emerging sources. Any how, the biggest challenge lies in integrating these applications with other business operation systems to bring together into a unified whole which can be easily shared within one’s businesses. This is where REST APIs comes in, which permits the interaction between applications & servers to boost the product functional capability & getting data where & when they need it, creating an overall well-connected eco-system.

For example, in order to manage & control business / enterprise assets some organizations make a choice of cloud-based systems. Earlier, Business measures which have been stored within an existing organization are now locked behind such a third-party applications and web interfaces. Business’s need this information to make data-driven decisions, and APIs make that possible. APIs will break down the data access by defining the interactive commands for the application systems. Furthermore, APIs can also be used in the third-party integration tools to call for the data. They can be integrated with other application systems to process business inquiries.

MQTT Broker integration with REST API:

While building an IoT application, there is a need to control and manage the edge devices from the manager application. REST API will help you control your edge devices via the MQTT Broker. It allows you to query MQTT clients, sessions, send messages, add new authentication keys. You can also query and monitor the connected devices.

We have carefully selected the most useful communication that is needed between any application and its broker to provide you the best management experience/functionality. The following are the list of interactions available now

  1. Send a message to any specific device.
  2. Send a message to all devices based on a subscription.
  3. Add a MQTT Device Authentication username and password dynamically from your application.
  4. Remove a MQTT Device Authentication String from the MQTT Broker
  5. Get the list of active devices connected right now to the MQTT Broker.
  6. Get the count of clients connected

For more details on the API, refer to the  MQTT Broker API page 

One of our customers, FAB Controls is an IoT solution provider in the United Kingdom who provides IoT solutions to the lighting and energy industries. EmMonIT is their elite solution for emergency lighting control. Their emergency lighting control device is efficacious in monitoring lighting steadily to set the seal on operating successfully. MQTTRoute plays an indispensable role in their emergency monitoring solution. MQTTRoute acts a central broker and therefore it collects data from lighting control devices and pushes it to Google pubsub to create simple and real-time visualization of data. Besides this, as MQTTRoute supports REST APIs, the lightning control devices can be controlled & monitored from the manager application. This provides a virtual foolproof emergency lighting by enabling them to constantly check the status of emergency lighting anywhere at anytime.

Unsolicited Messages:

MQTT Broker now supports sending of Unsolicited messages to the Edge Device. Yes, you read it right. You can now send messages to any specific device for a topic for which the client is not already subscribed to. This is an enhancement to support device development platforms like Telit.  Send the http call to /clientsend with the target device, topic provided by the device for receiving unsolicited messages, message, QoS and Retain as required.

We have also added an advanced custom implementation inside the /lib folder of the product to send the data received into your Python class file to process it in a better way.

Try the fastest MQTT Broker now.

MQTT Implementation on Celikler Holding’s Power Plant Monitoring

MQTT Implementation on Celikler Holding’s Power Plant Monitoring

Celikler Holding is one of the largest industrial companies from Turkey that operates on the large sectors such as Energy, Construction, Commitment and Tourism. Celikler Holding, has gained more attention as a player in the country’s energy sector. They are notable for bringing new innovations to the sector by utilizing modern technology in their projects and they pursue to serve the evolution and rise of the country’s wealth by benefiting the production.They consistently focus ahead by acting in accordance with the regulations of the quality management system it has set, by improving its effectiveness, being reliable and reverent to the environment and specializing in the sectors in which it operates. In 2018, Celikler Holding began using MQTTRoute to monitor power generation from multiple power plants. The use of MQTT here has been so successful & this IoT use case has benefited Celikler Holding by providing a secured communication between power plants.

Security issues in data transfer

The Industry 4.0, particularly, IoT in manufacturing provides an option for the transition of the manufacturing Industry. However a secure way of collecting and utilizing the data is essential for the industries to attain efficiency. In the industrial world, data theft has become more serious & industries have become more vulnerable to data breaches. This is one of the key issues, the industrial sector should overcome & demand an exceptional guarantee of the integrity of the request issued and data received by various equipments.

For years, Celikler Holding has been monitoring power generation by connecting every user’s mobile phones to the MODBUS interface on the individual monitoring console. This mandated the professional to be near every Power plant control dashboard to view the status. Besides that, the security issues prevented them from connecting the MODBUS protocol directly to the internet.

The application layer messaging protocol, MODBUS provides client/server communication between devices connected to various network types. MODBUS is the most extensively deployed network protocol in the industrial manufacturing production line owing to the fact that it is more simple & highly efficient. But, The direct implementation of MODBUS may create numerous vulnerabilities that could permit a hacker/intruder to execute unwanted activity or send autocratic demands.

Absence of Probity: MODBUS don’t have any integrity checks built into it & hence it entrusts on other protocols to protect integrity.

Absence of Secrecy: MODBUS has no built-in security features & no built in command to identify or verify the connected devices.

Absence of Authentication: There is no authentication at any level of the MODBUS protocol.

Hence they need a solution to securely transfer the power generated data from multiple power plants. To implement a secured way of collecting & transferring data they need an alternative messaging solution which does not allow attackers to penetrate in.

Why MQTT?

MQTT was intended for light-weight communications between connected devices & servers. It provides some security protection & shield, even though the security option was not built inside the protocol. The protocol permits for client authentication which authorizes a two-side hand shake. This technique lets for encryption of data in the message if SSL/TLS is available on the connected device. The mutual authentication and encryption could prevent hijacking and man-in-the middle attacks.

In that case, MQTTRoute comes with a device level auth and TLS/SSL to make secure connection between the modbus gateway and MQTT broker. And also, the Modbus MQTT Gateway that comes as part of the Bevywise IOT Solution collects all data from power plant and send it to the Central MQTT Broker. In addition, Celikler Holding gets utilized with Bevywise’s IoT Application framework, so that the Mobile app can be connected to the MQTTRoute. This avoids the need of professionals to be near every Power plant control dashboard to view the status. This enterprise IoT use case has proved, how MQTT implementation can benefit manufacturing industries in case of security.

In conclusion, we were able to use our MQTT Client modules and quickly build and complete Modbus MQTT Gateway to provide them a complete solution. This is one of the internet of things success stories of MQTT implementation.

“Bevywise MQTT Broker is very reliable, powerful and a very affordable solution. The support understood our technical issues and solved them efficiently. We are happy for our decision to choose Bevywise for our Industry4.0 Implementation.”
-Ihsan Gulec, Measurement & Control Engineer,
Celikler Holding. Turkey.

“We are happy that we were able to provide a complete solution for Celikler using our Gateway & the MQTTRoute for their need. Appreciate Celikler teams patience and time in explaining us the requirement that helped us solve it.”
-Jebason, Customer Success Manager, Bevywise Networks

Download the complete IoT Success Stories of Celikler holding.

Try downloading the MQTT Broker for free here.

download case study

We will be happy to hear your problems / requirements to provide a complete solution. Schedule a call now.

Use SCADA Integration to Connect New Age MQTT Devices

Use SCADA Integration to Connect New Age MQTT Devices

The strength of technology in building, monitoring & controlling the machinery has become an imperishable part of the Industrial world and Industries have long adapted it. Compiling data & receiving commands in and out of the shop floor, around megalopolis and in energy & power plants have been in place for ages. However, Manufacturing industries are facing certain limitations with the traditional approach of controlling machinery because of the lack of ability to be inventive & adaptable. This is one of our IoT success stories of MQTTRoute implementation. One of our customers from India has been building steam engineering and control instrumentation solutions that work for the process industry for over half a century. Their target is to provide solutions in Energy, Efficiency and Process Automation, using the finest technology the world has to offer. They use MQTTRoute for modbus integration into SCADA systems to provide complete automation solutions for process Industry.

The challenge for granular asset visibility

Far & wide, almost in every industry and in modern society, the supervisory control and data acquisition (SCADA) system is used and on which the entire industrial operation is reliant. SCADA is an automation & operationalize control system which offers an intuition to the operators regarding the Industry operations. Almost in all the industrial sectors, SCADA has taken its place to pick up ingress to the complete plant from an authority room. It is a system of monitoring, gathering and processing real-time data locally or at remote locations that allows industries to control industrial processes. However, the way of facing ever-thriving compulsion from more firm regulations, cost volatility, hostile environmental conditions has forced manufacturing Industry to change. Process control & monitoring isn’t new in the industry, but the traditional SCADA systems can’t provide the granular asset visibility needed. And also, SCADA is still currently limited to the shop floor. Data taken from the industrial equipments are being viewed only inside the plant. Hence, progressive & enterprising companies have been increasingly embracing IoT technology to better manage their assets anytime, anywhere and prevent costly spills.

Turning machinery into superior smart systems

Global remote controlling, monitoring, simplicity in deployment, lower cost, rise in data precision are the necessities IoT affords for asset-heavy industries. Though IoT is quite the latest technology compared to SCADA & Programmable logic controllers PLC, its potentiality is certainly flexible to present-day industry demands. Nonetheless, when SCADA launch into, it authorized manufacturers network to operate cooperatively in real-time, in the same vein IoT is doing today. Therefore, it’s extremely evident that the power of SCADA systems and its technological abilities are pertinent in 4th Industrial revolution even today. However, the SCADA systems fall short in creating a truly connected ecosystem. Hence, fundamentally IoT should be considered as a technology that is deployed on top of SCADA architecture. This coordinated approach will make extensibility, data analytics, standardisation & interoperability a certainty. Intelligence / Informations initiated by SCADA systems make a move as one of the data sources of IoT. SCADA’s aim is on monitoring and controlling. Despite this, IoT is more concentrated on examining equipment data to boost up productivity and influence the business line. IoT is basically a pinnacle of breakthrough in the connectivity of hardware and data networks that SCADA provides. In short, IoT begins where SCADA ends.

Role of SCADA MQTT Broker integration in process Industry

As discussed above, our customer with its diverse industry experience and process knowledge can help to improve quality, consistency and accuracy of any process industry. It furnishes out-and-out turnkey solutions from design, detail engineering, drawing, documentation, supply, installation and commissioning of the effortless to most complex industrial processes. Since there were certain limitations in SCADA platform, they need an effective IoT framework which supports modbus protocol that can communicate between their devices & Industry’s SCADA system. That is as said earlier, IoT should be implemented at the top of SCADA. Hence, MQTTRoute, a complete IoT application framework integrated to Modbus RTU (communicates in Modbus protocol) with which the data generated by their devices can be acessed simultaneously by SCADA system. MQTT Broker will let them push data from sensors to Modbus slave (RTU), from there SCADA will read & monitor the received data. This will help them provide a complete automation & control solutions to their industrial customers rather than providing a simple monitoring solution.

SCADA is all about the human machine interface (hmi) which permits humans to have remote access to a process. Whereas MQTT Broker is generally used as a machine-to-machine communication tool that ensures data is shared with both people and machine, rather than just people. In short, SCADA MQTT integration will makes sure that everyone and everything is kept in the loop at all times. As a result, The MQTTRoute implementation addresses their need and provides them a complete solution. This is one of our IoT Success stories.

In conclusion, replacing the SCADA system with other system will surely cost a huge amount to the Industries. But the Modbus SCADA integration can provide a complete automation helping manufactures to carry out any necessary analysis and control to their production process.

For more details and queries on MQTTRoute, you can visit our website.

Download the MQTTRoute, the complete MQTT Application Framework now.

download now

We will be happy to hear your requirements to provide a complete solution. Let us talk now.

Free MQTT Broker for IoT / IIoT Implementation

Free MQTT Broker for IoT / IIoT Implementation

We are excited to announce the availability of FREE version of MQTT Broker. A few days back, we have released a new version of our MQTT Broker, MQTTRoute 3.0. With the new update, we are introducing the accessibility of FREE MQTT Broker that supports all features with complete MQTT Support. The fully functional MQTT Broker will be available for free download without any feature restrictions for 30 days.

Fully Functional Free MQTT Broker

M2M communication is indispensable for all IoT / IIoT deployments. A lightweight middleware can readily manage & control your devices & will help you work on your core business challenge. This mandates the need for selection of perfect MQTT Broker for your IoT projects / implementation. Keeping this in mind we developed a powerful MQTT Broker with the full-fledged features to better manage your devices & to have a powerful IoT solution. Our new MQTT Broker version, MQTTRoute 3.0 comes up with some additional custom hooks & multiple dashboard support to ease the development challenges face by budding developers. We at Bevywise always strive hard to provide a best solution for our customers with complete functionalities & enhanced support. In that case we are introducing FREE version of MQTT Broker that supports all features with complete MQTT Support. We don’t restrict users with respect to features for first 30 days. The full-fledged functionalities include Multiple dashboard creation, Built-in widgets, UI Customization, Custom storage configuration, AI/ML Integration & more. This is all about supporting a single user who needs to connect the minimum number of devices for his / her IoT projects / implementation.

Your FREE version Last forever

After 30 days, user can continue using MQTT Broker with the basic features by connecting upto 10 clients. Features are listed below:

Complete MQTT Support

We built the MQTT Broker very much inline with the protocol specification of MQTT. Bevywise MQTT Broker supports 3.1 and 3.11 protocol specification. Beyond this, we have done a recent update that Bevywise MQTT Broker now supports MQTT 5 beta version. MQTT 5 specification is initially available only for ubuntu users. We will provide the availability for other operating systems soon.

Integration with Databases

IoT data needs to be integrated with databases or any big data engine. Hence we allow users to store data in MySQL, SQLite databases as they need for further analysis and decision-making. You can process the data by them before they send it to the storage.

Secured Communication

MQTTRoute has the most powerful & flexible security options. MQTTRoute provides an option to enable encrypted data transfer for enhanced data security. You can enable MQTT Authentication to securely connect your edge devices by using an auth key & token and make sure no one can intrude into the system.

Effectual Dashboard

MQTTRoute provides an option to view the list of connected devices and complete details about the device activities. Users can dig deeper into each device by messages, topics & send a command to any of the connected devices. Users are provided with an option to change the broker to their language via localization support.

Message transformation with rules

MQTTRoute provides rules engine to create event / timer based rules for the sensor data. With this users can easily create an alert message and send a message to a specific subscriber or any application and also the rules can be scheduled on a specific date.

The above mentioned functionalities will automatically gets activated once the 30 days free trial ends.

To know more about the features visit MQTT Broker page

We do have community support for the free version users. Try posting your queries in Bevywise products Forum.

Download the FREE version of MQTT Broker now to enjoy the Complete functional MQTT Broker for 30 days.

download now

Do write to [email protected] for any questions or feedback. 

Fight Industrial Data Security Breaks with Secure Enterprise MQTT Broker

Fight Industrial Data Security Breaks with Secure Enterprise MQTT Broker

We all know that our world is more connected. Billions of intelligent tools and machines are generating enormous amounts of data, which creates enormous potential for businesses and other organizations to optimize their operations and achieve efficiency. As IoT devices continue to evolve, every newly connected product is vulnerable to hackers, and security turns into a significant concern. Fighting the industrial data security breaks is a 100% mandate to protect critical data in any place it dwells. Bevywise MQTTRoute provides an option to enable encrypted data transmission for better MQTT data security. It works with all standard SSL / TLS certificates and runs with a self-signed certificate. This article provides complete guidance on securing the delicate data that you transfer over the Enterprise MQTT Broker.

MQTT Broker Security Fundamentals

With regards to security in Enterprise MQTT Broker, there are some fundamental concepts to take into account they are identity, authentication, authorization, and encryption. In this tutorial, we take a gander at how you can confine access to a broker, and protect your data using different security systems.

Identity

Every client has a unique Client ID. The Enterprise MQTT broker indicates that the client must report the client ID when requesting a connection. When the broker receives a connect command from the client, it determines whether to allow the client to connect only if the received message contains a legitimate client ID, user name, and password. The client can use UUID, mac address of the network device, or other unique client information as the client ID.

Authentication With X.509

This is the safest method for client authentication. In addition to authentication with username and password, the MQTT broker allows a device to authenticate with an X.509 certificate. This certificate provides authentication at the transport level. X.509 uses a public key infrastructure to verify that a public key belongs to a client. In the X.509, a certificate authority is introduced to verify the identity of a client. During the handshake process, the client presents the broker with its certificate, which contains information such as identity and public key. Then the broker relays this certificate to the certificate authority for verification. After verifying the client certificate, the broker ensures it is genuine or not and gain trust in the binding with the client name and public key.

Client Authentication

There are three ways to verify the identity of the MQTT client on Bevywise MQTT broker : the Client IDs, Usernames and Passwords, and the Client Certificates.

Client ids

All MQTT clients must provide a client id. When a client subscribes to a topic the client id links the topic to the client and the TCP connection. With constant connections, the broker remembers client IDs and subscribed topics. When configuring the MQTT client you need to relegate the Name / ID to the client. However the Bevywise MQTT Broker allows you to impose client id prefix restrictions on the client name, and this provides some basic client security. You will find this setting in the security settings section of the broker.conf file.

########### prefix for Random Clientid Generation ###########
[MQTT]
CLIENTID_PREFIX = Bevywise-

Username and Password

An Enterprise MQTT broker can request a valid username and password from a client before allowing a connection. The username and password combination is transmitted in plain text and is not secure without some form of transport encryption. However, it does provide an easy way of restricting access to a broker and is probably the most common form of identification used. The username used for authentication can also be used in restricting access to topics. On the Bevywise MQTT broker, you need to configure settings for this to work. Again you will find these settings in the security section of the broker.conf file. The devices can connect using MQTT Username / Password or you can connect it without the username and password. You have to change NO to YES if you are planning to use Authentication.

################ Device Authentication #################
[AUTHENTICATION]
AUTHENTICATION_ENABLED = YES
# YES || NO

To create the passwords you will need to use the utility that comes with the broker. You can add the Username and passwords on the UI under the Security tab for secure client connections.

Authorization

Authorization is managing the clients’ rights. The most common types of authorization used are Role-Based Access Controls (RBAC) and Access Control List (ACL). RBAC provides a level of abstraction between the client and the main resources. It facilitates the administration of security in a large organization. This allows the broker to authorize the clients published or subscribed topic. ACL associates certain clients with a list of permissions that includes who can access the resources and which operations are allowed. ACL provides policies on what topics a client can subscribe / publish. Using ACL or RBAC, the broker implements topic permissions to restrict a client from publish / subscribe to unauthorized topics. Each topic permission allows the broker to specify authorization for clients and limit them to subscribe and publish messages. If a client attempts to perform an unauthorized operation, the broker can perform actions such as disconnect the client by preventing it from publishing data to other clients.

Authorization with Access Tokens

Another approach to providing authorization is a token authorization. Token authorization permits a client to request the scope or privileges that the client has. To connect to the broker with an access token, the client must use the password field to send the access token with the connect message. The client must be given an access token before requesting a connection. There are a variety of token services available. The most commonly used are OAuth and OAuth 2.0.

OAuth

It is a token-based authentication that is used to provide SSO and permits information to be utilized by third party services. It likewise requires an identity provider for authenticating clients’ access.

OAuth 2.0

It authorizes third-party applications to access the client account and authenticates the client by following the authorization code flow.

Securing Data

There are numerous possibilities to hack the data transfer between Clients and Broker. To protect the contents of your MQTT messages, you can use TLS or SSL Security and Payload encryption. Enterprise MQTT Broker eliminates “Man in Middle attack” by enabling data transfer through TLS port.

TLS / SSL Security

TLS / SSL security is a more commonly known security used on the web. This security is part of the TCP / IP protocol. TLS provides a secure communication channel between the client and the server. TLS certificate is provided for both server and client, and those certificates will be verified and authenticated by Certificate Authority before connection. The broker will connect only if the Certificate and host IP match.

Communication between clients and the server must be ensured by enabling TLS mode and setting passwords for the connection. You can use a single password for all clients or individual passwords for each client. Open conf/ folder on broker.conf and update TLS_ENABLED to TRUE . All other values can be changed if necessary. Using a non-regular port number for Broker and a secure web socket will further enhance security against DDOS.

#########MQTT BROKER CONFIG#######
[CONFIG]
PORT_NO = 8883
WS_PORT_NO = 10443
TLS_ENABLED = TRUE
# TLS_PORT must be 88xx.
TLS_PORT_NO = 8883
WSS_PORT_NO = 11443

Payload Encryption

This is done at the application level and not by the broker. You can encrypt data without configuring the broker. It likewise implies that data is eventually encrypted and not just between the broker and the client. However, this type of encryption doesn’t protect passwords on the connection itself. Because it doesn’t involve any broker configuration or support this is likely to be a very popular method of protecting data.

WILL and Retained message

Last WILL, will help the subscribers to know when the publishing device has gone down or got disconnected from the broker. Retain tag tells the broker to keep the last published message for the new subscribers to know the last published messages while connecting for the first time. Besides, the Enterprise MQTT Broker provides both these messages as needed for the realtime.

DataBase Storage

The broker will store the data into the database for further analysis and decision making. The default DB supported is SQLite. But the DB Configuration can be modified to make it work with MySQL or any other Big Data engine. Please refer to the help document to set up MySQL, its dependency packages, and other big data engines.

Intuitive User Interface

Through a web-based primitive User Interface broker, you can view the active devices and recent activities of different devices. It also helps to view the activities and messages sent from and to specific devices.

Get your free version of MQTT Broker now for secure data transfer.

download now

The product page and the help documentation will provide more information on configuring and running the Broker securely. For more queries, feel free to contact us at [email protected].

Build a Fleet Management System with Ease

Build a Fleet Management System with Ease

IoT technology is used to make the transportation and logistics industry increasingly effective and solid. Fleet management systems play an important role in the transportation system. Here we have depicted the Bevywise MQTTRoute which gives the technology required to track associated fleets. Bevywise MQTTRoute is a profoundly extendable, adaptable, and versatile MQTT Broker utilized for gathering information from IoT edge devices in which it is easy to transfer data to and from associated vehicles in a dependable and quick way. This documentation provides developers with a comprehensive guide to using this IoT application framework to track associated fleets.

MQTT Implementation

Fleet management is now made simple with IoT. It offers a high return on investment, improved fleet optimization, operator safety, and reduced fuel costs. Nevertheless, it faces some challenges in managing fleets. One of the biggest challenges is bidirectional messaging and real-time connectivity resulting in loss of connection and significant network latency. Bevywise MQTTRoute facilitates the reliable and fast transfer of data to and from connected vehicles.

The MQTT Route Fleet Management System enables you to maintain a continuous connection between the vehicle and the cloud, ensures reliable data transfer between vehicles and the cloud, setting up a secure TLS / SSL connection, deploy MQTTBroker and run it in a private or public cloud and integrate messaging data with other existing business systems.

The factors that affect fleet optimization are:

  • Live Tracking and Notifications
  • Outing History
  • Fleet Safety and Security
  • Charts and Reports
  • Fuel Management
  • Admin Console

Live Tracking and Notifications

The intuitive dashboard exhibits real-time information from vehicle sensors and gathers it using MQTT to create notifications. The collected data is stored on the MySql. For powerful visualization and analysis of data, you can use Advanced data storage for custom usage to store your data in Elastic Search or other data engines. Coordinate your ML Algorithm into the Python assembled MQTT Broker and get your data ready for decisions. Direct the incoming real-time events and guide it to your ML engine utilizing the scheduler module to make custom alerts and notifications.

Map
Fuel Consumption

Outing History

You can create historical graphs and charts, to preview and download any vehicle’s historical data for a specific date range. You can also check the details of any previous trip, including distance, fuel mileage, and driving conduct during the excursion. The history graph provides a comparative report of payloads issued on two different days, months, or years. You can also download the graph as a PDF.

Outing History
Driving Behaviour

Fleet Safety and Security

Control hasty driving behavior, such as excessive speed, sudden acceleration, and braking. The IoT platform and Mobile SDK are tightly integrated with the firebase cloud messaging system, which sets burglar alarms on the phone to let you know if the vehicle is driven without permission. The web platform is also integrated with the WebSocket-based notification engine for notifications in the web user interface. Real-time driving behavior dashboards and charts let you understand the intensity of hasty driving and take the appropriate action.

Safer Drive
Safety score history
 

Charts and Reports

Consequently get reports of distance, driving time, fuel expended, and other indispensable data to lessen manual slip-ups and improve consistency. Get definite vehicle use, fuel, driver execution, and other downloadable reports of your fleet to improve assets and increase productivity. The report tab in MQTTRoute has build-in visualization, in which the users can visualize the data in a chart or graph. The reports can also get downloaded in which it is stored in the big data engine in the back-end and automatically converted to PDF.

Distance
Alerts

Fuel Management

The fleet costs can be reduced by observing fuel utilization and inefficient driving conduct. The intuitive dashboard gives you the permeability of all viewpoints including fleet usage, driving conduct, fuel utilization patterns.

The developers can create widgets for measuring fleet usage, driving conduct, fuel utilization patterns. All widgets created by the developer are placed on the interactive dashboard which gives you the permeability of all viewpoints. The following code snippet is used to build a custom URL inside custom_ui_server.py.

def custom_urls():
urllist={
“AUTHENTICATION”:’DISABLE’,
“urls”:[{“/extend/Dashboard”:dashboard}]
}
return urllist

Fuel Consumption
Fuel Mileage
 

Admin Console

Manage multiple users on the platform with appropriate privileged access through the Admin console. Admin console has an elegant Dashboard that gives brief details about the organizations to manage drivers and assign them to specific vehicles. Bevywise MQTTRoute provides an API for integrating relevant data into internal enterprise applications. This allows the server infrastructure to provide the opportunity to consolidate, collect, store, and test various vehicle information and the impact of test results with clients and end users.

Fleet Management Dashboard

Download MQTT Broker now and start building your application today.