I am Daniel Gutierrez, and I am working in a project where I have a main device collecting data from sensors, and this main device then publish the sensor data to a HiveMQ broker. The format of the topic is:
Where systemID is a unique ID, sensorType is a string, and sensorID is an alphanumeric value. For example:
Then, the format of the payload is a JSON payload that looks like:
Right now, I am using HiveMQ as broker, my device as client that publish data, and OpenRemote as client that subscribe the data and update the state of one light asset. But I would like to use (in the future) the MQTT broker from OpenRemote to be completely independent of HiveMQ. This is, OpenRemote as broker, my device as client to publish, the light asset as client to subscribe.
I was not able to publish any message, and I found that to do it, I need to use a specific format.
If I understand you correctly, you would like to use the OpenRemote MQTT API and you don’t want to change the topic you are currently using (systemID/sensorType/sensorID)?
You can’t change the topic your main device uses to publish the data?
You are right, I want to use the MQTT API. And no, we cannot change the topic since the topics are already being used by another functionalities of the system. We would like to publish/subscribe the topics as we had, but instead of using HiveMQ URLs we would like to use OpenRemote URLs.
Thanks! That is exactly how I did until now, but the idea is to not have different services with different companies. We would like to have everything together Being independent of HiveMQ or any other MQTT broker provider will make everything a bit easier for the project!