Skip to content
This repository has been archived by the owner on Dec 3, 2023. It is now read-only.
embee8 edited this page Feb 8, 2017 · 2 revisions

Introduction

Welcome to the XiFox connector wiki pages. If you are not familiar with Xively, LPWAN, nor Sigfox, this Wiki details what components are needed and how they are setup for testing.

The experimental XiFox connector has been created for organizations that anticipate the need for multiple connectivity methods for their Internet of Things or connected product infrastructure. For example, suppose an organization is currently using Xively for WiFi technology for their various deployments but also requires a lower power or longer distance technology solution.

XiFox will allow for the integration of new Sigfox devices into the same Xively connected product management infrastructure. For organizations that are integrating the service and sales management of their connected objects through Salesforce, Xively and the XiFox connector will allow Sigfox connected devices to immediately work with Salesforce work flows.

In order to bridge the Sigfox and Xively environments, some fundamental mappings between the Xively and Sigfox environments are implied. Sigfox device types map directly to Xively device templates. Devices in those type containers map directly to a Xively device. Finally, Sigfox devices normally have a small standard payload in byte format (maximum 12 Bytes). Each of the discrete fields in the byte format maps to a specific JSON field in the Sigfox callback, which are eventually mapped to Xively channels/topics.

For example, suppose there exists a Sigfox device type called Environment Sensor. The application acquires its data from 5000 low power Sigfox devices that intermittently measure the temperature, humidity, light level and ambient movement every 30 minutes. The devices have been built with a battery and have a usage life of 18 months.

In the Xively environment, there is a matching device template called Environmental Sensor. Associated with the device template are 4 channels: temperature, humidity, light and movement. Xively rules have been created to trigger a Salesforce case when the nominal levels of these readings go beyond a threshold.

The XiFox connector will be configured to associate both of these environment such that every measurement sent by the Sigfox environmental Senors will be immediately received by the Xively environment. Salesforce cases will immediately be generated by any abnormal readings.

Clone this wiki locally