Skip to content
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

Doubled Publication of MQTT Messages in different Formats with the same topic #2102

Open
paulau opened this issue Jan 23, 2025 · 1 comment

Comments

@paulau
Copy link

paulau commented Jan 23, 2025

Hallo,

We have a problem with our Installation of Frost. (It is the same installation as in my previous issue,
#2097 which was successfully closed).
It shold appear apparently in similar installations.

We submit the tasks for our Actuators, using mqtt:

mosquitto_pub -h localhost -p 1883 -u admin -P admin -t 'v1.1/TaskingCapabilities(1)/Tasks' -m '{"taskingParameters": {"target_temperature": 20}}' -i trtret

We expect, that clients do receive one message. Instead, they receive two messages:

v1.1/TaskingCapabilities(1)/Tasks {"taskingParameters": {"target_temperature": 20}}

v1.1/TaskingCapabilities(1)/Tasks {"@iot.selfLink":"http://localhost:8080/FROST-Server/v1.1/Tasks(18775)","@iot.id":18775,"creationTime":"2025-01-23T20:55:47.46Z","taskingParameters":{"target_temperature":20},"[email protected]":"http://localhost:8080/FROST-Server/v1.1/Tasks(18775)/TaskingCapability"}

Quite the same happens with MQTT Message to submit observations 'v1.1/Datastreams(1)/Observations'.
See points 3 and 4 of Issue #2097 . Clear identifiers should be changed to be different between subscriber and publisher.

It seems, that we should not really see the second message with the same topic. Schould the second message be for internal Frost needs and not to be published for external users/clients?

Thanks,
Greetings,
Pavel

@hylkevds
Copy link
Member

Duplicate of #128 and opengeospatial/sensorthings#5
This is how MQTT works. In Version 2 we will fix this by using a separate create topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants