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
See the discussion thread "Commands using the HTTP adapter" in the mailing list:
We need to define and implement a mechanism for applications to notify protocol adapters that there is "no command currently available".
This especially targets protocol adapters where devices are usually not permanently connected, but that behave like HTTP with a request-response pattern.
Excerpt from the mailing list discussion: we want to only use this in a protocol adapter, if it was enabled for it at a tenant level. By default, this should just be ignored.
The text was updated successfully, but these errors were encountered:
See the discussion thread "Commands using the HTTP adapter" in the mailing list:
We need to define and implement a mechanism for applications to notify protocol adapters that there is "no command currently available".
This especially targets protocol adapters where devices are usually not permanently connected, but that behave like HTTP with a request-response pattern.
Excerpt from the mailing list discussion: we want to only use this in a protocol adapter, if it was enabled for it at a tenant level. By default, this should just be ignored.
The text was updated successfully, but these errors were encountered: