Dynamic usage of MQTT Machine Attribute / Machine

This might just be a feature request or Iโ€™m missing how to do this.

If I had a takt time counting down on say mqtt topic

Line1/takt
Line2/takt

Is there a way of dynamically show this machine attribute based on a variable. Or show a machine based on a variable.

Ok, writing it out it I found a janky way, you would have to use a TEXT match in a trigger to then set the machine.

I would like real variable input for the machine and the machine attribute :slight_smile:

Hey @mellerbeck -

Right now we donโ€™t support this sort of dynamic (app defined) subscriptions to MQTT - There are 2 different ways that we are looking to support this, on slightly different time horizons:

  1. Add support for wildcards in subscriptions to mqtt in machines - this is a fairly simple addition that will allow some more dynamic subscription. This will likely only support single level wildcards, as it reduces some of the complexity in robust rate limiting.
  2. Add a more generic, and dynamic, way to ingest events into the product without the need for the concept of a machine, which can be overly restrictive to model your shop floor. This would also be something that could be extended to support things like Tulip-hosted webhooks.

#1 is something that we are activly looking into, and #2 is something we are seriously considering for a project next year.

Pete

1 Like