Impinj IoT Device Interface Release Notes, version 1.7
This document describes the changes to the Impinj IoT Device Interface as of version 1.7, which corresponds with the 8.1 version of the overall reader firmware.
Changes are relative to the previous release, which was the version 1.6 release that corresponded to the 8.0 version of the overall reader firmware.
Breaking Changes
There are no breaking changes in this release. The base API URL is still
api/v1
.
Additions
- Security improvements
- New
digest
option for HTTP/HTTPS authentication, to supplement the existingnone
andbasic
options. Set through the new/system/access/authentication
endpoint. - Ability to specify reader users and passwords through the following
API endpoints:
/system/access/users
/system/access/users/{userId}/password
- Added multiple endpoints and data types to manage CAP certificates on
the reader, all under
/system/certificates/cap/certs/
.
- New
- Reporting improvements
- New optional
AntennaActivationEvent
that can be sent after successfully ramping up power on an antenna and just before starting an inventory micro-cyle. - New optional
xpcHex
field, for tags that support XPC (eXtended Protocol Control) words.
- New optional
- Data egress improvements
- Optional customization of the
keepAliveIntervalSeconds
in theStreamConfiguration
parameter, for HTTP/S streaming output. The default value is still 30 seconds. - LWT (Last Will and Testament) changes to match industry best practices.
The new default message for the
willMessage
is "connection lost" for ungraceful disconnections, and the message will only be sent if thewillTopic
is set. Also added the optionalconnectMessage
(for the initial connection and and reconnections) and optionaldisconnectMessage
(for graceful disconnections from the broker). The default QoS (Quality of Service) level is now 1.
- Optional customization of the
- RFID improvements
- Added a new EPC filter verification type,
passive
, which verifies that backscattered EPCs match configured filters before passing them on. Thepassive
operation uses information already available to the reader, so it does not require additional tag singulation over the air. It is the new default value. Note that thepassive
mode is not compatible with the TruncatedReply features, as it needs the full EPC to verify the filter.
- Added a new EPC filter verification type,
- Schema clean-up
- Increased the minimum length of a DNS SearchDomain from 1 character to 2.
- Associated the
SavedPresetBadRequest
response with theErrorResponse
parameter, like other error response values.
Deprecations
No endpoints were deprecated in this release.
Removals
No endpoints were removed in this release.