iD Cloud EAS Read Mode
What is this read mode?
This read mode is a reskin of the HTTP EAS read mode but instead of getting EPC sold status from an user-defined HTTP server it targets Nedap's iD Cloud to retrieve the read EPC disposition and trigger, or not, an alarm.
This mode is not included by default in our devices. If you need it for an existing device, please contact support if you did not tell sales when placing an order.
Configuration options
These 3 are the only parameters to configure with this read mode:
Client Id: Username for your Nedap account, please see the value placeholder to check what format should this Id take
Client Secret: the nedap account password, it should be in the format of a 64 character long string of hex characters: 0-9a-f
Location isn't mandatory, but it should match the full url of the store id in iD Cloud
Important note: The user account should have enough permissions to query iD Cloud's /rfid_stock/v1/epc_state API call, otherwise it won't work. Contact Nedap support if you aren't sure if you have the needed permissions.
Important note #2: iD Cloud is unable to process tags not encoded in SGTIN-96 codification so it's imperative that all tags that must be protected must be encoded in SGTIN-96 or the Alarm will never be triggered on them.
The dispositions that will trigger the alarm are: sellable_accessible and sellable_not_accessble. All others won't trigger an alarm.
Customizations
A client asked us to add an extra filter for Hard Tags that were not codified in SGTIN-96 so they bypass iD Cloud validation and trigger an alarm right away.
The three values of Mask offset, Filter mask and Mask length work the same way as the EPCGen2 filter however for obvious reasons they don't feature the hwmask functionality, otherwise all options found here work.
Critical Note: It's crucial to put some kind of filter here otherwise all tags will trigger an alarm
Advanced Configuration
Please refer to the HTTP EAS read mode for the rest of the settings.