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

[MQTT]: Retain true for properties #83

Open
egekorkan opened this issue Dec 12, 2019 · 0 comments
Open

[MQTT]: Retain true for properties #83

egekorkan opened this issue Dec 12, 2019 · 0 comments
Labels
Has Use Case Potential The use case can be extracted and explained mqtt related to mqtt protocol binding Needs discussion Selected for Use Case

Comments

@egekorkan
Copy link
Contributor

egekorkan commented Dec 12, 2019

For a topic that Exposed Thing publishes to, what does it mean to have to retain flag information in the forms?
Let's say we have the following form for a property:

{
  "href": "mqtt://example.com/example/light/currentswitch",
  "op": ["observeproperty"],
  "mqv:controlPacketValue": "SUBSCRIBE",
  "mqv:options": [ { "mqv:optionName": "retain", "mqv:optionValue": 1 }]
}

So this should mean that an MQTT subscriber should subscribe to this topic in order to observe a property. Should the subscriber ignore the last line since it is not something it should do, i.e. the publisher publishes with retain flag set to true so that the last value of the property is in the topic. OR can the publisher use this last line to give a hint that it publishes with retain set to true, so the subscriber should understand that it will get the last value of the property upon subscription, i.e. do a readproperty.
My answer would be that if the publisher publishes with retain set to true, there should not be this line and there must a readproperty op value. Thus, there would be some information (publisher publishing with retain set to true) not visible in the TD. This also implies a change to the editor's draft.

@egekorkan egekorkan added the mqtt related to mqtt protocol binding label Jul 14, 2021
@egekorkan egekorkan added Has Use Case Potential The use case can be extracted and explained Selected for Use Case labels Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Has Use Case Potential The use case can be extracted and explained mqtt related to mqtt protocol binding Needs discussion Selected for Use Case
Projects
None yet
Development

No branches or pull requests

1 participant