Rigado Edge Connect is an optimized BLE connectivity app that runs on a Rigado gateway. Edge Connect scans for BLE data and makes it available to BLE Pipelines. Edge Connect also supports other Low Power Wireless protocols (Wirepas) with additional protocols on our roadmap.

Edge Connect handles incoming data using reusable components called Recipes. Recipes encapsulate Sensor functionality and may publish data to a cloud server (Azure, AWS, MQTT, HTTP, etc.). Recipes expose configurable elements to adjust recipe behaviors. For example, the publishing interval for sensor data, security credentials for connecting to a cloud, and other adjustable information.


Note: Rigado largely handles gateway configuration for customers.

Custom Configuration

Rigado provides a way for configuration to be customized using a domain specific language written in JSON called Edge Connect Language. If existing recipes and configurable options do not meet the needs of a project or solution, reach out to the sales team at Rigado to get a conversation going.

Sending Configuration

  • Configuration is composed, maintained, and delivered in JSON format.
  • Customers may deliver configuration to our CLI command and API endpoint.
  • Edge Connect configuration resides within the App Sets type of a gateway's configuration.

If Configuration States is not yet enabled for your Edge Direct instance, gateways must be online to receive configuration commands. A configuration command---and its payload---will only be sent to a gateway once. If the gateway is offline, it will not receive the new configuration.

Complete Configuration Reference

Reference for all configuration options and available filters can be found in the Edge Connect Configuration Reference