Stuck with what's happening with MQTT topics

[Trying_to_learn]

Folks, I'm stuck.

The story:

I have MQTT and use it to move messages between machines.

One of which is my Public_IP address.

Yet, if I run MQTT Explorer it says that topic is empty.

Strange as it is published to that topic.

See piccies.
(Follow red line for how it gets published.)

You can see the value it it goes to an MQTT out node.

The node's config:

MQTT Explorer's take on things.

See how it is EMPTY.

I test it from a CLI and it doesn't get set there either.

Where's the elephant I'm not seeing?

Just to make sure I'm not going nuts, I tested it with a whole new topic.

I also checked ALL my machines.
NO ONE ELSE is broadcasting on that topic.
ONLY THAT ONE MACHINE AND ONLY IN THAT ONE PLACE.

UPDATE:

Even more weird.

I set the IP address to 1.1.1.1 - just for the fun of it.
It is acknowledged in the MQTT in node.

And you can see the IP address in MQTT Explorer

But if I set it back to what it REALLY is - partly hidden but anyway.....

You can sort of see the real IP address. Anyway, I enter it and broadcast it from the CLI.
You can see how it is sent/received by the MQTT in node - as before.

But MQTT Explorer goes back to showing only {}

[Trying_to_learn]

Ah, seems I am running an OLD (discontinued) version.

Can't find an update at the SNAP site.

Sorry folks.

(If you can help me get a newer one.)
Ubuntu 22.04 LTS

[Colin]

@Trying_to_learn

I am running an OLD (discontinued) version.

Of what ?

[Colin]

If you mean mqttExplorer then I am running the snap version latest/stable 0.4.0-beta4 on Ubuntu 24.04 and I have seen no issues.

[TotallyInformation]

@Colin

0.4.0-beta4

I believe that IS the latest. Thomas long ago moved on from the project I believe and it is no longer being developed.

One day I may have the time to complete my Node-RED version of something similar!

---

Scrub that, there is a "beta6" version. But it only lists a single change of little seeming consequence.

[Colin]

@TotallyInformation

there is a "beta6" version.

That is also available as a snap, in the latest/beta channel.

[Colin]

@TotallyInformation

One day I may have the time to complete my Node-RED version of something similar!

Yes please!

[Trying_to_learn]

Could you elaborate on how I get it?

If/when I go to SNAP all I see is the existing version I have listed.

[Trying_to_learn]

@Colin

If you mean mqttExplorer then I am running the snap version latest/stable 0.4.0-beta4 on Ubuntu 24.04 and I have seen no issues

Indulge me then.

Get your public IP address and broadcast it to a topic. (Say Public_IP) and look at what MQTT Explorer says is in the channel.

[TotallyInformation]

@Colin

Yes please!

Yes, well, rather a lot going on just now and I'm afraid this has dropped down the priority list somewhat. I see how inspired I feel.

Right now, I've FINALLY gotten round to trying to document setting up Cloudflare Zero Trust to use with Node-RED and UIBUILDER. Long overdue.

[Colin]

It isn't to do with one's IP it is only specific IPs that give the problem. When one publishes "58.169.129.172" to a topic (any topic) mqttexplorer shows {}. I think a clue is that if you click on the value and look in the right hand side it says Decoded SparkplugB

See MQTT-Explorer 0.4.0-beta4 SparkplugB decode some strings as "{}" · Issue #792 · thomasnordquist/MQTT-Explorer · GitHub

It is fixed in the edge version which you can get by running
sudo snap refresh --edge mqtt-explorer

[Trying_to_learn]

Thanks.

Did command and that Fixed it.