Integrating OpenRemote with Flespi

Hi Everyone,

I have been letting our version of OpenRemote gather dust due to some issues, but I will be resuming on this soon, but one thing I had thought about during this period is to use Flespi as the GPS Tracking Middleware to directly connect to OpenRemote.

Can you advise whether this has been done before, and if so, can you advise on how this can be achieved please.

For those who don’t know about Flespi, the website www.flespi.com would no doubt impress.

Flespi uses MQTT, which I dare say would be ideal in this instance.

Thank you in advance,
Michael

@panos do you know anything about this? (or know people within the fleet domain that do?)

Hi @Technique ,

Not sure if this has been done before, there have been some people over the past years making questions related to flespi, but I haven’t seen a concrete implementation.

You can use an MQTT agent to connect to Flespi and start retrieving data from there. If you end up writing any custom code, we’d be happy to see a PR from you!

Hi everyone,

Is the MQTT agent a component in OpenRemote(OR), or is that external to OR.

Flespi has it’s own MQTT implementation and an MQTT Broker. Would this suffice, or would other components be needed as well?

Would you happen to have any suggestions on what can be done with OR and Flespi’s resources?

Hey, I take data from flespi and inject it to Openremote but I do it externally. I have a python script running to fetch data from flespi and send it to my assets in the openremote. I think using flespi streams is also possible. I just prefer to use python externally so that I can perform calculations.

Hi Saarthi,
Thank you for this.

I would rather minimise and use the direct tools that both OR and Flespi have, to minimise hassles, etc…

Agents are a common built-in feature that allows linking to external services / devices.
You can use an MQTT Agent to listen for messages on your own broker.

More details here:

.
As an alternative, you can communicate with our own integrated MQTT broker instead.
You can publish- or subscribe to changes in attribute values that way.
More details on that here:

Many thanks for this.

Time to put pen onto paper. Wish me luck.