eclipse-basyx / basyx-java-server-sdk

MIT License
49 stars 42 forks source link

No MQTT Events send when changing MLPs #299

Open de-ich opened 1 month ago

de-ich commented 1 month ago

Hello,

I was testing the MQTT event feature of the submodel repository. MQTT events for changed "Property" elements work just fine. However, changing values of "MultiLanguageProperty" elements (or adding/removing of languages) do not seem to lead to an MQTT event.

I used the following setup:

Best regards Matthias

mdanish98 commented 1 month ago

Hi @de-ich ,

Thanks for raising this issue.

Would it be possible for you to share the configurations you used in this? like application.properties etc

de-ich commented 1 month ago

Sure. I use the following configuration files (note that I needed to add 'txt' file ending due to upload limitations of Github):

docker-compose.yml.txt aas-env.properties.txt aas-registry.yml.txt sm-registry.yml.txt mosquitto.conf.txt

aaronzi commented 1 month ago

Thanks for sharing your configurations. I see that you are using the SNAPSHOT images for BaSyx. Can you please check from when these images are? We update these images regularly, but the tag name remains the same. So if you have used BaSyx in the past, these images might be out of date. I switched to the milestone release of BaSyx to eliminate this possibility of having an outdated image. Here is a complete setup for reproduction:

MQTT-Issue.zip

Now to your issue:

Updating MLPs via the UI does not work right now. Were you able to update the MLPs in the submodel repo at all? Please check if that works. I would say that the event isn't triggered because the MLP does not get updated in the repo.

aaronzi commented 1 month ago

Some additional info:

There was a bug when updating SubmodelElements (including MLPs). This bug has just been fixed as part of this PR: #280 I think this fix is not in the latest version of the snapshot images yet. Therefore the BaSyx backend components do not support updating MLPs yet. The next release on Docker Hub should resolve this.

aaronzi commented 6 days ago

Update: Since updating an MLP currently uses PUT-Requests this issue is the same as #300. Therefore please take a look at the latest comment there.