In this lesson, we are going to introduce what is QCT protocol and why we need it.
I'm here to protocol stands for message queen telemetry transport.
Now it's a lightweight messaging protocol for small sensors and mobile devices optimized for high latency
or unreliable networks, enabling a smarter projects and devices.
And nudity is a simple messaging protocol.
It's designed for constrained devices with low bandwidth.
So it's the perfect solution for Internet of Things applications.
And security allows you to send commands to control outputs, read and publish data from sensor loads
and much more.
Therefore, it makes it really easy to establish a communication between multiple devices.
If you like home automation and you want to build a complete home automation system, you can easily
do that using security.
Now.
In order to use NQT, you need to know that man commands.
And these are publish messages, topics and brokers.
Now let's start with the main concept of publish.
The first concept is to publish and subscribe system and publish unsubscribe system advice can publish
our message on our topic.
Or it can be subscribed to a particular topic to receive messages so it can send a team to Charleston
sort of value to a specific topic online.
While the messages, which is a second concept, all of the information that you want to exchange between
your devices, whether it's a command or debt.
The third concept here is that topics it's another important concept.
Topics are the way you register interest for incoming messages or how you specify where you want to
publish that message.
Topics are presented with strings separated by a forward slash.
Each forward slash indicates atomic level, and you can easily take this as an example, if we added.
I'll see you.
And a forward slash, it means that we have this topic, if we add ESB after, that means that you are
specifying another topic inside this one.
So this is the main topic and this is the sub one, and we can't keep going like that.
Now the Foxconn concept here is the broadcast.
You also need to be aware of that.
The broker is primarily responsible for receiving all messages, filtering their messages, decide who
is interested in them and then publishing the message to all subscribed clients.
So it's a very important concept when it comes to multi level and multi devices systems, but mainly
we will use the publish.
Concept, and we will publish data to that NQT online servers from the ISP, Bolt and ISP will receive
the data from our Arduino board.
That's it.
This is the main concept.
This is what is.
I'm Kutty why it's important to use it.
You can replace it with any other API like Google Firebase.
Any other API can work, but you need some coding experience to adjust the code.
Thanks for watching this.
That's all.
This is us far from educational engineering team.