The impetus behind celebrating Christmas on August 25

The impetus behind celebrating Christmas on August 25

What makes us celebrate Christmas on August 25?

Can you all imagine celebrating Christmas in the month of August? It looks mystical, right? However, we, the members of Bevywise Networks celebrate Christmas festival on 25th of August. Our tables are adorned with stars and kudils; a group of employees sung a prayer song; Christmas cake is distributed to all; we enjoyed playing a Santa game and gifts were presented to all by the Christmas grandpa.  It may seem weird to you all. Usually Christmas celebration takes place on 25th December every year. But we celebrate Christmas festival this year on 25th of August. There is a valuable answer for all questions; a valid solution for all problems; There is Bevywise for all IoT related problems. Let me elaborate the incident which made us celebrate Christmas on 25th August.

Cattle Superintendency post :

A post regarding cattle management has been published by us on 19th August 2022. The post expounds how easy it is for the ranchers to monitor and manage the cattle remotely using the MQTT Broker. Our IoT enabled cattle management helps them to sit back and tackle their cattle, instead of running around it all the time. Implementation of MQTT Route on the cloud in the livestock industry helps the ranchers monitor and manage their cattle.

Cattle Management

Customer from Palestine:

There is a good impression for that post. As a result of that post, a customer, from Palestine, who is in need of this application approached us. He also shared us why he is in need of this application, which is very emotional. Before the rinderpest, a pregnant lady resided in his cow shed as a refugee. He bestowed her with lots of affection and care. But he had only a brief period of time to look after her, as he had to engage and follow his cattle. In search of a solution for the intendance of cattle, he coincidentally came across our cattle management post on social media on 19th August 2022. A chat with us was initiated by him. He agreed to attend the product demonstration and the discussions were going on for many hours.

Palestine customer

Operation Emergency Campaign:

Being impressed by our product, he proposed for customization after elucidating us about the pregnant lady who is about to deliver a baby in few days. He requested us to finish the task within one or two days. It is impossible for anyone to finish the task within concise of time. But we took it as a challenge to complete it in that short span. Forthwith, our Bevywise team initiated an “Operation Emergency Campaign” to get it done. This whole project was done within 24 hours by our team with accountability and self-motivation.

A small token of love from our customer:

In the next couple of days, our janitor found a mystery parcel near our office door which was kept by a long-bearded person wearing a red shirt. The parcel comprises of greeting message and some gifts as a token of thanks to our team. We are surprised to find that the gift is from that Palestine customer, for whom we worked on “Operation Emergency”. The gifts include sketch pens for the UI designers and Flask for the developers. It’s a mere surprise for us.

Weird answer from the customer:

Subsequently, we decided to present a baby kit to that child. We initiated a chat with that Palestine customer to ask his address. Everything went normal until he revealed his true identity. He answered that they have come from the past by time travelling. It seemed strange to us. In order to evince their identity, he sent us a set of riddles, which hinted the name of that new born baby.

Christmas gift

A – According to the Bible, there is a person like us except sin. Who is he?

B – Baby born to virgin mother

C – Cattle shed was his birth place

D – Divinity surrounded

E – Enlightenment is taught to the world by the baby

F – Faithful in little things

G – Glorified in his humanity

H – History was divided before and after his birth

I – Influential person in the world history

J – J is the starting letter of his name

Their true identity:

After decoding the riddles, we got to know that the name of the baby is “Jesus Christ” and that the pregnant lady is none other than Mary and the one who approached us is an old Prophet named John Stephen. It’s a mere shock for us. We felt some sort of divinity after this incident. We are anticipating many challenges like this to reach more heights.

So in order to celebrate the victory of Bevywise MQTT Broker and the efforts of our team, we celebrate Christmas festival on August 25th. On the behalf of Bevywise team, we wish you all Merry Christmas and may the upcoming year brings all kinds of goodness to all.

Wish to make your IoT implementation story a great success? Try signing up  Hosted MQTT Broker

Developing Scalable IoT Application with MQTT Broker

Developing Scalable IoT Application with MQTT Broker

Do you want to quickly and easily create an IoT implementation that meets your requirements? This is the right blog for you. Let’s see what would be the best choice to develop an IoT application easily. Building an IoT application comes with several challenges that are security, connectivity, data collection & processing etc. You already know that building an IoT application from scratch is one of the most difficult tasks. Because you must develop code for each one individually. Can you believe that a single framework contains everything you need to build any IoT application? Yes, Bevywise MQTT Broker is an IoT application framework that is suitable for the implementation of any IoT application. It provides a solution to all of the challenges mentioned above. Now let’s look at how we can configure an IoT application using that framework. 

Components required

Creating an application usually necessitates the use of components. It is essential that we have to ready with the components for developing an IoT implementation. Let’s take a look at what they are. MQTT Protocol, MQTT Clients, and MQTT Broker. When it comes to developing a large-scale IoT application, the MQTT protocol is the best choice. MQTT was found to be a flexible and scalable network protocol that is well-suited for developing an IoT application for greater implementation after taking into account a variety of developing and mature IoT protocols. MQTT Clients, which are the devices used for your implementation, can be used to develop your IoT application based on your requirements. MQTT Broker is the one that act as a middle ware to connect and communicate the MQTT clients. In that case, our Bevywise MQTT Broker also comes with Python extensions, making it perfect for building a full-fledged IoT application with high-level IoT implementation. 

MQTTRoute, a Bevywise MQTT Broker offers a free trial that allows you to experiment with the features and Python extensions to create IoT applications. You can get the free trial pack link by here – 

The MQTTRoute framework comprises all of the necessary options required to develop an IoT application. You can readily construct a large-scale IoT application with this and benefit from it. If you want to get in-depth detail about the installation and basic configuration of MQTTRoute. You can get it right here –

Now, Let us move on to the example to know more about the MQTT protocol. Assume you have two devices and various weather sensors (a humidity sensor and a temperature sensor). You’d like to send data on the humidity level and the temperature level to two different devices.

This task can be simply managed with MQTT. You must first set up a MQTT broker service. Then, on the broker, you may connect two sensors as clients and configure them to deliver data on the topics “Humid” and “Temp.” 

After that, you can connect the devices to the broker and subscribe the first one to the topic “Temp” and the second to the topic “Humid.” As a result, whenever the sensors publish the appropriate information to the broker, two connected devices will receive messages regarding humidity and temperature.

In the above example, the client sends the message to the MQTT broker, because as previously states that the clients cannot communicate each other directly. The messages sent by the clients are stored to the default database in the broker then it sends the messages to the appropriate subscribed client. The MQTT broker’s interaction with the devices was indicated in this example. Depending on your needs, developing an IoT application will require a specific UI and database. They can be found in the Python Extensions of the Bevywise MQTT Broker. Let’s look at how the Python Extensions for MQTT Broker allows you to customise an IoT implementation to your specific requirements. Here’s how these extensions can be used to create an IoT application.

Custom data storage based on IoT implementation

First and foremost, it is important to store data for an application. As previously stated, data for an application will be automatically stored in the MQTT Broker’s default database. By default, the Bevywise MQTT broker has the ability to store data in the following databases. MYSQL, MSSQL, PostgreSQL, and SQLite  However, we have the custom storage extension for you if you need advanced storage for developing your IoT implementation. If your IoT application necessitates the use of other advanced databases, you can specify the name and port of the database and use it in your implementation. For my IoT implementation, I’m using an elastic database through the use of the custom storage option. Because I want to analyse large amounts of data quickly and in near real time, which the Elastic Search database allows me to do. 

Let’s see how to configure the elastic search database here:

  • Make the necessary changes in the data_store.conf folder first. Set the DATASTORE option to CUSTOM after enabling the CUSTOMSTORAGE option.

  • The database’s PORT number and the INDEX NAME, which is the name by which you want the data to be stored and is specified here based on your needs.

  • We have commited the configuration files and the python extensions file in Git. Please refer to the data_store.conf folder and perform the above procedure using the link provided here.

  • After that, set up the folder. The elastic search connector was used to set this up. Refer to the code below for a better understanding.

  • The websocket process is used to display stored data in the user interface. This will be useful when implementing a custom UI.

  • You can refer the extension files here –

Crafting your own UI

The data is usually stored in a MQTT broker before being sent to the appropriate subscriber. But how can we be certain that the data is arriving and that the process is proceeding? That’s why we have a user interface for viewing messages between clients. By default, the Bevywise MQTT broker’s UI is useful for extracting data from devices, but you can also customise your dashboard and widgets here. However, if you want a completely different UI for your IoT implementation, use our Custom UI functionality for your high-level IoT application, which is one of the python extensions.

You can refer the extension files here –

If you want to develop your own UI code based on your requirements for any IoT implementation, then insert it in a folder. The code below is an example of how to see data in a line graph format for my IoT application; kindly refer this too.

Reference code for line graph

xaxis: {
type: ‘date’,
range: [olderTime, futureTime]
Plotly.relayout (graph_id, minuteView);
Plotly.extendTraces (graph_id, update, d)



This UI reference code is for live temperature monitoring application. Plotly provided this reference code. It takes the temperature of a room and displays it in a user interface. We can view it through the line graph’s output in this case.

Configure scheduler to generate alerts

We’ve already seen how to create your own database and customise the UI to view the data the way you want it. Taken the example given below, the room temperature monitor, and we’ll look at how to create conditions, alarms, alerts, and warnings in it. To do the above, you’ll need to use a custom Scheduler. This is also one of the Python extensions in the MQTT Broker.

You can refer the extension files here –

Create your code based on your IoT implementation and insert it into the #write your code here section. A small example of the scheduler option is provided below, and you can write your own code to suit your needs.

Reference code for Alerting high temperature in room

def schedule_conf( ):





{‘OnceIn’ : 5,‘methodtocall’ : fiveminschedule },

{‘OnceIn’ : 10,‘methodtocall’ : tenminschedule } ] }

if ( p_avg < data3 [‘msg’] [‘message’] [0] ){

document.getElementById (“Alarm”).innerHTML=data3 [‘msg’] [‘message’] [0] + “ALERT!” + “Temperature High”;


return schedules

The above code represents the condition applied which aggregate the temperature between every 5 minutes and 10 minutes schedule data and also refers to the alert setting when the temperature is high in the room. The data from the scheduler is pushed into the UI by the conditions listed above. If the temperature in the room is too high, we will receive an alert message via the UI. This way, you can easily configure it based on your needs to suit your IoT implementation. 

Enabling Advanced Authentication

Let’s take a look at MQTT broker security now. The data security in MQTT Broker is excellent. It is dependent on the security of TLS / SSL. However, your data still requires security, and we offer Custom authentication if you think security is essential for your IoT application. Custom authentication functionality in Python extensions will prove to be beneficial. Because, Bevywise MQTT Broker provides custom authentication functionality, allowing users to integrate any central IAM and SSO for your big level IoT implementation & for managing lot of users in your application based on your requirements.

Let’s see how to configure authentication in broker.conf folder


You can refer the broker.conf and extension files here –

# Request Retries Count

requests.adapters.DEFAULT_RETRIES = 3

# Request URL

url = “”

# Request Timeout

request_timeout = 0.1

# Request Method

request_auth_method = “POST”


When we manage a large number of users, as previously stated, if one of them forgets or mistypes his password, you can specify how many times you can try again in the requests.adapters.DEFAULT RETRIES field. This field’s default value is 3. You can change the count based on your IoT implementation. You can enter the URL of your authentication landing page in this field, “url = “”. This validates your attempt to connect using with your login credentials.

All of the functionality described above is provided by the Python extensions in  Bevywise MQTT Broker. With these, you can easily set up a large-scale, flexible, and scalable implementation of your IoT application.

In our MQTTRoute, all python extensions were pushed to Git. Use this link to refer to all of the folders –


To develop a scalable IoT application, start by downloading the free Bevywise MQTT Broker.


For the detail information about python extensions to develop any scalable IoT implementation, refer this link provided here –


On premise vs Cloud  MQTT Broker – Which is best for your IoT implementation?

On premise vs Cloud MQTT Broker – Which is best for your IoT implementation?

Key thoughts for choosing Cloud or On-premise MQTT Broker

Choosing between cloud MQTT Broker and on-premise MQTT Broker is a major decision that should be taken carefully and deliberately. This blog is for you if you are about to make this decision but are concerned about security or privacy and want to have greater control over your data. This will help you in comprehending the distinctions so that you can make an informed decision for your business. To make the best decision for your organisation, consider the following factors: deployment, control, security, scalability, and compliance. These factors will help you in determining the best approach for your application development.

Cloud Hosted MQTT Broker Vs On-Premise MQTT Broker 

You have improved security, performance, control over how your data is utilised, and who has access with an on-premises MQTT broker. You can also make changes to security settings yourself rather than having to wait for someone else to do it.

When employing cloud services, however, scaling up and down is more easy as needed. Both approaches bring something different to the needs of the organisation, but only after deep evaluation can you determine which solution is best for your enterprise. When deciding between an on-premises and cloud solution, you need to consider the following points:

On-premise Vs Cloud accordance with the following factors 


To enable MQTT communication in Cloud Hosting, you do not need to setup anything on the server. Managed MQTT brokers allow you to concentrate only on the development of your application, freeing you from the burden of server administration. Manage and maintain everything on your server with an on-premise MQTT broker. The solution provider handles managing the solution and related processes while using on premise.


Streamline your IoT application development with cloud hosting by controlling and managing your devices via REST based APIs from the manager application. Control & integrate your IoT solution with your ERP or business management applications. In on-premise your data, security, and privacy are all in your complete control. Your enterprise is entirely responsible for maintaining uptime and troubleshooting downtime.


Secure and safe handling of your data, as well as secure connection and communication of your devices, are all provided by dedicated cloud hosting. Compliant with security standards in data management and to ensure that your hosted information is protected without compromise. When you store your data on-premises, you have complete control over the security and privacy of your information.


On-premise solutions can be accessible remotely, but they frequently require third-party assistance. If network problems occur and your Internet connection is lost, you can still access your data using on-premise solutions. In terms of cloud, when you wish to extend your business, establish a new site in any country. In minutes, you may increase the capacity of your server. It allows data to be accessed from anywhere in the world. This gives you the freedom to work from anywhere at anytime. 


A major advantage of cloud implementation is scalability. You can adjust your on-demand consumption as needed, allowing you to scale up as your business grows. Cloud solutions provide more flexibility because they may scaled up and down on demand to meet the needs of the business. Cloud MQTT Broker is always ready to serve any business-critical IoT solutions with its scalability and reliability. To keep up with usage or demand, on-premise implementation requires further hardware or software upgrades.


Enterprises that establish the broker in On-premise, they are responsible for the server hardware, power consumption, and storage costs. By choosing to use the cloud computing model, you only pay for the resources you use, with no maintenance or upkeep costs, and the price adjusts up or down depending on how much is used. You don’t have to worry about server hardware, or maintenance when you use the cloud.


After gaining clarity by reviewing the above factors to fit your needs, you can easily determine which plan you require. On-premise vs cloud plans have different benefits. Both of these can be very beneficial to your business. 

The basis of the IoT is the connectivity and the remote control.  The most feared part is the security. However, the dedicated servers provide much more secure options equivalent to something that you get on On-premise.  Unless you have limited network connectivity for your factory in your industrial area, we would recommend a cloud hosted for a hassle free operation.

To get started with your IoT deployment, Sign-Up with trial now.

Kindly reach support if you have any queries.