Strategy Suggestions Requested for Managing Location Data for Stationary Devices

TagoIO Analysis and Actions
1

Team,

I’d like to be able to show the location of stationary devices on a map widget for a large ranch. There could be 100s of these devices, but they will not move.

What do all of you think the best strategy would be?

  • Store location data, per device in immutable location bucket/device
    • Still have to get it into the bucket and the best way would be scripting, maybe a daily script?
    • Advantage is single device for the map widget (is that good?)
  • Store location data in parameters - do a query when map widget starts
    • Seems to be very logical.
    • It would be sort of real-time- optimizes storage
  • Store location data in parameters - but COPY infrequently to device store
    • Seems to fit better with idea of map widget
    • Requires a copy over analysis script which wouldn’t be horrible.
  • Store location data in TAGS
    • Doesn’t seem like the way TAGS wants to be used, but TAGS are easier than parameters
    • Similar to options above for parameters.

Opinions SOUGHT!!!

Thanks everyone.

Cheers,

Marlan

1 Like
2

Hi Marian,

I think you can do an mixed approach.

You can save the current location of each device in its own device bucket as a normal variable, for example (like storing GPS readings)

The issue is that it’s very awkward to load hundred devices in a single dashboard.

You can to create an analysis script and an auxiliary device/entity, with some action enabled, you can make the analysis write into the aux device bucket and have all the info belong to the same group. For example, this script can query either on demand or scheduled to write all the current locations into a single variable in this aux device. Then you just have to call it once when setting up the dashboard. You will have multiple points with the same group, but only “one” device to manage.

2 Likes