MQTT Topic "40hero/delaware/office/iiotdemo/devices/S8VKX" payload

{
  "timestamp": 1729185434378,
  "schema": "s8vkx",
  "Status": {
    "MemoryErr": false,
    "OverheatAbn": false,
    "CurrentMeasErr": false,
    "VoltageMeasErr": false,
    "OverheatingAlm": false,
    "YearsToReplaceFUL": true,
    "YearsToReplaceHLF": false
  },
  "OutputVoltage": 24.2,
  "OutputCurrent": 2.2,
  "PeakHoldCurrent": 5,
  "YearsToReplace": 14.6,
  "PercentToReplace": 97.4,
  "TotalRunTime": 3438,
  "ContinuousRunTime": 24323
}

This processing code

# these variables are autogenerated from your instance location
let enterprise = "40Hero"
let site = "Delaware"
let area = "office"
let line = "iiotdemo"
let schema = "_historian"

let tagname = "mytag"

let value = this.without("timestamp")  # Remove the timestamp field
value.timestamp_ms = this.timestamp  # Add new field timestamp_ms

produces this in the historian

the tagname is repeated.....

tag browser

I discovered that my "repeated" tag name is related to the variable "payloadTagName" now if I use this code

# these variables are autogenerated from your instance location
let enterprise = "40Hero"
let site = "Delaware"
let area = "office"
let line = "iiotdemo"
let schema = "_historian"

let tagname = "mytag"
let payloadTagName = "myPayloadTagName"
# Directly modify the root object to remove timestamp and add timestamp_ms
let value = this.without("timestamp")  # Remove the timestamp field
value.timestamp_ms = this.timestamp  # Add new field timestamp_ms

I get this in the historian....

and now the new tag in the tag browser

more info....I deleted everything in the tag table and tag_string table.... weirdly I don't have any mytag$mytag names....but the tag browser shows what looks like there is?

I like the implicit idea of using the topic structure as long as it doesn’t repeat. But it should also be an option to explicitly define the tag and grouping in the processor. It’s just unclear to me how they relate. The conditions of when and how it uses the topic implicitly or how it works explicitly. This case OR this case

Use topic structure if tag name and tag group are undefined in the processor.

If it fetches from kafka....why did deleting the tags in the DB delete everything else except this.... I used to have lots of tags....because i've been testing and it was a mess.

but the PoC is technically complicated so it will not be easy :/ it involves adjusting kafka to allow to be again one MQTT topic = one Kafka Topic (without Kafka keys)

then we can just query all topics and we are ready to go

for reference, this is how I ended up getting what I desired.... "tagname" used as the "group" and "payloadTagName" used as my tag name, which is just the last part of the topic. Then each key from the payload shows below that.

# these variables are autogenerated from your instance location
let enterprise = "40Hero"
let site = "Delaware"
let area = "office"
let line = "iiotdemo"
let schema = "_historian"

let tagname = "devices"
let mqtt_topic_appendix = meta("mqtt_topic").replace_all("40hero/delaware/office/iiotdemo/devices/", "")
let mqtt_topic_appendix_sanitized = $mqtt_topic_appendix.replace_all("/", ".")
let payloadTagName = $mqtt_topic_appendix_sanitized

let value = this.without("timestamp")  # Remove the timestamp field
value.timestamp_ms = this.timestamp  # Add new field timestamp_ms

Our idea was to: 1. have the tag browser show all current and previous tags (even across restarts) in kafka 2. when you click on a tag, be also able to see th real-time data (done) 3. when you click on a tag, be also able to query the historical data besides just showing the sql command 4. extend the filter function to allow also fitlering by "metadata" (so static information that might be appended to some payloads with the key "metadata") and allow more complex queries. Then you would be able to search for your tags like "select all tags where "type=energy-meter" and "site=cologne" 5. maybe provide this also as an API is this what you mean?