Skip to Content
avatar image
Former Member

How can I use all the Property Categories created for my Digital twin with the IoT Plugin in WebIDE


I have created a digital twin of my Oregon Scientific LW301 Weather Anywhere Meteo Station. This meteo station is composed of different sensors : 3 Thermometers/Hygrometers, 1 Pluviometer, 1 Anemometer and 1 UVmeter.

I have created BasicData and MeasuredData Property Categories for each of those sensors in the defaultPakcage with different Properties in each categories. The ThingType contains 7 (1+6) Basic Data categories (the 1 being the DefaultPropertySet) and 6 Measured Data Categories.

MessageTypes, DeviceTypes and Device have correctly been created automatically in IoT services when creating a Thing out of this ThingType

I’m now trying to create an app with the IoT Plugin in WebIDE

1) At a point in time in the WebIDE wizard, I have to select a PST but what I see is a list of the different “Basic Data” Property Categories I have created for my device (see picture here under) and also the DefaultPropertySet that exist by default.

Which one should I use at this point ?
a) If I use the IoTUIDefaultPropertySet as PST, I can see 6 different Named PST all called DefaultProperty. Are they all the same. I can't distinguish anything from the name and trying to look at each of those they seem to be similar. On top when selection one of those, I can't have access to the properties available for myThingType.

b) If I use one of the PropertySets I have created, it is only reflecting the basic data for one Property category (one sensor category). On top, I can only see the properties of this Property category when defining the Thing List in the wizard. As soon as I have to select the Thing Card Header information by example I can only see "Customer Name" and "Thing Name". I don't even know where those properties are coming from.

I thing I need some advices on how to tackle this Digital Twin and the app creation. Thanks for your precious help as I would like to be able to show quite fast that we can really create interesting digital twins to my IoT prospects !



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 01, 2017 at 05:41 PM

    The (master data) property set you choose drives the initial selection of things shown on the map and in the thing list. The idea is that all of these things have a set of common (master data) properties in common which can be used to differentiate them in e.g. the thing list.

    The additional attributes are coming from the "built-in" (master data) properties every thing has (e.g. thing external id). You can find reference to them in the documentation where they are usually reference with an underscore in front (e.g. _customer).

    The ability to use all of the built-in attributes in all places where things show up in the UI is something that still needs to be developed. The different underlying composite services feeding properties into the ui re-use components (you can see their signature when you use your browsers debugger) do serve up different subsets of properties - hence only a subset is available in any given place in the UI.

    Add comment
    10|10000 characters needed characters exceeded