• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Compound Events - Condition Point Names Confusing

    Wishlist
    2
    3
    2.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mjbcomputers
      last edited by

      When you have allot of points, and are utilizing compound events, the reference numbers in the condition window can get confusing. The only way to figure out your statement is to reference each point by expanding the tree in the event types. This can be very time consuming.

      Can the compound events be setup like the Meta points? This would allow you to assign your own name for the variables in your condition window?

      1 Reply Last reply Reply Quote 0
      • M
        mlohbihler
        last edited by

        Compound events were created before meta points and import/export, and so did not have the same convenient resources around to use. For now they have been excluded from M2M2, but if reintroduced they would be done differently - more like meta points as you suggest.

        Best regards,
        Matthew

        1 Reply Last reply Reply Quote 0
        • First post
          Last post