61
Receive UID from HF ID tag automatically
Service available
: DTE105, DTE605
This service is supported in the channel mode "RWH"
Method: POST
URL:
Request body data:
{"
code
":"request","
cid
":1010,"
adr
":"data/port[1]/rfid/id_tag/uid/datachanged/subscribe","
reply
":"
reply
text
","
data
":{"callback":"http://192.168.1.1:34003/io1-uid-nw"}}
Request
element
Value
Remark
code
"request"
-
cid
<CorrID>
Correlation identifier.
Multiple subscriptions from one source
are allowed, but each will need a unique
"cid". e.g. 1010
adr
"data/port[
N
]/rfid/id_tag/uid/datachanged/subscribe"
For DTE10x :
N
=1…4
For DTE60x, DTE80x, DTE9Xx:
N
= 1
e.g. 1
reply
"<string>"
Optional:
Text to be send back in the response.
If not needed, this element can be
removed from the request.
e.g. "reply text"
data
{ "callback": "http://<
ip address
>:<
Port
>/<
Event
>"}
Data of the IoT Webserver
(1)
:
IP address
: IP address
e.g. 192.168.1.1
Port
:
Port number.
e.g. 34003
Event
:
Name of the event. Can
be set freely by the
User.
e.g. io1-uid-nw
(1)
Please check, that the IoT Webserver is available under the IP address and the ip port is not blocked by the
firewall.
Response data:
{"
cid
":1010,"
adr
":"
reply text
","
code
":200}
Response
element
Value
Remark
cid
<CorrID>
Correlation identifier. Same as send in request, e.g. 1010
adr
<string>
Optional.
Text sent in element "reply" of the service request
e.g. "
reply text"
code
<status code>
Response code of the IoT core
See chapter ->
e.g. 200
