Hi Rich, I think I managed this as you said The missing information for me was I need separate ThingAsset and configure AgentLink. Now it’s a lot more clear, thank you!
I’m also able to connect to external broker I’m getting confused in pub sub topic .In which manner we have to write it
like this {realm}/{clientId}/attribute/{attributeName}/{assetId}
or some thing different
thank you
Not an expert on this topic, so hopefully I don’t give false information… Otherwise I will be corrected
In the AgentLink configuration of the attribute of the asset you have created (in addition to the MQTTAgent that you need for the connection) you can add the Publish Topic or Subscription Topic parameters. If you are publishing you can define the topic (e.g. temperature), otherwise if you are subscribing you have to follow the topic name you have set somewhere else.
If this does not work, please explain a bit more about your set up.
Hi Rich,
I have the same problem as OP.
I created an ElectricityConsumerAsset whose parent is my MQTT Agent, connected to an external broker.
If I expand one of the existent attributes, i. e. “power” and add Agent Link, then when I select my MQTT Agent there are no options for publish/subscribe topics:
Is the Demone MQTT Agent of the type ‘MQTTAgent’? The Agent link doesn’t seem to recognize the type (that is why it’s saying ‘no schema match found’ and only gives the JSON option).
If the agent that is selected is the standard MQTT Agent, it will know which form options to show, and you can add the parameters for publish and subscribe topics.
It’s hard to say what’s going wrong without seeing your set up. If I understand correctly you were able to select the MQTTAgent from the Agent Link dropdown, but then it gives you the ‘No schema match found’?
If that is the case I need to call in a developer to come up with a reason why this might happen