Skip to main content
4-Participant
March 30, 2025
Question

Kepware IOT Gateway and UNS

  • March 30, 2025
  • 1 reply
  • 813 views

At the moment Kepserver is only able to publish it's data to a MQTT broker as a json string. Because og this I need an extra software tool to split tags into topics and republish them into a UNS.

I need Kepserver to be able to publish each tag on a separate topic for example corresponding to the structure of the tag groups in Kep. Is thes a part of Kepware's reoadmap?

 

 

1 reply

18-Opal
March 31, 2025

Hi, 

 

To look into this properly, could you clarify a few things:

  1. Which version of Kepware/KepServerEX are you using or referring to?

  2. Are you looking for official roadmap information from PTC/Kepware?

  3. Do you want alternative tools or middleware to help you split and republish MQTT messages into UNS-compliant format?

Thanks,

4-Participant
April 1, 2025

hI,

 

1.. Currently running 6.15.132, but I think the issue is the same in the latest release

2. Yes

3. I use Node Red to do this today, I I think It's imortant to things like this as close as possible to the edge ==> Kep...

 

 

Kind regards

 

18-Opal
October 21, 2025

Hi @TT_12004561 ,

 

Thanks for the details.

Currently, Kepware’s IoT Gateway publishes data to MQTT brokers as JSON payloads, but it does not natively support publishing each tag as an individual topic or in UNS (Unified Namespace) structure. The MQTT client in Kepware is designed primarily for bulk data publishing, which means the payload structure is not tag-level configurable.

At this time, this feature (direct UNS-compliant topic publishing) is not part of the released Kepware roadmap. However, PTC is aware of the increasing adoption of UNS models, and this capability is under internal discussion for future releases.

For now, you have two main approaches:

  1. Continue using Node-RED or a lightweight middleware (like HiveMQ Edge or MQTT Sparkplug gateways) to parse and republish the JSON payloads into topic-based UNS format.

  2. Use ThingWorx Edge MicroServer (EMS) if you’re already within the ThingWorx ecosystem — it allows more flexible mapping of tags to MQTT topics.

Thanks,