I just tested the same scenario using MQTT.fx and it works as you described: freshly received retained messages are not understood to be retained. It’s only available upon subscribing to the topic.
That’s interesting. What else does the broker not share with a client after it has already connected and subscribed? For example, if a message is published with a different level of QOS, will the new level be available to MQTT Explorer? Or is like retain and only available upon subscribing to the topic?
I believe the thought is that a client can distinguish live events from possibly old and outdated events.
Retained topics might for instance no longer be relevant, and therefore it is useful to make the distinction.
Fix unrounded time intervals in the message history
Fix weird plot curve interpolations
Finally: @stevemann I am not entirely certain where the Microsoft Store puts its applications, but I do not believe you’ll find a simple .exe (rather an .appx). You should probably use the installer or portable version from mqtt-explorer.com, the installer will give you a link on your desktop and installs the app in the default “program files” directory.
I love this app! Silly question but can this be run as a Hass.io add-on instead of it being a separate app? I don’t always use the same computer to access my instance and would be nice to avoid the faff of opening another app. For those who access their instances remotely it would be nice to be able to use MQTT Explorer remotely as well.
MQTT Explorer is an MQTT client, just like Home Assistant is an MQTT client, but it presents MQTT topics, and their messages, in a detailed and efficient manner (using a tree-view) thereby making it a very useful tool for debugging MQTT problems. It serves as an independent means of examining what’s happening on your MQTT Broker.
The nature of these questions suggest to me that you do not understand the fundamentals of MQTT. I recommend you follow this excellent tutorial series (it’s what I used to learn about MQTT):
.