Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status Tell us more
Created by Guest
Created on Aug 16, 2022

Allow PI Adapter for MQTT (Generic) to process non-json payloads

Some MQTT devices do not send json payloads; for example, some devices send a single value as the payload for a specific topic. It would be beneficial for the adapter to be able to handle this rather than to convert these payloads into json before they get to the adapter.
  • ADMIN RESPONSE
    Aug 16, 2022
    We would like to know more about the frequency in which our customers come across this scenario. Please share your use cases in the comments section.
  • Attach files
  • Zahab Nabeel
    Reply
    |
    Oct 8, 2024

    Spent 6 hours on a project where we needed data from a solar panel that was accessed through MQTT Adapter in the form of numerical values. We succeeded easily with integration with AVEVA Historian using the MQTT however kept failing with PI Adapter due to inability to find the items. After so much efforts and time spent we came across this enhancement request and figured we do not even support it. I hope it would be added soon just as it is already available and easily configurable with AVEVA Historian.

  • Guest
    Reply
    |
    Aug 16, 2022
    In this use case the PI Adapter was proposed but devices are already in place and publishing raw data payloads to the MQTT broker so it is not feasible to change the data to JSON or Sparkplug. Workarounds to convert the data to Sparkplug increases the effort needs, and the costs involved.