Frequently Asked Questions about Devices
How do I register a Device?
Please see the Device Registration page.
What does Allocate EUI do?
If a device does not have an OEM assigned EUI, an EUI will need to be programmed into the device.
Users can allocate EUIs for their devices from the Senet EUI registry. By default, each account is limited to 10 allocated EUIs.
What if my device is not in the Device Type dropdown list?
The Device Type can be left blank.
Why can't I register any more devices?
Users are limited to 10 devices by default. Please contact email@example.com to increase the maximum devices for an account.
I deleted all of my devices. Why can't I register a new device?
Allocated Device EUIs persist in a User's account. Register a new device with an EUI that has already been allocated.
To view an account's allocated EUIs, open Edit Account Information (See Edit Account Information).
The EUIs will be listed under Allowed Device EUIs.
How do I edit a device?
Edit a device from the Dashboard Tile View.
Edit a device from the Dashboard Table View.
Edit a device from the Device Details View.
How do I delete a device?
Although the device is removed from the Dashboard, the Allocated EUIs are not removed from the account. The device data is also not deleted with the device. Just re-register the device EUI and the previous data will be accessible.
What is a Notification Target or Notifier?
Notification Targets are IoT platform providers that provide north-bound data processing and analytic services. Notification Targets are configured at the Device and Application level.
Device Notification Targets are typically configured by a Developer when evaluating a particular IoT platform. This allows the Developer to troubleshoot connection and data transfer issues prior to establishing a production level integration with the platform.
Application Notification Targets are configured at the Application level and apply to all Devices on the Application. Once an IoT platform is selected for integration, the Application Target is configured so that all Devices on the Application forward data to the platform.
Differences Between the Notifier Types:
Individual Device Notification Target connections are considered temporary and are added and removed frequently. Application Notification Targets represent the final production integration with an IoT platform and are expected to remain connected at all times.
Device Notification Targets automatically disable themselves after 10 consecutive failed attempts to successfully deliver a message. An Application Notification Target (production) will remain available and will continue to deliver messages until service is restored.
Please see the Data Streaming page for more detailed information on Notification Target configuration.
What is a Notification Error?
Notification Errors can be encountered when forwarding Device uplink data northbound to an IoT platform Application. These error counts are displayed in the Application Dashboard and details about each error can be seen in the Application Events view. The management platform may occasionally report “Error sending message (status code 408) - Error [Request timed out after: x seconds]”. This does not always mean that the back-end Application did not receive the message, only that the management platform has reached a threshold (x seconds) and is no longer going to wait for the response from the back-end Application. Many of these errors, along with Avg. Request Times increasing towards the threshold reported in the timeout, may indicate the back-end Application is unable to process the current load.
How do I forward uplinks to an IoT platform?
Please see the Data Streaming page.
How do I recover or view a device's App key?
In the Edit Device window (See Edit Device), click on the key icon next to the Device EUI field. The App EUI and AppKey will then be displayed below the Device EUI.
How do I view or generate an API Key for sending downlinks?
The Active API key is ONLY displayed in the Senet Portal after it has been generated. Once a user leaves the Edit Account Information page, the API Key will not be displayed again. To obtain an active API key, see Implementing the Downlink API.