Introduction
The LoRa API helps you to manage your LoRaWAN devices and application servers.
KPN’s Low Power Long Range (LoRa) network service complements existing 2G, 3G, 4G and LTE-M networks. It is based on the LoRaWAN protocol for Internet of Things (IoT). The network eliminates significant barriers (such as cost and energy consumption) so that numerous (battery-powered) devices can be connected.
KPN has equipped hundreds of existing mobile transmission towers across the Netherlands with a LoRaWAN gateway and antenna, achieving full coverage of the Netherlands and allowing millions of devices to be connected.
API specification
Base URL
https://api-prd.kpn.com/data/lora/thingpark
Conceptual model
Definitions
ABP
Activation by personalization. In some cases, you might need to hard code the device address (DevAddr
) as well as the security keys in the device.
ABP provisioning is no longer supported and not available in the API. Over-the-Air Activation (OTAA) is the standard.
Application routing profile
Configuration data in the LoRa network referencing the application server of the customer.
Application server
LoRa application server of the customer which is able to receive LoRa uplinks and initiate LoRa downlinks.
Device
A sensor or actuator implementing the LoRaWAN protocol stack. A device is identified by DevEUI, a globally unique IEEE EUI-64 identifier.
DevEUI
The DevEUI is a 64-bit globally-unique Extended Unique Identifier (EUI-64) assigned by the manufacturer, or the owner, of the end-device.
Device alarm
An occurrence out of the ordinary on a device logged by the LoRa network.
HSM group
HSM (High-Security Module). The data in the LoRa platform is protected by an HSM which stores root-keys for the encryption of the device-data. Within the platform, there may be multiple groups of HSMs, but currently only 1 group is present.
The HSM is mandatory for LoRa provisioning. Legacy interface version 1.1.1 can be used to provision a non-HSM device.
OTAA
Over-the-Air Activation. Devices perform a join-procedure with the network, during which a dynamic device address (DevAddr
) is assigned and security keys are negotiated with the device.
Thingpark GUI
The Thingpark GUI by Actility allows you manage your devices in an web GUI. You can also see the LoRa messages sent and received by their devices. You need you Thingpark credentials to use this API.
API workflows
Activate the LoRa API
After you created a project in the KPN API Store we have to match your Thingpark GUI user credentials with your KPN API Store user credentials. We call that 'activation'. You have to do it just once. After that, you can use the project by sending your requests with you KPN API Store access token.
You have to activate each new project because it has a new set of
client_id
andclient_secret
.
Retrieve LoRa subscription information
Before you provision a device or application routing profile, you can retrieve the available resources in the subscription:
- Connectivity plans: The available connectivity options provided by sales. Includes the number of messages per day and localization feature(s).
- Device profiles: Indicates the type of device. Typically used to optimize the motion indication (is it a static device or is it expected to be moving).
- HSM groups: Indication of available HSMs to be used. Currently, there is only 1 option. The hsmGroupId is needed while creating devices and application routing profiles.
LoRa application routing profile management
The application routing profile is used to configure the application server endpoint and is used and referenced by the LoRa device management in the next section. You will need at least 1 application routing profile pointing to your application server to be able to start creating devices.
LoRa device management
This workflow provisions the LoRa device into the KPN network. Before you can create a new device you need to know 3 important parameters:
Parameter | Description |
---|---|
Device EUI (DevEUI) |
Globally unique IEEE EUI-64 device identifier. |
Application EUI (AppEUI) |
Globally unique IEEE-64 identifying the LoraWAN join server. |
Application Key (AppKey) |
Root key of the device (16 bytes). |
LoRa device alarm management
You can retrieve and acknowledge device alarms by using this workflow.
Retrieve LoRa statistics
This workflow retrieves the frame (traffic) statistics and health statistics of the device(s).
Features
- LoRaWan application services mangement.
- LoRa device management.
- LoRa application routing profile management.
- LoRa device alarm management.
- LoRa statistics retrieval.
Getting started
Make sure you've read What's in it for you for more info on how to register and start testing APIs.
Authentication
The API follows the KPN Store API Authentication Standard to secure the API. It includes the use of OAuth 2.0 client_id
and client_secret
to receive an access token.
Go to the Authentication tab on top of this page to find out how to:
- Authenticate to an API using cURL.
- Authenticate to an API on Swaggerhub.
- Import Open API Specifications (OAS), also called Swagger files into Postman.
How to...
Activate the LoRa API
The following endpoint activates the LoRa API: POST /activate
.
Send your Thingpark GUI user credentials in the body of the request to authorize the API Store to make use of your LoRa instance for future LoRa API requests.
^^cURL request^^
{
POST 'https://api-prd.kpn.com/data/lora/thingpark/activate' \
--header 'Authorization: Bearer **' \
--header 'Content-Type: application/json' \
--data-raw '{
"thingpark_username":"**",
"thingpark_password":"**"
}
Body parameters
Parameter | Type | Description |
---|---|---|
thingpark_username |
string |
Your Thingpark GUI username. |
thingpark_password |
string |
Your Thingpark GUI password. |
Response
The expected response is 200 OK
.
Retrieve LoRa subscription information
The following request retrieves a list of connectivity plans: GET /connectivityPlans
.
^^Response example^^
[
{
"id": "kpn-acc-ope-cs/testing",
"ref": "608",
"name": "kpn-acc-ope Testing CP",
"grantedConnections": 10,
"usedConnections": 1,
"communicationType": "UNICAST"
},
{
"id": "kpn-acc-ope-cs/often-geo-2019",
"ref": "624",
"name": "Often Geo 2019eb",
"grantedConnections": 100000,
"usedConnections": 0,
"communicationType": "UNICAST"
}
]
Parameter | Type | Description |
---|---|---|
id |
string |
ID of the connectivity plan. |
ref |
string |
Reference of the connectivity plan. |
name |
string |
Name of the connectivity plan. |
grantedConnections |
integer |
Number of granted connections of the connectivity plan. |
usedConnections |
integer |
Number of used connections of the connectivity plan. |
communicationType |
string |
Communication type of connectivity plan: UNICAST , MULTICAST . |
Create an application routing profile
The following request creates a new routing profile: POST /routingProfiles
.
^^POST /routingProfiles^^
{
"name": "your-routing-profile-name",
"default": false,
"hsmGroupId": "HSM_KPN-OPE.1",
"rsaPublicKey": "-----BEGIN PUBLIC KEY-----MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAn0/KaJwVk7lyRMsGUKiYtnMp4kwo45+eaFB9NnYeZe/I5wnwQKC6goN9C1xQy38alc/rMyUbrhsyUmfYfZTPXSuMtveXS15KR2vZW+MGOeA9Bpr2X/N4dUyPTG6fpEAnIwSCeOor40oVXPPvl4bbOV1EdGm5QXWArl9nUDqmIzu0XzcM/VQVyhT7rHuAcIigXpNeUzGOBLmLFjuEqG2r/3VRW147L1tWr8mogyDv4uV+uHckD4ceIMds7jk9AgwVi4JdZv6nMg2wGX0IaVAnTghjgVmsU5k2azf01U0AWYHbwnEsnixnQhW4Rx71NmiKU2Fflhl/g5e8+ZjZhvCN7QIDAQAB-----END PUBLIC KEY-----",
"routes": [
{
"sourcePorts": "*",
"strategy": "SEQUENTIAL",
"contentType": "JSON",
"asId": "YOUR-AS-ID",
"asKey": "6dd70c8511e02ac833add9a146f5bf23",
"addresses": [
"https://your-application-server/path/"
]
}
]
}
Parameter | Type | Description |
---|---|---|
name |
string |
Name of the routing profile. |
default |
boolean |
Indicates if the routing profile should be used by default for new devices. |
hsmGroupId |
string |
HSM group ID which can be found from the retrieval of subscription data. |
rsaPublicKey |
integer |
Public key from the application server used to encrypt the Application Server Key (ASK). |
connectivityPlanId |
integer |
Connectivity plan ID which can be found from the retrieval of subscription data. |
asId |
string |
Application server identifier, used for authentication. |
asKey |
string |
Application server password, used for authentication (16 byte hexadecimal). |
addresses |
string |
List of HTTPS endpoint destination(s) of the application server. |
The response will echo the settings and includes some extra parameters:
Parameter | Type | Description |
---|---|---|
id |
string |
Identification in the LoRa network. |
ref |
boolean |
API reference for future requests (update/delete/retrieve). |
rsaEncryptedASKey |
string |
Application Server Key (ASK) encrypted with the public key in the request. The ASK is needed to encrypt/decrypt the LoRa payload by the application server. This field will be returned only once and cannot be retrieved from the platform after this call. Please store and protect this value well. |
^^Response example^^
{
"id": "TWA_100001135.2647",
"ref": "2647",
"name": "your-routing-profile-name",
"default": false,
"rsaEncryptedASKey": "8e4bda2fda868e536a821ee8930e8ceb3baaa22ea9588c5b220d61acf8678740496923c537aa551bdf13af815bbabb31ce66d3248b9489b7e19cc778b8aac787578b079778722c67908296d157ad21a1bb99eada4f7db48fd51a5276aecc621638d9c7aed50347e7546a13a07d97557413e8505f32d57edb2caaf63849558d01ad60c0c617bb6dcb4cd40e3b3ccff6bf2c50442c539337de01808725ac535ab3dccb77fe635015060984270bbe3d356644a7e8a6574fd726e165818ffb507b8ddfbbe9ce25692cbb69efeb0b024cd45d08e66f0d284bcbac1c56fe95744f3bae89920709ef27d19444f6559de16290da67e67ff85564c8f0cde9c3c4979608be",
"routes": [
{
"sourcePorts": "*",
"strategy": "SEQUENTIAL",
"contentType": "JSON",
"asId": "YOUR-AS-ID",
"addresses": [
"https://your-application-server/path/"
]
}
]
}
Create a device
The following request creates a new device: POST /devices
.
Please note:
- New devices should be provisioned as Over-the-Air Activation (
activationType
=OTAA
). - New devices should use HSM security (
hsmGroupId
field must contain a valid value). - If no
routingProfileId
orprocessingStrategyId
values are provided, thenprocessingStrategyId
will be automatically set toDATAFLOW
. - If no
connectivityPlanId
value is provided, then the first connectivity plan of the subscriber with available connections will be assigned to the device.
^^POST /devices^^
{
"name": "Test Device via API",
"EUI": "0059ac0000170311",
"activationType": "OTAA",
"deviceProfileId": "CUSTOM/Static V 1.0 Class A",
"hsmGroupId": "HSM_KPN-ACC-OPE.1",
"connectivityPlanId": "kpn-acc-ope-cs/often-geo-2019",
"routingProfileId": "TWA_100001135.861",
"applicationEUI": "0000000000000000",
"applicationKey": "00000000000000000000000000000000"
}
Parameter | Type | Description |
---|---|---|
name |
string |
Name of the device. |
EUI |
string |
Device EUI identification (8 bytes hexadecimal). |
activationType |
string |
Fixed value OTAA for Over-the-Air Activation. |
hsmGroupId |
string |
HSM group ID, which can be found from the retrieval of subscription data. Required . |
deviceProfileId |
string |
Device profile ID, which can be found from the retrieval of subscription data. |
connectivityPlanId |
string |
Connectivity plan ID which can be found from the retrieval of subscription data. |
routingProfileId |
string |
Routing profile ID of the application server. |
applicationEUI |
string |
AppEUI identifying the LoRaWAN join server (8 bytes hexadecimal). |
applicationKey |
string |
Device root key (16 bytes hexadecimal). |
The response will echo the settings and includes an extra parameter:
ref
: API reference for future requests (update/delete/retrieve).
^^Response example^^
{
"ref": "15532",
"name": "Test device",
"EUI": "0059ba0000000002",
"activationType": "OTAA",
"deviceProfileId": "CUSTOM/Static V 1.0 Class A",
"connectivityPlanId": "kpn-acc-ope-cs/often-geo-2019",
"routingProfileId": "TWA_100001135.2647",
"applicationEUI": "01234567890abcdef",
"hsmGroupId": "HSM_KPN-OPE.1"
}
Delete a device
The following request deletes a device: DELETE /devices/{deviceRef}
.
You have to pass the ref
parameter in the path of the request:
- Use the
ref
parameter that you saved when the device was created. - Use the
GET
method to retrieve theref
parameter again:GET /devices/{deviceRef}
Example path parameters
Parameter | Type | Description |
---|---|---|
deviceRef |
string (path) |
Reference of the device to be deleted. |
Retrieve LoRa device alarms
The following request retrieves a list of device alarms:
GET /deviceAlarms
Example request parameter
Parameter | Type | Description |
---|---|---|
deviceEUI |
string (query) |
EUI of the device to search alarms for. |
^^Response example^^
[
{
"ref": "5a6717531ffbe425b9c16bb6",
"alarmState": "MAJOR",
"occurrence": 1,
"acked": false,
"creationTime": "2018-01-23T11:06:59.073+00:00",
"lastUpdateTime": "2018-01-23T11:06:59.073+00:00",
"additionalInfo1": "SF12",
"additionalInfo2": "SF10",
"additionalInfo3": "13.000000dB",
"additionalInfo4": "-15.000000dB",
"deviceRef": "41201",
"deviceAlarmTypeId": 6
},
{
"ref": "5a6847972d3694372cad4fed",
"alarmState": "WARNING",
"occurrence": 9,
"acked": false,
"creationTime": "2018-01-24T08:45:11.742+00:00",
"lastUpdateTime": "2018-02-04T08:52:05.384+00:00",
"additionalInfo1": "20%",
"deviceRef": "32611",
"deviceAlarmTypeId": 1
}
]
Parameter | Type | Description |
---|---|---|
ref |
string |
Reference of the alarm. |
alarmState |
string |
State of the alarm. Possible values are, by ascending order of criticality: CLEARED , UNCLEARED , WARNING , MINOR , MAJOR and CRITICAL . |
occurrence |
integer($int32) |
Number of occurrences of the alarm. |
acked |
boolean |
Indicates if the alarm has been acknowledged. |
creationTime |
string |
ISO 8601 time of the alarm creation. |
lastUpdateTime |
string |
ISO 8601 time of the last alarm acknowledgement. |
additionalInfo1 |
string |
First additional information related to the alarm creation. Note: There can be more than 1 additional info. |
deviceRef |
string |
Reference of the device related to the alarm. |
deviceAlarmTypeId |
string |
ID of the device alarm type. Refer to the list of ThingPark device alarm types to get the corresponding label. |
Retrieve LoRa statistics
Get frame statistics for a device
The following request retrieves frame statistics of the devices corresponding to the provided parameters:
GET /deviceFrameStatistics
You have to pass certain parameters in the path of the request. See below:
Example path parameters
Parameter | Type | Description |
---|---|---|
deviceEUIList |
string |
List of device EUIs for which device statistics should be retrieved. |
baseStationId |
string |
ID of the base station which received the frame. |
startDate |
string |
Start date in ISO 8601 format of the period for which frame statistics should be retrieved. By default, only the last frame statistics resource is retrieved. |
duration |
integer($int32) |
Period (number of days) for which frame statistics should be retrieved. By default, the default duration is 7 days. |
aggregationStep |
integer($int32) |
Number of hours (between 1 and 24) used for aggregating the frame statistics. By default, all frame statistics are returned (no aggregation). |
^^Response example^^
[
{
"type": "UPLINK",
"date": "2020-01-31T13:00:00.000+00:00",
"frameCount": 2,
"payloadSize": 2,
"baseStationRSSI": -38.2,
"baseStationSNR": 2.6,
"payloadReceivedOnTime": 2,
"payloadReceivedLate": 0,
"payloadReceivedOnTimeSize": 2,
"payloadReceivedLateSize": 0,
"averagePER": 0.0
},
{
"type": "DOWNLINK",
"date": "2020-01-31T13:00:00.000+00:00",
"frameCount": 3,
"payloadSize": 0,
"payloadSentWithSuccess": 3,
"payloadSentWithSuccessSize": 0,
"payloadSentWithFailure": 0,
"payloadSentWithFailureSize": 0
}
]
Parameter | Type | Description |
---|---|---|
type |
string |
Type of frame. Possible values are UPLINK or DOWNLINK . |
date |
string |
SISO 8601 time of the frame emission/reception or time of the aggregated time slot. |
frameCount |
integer($int32) |
Number of uplink/downlink frames received or sent for this aggregated time slot. |
payloadSize |
integer($int32) |
Size of the frame payload or average size of payload associated to this aggregated time slot. |
baseStationRSSI |
number |
Received Signal Strength Indication (RSSI) for the base station that receives the frame. Only available in case of an uplink. |
baseStationSNR |
number |
Signal Noise Ratio (SNR) Indication for the base station that receives the frame. |
payloadReceivedOnTime |
integer($int32) |
Number of uplinks sent with no delay by the base station. Only available in case of an uplink. |
payloadReceivedLate |
integer($int32) |
Number of uplinks queued in the base station and sent with a delay. Only available in case of an uplink. |
payloadReceivedOnTimeSize |
integer($int32) |
Size of the accumulated uplink payloads sent with no delay by the base station. Only available in case of an uplink. |
payloadReceivedLateSize |
integer($int32) |
Size of the accumulated uplink payloads queued in the base station and sent with a delay. Only available in case of an uplink. |
Get health statistics for a device
The following request retrieves health statistics for all devices: GET /deviceHealthStatistics
.
^^Response example^^
{
"initCount": 11,
"activeCount": 55,
"rfConnectionErrorCount": 0,
"totalCount": 66
}
Parameter | Type | Description |
---|---|---|
initCount |
integer($int32) |
Number of devices with the healthState attribute set to INIT . |
activeCount |
integer($int32) |
Number of devices with the healthState attribute set to ACTIVE . |
rfConnectionErrorCount |
integer($int32) |
Number of devices with the healthState attribute set to RF_CNX_ERROR . |
totalCount |
integer($int32) |
Total number of devices in authorized scopes. |
Return codes
Code | Description |
---|---|
200 | Success. |
201 | Created. |
202 | Accepted. |
302 | Found. Link in location header. |
400 | Bad request. |
401 | Unauthorized. |
403 | Forbidden. |
404 | Not found. |
405 | Method not allowed. |
412 | Precondition failed. |
429 | Too many requests. |
500 | Internal server error. |
502 | Bad gateway. |
503 | Service unavailable. |
Application status message
The 4XX and 5XX status messages may contain additional application layer information. The Response may include an errorId
field which can be used for detailed analysis. The latest known errors are listed below under 'Error ID codes'.
^^Error response example^^
{
"code": 400,
"message": "Bad request: No ConnectivityPlan for ID: kpn-acc-ope-cs/often-geo-1919 and Operator: 24",
"errorId": "OSS-214"
}
Error ID codes
Code | Level | Message | Friendly message |
---|---|---|---|
1 | Invalid query parameter: %s. | ||
2 | Invalid document: %s. | ||
3 | Permission denied, not authorized to perform the operation. | ||
4 | INFO | Access denied, user not logging or session expired. | For security reasons, your session has expired due to inactivity. Please log in again. |
5 | Unsupported media type: %s. | ||
6 | Unexpected exception: %s. | ||
7 | Not found exception: %s. | ||
8 | Bad request exception: %s. | ||
9 | SQL exception: %s. | ||
10 | Unexpected exception: %s. | ||
11 | JSON parsing exception: %s. | ||
12 | HTTP Error: %s, Message: %s. | ||
20 | %s. | ||
21 | Request constraint violation: %s. | ||
22 | INFO | SQL integrity constraint violation: %s. | This resource cannot be deleted. The resource is currently in use. |
31 | Resource not found: %s. | ||
32 | Localization not found for language: %s. | ||
33 | Localization not found: %s for entity: %s and language: %s. | ||
34 | Operator not found: %s. | ||
35 | BaseStation not found: %s. | ||
36 | DeviceProfile not found: %s. | ||
37 | Application Supplier not found: %s. | ||
38 | ApplicationServer not found: %s for Application Supplier: %s. | ||
41 | ConnectivitySupplier not found: %s. | ||
42 | ConnectivityPlan not found: %s. | ||
43 | ConnectivityPlan not found: %s for ConnectivitySupplier: %s. | ||
51 | Subscription not found: %s. | ||
52 | SubscriptionOption not found: %s. | ||
53 | AppServersRoutingProfile not found: %s for Subscription: %s. | ||
54 | NetworkSubscription not found: %s for Subscription: %s. | ||
55 | Device not found: %s for Subscription: %s. | ||
56 | DeviceReport not found: %s. | ||
57 | DeviceHistory not found: %s. | ||
58 | DeviceAlarm not found: %s for device: %s. | ||
59 | AppServer not found: %s for Subscription: %s. | ||
61 | NetworkPartner not found: %s. | ||
62 | BaseStation not found: %s. | ||
63 | BaseStation not found: %s for NetworkPartner: %s. | ||
64 | BaseStation not found: %s. | ||
65 | BaseStationHistory not found: %s. | ||
66 | BaseStationAlarm not found: %s for BaseStation: %s. | ||
67 | Wrong System BaseStationReport: no BaseStationReport for LRRID: %s and/or duplicate System BaseStationReport. | ||
68 | Wrong Config BaseStationReport: no BaseStationReport for LRRID: %s and/or duplicate Config BaseStationReport. | ||
69 | Wrong RFCell BaseStationReport: no BaseStationReport for LRRID: %s and/or duplicate RFCell BaseStationReport. | ||
70 | Wrong WAN BaseStationReport: no BaseStationReport for LRRID: %s and/or duplicate WAN BaseStationReport. | ||
71 | Antenna not found: %s for BaseStation: %s. | ||
72 | LogicalChannel not found: %s for Antenna: %s, BaseStation: %s. | ||
73 | SignalAndNoises not found for LogicalChannel: %s , Antenna: %s , BaseStation: %s. | ||
74 | LRC index not found: %s for BaseStation: %s. | ||
75 | Interface index not found: %s for BaseStation: %s. | ||
76 | Wrong Power BaseStationReport: no BaseStationReport for LRRID: %s and/or duplicate Power BaseStationReport. | ||
77 | DevAddrBlock not found: %s. | ||
78 | Supplier not found: %s. | ||
79 | SubscriptionAdmMgr not found: %s. | ||
80 | BaseStationAntennaImage not found: %s for BaseStationAntenna: %s. | ||
81 | KeyMgrSubscription not found: %s. | ||
82 | KeyMgrAsKey not found: %s. | ||
83 | KeyMgrDevice not found: %s for KeyMgrSubscription: %s. | ||
84 | KmDeviceReport not found: %s. | ||
85 | IsmBand not found: %s. | ||
86 | The requested tag does not exist. | ||
87 | The requested tag does not exist. | ||
88 | The requested tag does not exist. | ||
89 | FullProvisioningRequest not found: %s. | ||
90 | BaseStation not found for public key(X.509 format): %s. | ||
91 | The module ID has not been found in the configuration file: %s. | ||
92 | The application ID has not been found in the configuration file: %s. | ||
101 | OccVersion Mismatch. | ||
111 | Language %s in not supported. | ||
112 | Supported languages is empty. | ||
121 | Unknown ID: %s. | ||
122 | ID already used: %s. | ||
123 | Decryption of %s failed: %s. | ||
124 | Encryption of %s failed: %s. | ||
125 | DX API cannot be used by this user. | ||
126 | SMP login cannot be retrieved: %s. | ||
127 | Deprecated. | ||
128 | Deprecated. | ||
141 | Failed to authenticate user: %s. | ||
142 | SMP authentication failed: %s. | ||
143 | Missing access code. | ||
144 | No Operator in TWA for ID: %s. | ||
145 | No ApplicationSupplier in TWA for ID: %s. | ||
146 | No ConnectivitySupplier in TWA for ID: %s. | ||
147 | No NetworkPartner for href: %s. | ||
148 | No ACTIVE NetworkPartner in TWA for ID: %s. | ||
149 | No Subscription for href: %s. | ||
150 | No ACTIVE Subscription in TWA for ID: %s. | ||
151 | No SMP subscription for: %s. | ||
152 | Auth type not known: %s. | ||
153 | Auth failed, Subscription SUSPENDED for href: %s. | ||
154 | Auth failed, Subscription DEACTIVATED for href: %s. | ||
155 | Failed to authenticate user: %s. | ||
156 | Failed to authenticate user: %s. | ||
157 | Failed to authenticate user: %s. | ||
158 | Failed to authenticate user: %s. | ||
159 | Failed to authenticate user: %s. | ||
160 | Auth failed, no NetworkPartner in TWA for ID: %s. | ||
161 | Failed to authenticate user: %s. | ||
162 | Failed to authenticate user: %s. | ||
163 | No AdmManagerSubscription in TWA for href: %s. | ||
164 | INFO | Failed to authenticate user: %s. | The address manager subscription has been suspended. The subscription may have been deactivated by the operator. Please contact your operator representative. |
165 | INFO | Failed to authenticate user: %s. | The address manager subscription has been deactivated. The subscription may have been suspended by the operator. Please contact your operator representative. |
201 | A Subscription exists for href: %s. | ||
202 | A Device exists for href: %s. | ||
203 | INFO | A device exists for EUI: %s. | The DevEUI must be unique. A device with the same DevEUI already exists. |
204 | A DeviceReport exists for EUI: %s. | ||
205 | No Subscription for href: %s. | ||
206 | No DeviceReport for EUI: %s. | ||
207 | No DeviceProfile for ID: %s. | ||
208 | No NetworkSubscription for ConnectivityPlan: %s and Subscription: %s. | ||
209 | No AppServersRoutingProfile: %s for Subscription: %s. | ||
210 | Location coordinates cannot be set since device location method is not MANUAL. | ||
211 | AppServersRoutingProfile: %s is a default profile for the subscription: %s. | ||
212 | INFO | No slots left for the NetworkSubscription: %s , totalUsed: %d , totalGranted: %d. | No more licenses are available for this network subscription. All granted licenses have been used. You must purchase more licenses for this connectivity plan or select another connectivity plan. |
213 | A NetworkSubscription exists for ConnectivityPlan ID: %s and Subscription: %s. | ||
214 | No ConnectivityPlan for ID: %s and Operator: %s. | ||
217 | INFO | A device exists for nwAddress/nwKey pair: %s/%s. | The pair network address/network secret must be unique. A device with the same network address/network secret already exists. |
218 | The nwKey property is mandatory for device with MAC type [LoRaMAC, WattecoMAC_3_2]. | ||
219 | The nwKey property must be empty for device with MAC type other than [LoRaMAC, WattecoMAC_3_2]. | ||
220 | The appKeys property must be empty for device with MAC type other than [LoRaMAC, WattecoMAC_3_2]. | ||
221 | INFO | Device constraints failed. Too many destinations: %s for the AppServersRoutingProfile: %s, max allowed by ConnectivityPlan: %s is %s. | The connectivity plan and the AS routing profile are not compatible. The AS routing profile defines too many destinations. Please select another AS routing profile or another connectivity plan. |
222 | INFO | Device constraints failed. AppServersRoutingProfile: %s has cloud routes, ThinkPark Cloud Routing not allowed by the ConnectivityPlan: %s. | The connectivity plan and the AS routing profile are not compatible. The AS routing profile defines ThingPark X destinations. Please select another AS routing profile or another connectivity plan. |
223 | INFO | Device constraints failed. AppServersRoutingProfile: %s has third party routes, Third Party App Servers Routing not allowed by the ConnectivityPlan: %s. | The connectivity plan and the AS routing profile are not compatible. The AS routing profile defines Third party AS destinations. Please select another AS routing profile or another connectivity plan. |
224 | INFO | AppServersRoutingProfile constraints failed. Too many destinations: %s for the AppServersRoutingProfile: %s, max allowed by ConnectivityPlan: %s is %s. %s devices are concerned by this limitation (pair AppServersRoutingProfile + ConnectivityPlan). | The AS routing profile cannot be updated because too many destinations have been defined. This is not allowed by a connectivity plan associated to this AS routing profile. |
225 | INFO | AppServersRoutingProfile constraints failed. AppServersRoutingProfile: %s has cloud routes, ThinkPark Cloud Routing not allowed by the ConnectivityPlan: %s. %s devices are concerned by this limitation (pair AppServersRoutingProfile + ConnectivityPlan). | The AS routing profile cannot be updated because ThingPark X destinations have been defined. This is not allowed by a connectivity plan associated to this AS routing profile. |
226 | INFO | AppServersRoutingProfile constraints failed. AppServersRoutingProfile: %s has third party routes, Third Party App Servers Routing not allowed by the ConnectivityPlan: %s. %s devices are concerned by this limitation (pair AppServersRoutingProfile + ConnectivityPlan). | The AS routing profile cannot be updated because third party AS destinations have been defined. This is not allowed by a connectivity plan associated to this AS routing profile. |
227 | Subscription: %s have a different operator from the connectivity supplier associated to this connectivity plan: %s. | ||
228 | Error during key[%s] encryption: %s. | ||
229 | No Subscription for ID: %s. | ||
230 | INFO | The OTAA activation is not allowed for device with MAC type other than [LoRaMAC, WattecoMAC_3_2]. | The device profile is not compatible with the OTAA. |
231 | The nwAddress property is mandatory for device with ABP activation. | ||
232 | The nwKey property must be empty for device with OTAA activation. | ||
233 | The appKeys property must be empty for device with OTAA activation. | ||
234 | The appEui property must be empty for device with ABP activation. | ||
235 | The appKey property must be empty for device with ABP activation. | ||
236 | The appEui property is mandatory for device with OTAA activation. | ||
237 | The appKey property is mandatory for device with OTAA activation. | ||
238 | Marker ID property must be an integer. | ||
239 | Longitude property must be an integer. | ||
240 | Latitude property must be an integer. | ||
241 | An ACTIVE Subscription exists for ID: %s. | ||
242 | Maximum size of device reached. | ||
243 | Maximum size of alarm device reached. | ||
244 | The asID property is mandatory for AppServer with DOWNLINK_AS_KEY downlink security status. | ||
245 | The downlinkAsKey property is mandatory for AppServer with DOWNLINK_AS_KEY downlink security status. | ||
246 | The asID property is not allowed for AppServer with NONE downlink security status. | ||
247 | The downlinkAsKey property is not allowed for AppServer with NONE downlink security status. | ||
248 | The maxTimestampDeviation property is not allowed for AppServer with NONE downlink security status. | ||
249 | A device with OTAA activation exists for nwAddress: %s. | ||
250 | No Subscription option for href: %s. | ||
251 | INFO | Invalid verification code: %s. | The verification code is not valid. Each device is associated to a dedicated verification code. Please retry. |
252 | INFO | No Supplier for IEEEOUI: %s. | The DevEUI belongs to a device supplier which is not authorized on this platform. Please contact the device provider. |
253 | INFO | AS uplink/downlink security is mandatory. | Uplink/downlink security is mandatory for Application Servers. Please activate it. |
254 | INFO | HTTP URLs are forbidden in AS destinations. | HTTP URLs are forbidden in Application Server destinations. Please only set HTTPS URLs. |
255 | WARNING | The Application Server '%d' of Subscription '%d' can't be deleted because it is linked to %d Routing Profile(s). | The Application Server cannot be deleted because it is linked to one or several AS Routing Profiles. You must remove the Application Server from AS Routing Profiles. |
256 | WARNING | The AS Routing Profile can't be deleted because it is linked to one or several devices. | The AS Routing Profile cannot be deleted because it is linked to one or several devices. You must remove the AS Routing Profile from devices. |
257 | WARNING | Shannon entropy of AS Key is too low. | The quality of the provided tunnel interface authentication key value is too poor. Please submit a stronger value. |
258 | An application server exists for AS ID: %s. | ||
260 | The appKeyEncryptionMode property is mandatory for device with OTAA activation. | ||
261 | No HSMGroup for ID: %s. | ||
262 | The appKey property is mandatory for re-encryption. | ||
263 | ABP activation is not allowed when the external join server option is activated for the subscription. | ||
264 | The appKey property is not allowed when the external join server option is activated for the subscription. | ||
265 | The appKeyEncryptionMode property is not allowed when the external join server option is activated for the subscription. | ||
266 | Device constraints failed. AppServersRoutingProfile: %s has Kafka routes, Kafka App Servers Routing not allowed by the ConnectivityPlan: %s. | ||
267 | AppServersRoutingProfile constraints failed. AppServersRoutingProfile: %s has Kafka routes, Kafka App Servers Routing not allowed by the ConnectivityPlan: %s. %s devices are concerned by this limitation (pair AppServersRoutingProfile + ConnectivityPlan). | ||
268 | Device TypeMAC inherited from DeviceProfile cannot be changed. Current device DeviceProfile TypeMAC: %s. | New DeviceProfile TypeMAC %s. | |
269 | No DeviceVendor for ID: %s. | ||
270 | %s. | ||
271 | Form data is null. | ||
272 | Unexpected IO exception: %s. | ||
273 | Device for EUI: %s cannot be deleted. Device does not belong to the Subscription: %s. | ||
274 | No columns can be found. | ||
275 | Device EUI is mandatory. | ||
276 | Missing columns. Min columns expected: %s, columns retrieved: %s. | ||
277 | Too many columns. Max columns expected: %s, columns retrieved: %s. | ||
278 | Device Profile ID is mandatory. | ||
279 | Device creation failed: %s. | ||
280 | Operation not accepted: %s, Operation must be: %s. | ||
281 | Invalid file encoding (%s expected). | ||
282 | Access denied, user not logging or session expired. | ||
283 | Device can't be associated with routing profile and subscription application servers at the same time. | ||
284 | INFO | Maximum number of licensed devices is reached: %d. | The maximum number of licensed devices is reached. The device cannot be created. |
285 | Device context reset command failed with error: %s. | ||
286 | Connection to LRC failed with error: %s. | ||
287 | Only available for LoRaWAN devices. | ||
288 | lrcLogAccessUri is null or empty. | ||
289 | INFO | At least one device uses the Managed Customer Network, Base Station tag removal is not allowed. | The Managed Customer Network is currently used by at least one device. The current Base Station tag cannot be removed. |
290 | No Subscription application server for ID: %s. | ||
291 | DeviceAlarm:%s cannot be acked, it has been already acked. | ||
292 | DevAddr %s is not assigned to supplier with IEEEOUI: %s. | ||
293 | Device constraints failed. Third Party App Servers Routing not allowed by the ConnectivityPlan: %s. | ||
294 | Device constraints failed. Kafka App Servers Routing not allowed by the ConnectivityPlan: %s. | ||
295 | Device constraints failed. Too many destinations: %s, max allowed by ConnectivityPlan: %s is %s. | ||
296 | Destinations on DX Bridge AppServer are not allowed. | ||
297 | DX Bridge Dataflow creation failed: %s. | ||
298 | DX Bridge Dataflow update failed: %s. | ||
299 | DX Bridge Dataflow deletion failed: %s. | ||
300 | INFO | Base Station tag of the Managed Customer Network is not defined. | The Managed Customer Network is not yet configured. Please contact your operator representative. |
301 | A NetworkPartner exists for href: %s. | ||
302 | A BaseStation exists for href: %s. | ||
303 | INFO | A BaseStation exists for LRRID: %s. | The LRR ID must be unique. A base station with the same LRR ID already exists. |
304 | A BaseStationReport exists for LRRID: %s. | ||
305 | No NetworkPartner for href: %s. | ||
306 | No NetworkPartner for ID: %s. | ||
307 | No BaseStationReport for LRRID: %s. | ||
308 | No BaseStationProfile for ID: %s. | ||
309 | BaseStation SMN cannot be updated if BaseStation has been validated: %s. | ||
310 | BaseStation state cannot be updated from [%s] to [%s]: %s. | ||
311 | BaseStation XML config is not valid for property [%s]: %s. | ||
312 | INFO | The running LRR software version on this base station does not support this command. LRR version must be superior to %s. | The running LRR software version on this base station does not support this command. All commands are supported based on LRR software version 2.2.17. |
313 | Maximum size of base stations reached. | ||
314 | Maximum size of base station alarms reached. | ||
315 | INFO | Invalid number of antennas in rfHardwareConfig attribute. | The Base Station profile cannot be saved because the RF hardware configuration and the number of antennas must be consistent. Please modify the configuration and try again. |
316 | Invalid number of antennas in antennasConfig attribute. | ||
317 | ERROR | The base station is currently processing another command. | The base station is currently processing a command. Please retry later. |
318 | An ACTIVE NetworkPartner exists for ID: %s. | ||
319 | Invalid number of boards in rfHardwareConfig attribute. | ||
320 | NetworkPartner %s missmatch with operator ID: %s. | ||
321 | INFO | A BaseStation exists for LRRUUID: %s. | The LRR UUID must be unique. A base station with the same LRR UUID already exists. |
322 | A BaseStationReport exists for LRRUUID: %s. | ||
323 | Maximum LRRID generation attempts reached. | ||
324 | BaseStation LRR UUID cannot be updated if BaseStation identificationMode has been set to LRR_UUID: %s. | ||
325 | No BaseStationVendor for ID: %s. | ||
326 | Installation ID is not configured. | ||
327 | INFO | License file is invalid. | The uploaded license file is invalid. Please upload a valid one. |
328 | INFO | License has expired since %s. | The license has expired. Please upload a new license file. |
329 | RCA Provisioning certificates generation failed: %s. | ||
330 | RCA Provisioning certificates revocation failed: %s. | ||
331 | RCA Provisioning certificates regeneration failed: %s. | ||
332 | Certificate cannot be regenerate for this BaseStation. BSSecurity must be 'IPSEC_X509'. | ||
333 | License is missing. | ||
334 | INFO | Maximum number of licensed Base Stations is reached: %d. | The maximum number of licensed Base Stations is reached. The Base Station cannot be created. |
335 | INFO | Maximum number of base stations reached, used: %d, granted: %d. | The maximum number of Base Stations is reached. To create a Base Station, you must purchase more credit. |
336 | No base stations credit transaction for href: %s. | ||
337 | A base stations credit transaction exists for href: %s. | ||
338 | The application callback features are not valid. | ||
339 | The application callback feature is not valid: [ %s = %s ] (%s). | ||
340 | The version parameter is missing or incorrect to perform the asynchronous command. | ||
370 | %s. | ||
391 | BaseStationAlarm:%s cannot be acked, it has been already acked. | ||
392 | Profiles catalog manager disabled. | ||
393 | The requested URL, following LRC routing strategy, isn't defined. | ||
394 | Invalid LRR software version: %s. | ||
395 | Error while sending LRR software download to LRC: %s. | ||
397 | This public key already exist for a base station: %s. | ||
401 | No ConnectivitySupplier for ID: %s. | ||
402 | A ConnectivitySupplier exists for href: %s. | ||
403 | A ConnectivitySupplier exists for ID: %s. | ||
404 | A ConnectivityPlan exists for ID: %s and Operator: %s. | ||
405 | WARNING | Deprecated. | The connectivity plan is currently used by at least one device. Features downgrading has been prevented to avoid side effects on devices. |
406 | WARNING | Deprecated. | The connectivity plan is currently used by at least one device. Features downgrading has been prevented to avoid any side effect on devices. |
407 | WARNING | Deprecated. | The connectivity plan is currently used by at least one device. Features downgrading has been prevented to avoid any side effect on devices. |
408 | WARNING | Deprecated. | The connectivity plan is currently used by at least one device. Features downgrading has been prevented to avoid any side effect on devices. |
409 | Deprecated. | ||
410 | WARNING | At least one device uses the ConnectivityPlan, update not allowed. | The connectivity plan is currently used by at least one device. Features updating has been prevented to avoid any side effect on devices. |
411 | Deprecated. | ||
412 | The ConnectivityPlan cannot be deleted because it is linked to at least one NetworkSubscription. | ||
413 | ConnectivitySupplier %s missmatch with operator ID: %s. | ||
451 | No Subscription License Manager for href: %s. | ||
452 | No Network Subscription Transactions for href: %s. | ||
453 | A Subscription License Manager exists for href: %s. | ||
454 | An ACTIVE Subscription License Manager exists for supplier: %s and subscriber: %s. | ||
501 | No operator for ID: %s. | ||
502 | Usage detail record already exist for month: %s and network partner: %s. | ||
503 | Usage detail record already exist for month: %s and connectivity supplier: %s. | ||
504 | CSV file generation fail: %s. | ||
505 | An Operator exists for ID: %s. | ||
506 | A DeviceProfile exists for Operator: %s and ID: %s. | ||
507 | A BaseStationProfile exists for Operator: %s and ID: %s. | ||
508 | An ApplicationSupplier exists for Operator: %s and ID: %s. | ||
509 | An HSM group exists for Operator: %s and ID: %s. | ||
510 | Usage detail record already exist for month: %s and operator: %s. | ||
511 | No IsmBand for ID: %s. | ||
512 | INFO | Profiles catalog manager disabled. | This feature is not available for your environment. |
513 | Connection to TWA ADMIN failed: %s. | ||
514 | A FullProvisioningRequest is currently in progress. | ||
515 | No FullProvisioningRequest has been initialized. | ||
516 | Cannot delete FullProvisioningRequest currently in progress. | ||
517 | Can only delete FullProvisioningRequest for types: [%s]. | ||
518 | %s. | ||
523 | The SSH RSA public key provided is not a valid public key. Please retry with a valid RSA public key. | ||
651 | %s. | ||
666 | You are trying to send an uplink for a multicast device? That SHALL NOT PASS. That would be a major issue and a total non-sense since MULTICAST devices DO NOT send uplinks. Please try something else. | ||
701 | A session token is required. | ||
702 | Session token not expected: %s. | ||
1001 | DevAddrBlock: %s must be in managed pool. | ||
1002 | INFO | No Supplier for ID: %s. | The supplier ID does not match any supplier. Please enter a valid supplier ID. |
1003 | DevAddrBlock: %s must be free or reserved to be assigned. | ||
1004 | DevAddrBlock: %s must be free or reserved to be reserved. | ||
1005 | DevAddrBlock: %s must be assigned or reserved to be reclaim. | ||
1006 | DevAddrBlock: %s must not be fragmented to be fragment. | ||
1007 | Single DevAddrBlock: %s can't be fragmented. | ||
1008 | DevAddrBlock: %s must be fragment to be defragment. | ||
1009 | INFO | Subs-Block of DevAddrBlock: %s must have the same state to be defragment. | All sub-blocks must have the same state to be defragmented. The defragmentation cannot be processed. |
1010 | INFO | Subs-Block of DevAddrBlock: %s must have the same supplier to be defragment. | All sub-blocks must be associated to the same supplier to be defragmented. The defragmentation cannot be processed. |
1011 | INFO | There is no free large DevAddrBlock of pool: %s left for auto-assign. | No more free block are available. The auto-assignation cannot be processed. |
1012 | DevAddrBlock: %s must be assigned or reserved to be updated. | ||
1013 | DevAddrBlock: %s must be a large and in iotdev pools to be configured. | ||
1014 | INFO | IEE OUI: %s must match with DevEUI prefix: %s. | The DevEUI prefix does not match the IEEE OUI of the operator. Please provide a DevEUI prefix matching the IEEE OUI of the operator. |
1015 | INFO | DevEUI prefix: %s match a DevAddr prefix allocated to another DevAddr block for IoT developer pool: %s. | The DevEUI prefix is already used in the DevAddr IoT developer pool. Please provide another DevEUI prefix matching the IEEE OUI of the operator. |
1016 | INFO | DevEUI prefix: %s match a DevEUI prefix allocated to another DevEUI block for IoT developer pool: %s. | The DevEUI prefix is already used in the DevEUI IoT developer pool. Please provide another DevEUI prefix matching the IEEE OUI of the operator. |
1017 | DevAddrBlocks can't be allocated to unallocated pool. | ||
1018 | Prefix CIDR format not supported: %s. Accepted format: HexaString/bitNumber or HexaString. HexaString must contain 3 to 4 hexadecimal digit and bitNumber must be between 10 and 16. | ||
1019 | INFO | The block you requested with the prefix: %s aren't all in the unallocated pool or they don't exists. | Some blocks are already allocated to a pool. The blocks allocation request cannot be processed. |
1020 | Unallocated DevAddrBlocks can't be released. | ||
1021 | INFO | The block you requested with the prefix: %s aren't all in: %s or they don't exists. | Some blocks are not free or not allocated to the requested pool. The unallocation request cannot be processed. |
1022 | DEvEUIBlocks allocation must be to the IotDev pool. | ||
1023 | Prefix CIDR format not supported: %s. Accepted format: HexaString/bitNumber or HexaString. HexaString must contain 11 to 12 hexadecimal digit and bitNumber must be between 42 and 48. | ||
1024 | DEvEUIBlocks release must be in the IotDev pool. | ||
1025 | INFO | Supplier ID: %s is not present in SMP database. | Invalid supplier ID. The supplier does not exist. |
1026 | There is no ko key with version: %s for operator: %s. | ||
1027 | There is no free large DevEuiblock left for assign. | ||
1028 | No ADM address Transactions for href: %s. | ||
1029 | There is no free large configured DevAddrBlock of pool: %s left for assign. | ||
1030 | INFO | IEEE OUI: %s already affect to a supplier: %s. | The supplier IEEE OUI has already been allocated to another supplier. The supplier cannot be created. |
1031 | INFO | You can't delete a supplier with asigned blocks. | The supplier is still associated to DevAddr blocks. The supplier cannot be deleted. |
1032 | INFO | IEEE OUI: %s already affect to an operator: %s. | The supplier IEEE OUI is already used by the operator. The supplier cannot be created. |
1033 | Ko key version: %s already exists for operator: %s. | ||
1034 | Operator: %s must be initialized before update ko keys. | ||
1035 | A Supplier exists for ID: %s. | ||
1036 | Operator: %s is already initialized. | ||
1037 | Operator keys maximum size is reached. | ||
1101 | No ADM Manager Subscription for href: %s. | ||
1102 | An ADM Manager Subscription exists for href: %s. | ||
1103 | An ACTIVE ADM Manager Subscription exists for ID: %s. | ||
1201 | Missing HSM group. | ||
1202 | INFO | HSM protection not allowed by Connectivity Plan: %s. | HSM protection is not allowed by the connectivity plan associated with the device. Please select another connectivity plan. |
1203 | INFO | HSM protection not allowed by AS Routing Profile: %s. | HSM protection is not allowed by the AS routing profile associated with the device. Please select another AS routing profile. |
1204 | INFO | HSM group mismatch with Connectivity Plan: %s. | Selected HSM group does not match the HSM group associated with the connectivity plan. Please select another HSM group or another connectivity plan. |
1205 | INFO | HSM group mismatch with AS Routing Profile: %s. | Selected HSM group does not match the HSM group associated with the AS routing profile. Please select another HSM group or another AS routing profile. |
1206 | HSM group not allowed. | ||
1207 | INFO | HSM %s encryption failure: %s. | The encryption of the AppKey by the HSM failed. Please retry. |
1208 | INFO | Software embedded encryption not allowed by Connectivity Plan: %s. | Software embedded encryption is not allowed by the connectivity plan associated with the device. Please select another connectivity plan. |
1209 | INFO | Software embedded encryption not allowed by AS Routing Profile: %s. | Software embedded encryption is not allowed by the AS routing profile associated with the device. Please select another AS routing profile. |
1210 | Missing HSM group. | ||
1211 | Missing RSA Public Key. | ||
1212 | HSM group mismatch with Connectivity Plan: %s. | ||
1213 | INFO | HSM group mismatch with device. %d devices are concerned by this error: %s. | The AS routing profile is associated with at least one device. HSM protection cannot be activated. |
1214 | INFO | HSM AS Key encryption failure: %s. | The generation of the AS transport key by the HSM failed. Please retry. |
1215 | HSM group cannot be updated. | ||
1216 | INFO | Software embedded encryption not allowed by device. %d devices are concerned by this error: %s. | The AS routing profile is associated with at least one device. HSM protection cannot be deactivated. |
1217 | INFO | The RSA public key provided is not a valid X.509 PEM public key. Please retry with a valid RSA public key. | The RSA public key is invalid. Please retry. |
1218 | HSMGroup cannot be changed, added or removed from a ConnectivityPlan already used by one or more devices. | ||
1219 | The hsmGroupID property is not allowed when the external join server option is activated for the subscription. | ||
1220 | HSM Security Status cannot be set to 'HSM_AS_KEY' when the external join server option is activated for the subscription. | ||
1221 | LRC cluster key not set for Operator. | ||
1222 | HSM protection not allowed by AS key: %s. | ||
1223 | HSM group mismatch with AS key: %s. | ||
1224 | HSM protection mandatory by AS key: %s. | ||
1225 | HSM AS Key encryption failure: rsaPublicKey bit length must be within 1024 to 2048. | ||
1226 | HSM %s encryption failure: %s. | ||
1227 | HSM get RSA public key failure: %s. | ||
1228 | Invalid %s private PEM key: %s. | ||
1229 | The RSA public key provided by HSM is not a valid public key. Please contact support. | ||
1230 | HSM group settings not well configured, address, user or password is empty. | ||
1301 | A Key Manager Subscription exists for href: %s. | ||
1302 | An ACTIVE Key Manager Subscription exists for ID: %s. | ||
1303 | No Key Manager Subscription for href: %s. | ||
1304 | No Key Manager Subscription for href: %s. | ||
1305 | Failed to authenticate user: %s. | ||
1306 | Failed to authenticate user: %s. | ||
1307 | Failed to authenticate user: %s. | ||
1308 | Failed to authenticate user: %s. | ||
1309 | Maximum size of device reached. | ||
1310 | A device exists for EUI: %s. | ||
1311 | A KmDeviceReport exists for EUI: %s. | ||
1312 | No AS key for ID: %s. | ||
1313 | No KmDeviceReport for EUI: %s. | ||
1314 | %s. | ||
1315 | ERROR | The AS Key can't be deleted because it is linked to one or several devices. | The AS transport key cannot be deleted because it is linked to one or several devices. You must remove the AS transport key from the devices. |
1316 | AS Key: %s is a default profile for the subscription: %s. | ||
1317 | asKey/ID and/or homeNsNetID are forbidden for pre-commissioned device. | ||
1318 | appKey and secureElement are forbidden together. | ||
1319 | SE key for HSM group %s and TKM info %s not configured. | ||
1320 | homeNsNetID is mandatory for commissioned device. | ||
1321 | Device claim failed: invalid devEUI %s or ownerToken %s. | ||
1401 | EPC connector provisioning is not activated in Operator settings. | ||
1403 | EPC connector provisioning mode is SPR: Ki parameter is forbidden. | ||
1405 | EPC connector provisioning mode is HSS/SPR: Ki parameter is mandatory. | ||
1406 | The device profile is not compliant with the device connectivity. | ||
1407 | The Connectivity Plan is not compliant with the device connectivity. | ||
1408 | The Connectivity Plan is not compliant with the device communicationType. | ||
1409 | Cellular device can't be directly associated with subscription application servers. | ||
1410 | The Application Server can't be deleted because it is linked to one or several devices. | ||
1411 | INFO | Operator domain could not be retrieved from SMP: %s. | Your request is not accepted. Please retry later. |
1412 | Error while sending device downlink to LRC: %s. | ||
1413 | The routing profile is not compliant with the device connectivity. | ||
1414 | Application serveur %s is not compliant with the device connectivity. | ||
1415 | Invalid exchange key version: %s. | ||
1501 | INFO | Maximum number of devices in LoRaWAN debugging mode reached for this Operator: %d. | The maximum number of devices in LoRaWAN troubleshooting mode has been reached. The LoRaWAN troubleshooting mode cannot be activated. |
1601 | Tag: %s cannot be added to BaseStation: %s. It has already been added. | ||
1602 | Maximum size of device reached. | ||
1603 | Maximum size of alarm multicast group reached. | ||
1604 | The maximum number of Base Stations is exceeded. | ||
1701 | The call of TWA admin 'self update' service failed. | ||
2091 | AppServersRoutingProfile: %d for Subscription: %d has to be of type %s. | ||
2370 | INFO | Invalid IMSI: %s. | IMSI number does not match any unallocated Ki. Please retry. |
2371 | The nwKKey property must be empty for device with ABP activation. | ||
2372 | The nwKKey property is mandatory for LoRaWAN 1.1 device if External Join Server option is DEACTIVATED, with OTAA activation. | ||
2373 | The nwKKey property must be empty if device is LoRaWAN 1.1 device or if External Join Server option is ACTIVATED, with OTAA activation. | ||
2374 | The nwKSEncKey property must be empty for device with OTAA activation. | ||
2375 | The nwKSEncKey property is mandatory for device with MAC type LoRaMAC or WattecoMAC_3_2, with ABP activation. | ||
2376 | The nwKSEncKey property must be empty if device is not LoRaWAN 1.1 or if MAC type is not LoRaMAC or WattecoMAC_3_2, with ABP activation. | ||
2377 | The sNwkSIntKey property must be empty for device with OTAA activation. | ||
2378 | The sNwkSIntKey property is mandatory for device with MAC type LoRaMAC or WattecoMAC_3_2, with ABP activation. | ||
2379 | The sNwkSIntKey property must be empty if device is not LoRaWAN 1.1 or if MAC type is not LoRaMAC or WattecoMAC_3_2, with ABP activation. | ||
2380 | The nwKKey property must be empty if device is LoRaWAN 1.0 device with OTAA activation. | ||
2621 | The nwkKey property is mandatory for re-encryption. | ||
2681 | DeviceProfile LoRaMAC versions non compatible with actual device LoRaMAC 1.1 versions. | ||
2682 | DeviceProfile LoRaMAC versions non compatible with actual device LoRaMAC versions. | ||
2701 | INFO | CSV import file contains more than %d directives. | CSV import file cannot contains more than %s1 directives. Please split your file into smaller files. |
2900 | No Subscription application server for IDs: %s. | ||
2951 | INFO | SubscriptionAppServer constraints failed. Too many destinations: %s for the SubscriptionAppServer: %s, max allowed by configuration is %s. | The application server cannot be updated because more than %s1 destinations have been defined in a route. |
2952 | INFO | SupplierAppServer constraints failed. Too many destinations: %s for the SupplierAppServer: %s, max allowed by configuration is %s. | The application server cannot be updated because more than %s1 destinations have been defined in a route. |
2991 | DX Bridge Dataflow recuperation failed: %s. | ||
2992 | Subscription application server with DX bridge type %s already exists. | ||
2993 | Maximum number of DX bridge applications reached: %d. | ||
2994 | Maximum number of DX bridge applications per type reached: %d. | ||
3001 | Maximum number of base station tag reached for managed customer network. |
HTTP response headers
The following tables display the standard response headers that are returned with each API response:
Standard response field name | Description |
---|---|
sunset | This field will be populated with the deprecation details. By default the value is n/a. |
api-version | Indicates the API version you have used. |
quota-interval | Used to specify an integer (for example, 1, 2, 5, 60, and so on) that will be paired with the quota-time-unit you specify (minute, hour, day, week, or month) to determine a time period during which the quota use is calculated. For example, an interval of 24 with a quota-time-unit of hour means that the quota will be calculated over the course of 24 hours. |
quota-limit | Number of API calls an user can make within a given time period. If this limit is exceeded, the user will be throttled and API requests will fail. |
quota-reset-UTC | All quota times are set to the Coordinated Universal Time (UTC) time zone. |
quota-time-unit | Used to specify the unit of time applicable to the quota. For example, an interval of 24 with a quota-time-unit of hour means that the quota will be calculated over the course of 24 hours. |
quota-used | Number of API calls made within the quota. |
strict-transport-security | The HTTP Strict-Transport-Security (HSTS) response header lets a website tell browsers that it should only be accessed using HTTPS, instead of using HTTP. All present and future subdomains will be HTTPS for a maximum of 1 year and access is blocked to pages or sub domains that can only be served over HTTP including HSTS preload lists of web browsers. Strict-Transport-Security: max-age=31536000; includeSubDomains; preload. |
Access control field name | Description |
access-control-allow-credentials | Tells browsers whether to expose the response to frontend JavaScript when the request's credentials mode (Request.credentials) is include. When a request's credentials mode (Request.credentials) is include, browsers will only expose the response to frontend JavaScript if the Access-Control-Allow-Credentials value is true. Boolean. |
access-control-allow-origin | Indicates whether the response can be shared with requesting code from the given origin. |
access-control-allow-headers | Used in response to a pre-flight request which includes the Access-Control-Request-Headers to indicate which HTTP headers can be used during the actual request. |
access-control-max-age | Indicates how long the results of a pre-flight request (that is the information contained in the Access-Control-Allow-Methods and Access-Control-Allow-Headers headers) can be cached. |
access-control-allow-methods | Indicates which HTTP methods are allowed on a particular endpoint for cross-origin requests.For example: GET, PUT, POST, DELETE. |
content-length | The Content-Length entity header indicates the size of the entity-body, in bytes, sent to the recipient. |
content-type | The Content-Type entity header the client what the content type of the returned content actually is. |