Device Integration

How can I re-register a device that has gone through a factory reset?

See Replace Device for what the Device sees — the 422 — Device already registered response, how a replacement is staged, and what the next registration returns. The Organization portal procedure is in the customer docs: https://docs.xyte.io/docs/replace-device

Offline detection

Each device has a last_seenproperty, which is updated on any API communication received from the device (telemetries, command completion, etc). An automatic process runs every 30 seconds to check if any device's last_seen timestamp exceeds the "Offline detection threshold" set in the Device Model Configuration (If enabled).

When an offline threshold is exceeded, an automatic Incident is created on the device, which will be automatically closed as soon as the device resumes communications.

Sending commands from Partner Portal

This feature is disabled for Partner to ensure End Customer security. A Partner can request one (or more) of their users to be added to the End Customer Portal and be able to login and execute commands on all accessible devices.

Widget data when devices are offline

Xyte automatically saves the "last state" when a device goes offline. During offline state, Widgets will display data from the "last state" and a banner notifying the user of this, is displayed at the top.

Device API rate limiting

Device rate limiting is according to the commercial plan set between the Partner and Xyte and is calculated for every 30 seconds. Exceeding the rate limit will cause the APIs to return the 429 Too Many Requests response until the rate limiting engine detects the device allowed to send requests again.

All requests are counted towards the limit.

Why does the Device Log show fewer entries than the telemetries my device sends?

Every telemetry your device sends is received and acknowledged (201, success: true). To keep device history readable, Xyte stores a new Device Log / history entry only when a value or the status changes. When a report is identical to the previous one (only the timestamp differs), no new entry is added; a keep-alive entry is still written about every 5 minutes.

Any change is stored immediately, so you may see entries seconds apart when values change, and about 5 minutes apart when nothing changes. No data is lost.

Tip: send timestamp in UTC (ISO 8601 with Z, e.g. 2026-10-28T13:27:25Z), or leave it out and Xyte uses the time the report was received.