60 docs tagged with "Customer"

Get a KONA Core account or start a trial, sign in for the first time, reset your password and reach the main page.

Activate a TEKTELIC device so that it joins KONA Core and sends its first uplink.

What Adaptive Data Rate does, how KONA Core applies it to your devices, which ADR settings you can change, and when to disable it.

Add email, SMS or MQTT notifications to an alarm rule, choose the recipients, use references in the message and test the notification.

Every event name KONA Core can record, with its source, type, severity where confirmed, what it reports and what to do.

The main parts of KONA Core, how gateways connect, and where payload converters and integrations sit between the device and your system.

Add many devices to an application at once from a CSV file with Device bulk commissioning, read the result and check the new devices.

Add many gateways to a gateway group at once from a CSV file, with their names, GW-IDs, MQTT credentials and locations.

Add an alarm rule to an application, choose the device, integration and data converter triggers, add an email, SMS or MQTT notification and test the rule.

Add an alarm rule to a gateway group, choose the gateway triggers, filter gateway alarms and faults by severity and state, add a notification and test the rule.

Change a gateway's settings in KONA Core and send configurations to one gateway, a gateway group or several gateways at once, then check that they are synced.

How LoRaWAN devices join KONA Core with OTAA or ABP, and how device classes A, B and C decide when a device can receive downlinks.

Check whether a device works in KONA Core: its Online or Offline status, its last activity time, the signal quality of its uplinks and its uplink history.

View a device's session values and frame counters in KONA Core, and reset the frame counters of an ABP device when it restarts its own counters.

The entities of KONA Core, from tenants and users to gateways, applications, devices and alarm rules, how they relate and in which order to create them.

How KONA Core records events for gateways, devices and integrations, how an alarm is raised and cleared, and where you see and forward them.

Publish KONA Core alarm events to your own MQTT broker with an MQTT notification in an alarm rule, and receive them with an MQTT client.

Send commands such as Reboot or Ping to a KONA gateway from KONA Core, read the command output, and find the other remote management tabs.

Find the messages your gateways exchange with KONA Core on the Gateway logs page, filter them, and copy the details to send to support.

Definitions of LoRaWAN and KONA Core terms used in this documentation.

Add an HTTP_V2 integration that sends each uplink to your HTTPS endpoint, with authentication, request headers and a retry scheme, and send downlinks back through it.

Configure a legacy HTTP (V1) integration that sends an application's uplinks to your server, and accepts downlinks from it.

Check that an integration delivers data: read its alarms and events, its UL delivery, retry and DL statistics and its data converter statistics, get notified of failures and fix the common ones.

What an integration does in KONA Core, how HTTP_V2, MQTT_V2 and MQTT_BROKER differ, why to use V2 instead of V1, and where the data converter sits.

Create, edit and delete applications in KONA Core, attach integrations, set API limits and assign an application to a Sub-Customer.

Create Customers and Sub-Customers in KONA Core, give each one a subscription plan and administrators, share gateway groups and applications, and delete them.

Use the TEKTELIC device models in KONA Core, or add, edit and delete your own device model with its manufacturer, type and device class.

Create gateway groups, add, move and remove their gateways, and delete groups you no longer need.

Add users to KONA Core, activate them, change their role, and remove access with Permanently disable or Delete.

The JSON objects a V2 integration works with: the decoder input and output for uplinks, the downlink request and the encoder input and output, with the V1 differences.

Move a legacy HTTP or MQTT integration to HTTP_V2 or MQTT_V2: create the V2 integration next to the V1 one, compare the data, then delete V1.

Check the health of your gateways in KONA Core: the Online and Activity status, the gateway statistics, the dashboard and the gateway's events.

Add an MQTT_BROKER integration, then connect your MQTT client to the KONA Core broker with the credentials and topics KONA Core creates.

Add an MQTT_V2 integration, so KONA Core connects to your own MQTT broker and publishes device data to your topic.

Configure a legacy MQTT (V1) integration that publishes an application's uplinks to your MQTT broker.

Create a multicast group in a KONA Core application, add devices to it and send one downlink that all its devices receive.

The LoRaWAN radio and MAC settings KONA Core applies to your devices, where you set them, their values and when to change them.

Add a TEKTELIC KONA gateway to KONA Core, set its MQTT credentials, point the gateway to KONA Core and check that it shows Online and Active.

Add a TEKTELIC device to an application in KONA Core with its TEKTELIC device model, check that it joins, and see its first uplink.

Add a LoRaWAN device from another manufacturer to KONA Core: create its device model, enter its keys, attach a data converter and check that it joins.

Add a third-party gateway to KONA Core by its GW-ID, allow UDP, point its packet forwarder to KONA Core and check that it forwards uplinks.

See which ideas the Concepts section explains and which concept to read before each group of guides.

Create a Custom v2 data converter that forwards the payload bytes and port without decoding them, attach it to an integration and check what your system receives.

What the decoder and encoder of a data converter do, how a converter is attached to an integration, which types exist, the runtime limits, and how to test a converter.

What a LoRaWAN frequency plan is, which regional plans KONA Core gateway models support, and why your gateways and devices must use the same plan.

What the LoRaWAN AppKey, NwkSKey and AppSKey protect, how KONA Core handles device keys, gateway credentials and API tokens, and how to keep them safe.

Put a downlink in a device's queue from the KONA Core UI or the REST API, choose the port and confirmed or unconfirmed delivery, and check that the device received it.

Sign in, connect a KONA gateway, create an application, add a TEKTELIC device and see its first uplink, then send the data to your server over HTTP.

How Provider and Customer subscription plans cap the gateways, Customers, Sub-Customers, applications, devices and integrations you can create in KONA Core.

The predefined TEKTELIC converter types in KONA Core, which integrations can use them, how to pick a converter for a TEKTELIC device, and how updates reach you.

How the System, Provider, Customer and Sub-Customer levels of KONA Core divide ownership, visibility and subscription limits.

Upgrade the BSP firmware of KONA gateways from KONA Core, for one gateway or a whole gateway group, and track the upgrade status.

The path of an uplink to your integration and of a downlink back to the device, with the checks, queues and normal waiting times.

Check how many gateways, devices and Sub-Customers you use in KONA Core, read converter statistics by day and month, and get usage over time and reports through the API.

Find who changed what in KONA Core: what the User Activity Log records, how to filter it, and how to export it as a CSV file.

The administrator and user roles at each KONA Core tenant level, what each role can open and change, and how access passes down the hierarchy.

What TEKTELIC KONA Core Network Server does, where it sits in a LoRaWAN network, and how you access it.

Find, filter and read alarms on the Alarms page, change the time window, see severities and states, and export the list to a CSV file.

Write a Custom v2 decoder in JavaScript that turns a device's binary uplink into JSON, test it locally, and check that KONA Core runs it without errors.

Write a Custom v2 encoder in JavaScript that turns the JSON your system sends through an integration into the bytes and FPort of a downlink.