It's always a pleasure to watch your tutorials Rui! It only takes one time to understand and that is pretty awesome, thanks for this nice way of explaining!
I have an exam in 2 days and needed to know some more info on MQTT since the teachers's slides were awful and didn't explain much, thank you so much for this
Rui I have to apologise. Initially I was about to drop watching this video because I was not sure I would be able to understand your accent. but after watching further the pace and level of your introduction was perfect. I hate having to wait for people to get to the point.
Trying to dive into IoT home automation head-first has been a challenge. I was having a real hard time trying to wrap my head around how MQTT works, and this video did a great job at breaking it down. Thanks so much for putting this quick presentation together.
Thanks as always. This would have been clearer if the block diagram at 1:15 should have indicated the grey box was the Broker. So the same diagram from 3:34 would work. A block diagram with an example of many subscribers might also help get an idea across of the power of the broker topology. And then a word or two about many to one and many to many topologies which should be easy to grasp after the many subscribers is understood. Please add a link to the next unit in the "more information" dialog.
Hello Rui, thank you very much for this instructional. I am currently working in a document about application layer protocols in IoT and I'm struggling with some topics (I'm a Industrial Engineerig). Where can I grab some resources about this topic. Saludos desde Guatemala, muchas gracias
Hi Rui, I dont understand a thin: 1. the broker is in the ability to save the information, for after send to a subscriber ? 2. Or Is It all in real time? 3. A question for solution this, for example, I have that develop a code that it conects as subscriber and saved the information? Help me, please!
1) No, the broker only transmits the data to all subscribed devices 2) Yes, it's real time 3) The subscribed device/client should be the one saving the data
You can have multiple brokers in your network. In your devices, you define which broker do you want to connect to (by entering the ip address and port number)
I'm new to all this and greatly appreciate your tutorial, but I'm also suspicious of this technology. Are there a lot of MQTT Brokers, are they fee based and are there MQTT Brokers that should be avoided? Once a device like a motion sensor and/or camera is setup using an ESP8266, can MQTT Brokers access the router and/or modem to intercept data transferred from other devices for the purpose of data mining?
Yes, I think you're right and it's called: "Message Queuing Telemetry Transport". According to the official website, a few years ago MQ didn't stand for anything: mqtt.org/faq read the first common question "MQTT stands for MQ Telemetry Transport." Since it was adopted as a standard protocol, it has been renamed and it's now called: "Message Queuing Telemetry Transport" www.oasis-open.org/committees/tc_home.php?wg_abbrev=mqtt
I see your point, with MQTT all your devices can still process all the messages, if they are all subscribed to the same topic, but they need to be connected to the broker. Thanks
MQTT does not actually stand for MQ Telemetry Transport, that was its former definition but the primary focus of the protocol has changed from proprietary embedded systems to open Internet of Things (IoT) use cases. MQTT is no longer considered an acronym. MQTT is simply the name of the protocol. Read more about this here www.hivemq.com/blog/mqtt-essentials-part-1-introducing-mqtt/
Boa noite Rui, sou um novato neste mundo da domótica e gostaria de saber se eu ao criar o meu próprio broker o posso acessar através de qualquer lado ou se continuo a estar restringido ao meu router de casa. Obrigado e bom vídeo!
Depende de onde o router tiver instalado, se for num Raspberry Pi local está restrito ao router de casa. Se instalares MQTT broker num servidor Linux (por exemplo no Digital Ocean), consegues aceder o broker de qualquer parte.
Rui Santos, muito obrigado pelo resposta! Então quer dizer que não há maneira de ter isso instalado de borla, correto? Teremos sempre de pagar o servidor
Podes também abrir as portas do router para permitir que o teu broker esteja disponível online. Mas o mais seguro seria utilizar um servidor externo ou um MQTT cloud broker grátis
Tú istáblixi 0:20 isso é tão Russo. Super bacana, valeu Rui. Se quer ver trem feio olha meus vídeos fazendo review ...kkkk nem eu gosto de ficar ouvindo
Can someone please explain in a few words the advantages and disadvantages of MQTT vs simply serving JSON data from your device based on the given HTTP request?
In summary, MQTT is the best option for IoT devices (microcontrollers) with limited resources. It also has the advantage of multiple clients receiving the same published message (when they are subscribed to the same topic). It's very reliable to establish a two way communication in MQTT and the broker ensures that all messages are properly distributed to the clients. There are many other advantages, but in my opinion these are the most important.
hello my friend how make your dashboard node-red public for access by anyone on the web pleas help me no one tel me how i slove this probleme pleaz help and explain in detail
I would like to know how to protect with login and password the interface 1880 / ui dashboard in nodered I cannot find this information anywhere! I have the nodered installed in a VPS anybody enters and can control my automation how to solve it?
This wasn't the video I wanted to say I wanted to know what's the best way to add Wi-Fi to a rock 64 nine Wi-Fi unit nobody is put this one topic there only 30 bucks
You're right and it's called: "Message Queuing Telemetry Transport". According to the official website, a few years ago MQ didn't stand for anything: mqtt.org/faq read the first common question "MQTT stands for MQ Telemetry Transport." Since it was adopted as a standard protocol, it has been renamed and it's now called: "Message Queuing Telemetry Transport" www.oasis-open.org/committees/tc_home.php?wg_abbrev=mqtt
