AVEVA™ Data Hub Feedback Portal

Welcome to our new 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 Data Hub. For links to our other feedback portals, please see RESOURCES below.

Add a new idea Subscribe
Status Tell us more
Product PI Adapters
Categories AVEVA Adapter for MQTT
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

Enable Auto Discovery for PI Adapter for MQTT SparkplugB to always listen for Birth and Death messages

When utilizing the SparkplugB protocol for MQTT, it would be beneficial for the adapter to be always listening for birth and death messages from specific Edge of Network nodes. This way, the device can send a birth message to have itself added to the data selection array, then a death message to have itself removed. This would enforce a data selection array that's always reflecting the current state of devices connected to the broker, doesn't miss any data messages, and doesn't bloat over time.
  • ADMIN RESPONSE
    Aug 16, 2022
    We would like to collect more use cases for this feature. Please share in the comments section.
  • Attach files
  • Guest
    Reply
    |     Aug 16, 2022
    We've been using the PI Connector for a while before switching over to Adaptor, and this is one of the most critical features missing from the Adaptor, that is currently only available with the Collector. It should be possible to define an "autoAddTopicFilters" array, where metrics that satisfies the filter will automatically be added to the data selection array. Today we have to manually open Postman, find our internal instructions on how the JSON format for a discovery looks like, and start a discovery. This whole manual process is tedious, adds a lot of extra work for us, and is completely unnecessary. If the "autoAddTopicFilters" array was implemented, then new tags, would automatically be available in PI as soon as we make changes or add/remove metrics from one of our EoN nodes. The fact that no configuration would be required after the Adaptor has initially been setup, would save us a good amount of manual work. The idea to remove tags that are no longer available in the EoN would make the solution even better (maybe mark the tag OFF SCAN?) as it gives us an overview of which metrics are currently available from the EoN.