1.1. What problem does Macros solve?

Macros are helpful for the extended customization of a trivum solution. They enable a sequence of several actions to be defined as one action, which can then be called in several ways, like by a single button push, or an HTTP call, or by KNX.

1.2. How does trivum implement Macros?

trivum defines macros as a sequence of macro steps that can be any actions:

  • Arbitrary trivum action (e.g. start source in a zone, group, volume etc)

  • Pause for a predefined amount of time

  • Send a KNX telegram

  • Send an HTTP request

  • Send a TCP/IP command

  • Send a UDP command

  • Send an MQTT message

1.3. Benefits of Macros

Macros increase the flexibility of the trivum systems and also enable the control of devices in the network thanks to TCP, UDP or MQTT.

Macros expand the possibilities of automating a trivum installation.

1.4. How can you customize Macros?

trivum supports up to 128 macros, each with up to 32 macro steps.

For each macro, the name can be changed and the various MacroSteps can be created. The order of the MacroSteps can be changed afterwards and individual MacroSteps can also be deleted.

Different properties can be changed depending on the MacroStep.

  • trivum action: Choice of zone

  • Wait action: Waiting time in milliseconds

  • KNX

    • Group address, e.g. 3/4/5

    • data type (bool, uint8, uint16, text14)

    • Data to send

      Please note: To control a KNX object, it is also possible to create an object in the 'Automation' area and there under 'Automation Objects'. These objects then provide actions that can also be addressed using a 'trivum action'.

  • UDP

    • IP Address (IPV4)

    • port

    • Data

  • TCP

    • IP Address

    • port

    • Data

  • HTTP

    • IP Address

    • port

    • Data

  • MQTT

    • topic

    • Value

    • Option for retain

1.5. What are the limitations of Macros?

  1. The individual MacroSteps do not check whether UDP, TCP, HTTP, MQTT or KNX messages have arrived at the recipient.

  2. It is not possible to evaluate any messages received from other network devices.

  3. HTTP commands do not support HTTPS.