We put everything you need to know about MQTT and MQTT 5, the basic concepts, features and facts, into one comprehensive E-Book. You may download it here bit.ly/3XsgQK5
How is it used the LastWillQos? For example in case the LastWillQos is 2, and all the subscriber for the lastWillTopic use 1 as Qos, what will be the Qos used by the broker to send the message to the subscribers? I think that it will use the LastWillQos, otherwise it doesn't make sense to specify it as part of the CONNECT message
A subscriber defines the maximum QoS it supports. So if a subscriber subscribes with QoS 1 but the original publish (in your example via a LWT publish issued by the broker) would be QoS2, the subscriber would still get it with QoS 1. Not all subscribers support all QoS levels and this ensures that each subscriber gets the messages with QoS levels they support
If we retain online it will show the device as online even if it isn't atm. It will only publish offline once the device disconnects ungracefully. Shouldn't this be avoided?
Thank you for your feedback! Could you please submit your question to community.hivemq.com? One of our team members will be able to help you out there.
We put everything you need to know about MQTT and MQTT 5, the basic concepts, features and facts, into one comprehensive E-Book. You may download it here bit.ly/3XsgQK5
Thank you, this is good info to get started with MQTT.
Glad you liked it
Excellent video series. Thanks!
Thank you. Glad you like it and it's useful to you!
Thanks for the help professor! Really good and short mini-course! :)
Really well explained, thank you !
Glad it was useful to you, Grzegorz. Thank you!
How is it used the LastWillQos? For example in case the LastWillQos is 2, and all the subscriber for the lastWillTopic use 1 as Qos, what will be the Qos used by the broker to send the message to the subscribers? I think that it will use the LastWillQos, otherwise it doesn't make sense to specify it as part of the CONNECT message
A subscriber defines the maximum QoS it supports. So if a subscriber subscribes with QoS 1 but the original publish (in your example via a LWT publish issued by the broker) would be QoS2, the subscriber would still get it with QoS 1. Not all subscribers support all QoS levels and this ensures that each subscriber gets the messages with QoS levels they support
@@DominikObermaier thanks a lot for your answer, it makes perfect sense. I haven't considered that not all subscribers could support all QoS levels.
Thanks you 👌
Welcome 😊
If we retain online it will show the device as online even if it isn't atm. It will only publish offline once the device disconnects ungracefully. Shouldn't this be avoided?
Thank you for your feedback! Could you please submit your question to community.hivemq.com? One of our team members will be able to help you out there.