MQTT Agent External Broker config

Agents, Protocols and APIs
12

Hi,

Thanks for taking the time to explain your use case a little more.

Indeed using OpenRemote as an MQTT bridge to your existing MQTT broker makes sense; at a very basic level we have an MQTT Agent which utilises HiveMQ Client and allows OpenRemote to pub-sub to another broker but this is for simple use cases.

I would suggest a custom ContainerService that uses an instance of the MQTT client to connect to your broker and subscribe to some wildcard topic(s) for your devices. This container service can then contain the specific business logic to:

  • Extract a unique identifier
  • Create an asset and maybe a retricted user in OpenRemote (linking the user to the new asset)
  • Updating the attributes of this asset when data is received
  • Create an insights dashboard for the user/device

@martin.peeters I guess the work you have done on dashboards doesn’t currently support variables (e.g. regex/substring user name and use this in widgets for attribute source)?

1 Like