-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: TimeSeries submodel data (from MQTT and InfluxDB) does not display after uploading the shell on Basxy Web UI #95
Comments
Hi @SUpadhyay07, please try the actual newest version which would be |
Hi @aaronzi |
What are you using as 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. |
Hi @aaronzi For the attribute I attempted to resolve this by renaming the attribute name in the Expected BehaviorThe QuestionHow should I proceed to handle this situation where multiple MQTT topics are coming with the same Any guidance or examples would be greatly appreciated! |
Hi @SUpadhyay07, is it not fetching the data from influxdb or is the AAS web UI just not able to map it correctly?
It just checks if the record from the metadata collection is in the header of the data coming from influxdb. For example, 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). |
Hi @aaronzi Here are the details regarding my AAS Shell creation:
For example:
I can confirm that the data is successfully visible in InfluxDB (http://localhost:8086/). However, the data is not appearing in the AAS Web UI. Currently, I am using a single bucket in InfluxDB, which handles data from multiple machines, each having multiple temperature sensors. I suspect the issue lies here, as the data might not be uniquely identified. As a workaround, I am considering implementing a Python script to process and republish the topics into InfluxDB with unique names for each sensor, ensuring they can be easily identified. What are your thoughts on this approach? Do you think this is the right solution, or is there a better alternative? |
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:
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)
The text was updated successfully, but these errors were encountered: