# Stuck with what's happening with MQTT topics

**URL:** <https://discourse.nodered.org/t/stuck-with-whats-happening-with-mqtt-topics/99714>\
**Category:** General\
**Created:** [19 November 2025 03:07 UTC](https://discourse.nodered.org/t/stuck-with-whats-happening-with-mqtt-topics/99714 "2025-11-19T03:07:51Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [19 November 2025 21:54 UTC](https://discourse.nodered.org/t/stuck-with-whats-happening-with-mqtt-topics/99714/11 "2025-11-19T21:54:14Z")

</div>

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

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/c/5c868fc1fa81f54cef82882144214f006e3c294a.png)

See [MQTT-Explorer 0.4.0-beta4 SparkplugB decode some strings as "{}" · Issue #792 · thomasnordquist/MQTT-Explorer · GitHub](https://github.com/thomasnordquist/MQTT-Explorer/issues/792)

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

---

_[View the full topic](https://discourse.nodered.org/t/stuck-with-whats-happening-with-mqtt-topics/99714)._