BUG: TimeSeries submodel data (from MQTT and InfluxDB) does not display after uploading the shell on Basxy Web UI

[SUpadhyay07]

Description:
In the latest AAS Web UI (v2-240801), my TimeSeries submodel data (from MQTT and visible in InfluxDB) doesn't display after uploading the shell. This works fine in the previous version (v2-240327). However, two other submodels (Nameplate and Document) work in the latest version but not in the previous one. I need all submodels to function in a single version i.e. the latest version.

Versions:
Latest: eclipsebasyx/aas-gui:v2-240801
Previous: eclipsebasyx/aas-gui:v2-240327
Please let me know if further details are needed.

Attachments:

1. Previous: eclipsebasyx/aas-gui:v2-240327 --- Data visible but selecting multiple attributes shows only one.
2. InfluxDB: Data available, expected to display in Latest: eclipsebasyx/aas-gui:v2-240801 -- With all the attributes
3. Latest: eclipsebasyx/aas-gui:v2-240801 --- TimeSeries data not fetched from InfluxDB.

This issue is urgent. Please provide suggestions on why multiple attributes are not displaying in aas-gui:v2-240327, and let me know when I can expect a bug fix in the latest version(eclipsebasyx/aas-gui:v2-240801)

[aaronzi]

Hi @SUpadhyay07,

please try the actual newest version which would be eclipsebasyx/aas-gui:v2-241006. If this version causes problems as well, please notify us here.

[SUpadhyay07]

Hi @aaronzi
Thank you for the quick response.
I attempted this with the updated web UI(eclipsebasyx/aas-gui:v2-241006), but I'm encountering an authorization error related to the linked segment in the InfluxDB Docker container. I've attached a screenshot of the error. Below is my query for the linked segment:.
from(bucket: "basyx")
|> range(start: -60s)
|> filter(fn: (r) => r["_measurement"] == "cpu_load")
|> filter(fn: (r) => r["_field"] == "Value")
|> filter(fn: (r) => r["host"] == "basyx_host")
|> filter(fn: (r) => r["topic"] == "machine/SI0559/ipc/cpu/load")
|> yield(name: "mean")

[aaronzi]

What are you using as endpoint in the LinkedSegment? My guess is that the orgId does not match the one of influxDB. But if you are using influxDB in the config provided in the Time Series Data Example from BaSyx, you can change the endpoint to this:

http://localhost:8086/api/v2/query?org=basyx

Here, the org name is used instead of the id. This has the benefit of not being changed automatically after restarting the Docker containers.

[SUpadhyay07]

Hi @aaronzi
Thanks for your feedback earlier. I was using the organization ID previously. However, I am now facing a new challenge.

For the attribute temperature, I have multiple subtopics. In the metadata of the submodel, I have specified temperature. However, from MQTT, there are multiple topics coming with the temperature attribute.

I attempted to resolve this by renaming the attribute name in the docker-compose file of Telegraf and in the metadata as well, but it is still not fetching the data from influx for temperature rest it is showing the data.

Expected Behavior

The temperature data from multiple MQTT topics should be properly mapped.

Question

How should I proceed to handle this situation where multiple MQTT topics are coming with the same temperature attribute? Is there a specific configuration or mapping that needs to be adjusted in the metadata or Telegraf setup?

Any guidance or examples would be greatly appreciated!

[aaronzi]

Hi @SUpadhyay07,

is it not fetching the data from influxdb or is the AAS web UI just not able to map it correctly?
I can imagine that this line might cause some problems:

basyx-aas-web-ui/aas-web-ui/src/components/Plugins/Submodels/TimeSeriesData.vue

Line 546 in 118b694

this.yVariables.some((yVar) => key.includes(yVar.idShort))

It just checks if the record from the metadata collection is in the header of the data coming from influxdb. For example, temperature could match topic1/temperature but also topic2/temperature. It's best to avoid such scenarios for now, either by naming the records in the metadata more precisely, or by avoiding duplicates in subtopics in mqtt.

Have you checked if the data is being transferred to influxdb at all using telegraf? Please also check using the influx frontend (http://localhost:8086).