Excellent, calm, measured explanation of the subject. No annoying music. No annoying verbal tics. No annoying, flashy editing. No annoying anything! Just subscribed.
I prefer no music because I watch instructional/educational videos at 3x speed (with an extension). Often with closed captioning too. Music really throws it off.
This is the clearest explanation to date I have seen and I've been doing IoT since 2004. Going to send it to my students. Love it. So clear, thank you!
I’ve got to say that even though I’ve seen a few vids on various people explain MQTT in concept explanation that this is by exceedingly far the most thoughtful, concise, contextual and so well explained video in clarity of all the previous videos I’ve seen on this topic. It’s calmly explained as well. I’ve got a much more through understanding also. My next question is there a low cost device and or software that can be used for the MQTT broker in a PLC System? I’ve seen 1-2 Opto Devices, but I’m not sure what you all have for MQTT oriented broker solution.
Amazing work. Thank you so much. I've never commented before but you can't imagine how helpful your videos are to me as a beginner. I started out with Node-red and have been following your series since then. Keep up the good work.
Thanks for your efforts and quality content. While watching I thought that the video must be about to end because who shares all that for free but I wasn't even halfway into the video. Thanks again. :)
I'm always liked to watch your videos: your speach is so clear and structured that after I watched any of your tuts - I feel that I'm already an expert on the topic. Thank you for that!!!
You have a star network in your example but a popular thing these days is a mesh network. One main advantage of a mesh is the ability to relay messages and the other advantage is it is decentralised so you can tap into the mesh in an adhoc way, able to send controls from any node to any other node with all nodes identical on the network layer. I wonder if MQTT can be used in a mesh. My interest in it is to control the network over the internet using AWS or similar. This is because most people use a dynamic IP address so it gets around that problem.
Amazing video. Nice explanation. Suppose devices from the factory want to send messages to the cloud where we will deploy the broker? Is it a customers factory server or a cloud server? what is the best practice? High level diagram of real time use case would help
at 7:04 you say retained messages are just a copy of the most recent message. But cant there be more than one? I could swear the Q in MQTT is for queue... Nice video though!
Great video. Only question is where is authentication defined? Does each client need a unique uname/pword or can multiple clients share one? If shared, how are clients identified uniquely?
have you ever work on android broker such as moquette or something like that ? when we have one esp8266 and we want to connet to it with 20 mobile phone what happen? each esp8266 or esp 12e can just have 8 TCP/ UDP connection what's your idea if we have 20 mobile phones and simultaneous they want to connect to one esp publisher? if we run an android broker on one of mobile phones and other connect to it we can connect to esp by one TCP/UDP from broker to esp, is it true? have you ever work on android broker such as moquette or something like that ? and we don't have any cloud on the net!!!!
does all mqtt broker supports Retain Messages, Birth, Death, and Last Will and Testament Messages? i am planning to use mosquitto broker and i dont know if it support those functions
From what i understand, MQTT just requires a network to be made, not the actual internet right? I'm using AWS greengrass and planning to have 2 devices communicate locally over mqtt, what would happen if there is no internet connectivity with the cloud?
You are correct. MQTT doesn't require the Internet to work; it only requires a TCP/IP-based network, including private LANs, WANs, and cellular networks.
I think some real life implementation for the birth, death and last will messages would be nice to help me understand the purpose a bit better. You have a broad example and I do think the explanations overall and of that was good but I'm having a hard time thinking of the overall use case. Also I was looking into this video regarding trying to learn about mqtt for home assistant and I'm confused how it's not default an mqtt system. I know I don't use topics to send and receive messages but what would using default home assistant communication be called then?
what a nice explanation about brokers and mqtt functionality! great! good work! May i use your the video info (w/the correspondig intelectual property credits) in a document i'm working on? thank you in advance!
I am working on a wrist watch project and need a way to move 1 to 40 Mbyte data files from an Android and iOS mobile device to the watch over Bluetooth Classic. ESP32 drives the watch. Have you seen a solution? -Frank
Great explanation, we are attempting to use this protocol I have wondered how it works. Can anyone tell me if there are networks of IOT developers here with in the USA that we can post a project to?
Yes, absolutely. The topic is simplified here, but you can create a topic "tree" with different levels separated by a slash. It's not exactly a folder-like structure, but something like "cluster1/clientA/data" and "cluster1/clientB/data" then a "cluster1/#" subscription would do the trick. Many of our other MQTT videos go into more technical depth if you want to check them out!
It might be a network configuration issue -- if the client cannot reach the broker across a given network then you can get connection errors. If the connection is 100% working, I would double check the broker security configuration.
Maybe someone can elaborate on this: a security feature of MQTT apparently is, that devices are not aware of other devices due to the publish/subscribe methodology. But if the broker sends out Birth/death/LWT messages out to other devices, other devices will become aware of other devices and can notify or attempt reboots. That's a contradiction, isn't it?
A better way to think of the security feature is that devices are not aware of each other's identity. I may not have your IP address or host name, but if I know what topic you publish your state changes over, I know your status. The topic and message are whatever you choose, they aren't tied to the individual device, so there's some obscurity there. Also, if there are some devices that you *don't* want to know about your status changes, just use the access control list (ACL) to prevent other client user accounts from subscribing to those topics.
Excellent, calm, measured explanation of the subject. No annoying music. No annoying verbal tics. No annoying, flashy editing. No annoying anything!
Just subscribed.
best comment. this is how web videos should be, this one is a perfect example by the way.
Could not have said it better! Liked & dubbel.
I prefer no music because I watch instructional/educational videos at 3x speed (with an extension). Often with closed captioning too. Music really throws it off.
I can only agree. Perfect video tutorial! Just subscribed!
PS, this helped me a lot with my thesis, thank you for that!
My favorite MQTT Broker explanation...I share this weekly with my customers that want to learn more about MQTT. Great job OPTO 22!
Glad it was helpful!
This is such a great explanation you barely even notice that the guy starts each sentence in Los Angeles and ends it in Melbourne.
This is the clearest explanation to date I have seen and I've been doing IoT since 2004. Going to send it to my students. Love it. So clear, thank you!
Awesome, thank you!
I’ve got to say that even though I’ve seen a few vids on various people explain MQTT in concept explanation that this is by exceedingly far the most thoughtful, concise, contextual and so well explained video in clarity of all the previous videos I’ve seen on this topic. It’s calmly explained as well. I’ve got a much more through understanding also. My next question is there a low cost device and or software that can be used for the MQTT broker in a PLC System? I’ve seen 1-2 Opto Devices, but I’m not sure what you all have for MQTT oriented broker solution.
what amazing video, 10 minutes of pure informations, congrats
Much appreciated!
I rarely comment however I have to tell you what an amazing job you did on this content.
Thank you for your comment...we appreciate it!
`Clearly Explained`
I have ADHD and normally I'd lost my focus in the first couple of minutes but I kept watching this video for 10mins.
Great to hear!
Amazing work. Thank you so much. I've never commented before but you can't imagine how helpful your videos are to me as a beginner. I started out with Node-red and have been following your series since then. Keep up the good work.
Thanks Ha My Tran! We are so glad that you found it helpful. Keep at it!!
This is a the best explanation of a complex topic. Watching again
Thanks so much!
really appreciate the way you have made and edited this video, i likes the way you gave tiny sound to each graphics that makes it look it more alive
Thanks Vinay! I'm really glad you liked the video. Keep watching.
Insanely easy to understand video. I understood in a sec. Thanks! Kudos to your work.
Glad you liked it!
wow this is the best video on TH-cam, you helped start my PhD hitting the ground running
Great to hear!
Thanks for your efforts and quality content. While watching I thought that the video must be about to end because who shares all that for free but I wasn't even halfway into the video. Thanks again. :)
So nice of you
I'm always liked to watch your videos: your speach is so clear and structured that after I watched any of your tuts - I feel that I'm already an expert on the topic. Thank you for that!!!
Thanks!
Now "that" is how you explain a system correctly. OUTSTANDINGLY EXCELLENT :O) Thank you.
You're the best!! Thanks for the love!
Enormous help, so much information yet still comprehensible, thank you!
Thanks Samuel!
first time ever commenting on the video. Excellent explanation, definitely a keeper !
Awesome, thank you!
Great video. Love the pace and the clarity.
Hi Harry, Keep watching! We've been busy making more tutorial videos.
Thanks, really helpful intro. I've been trying to find something like this....easy to listen to and understand
Glad it was helpful!
EXCELLENT video! Just the sort of lower level feature information other videos seem to gloss over. Thanks!
Thanks playaspec, Keep watching! We've been busy making more tutorial videos.
This content is so good.
Thanks Zack! That means a lot coming from you.
Nice and simple explanation, yet covering everything required.
Glad it was helpful!
I have an exam on IoT in few hours, this video helped a lot thank you 5/5
Thank you for a very clear and concise explanation...Excellent
Nice work dude !! Clearly explained each concept, Thank you so much
Most welcome!
perfectly explained. welldone for the good work👏👏
Thanks and welcome
You have a star network in your example but a popular thing these days is a mesh network. One main advantage of a mesh is the ability to relay messages and the other advantage is it is decentralised so you can tap into the mesh in an adhoc way, able to send controls from any node to any other node with all nodes identical on the network layer. I wonder if MQTT can be used in a mesh. My interest in it is to control the network over the internet using AWS or similar. This is because most people use a dynamic IP address so it gets around that problem.
Thanks. I just came looking for MQTT primer and yours is excellent! Will be checking out your other videos as time permits.
Awesome! Thank you!
Well done. Very clear. No fluff.
Glad you liked it!
Nice....Finally a good explanation
Thanks for the support!
Amazing video. Nice explanation. Suppose devices from the factory want to send messages to the cloud where we will deploy the broker? Is it a customers factory server or a cloud server? what is the best practice? High level diagram of real time use case would help
That explanation was really good,Thank you
Keep going with the excellent work that you do.
Hi Fernando, We're busy making more MQTT tutorial videos. Keep watching this space! More new videos coming out every week.
Very clear and informative, thanks! 👍
Glad you enjoyed it! Thanks for watching
short and straight video nice
Thanks!
Clearly explained indeed..Thank you.
perfectly explained. Thank you
Glad it was helpful!
Well done.
Thanks Jeff!
Thank you.Very clear explantion.
Excellent work !
Thanks so much!!!
at 7:04 you say retained messages are just a copy of the most recent message. But cant there be more than one? I could swear the Q in MQTT is for queue... Nice video though!
simple and clear. thank you!
Awesome video! thank you!
My pleasure!
Great video. Only question is where is authentication defined? Does each client need a unique uname/pword or can multiple clients share one? If shared, how are clients identified uniquely?
Great video. I needed this. So very well done. Thank you.
Glad it was helpful!
have you ever work on android broker such as moquette or something like that ?
Thanks for sharing the information. Loved the way you made the video. Thumbs up and subscribed!
Awesome, thank you!
Awesome video! Very clear and informative
Glad it was helpful!
outstanding video, super clear explanation
Much appreciated!
Very helpful. Thank you!
How come the Certificate is optional for a TLS connection, isn’t that a pre requisite ?
Amazing again. Thanks
Thanks so much!!!
You are absolutely awesomeness bud!!
You rock!
again! wow! what a nice video! love it!
Thanks! You're the best.
have you ever work on android broker such as moquette or something like that ?
when we have one esp8266 and we want to connet to it with 20 mobile phone what happen?
each esp8266 or esp 12e can just have 8 TCP/ UDP connection
what's your idea if we have 20 mobile phones and simultaneous they want to connect to one esp publisher?
if we run an android broker on one of mobile phones and other connect to it we can connect to esp by one TCP/UDP from broker to esp, is it true?
have you ever work on android broker such as moquette or something like that ?
and we don't have any cloud on the net!!!!
Very good video, now bookmarked! Came here following references originating from home-assistant.io, which I'm just learning.
Glad it was helpful!
Great explanation !!! Thx !!!
Can you tell what your opening music is, very nice tune!
does all mqtt broker supports Retain Messages, Birth, Death, and Last Will and Testament Messages? i am planning to use mosquitto broker and i dont know if it support those functions
Excellent.
Thanks for the support!
Excellent explanation ! You are really gifted to explained with so much clarity complexes subjects! Please keep up doing great video like this 👍
very well explained
Glad you think so!
Brilliant content, thank you.
Glad you enjoyed it!
Excellent Video to Understand MTTQ.
Pls Answer
1 thing I want to ask, which software you use to make this Animation Videos.
Thanks for watching! We use Final Cut Pro X, After Effects, Cinema 4D and Premier.
@@Opto22 Thank You for Your Reply.
Great explanation.
Glad you liked it
From what i understand, MQTT just requires a network to be made, not the actual internet right? I'm using AWS greengrass and planning to have 2 devices communicate locally over mqtt, what would happen if there is no internet connectivity with the cloud?
You are correct. MQTT doesn't require the Internet to work; it only requires a TCP/IP-based network, including private LANs, WANs, and cellular networks.
Nice! I can use that for my lecture on MQTT.
I think some real life implementation for the birth, death and last will messages would be nice to help me understand the purpose a bit better. You have a broad example and I do think the explanations overall and of that was good but I'm having a hard time thinking of the overall use case. Also I was looking into this video regarding trying to learn about mqtt for home assistant and I'm confused how it's not default an mqtt system. I know I don't use topics to send and receive messages but what would using default home assistant communication be called then?
This is super helpful, thank you!
Glad it was helpful!
Thanks for great explanation!
Glad it was helpful!
"Premise" is a proposition, a component in a logical argument; "premises" is land, building, or real estate.
So as example, what could be a broker agent, is Amazon AWS a broker?
AMAZING VIDEO, Thank you very much.
Glad you liked it! Thank you!
what a nice explanation about brokers and mqtt functionality! great! good work! May i use your the video info (w/the correspondig intelectual property credits) in a document i'm working on? thank you in advance!
wow......seems like he loves his work.
Thanks Alpha coder!
We developed the Pub-Sub model, which was further developed by IBM & MS.
cool
I am working on a wrist watch project and need a way to move 1 to 40 Mbyte data files from an Android and iOS mobile device to the watch over Bluetooth Classic. ESP32 drives the watch. Have you seen a solution? -Frank
Awesome video.. 👍🏻👍🏻
Thank you..
Thank you too!
Great explanation, we are attempting to use this protocol I have wondered how it works. Can anyone tell me if there are networks of IOT developers here with in the USA that we can post a project to?
pretty cool explanation !! Thanks :)
That's awesome - super thanks!
you made my day
mine, too!
Well explained what I want to know, Thanks!!
Glad it was helpful!
Excellent explanation!
Glad it was helpful!
Very valuable video. Thank you.
Glad you think so!
is it possible to cluster the MQTT Clients (subscribers) based on the topic
Yes, absolutely. The topic is simplified here, but you can create a topic "tree" with different levels separated by a slash. It's not exactly a folder-like structure, but something like "cluster1/clientA/data" and "cluster1/clientB/data" then a "cluster1/#" subscription would do the trick.
Many of our other MQTT videos go into more technical depth if you want to check them out!
Amazing. Thanks
Maybe I would like to hear is what type of messages can be send, what type of data?
Thank you too!
Great suggestion!
Such a great video, thanks a lot! >
Glad you enjoyed it!
Thank you!
Excellent, thanks for sharing !
Glad you enjoyed it
MQTT while connected to 1883 port but at port 8883 it shows the TLS/SSL error. Could you please explain why this happens like that?
It might be a network configuration issue -- if the client cannot reach the broker across a given network then you can get connection errors. If the connection is 100% working, I would double check the broker security configuration.
Perfect explanation
Thanks! You're the best.
Thank you verry much.
Thanks! Keep watching
great explanation
Glad you think so!
thank you
Thanks for watching!
subscribed indeed ! u rock !
Thanks so much!
i really love your videos and you
Thanks Max we really appreciate it.
very well explained👍
Thank you 😃
Maybe someone can elaborate on this:
a security feature of MQTT apparently is, that devices are not aware of other devices due to the publish/subscribe methodology.
But if the broker sends out Birth/death/LWT messages out to other devices, other devices will become aware of other devices and can notify or attempt reboots. That's a contradiction, isn't it?
A better way to think of the security feature is that devices are not aware of each other's identity. I may not have your IP address or host name, but if I know what topic you publish your state changes over, I know your status. The topic and message are whatever you choose, they aren't tied to the individual device, so there's some obscurity there.
Also, if there are some devices that you *don't* want to know about your status changes, just use the access control list (ACL) to prevent other client user accounts from subscribing to those topics.
Well explained 🇦🇺👍
Thanks 👍
Good Stuff! subscribed !
Thanks for the sub!