Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.
© 2026 The ThingsBoard Authors
180 Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

North America Data stored in North America Europe Data stored in the European Union

Rather run it yourself? Install on your own servers

EdgeEventController

EdgeEventController exposes REST endpoints for querying edge events: the downlink queue that the ThingsBoard server keeps for each Edge, like entity assignments, rule chain pushes, and RPC calls. Call it on the server: it backs the Downlinks tab of the Edge. On an Edge node, this log stays empty.

Endpoints

Section titled “Endpoints”

Base path: /api/edge/{edgeId}/events

Method Path Description
GET /api/edge/{edgeId}/events Returns a paginated list of edge events. Supports pageSize, page, textSearch, sortProperty, sortOrder, startTime, and endTime. Requires TENANT_ADMIN or CUSTOMER_USER authority.

Cloud events vs. edge events

Section titled “Cloud events vs. edge events”

Two event logs help diagnose synchronization:

  • Cloud events at /api/edge/events: Outbound messages queued on Edge waiting to be sent upstream to the server, like telemetry, alarms, and entity changes. Accessible via EdgeController.
  • Edge events at /api/edge/{edgeId}/events on the server: downlink messages the server sends to the Edge, like entity assignments, rule chain pushes, and RPC calls. Accessible via EdgeEventController.

Both queues use the same pagination interface and are useful for diagnosing synchronization issues. If the cloud events queue grows without draining, check the gRPC connection status via Edge status & events and message statistics.

© 2026 The ThingsBoard Authors · Privacy Policy · Cookie Policy ·