Describe the bug
When I connect the AAS Repository with a MQTT Broker and I create/update/delete a submodel then the ID of the Submodel is not Base64 encoded.
To Reproduce
Steps to reproduce the behavior:
- Set up a basic AAS Environment and Mosquitto Broker
- Connect the environment with thhe mqtt broker
- Create new AAS with a submodel
Expected behavior
The ID of the Submodel should be Base64 encoded.
BaSyx (please complete the following information):
- BaSyx Version v2.0 -> Docker Image: eclipsebasyx/aas-environment:2.0.0-SNAPSHOT
- BaSyx SDK Java
- AAS Version DotAAS V3
Screenshots
If applicable, add screenshots to help explain your problem.
Used Asset Administration files (.aasx/.json/.xml)
Please drop your AAS files here that were used when the bug was encountered.
BaSyx configuration
apiVersion: v1
kind: ConfigMap
metadata:
name: aasenvironment-configmap
data:
BASYX_BACKEND: InMemory
SPRING_SERVLET_MULTIPART_MAX_FILE_SIZE: 100MB
SPRING_SERVLET_MULTIPART_MAX_REQUEST_SIZE: 100MB
BASYX_ENVIRONMENT: file:aas
BASYX_CORS_ALLOWED_ORIGINS: "*"
BASYX_CORS_ALLOWED_METHODS: GET,POST,PATCH,DELETE,PUT,OPTIONS,HEAD
BASYX_AASREPOSITORY_FEATURE_REGISTRYINTEGRATION: "http://aasregistry-service.aas-registry:8080"
BASYX_EXTERNALURL: "https://my-aas.aas"
BASYX_FEATURE_MQTT_ENABLED: "true"
MQTT_CLIENTID: "Abatement"
MQTT_HOSTNAME: "mosquitto-service.aas-environemnt"
MQTT_PORT: "1883"
System (please complete the following information):
- OS: Talos Kubernetes
- CPU architecture: amd64
- Browser Firefox
- Version latest
Additional context
A screenshot from my MQTT Viewer.

Describe the bug
When I connect the AAS Repository with a MQTT Broker and I create/update/delete a submodel then the ID of the Submodel is not Base64 encoded.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The ID of the Submodel should be Base64 encoded.
BaSyx (please complete the following information):
Screenshots
If applicable, add screenshots to help explain your problem.
Used Asset Administration files (.aasx/.json/.xml)
Please drop your AAS files here that were used when the bug was encountered.
BaSyx configuration
System (please complete the following information):
Additional context
A screenshot from my MQTT Viewer.