Sigfox Backend Connectivity

Agents, Protocols and APIs
1

We recently set up OpenRemote on-premise, and we want to use it as a listener to a Sigfox Backend, to visualize any metrics retrieved. The OpenRemote agent shouldn’t issue HTTP requests to the Sigfox Backend, but only listen for Callbacks (messages come in roughly 1 hour between each other).

We are having difficulties with connecting to the backend, as well as understanding how to properly set up Agents, Agent Links and Assets.

Is there someone familiar with:

  • Making it so OpenRemote only listens to the backend without issuing requests?
  • Setting up the variables to be read from the sent Callback?
  • Visualizing them inside OpenRemote as history graphs? (I know that this involves Agent Links between an Agent and an Asset)

As an example, let’s say there is an air sensor which connects to the Sigfox backend. In OpenRemote, we should be able to see that sensor on the map, see indications for “DeviceID”, “Time”, “Oxygen Level”, and “Humidity”. The “Oxygen Level” and “Humidity” values should be able to havea graph showing the different values every few hours.

Thank you in advance!

2

Hi, welcome to the forum!

I’m not familiar with this tool, but as you’re referring to “listening to the backend”,
I assume you’re looking for HTTP webhooks using WebSockets?

In OpenRemote you can achieve that using Agents.
Most of these listen for changes, while some having polling logic for sending requests.
A list of the supported agents can be found here;

.
To gather data from agents, and place them in an attribute, you use an AgentLink.
You can look at that page from earlier, or follow similar steps on this HTTP tutorial here.
(you won’t use the HTTP Agent here, but a different one)

Hope this helps!