#146 Metric Alias

2.0.0.0: Device
closed
nobody
Alias (2)
2021-11-03
2021-11-02
vincentger
No

Hey guys ,

i am fairly new in the MQTT topic. I am trying to replicate a metric structure that other devices already send to an existing server and got quite far with it:

Mine:

{"timestamp":1635884974801,"metrics":[{"name":"output/Z01Power","timestamp":1635884974801,"dataType":"Int16","value":371}],"seq":20}

Existing Devices:

{"timestamp":1635863671694,"metrics":[{"name":"output/Z01Power","alias":330,"timestamp":1635863667777,"dataType":"Int16","value":264}],"seq":141}

I cant figure out how to add the "alias" property/attribute to the message.

Discussion

  • hermsen

    hermsen - 2021-11-03
    • status: open --> closed
     

  • hermsen

    hermsen - 2021-11-03

    Hi,

    thank you for your interest in our library.

    My previous reply seems binned somehow so here goes again.

    We are on the verge between implementation and testing of the new Alias mechanism. This is why the current binary does contain alias support yet.

    When alias support is sufficiently tested we will update the binaries so you can enjoy it.

    Alias is a mechanism that enables a small optimization in communication.
    Aliases are automatically assigned to metrics during only BIRTH. Aliases should therefor not be confused with Properties.

    Only metrics can have an Alias, Aliases are fully automatic ically assigned during NBIRTH/DBIRTH phase. Aliases cannot and nay not be changed during normal communication. Usually only Edges utilise Aliases.

    I have closed this ticket since aliases are adressed in ticket [#104].

    With kind regards,

    Team co5e

     

    Related

    Tickets: #104


    Last edit: hermsen 2021-11-04

Log in to post a comment.