NOTE: From firmware 2.0, the output of the RESTful API to obtain gateway configuration
from AC will be changed (GET http://{your AC domain}/api/cassia/info?mac= <hubmac>).
The container status will be removed from the default API output, to avoid the oversized
UDP packets problem. Container status can be got separately by the same API with the
additional parameter ‘fields=container’. Please refer to SDK WIKI for details.
NOTE: Room-based and triangle-based location tracking APIs and gateway auto-selection
APIs lead to increased gateway traffic (high 4G cost) and increased CPU consumption. It is
recommended to only enable “BT Positioning” and “Gateway Auto-Selection” on the AC
setting page when needed. What is more, after upgrading AC from version 1.4.3 to version
2.0.2 and above, please double check if the “Gateway Auto-Selection” in AC setting page is
still OFF.
NOTE: From v2.1.0, if the end-user’s HTTP Restful API request contains “Accept-Encoding: *”,
the gateway will use gzip to compress the content of the HTTP response. It will reduce the
traffic between the gateway and AC. It will also accelerate the HTTP response. If the HTTP
request doesn’t contain Accept-Encoding, the gateway will not compress the HTTP response
(legacy behavior).
NOTE: From v2.1.0, in return message of scan API through AC, parameter name (‘event
type’) has been changed from ‘evt_type’ to ‘evtType’. This is to keep consistent with local API
in which ‘evtType’ is used. For example,
{"bdaddrs":[{"bdaddr":"E1:D2:F8:F9:82:E0","bdaddrType":"random"}],"adData":"020100000
00000000000000000","name":"(unknown)","rssi":-29,"evtType":0}
For details on Cassia RESTful API guidelines, please check the Github wiki site:
https://github.com/CassiaNetworks/CassiaSDKGuide/wiki.
To Next Page
Loading...
