You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no good solution here at the moment. The following scenarios are possible:
Consumer subscribes and by chance the Thing publishes a new value
Consumer subscribes and gets a value that is published some time ago with retain. The issue is how to give the timestamp of the published payload to the application level. The message can be very old
The request-response mechanism is implemented in all sides where the Consumer forces the Thing to publish to a topic given by the Consumer.
There are issues in the specification level to solve this.
I apologize for the inconvenience, but I need your confirmation on the following issues.
Problem
There is no response when I call readProperty on MQTT Binding.
A sample program is placed below.
https://github.com/hidetak/test-node-wot/tree/main/no-response-mqtt-read-property
Also, if observeProperty is executed and then writeProperty is executed, the written value can be retrieved, but sometimes it is retrieved twice.
environment
Steps to reproduce
get the following code
https://github.com/hidetak/test-node-wot/tree/main/no-response-mqtt-read-property
When executed, the following string is output.
Expectations are as follows.
Sometimes
observed count value is: 100
is output twiceI apologize if there is a problem with my usage.
The text was updated successfully, but these errors were encountered: