I’ve been testing the Event Streams with the MQTT source (8.3 beta 4). I cant find any way to store the topic in the database? Payload is in the {event.data}, but is the topic avaliable? It seems the {event.metadata} is empty. The topic needs to be included in the event object!
Just starting to have a play around with Event Streams too. Beyond also encountering that there doesn’t appear to be anything in {event.metadata} from MQTT as source, some other feedback for MQTT as a handler:
- Publish Topic to support Handler Expressions - would allow the topic to be dynamic based upon some element of event.data or event.metadata
- Might also be nice to have a button to access the expression builder interface as used throughout other Designer components
- Nominate a Set to publish to, utilising the currently connected server within that Set. Single server selection defeats purpose of defining a Set.
- Also the case when calling system.cirruslink.engine.publish directly from script - that should also support passing in a Set, allowing Engine to determine the appropriate server as connected to
- Ability to select whether to set Retain flag or not - presently not exposed and always not retained
These are all good suggestions. I’ve added issues to our backlog for these.