MQTT + Sparkplug B Tutorial: A Complete Guide To MQTT and Sparkplug B with Practical Demonstration.

[@industry40tvonline]

If you enjoyed this video you will also find my free newsletter valuable. Join 2500+ subscribers to get weekly actionable tips on the architecture and development of IIoT solutions. → SUBSCRIBE HERE: www.industry40.tv

[@sudarsanvenkata]

Thanks for MQTT Sparkplug demo. I appreciate you work and learnt more from this demo. Waiting for more informative videos from you on Industry 4.O

[@industry40tvonline]

I'm glad you learnt something from the video, Sudarsan. Thanks for watching and for the feedback, it means a lot. More videos are coming.

[@Ecuaciondelagrange]

Your explanations and how you transmit your knowledge are amazing! Congratulations!.

[@Gr4chu5]

As somebody who's only just begun working on an iiot application with mqtt, your video has been the biggest help in developing the foundation I need to start building. Thank you for your excellent work!

[@industry40tvonline]

Thank you for your feedback, Gr4chu5. I appreciate it.

[@mikedash4351]

Great video. Everything is very clearly explained, with plenty of technical details.

[@industry40tvonline]

Thank you, Mike.

[@maxwellschaphorst8050]

Only 8 mins in but wanted to say, you explain things extremely well! Also great diagrams to help illustrate the concepts. Well done, I will be subscribing

[@industry40tvonline]

Thank you for the feedback, Maxwell. I'm glad you find the video informative. And thanks for subscribing, I'm looking forward to serving you with more content!!

[@ДонПедро-г6ы]

Thank you, buddy for clear explanation👍🏼 Looking forward for next tutorial🤖

[@EctoboxInc]

Such a great review of MQTT and SparkplugB. I continue to come back to this as a reference!!

[@industry40tvonline]

Glad you enjoyed it!

[@alexandr0id]

Very nice overview, just enough details and practical explanations! Thank you for the video!

[@industry40tvonline]

Thank you for the feedback. Much appreciated.

[@althechemist4484]

Fantastic job man well done

[@EmileAckbarali]

Finally got a chance to look at this. Just brilliant!

[@industry40tvonline]

Thanks for the feedback, Emile. I'm glad you like the video.

[@ayatarek9890]

that was very helpful! thank you

[@willemhaifetz-chen1588]

Thanks, super clear

[@emargee]

Thanks, this summary helped me a lot. I appreciate the effort the video must have taken.

[@industry40tvonline]

Thank you for the feedback Mark. I'm glad the video helped you.

[@chadilac9]

Very informative and well put together video! Awesome to stumble upon, keep up the great work

[@industry40tvonline]

Thanks, Chad.

[@mazensalhi4496]

Very well done and presented. Thank you!!

[@industry40tvonline]

Thanks, Mazen. I'm glad you found the presentation useful.

[@pourmog]

excellent content! thank you for sharing

[@industry40tvonline]

Thank you, pourmog.

[@vinaysaketh3449]

Thanks great video

[@industry40tvonline]

Glad you enjoyed it, Vinay.

[@industry40tvonline]

Glad you enjoyed it, Vinay.

[@93GG93]

Hi Kudzai, from 23:40, you mentioned the "Last Will and Testament" but in the Sparkplug B Specification (see below) it is mentioned only once and not even once in the MQTT v3.1.1 specification. The below text says it is a MQTT v3.1.1 feature but how come that it is not mentioned in the MQTT specification? Do you maybe know? I have seen it is in the HiveMQ documentation, but I find it strange that its not mentioned in the MQTT specification and therefore, for me as a student, hard to understand. "The Sparkplug™ specification defines the use of the MQTT V3.1.1 “Last Will and Testament” feature to provide MQTT session state information to any other interested MQTT client in the infrastructure. The session state awareness is implemented around a set of defined “Birth” and “Death” Topic Namespace and Payload definitions in conjunction with the MQTT connection “Keep Alive” timer".

[@sumitbirla5895]

Great explanation of MQTT + Sparkplug B. Question: how does an HMI retrieve the current values when it comes online? It appears MQTT will only transmit when the value changes.

[@industry40tvonline]

Thanks for watching, and for the feedback Sumit. Great question. So it all depends on the MQTT broker implementation. Some brokers create DBIRTH messages on behalf of all connected devices whenever a new application such as HMI comes online. Such that the HMI that has just connected receives that initial DBIRTH message and then starts to wait for event change as well.

[@michaeldowdell2005]

Great job!!

[@industry40tvonline]

Thanks for the feedback, Michael.

[@93GG93]

Great video! Where is the MQTT-broker located? Is it just a server hosted by hivemq? Can a MQTT-broker be a physical component located in a company and running as a server on its own? Or is it always provided by a company like hivemq?

[@industry40tvonline]

An MQTT broker can be hosted even on a device such as a Raspberry pi, or a company's on-prem server, and you can even host it in your own cloud-base VM. Thanks for your comment.

[@chickenz4604]

Very Informative Video Sir, btw I have a HMI that can be connected to MQTT. I plan to use MQTT to directly save data from hmi to PC, do you have tutorial video for that? Thank you very much

[@industry40tvonline]

Thank you for the feedback, Chickenz. What type of HMI are you using?

[@srh1034]

Excellent Video! Any chance to provide a demo in Python?

[@industry40tvonline]

Thank you for the feedback, Sr H. Yes, I'll actually be providing a Python demo in an upcoming video.

[@srh1034]

@@industry40tvonline Super exciting! Looking forward to seeing that video

[@blaisofotso3439]

Hallo . can you please explain what is Edge , edge of network node.

[@pranavthakkar6687]

Thanks Kudzai. Can we do this on Nodered?

[@industry40tvonline]

Thanks for watching, PranaV. Yes, you can absolutely do that with Node-Red. Check out examples on how to send and receive Sparkplug B Messages on this forum Sending - forums.opto22.com/t/sending-mqtt-sparkplug-b-control-messages-from-node-red/3478 Receiving - forums.opto22.com/t/decode-sparkplug-encoded-mqtt-messages-with-node-red/2315/6

[@dpdAL]

Isn't the broker setting up itself as a single point of failure? Is there a way we can implement redundancy?

[@industry40tvonline]

True the broker can be a single point of failure. You can employ a cluster of MQTT brokers installed on different machines acting as a single broker for redundancy.

[@dpdAL]

@@industry40tvonline so will I have to subscribe to 2 topics with 2 instances for each data point? Won't that just increase the engineering effort and complexity of the application?

[@industry40tvonline]

@@dpdAL no, you won't have to do multiple subscriptions. The multiple brokers will be acting as a single logical broker, when one goes down, your traffic is automatically routed to other instances. Setting that up is not even hard, one-touch provisioning with most broker providers.

[@dpdAL]

@@industry40tvonline thanks Kudzai... You should do a tutorial on it.

[@chadilac9]

@@industry40tvonline did you also say you can setup multiple brokers so that if a host fails you switch over to a different or redundant platform?