https://forge.codesys.com/lib/cobolt/tickets/You searched for labels:"Alias"enFri, 01 Apr 2022 19:09:30 -0000https://forge.codesys.com/lib/cobolt/tickets/146/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.vincentgerWed, 03 Nov 2021 17:32:58 -0000https://forge.codesys.com/lib/cobolt/tickets/146/https://forge.codesys.com/lib/cobolt/tickets/104/It is more data- and processing- efficient to use aliases for metrics than to use the full metric name. A setting should be available to enable aliases. 1. send xBIRTH will send both the name and alias. 2. send xDATA will send only the alias. 3. receive xCMD should match first on Alias, but if no Alias is in the metric then it should match on Name. * [x] Edge and Device Alias xBIRTH and XDATA mechanism are implemented. * [x] Edge and Device decode xCMD alias implemented, * [x] CODESYS Host decodes aliases in xBIRTH and xDATA * [x] CODESYS Host sends alias xCMD Release note: For an Edge, the input to the function UseAliases controls whether aliases are generated and used for each metric in the edge and its child devices. For a Host, the use of aliases is entirely up to the Edge and its Devices - if the edge births with aliases, FB_Host will send NCMDs with aliases. Similarly if a device is birthed with aliases, FB_Host will send DCMDs with aliases.i-campbellFri, 01 Apr 2022 19:09:30 -0000https://forge.codesys.com/lib/cobolt/tickets/104/