Hey @Nicolas_Mascardi ,
It looks like you have a custom topic configured edgeAgent/logs in your MQTT nodes. With the access key and secret you have configured have you enabled access to all MQTT topics?
By default access keys only allow access to the device-specific topics (e.g. state and commands ) for every device you have allowed. So you’ll need to configure access to those custom topics you have defined (https://docs.losant.com/applications/access-keys/#additional-mqtt-topics-access ).
This is a great question, and its not uncommon, we’ve had a few forum threads around this topic that may help guide you as well:
Pro tip! The Losant MQTT Broker can now support custom topics . Custom topics can trigger workflows with the MQTT Trigger Node or can be published to using the MQTT Output Node .
[tip]
We’ll be back next Tuesday with a new tip. Until then, keep exploring
Hey @Lars_Andersson !
Below are some screenshots on how you can set a custom MQTT topic and set up a workflow to report state for devices. It is important to note that for this example, the MQTT message included a “devices” array in the message.
First, with an MQTT node, you can set the custom MQTT topic.
[Screen Shot 2020-06-10 at 11.44.00 AM]
Once you’re sending MQTT messages to that topic, you can use a JSON: Decode node to format the string to an Object.
[Screen Shot 2020-06-10 at 11.4…
Let me know if this gets you on the right path!
Thanks,@Aidan_Zebertavage
1 Like