0

MQTT Collector Doesn't Honor DataSet Name Change

v24.1 I've got an MQTT collector. For personal reasons, I wanted to change the name of the data set it was writing to. I stopped the instance of the collector and update the DataSet prefix field. Applied it and started it. It continued to write to the old DataSet. I renamed the data set to the new name I wanted and restarted the collector instance. It created a new DataSet with the old name. I ended up deleting the collector instance, applying, and recreating it.

2 replies

null
    • smason
    • 4 wk ago
    • Reported - view

    Hi ,

    If you change the DataSet, that change will only affect new tags that are logged from that point forward. When the collector picks up a tag, it assigns it to the specified DataSet it is configured to use. That information is then stored in a SQLite database and doesn't change unless you clear the Tags table and start again. If you want to start a new DataSet for all of the tags that have already been logging, select the Tags branch from the Configuration screen and click "DELETE ALL". This will wipe out the settings for all of the tags for that subscription. When you re-enable the session, it will pick up the tags again and assign them to the newly designated DataSet.

      • damon_vinciguerra.1
      • 4 wk ago
      • Reported - view

       I gotcha, it's an interesting artifact. But, I can work with that. Thanks!

Content aside

print this pagePrint this page
  • 4 wk agoLast active
  • 2Replies
  • 5Views
  • 2 Following