49
Get all subscriptions of the device
With this service the state of all registered events via subscribe service can be read by the host from the device.
Method: POST
URL:
Request body data:
{"
code
": "request", "
cid
": 9999, "
adr
":"getsubscriberlist",
"
reply
": "
reply text
",
}
Request
element
Value
Remark
code
"request"
-
cid
<Number>
CID must match to the cid of the subscribe event
e.g. 9999
adr
"getsubscriberlist"
-
reply
"reply text"
Optional: Text to be send back in the response.
If not needed, this element can be removed from
the request.
(1)
Please check, that the IoT Webserver is available under the IP address and the IP port is not blocked by the
firewall.
Reponse data:
{"
cid
":9999,"
data
":[{"adr":"DTE805AB-
0000001426/data/powersupply/datachanged","cid":int,"callbackurl":"http://192.168.0.79:34003/dte-powersupply-
state","duration":"lifetime",
"
adr
":"
reply text
","
code
":200}
Respons
e
element
Value
Remark
cid
<Number>
Correlation identifier.
Same as send in request.
e.g. 9999
data
{
"adr":"DTE805A…001426/data/powersupply/datachanged",
"cid":1012,
"callbackurl":"http://192.168.0.79:34003/dte-powersupply-state",
"duration":"lifetime"
}
adr: Service
cid of the subribed event
callback URL
duration of the event
(1)
adr
<string>
Optional.
Text sent in element "reply" of the
service request
e.g. "
reply text"
code
200
Response code of the IoT core
See chapter ->
(1)
Lifetime :
Value stored only till next power up of IoT Core
Once :
Value used only once, if request is
subscribe
, Process
UnSubscribe
after one notification
