Skip to content

DIM1 ‐ Device Identity

Jump to bottom
anotherjulien edited this page Sep 14, 2026 · 1 revision

Overview

DIM1 provides the primary catalogue identity signature of a Device.

For WHO1001, the observed structure is:

*#1001*WHERE*1*VALUE1*VALUE2*VALUE3*VALUE4##

Three of the four values can be correlated with the MHCatalogue database:

Field Catalogue mapping
VALUE1 AS_ITEM_SYSTEM.modobj
VALUE2 Unknown
VALUE3 EN_BRAND.brand_modobj
VALUE4 EN_LINE.line_modobj

Together, the known values can be used to resolve a diagnostic Device to its catalogue model, commercial brand, collection, and possible SKUs.

The resulting identification can be represented as:

Brand [Collection] SKU(s)

For example:

Arnould [Espace Evolution] 64191 / 64192 / 64391

Frame Structure

The observed WHO1001 form is:

*#1001*WHERE*1*VALUE1*VALUE2*VALUE3*VALUE4##

For example:

*#1001*01*1*107*6*6*8##

which gives:

Field Value
WHERE 01
VALUE1 107
VALUE2 6
VALUE3 6
VALUE4 8

WHERE belongs to the diagnostic addressing context and is not part of the catalogue identity signature itself.

VALUE1 - Catalogue Model

VALUE1 maps to:

AS_ITEM_SYSTEM.modobj

This is the principal link between the diagnostic frame and the catalogue Device model.

The resolution path is:

DIM1.VALUE1
     │
     ▼
AS_ITEM_SYSTEM.modobj
     │
     ▼
AS_ITEM_SYSTEM.id_item
     │
     ▼
EN_ITEM.id_item

EN_ITEM represents the common catalogue item underlying one or more commercial Device variants.

For the example:

VALUE1 = 107

the corresponding catalogue item is:

Flush mounted actuator and free control

Multiple commercial SKUs can therefore share the same VALUE1.

VALUE2 - Unknown

The meaning of VALUE2 has not been established.

For the example:

VALUE2 = 6

No sufficiently reliable mapping to the MH Catalogue has been demonstrated.

It must therefore remain:

Unknown

VALUE2 should not currently be interpreted as an Object, Virgin Object, Device class, form factor, firmware class, electronic platform, or other catalogue classification.

It is not required for the catalogue-resolution process documented on this page.

VALUE3 - Brand

VALUE3 maps to:

EN_BRAND.brand_modobj

The corresponding catalogue lookup is:

DIM1.VALUE3
     │
     ▼
EN_BRAND.brand_modobj
     │
     ▼
EN_BRAND.brand_name

For the example:

VALUE3 = 6

the matching commercial brand is:

Arnould

The resulting EN_BRAND.id_brand can then be used to restrict the commercial Device records associated with the catalogue item.

VALUE4 - Collection

VALUE4 maps to:

EN_LINE.line_modobj

EN_LINE represents the commercial product line or collection.

The lookup is:

DIM1.VALUE4
     │
     ▼
EN_LINE.line_modobj
     │
     ▼
EN_LINE.line_name

For:

VALUE4 = 8

the corresponding collection is:

Espace Evolution

The catalogue therefore identifies the commercial context as:

Arnould [Espace Evolution]

Resolving the SKU

Commercial Device Records

Once VALUE1, VALUE3, and VALUE4 have been resolved, the corresponding records in EN_DEVICE can be selected.

The relevant relationships are:

DIM1.VALUE1
      │
      ▼
AS_ITEM_SYSTEM.modobj
      │
      ▼
    id_item
      │
      └──────────────┐
                     ▼
                 EN_DEVICE
                  │     │
             id_brand  id_line
                  │     │
                  ▼     ▼
              EN_BRAND EN_LINE

The commercial SKU is stored in:

EN_DEVICE.code

while the standard Device description is available in:

EN_DEVICE.name

The resulting lookup conditions are conceptually:

AS_ITEM_SYSTEM.modobj = VALUE1

EN_BRAND.brand_modobj = VALUE3

EN_LINE.line_modobj = VALUE4

The matching EN_DEVICE rows then provide the possible SKUs.

Complete Example

Consider:

*#1001*01*1*107*6*6*8##

Ignoring the unresolved VALUE2, the known identity signature is:

VALUE1 = 107
VALUE3 = 6
VALUE4 = 8

Step 1 - Resolve the Model

VALUE1=107 matches:

AS_ITEM_SYSTEM.modobj = 107

which resolves to catalogue item 1184:

Flush mounted actuator and free control

This catalogue item is shared by several commercial Device variants.

Step 2 - Resolve the Brand

VALUE3=6 matches:

EN_BRAND.brand_modobj = 6

giving:

Arnould

Step 3 - Resolve the Collection

VALUE4=8 matches:

EN_LINE.line_modobj = 8

giving:

Espace Evolution

Step 4 - Resolve the Commercial Devices

The matching EN_DEVICE records are:

Brand Collection SKU Device description
Arnould Espace Evolution 64191 Flush mounted actuator and free control
Arnould Espace Evolution 64192 Flush mounted actuator and free control
Arnould Espace Evolution 64391 Flush mounted actuator and free control

The DIM1 frame can therefore be rendered as:

Arnould [Espace Evolution] 64191 / 64192 / 64391

with the standard Device description:

Flush mounted actuator and free control

Why Multiple SKUs Can Match

DIM1 does not necessarily identify a unique commercial SKU.

This is because the MH Catalogue separates the underlying Device model from its commercial variants.

For the previous example, VALUE1=107 identifies the common catalogue item:

Flush mounted actuator and free control

That same item exists in several brands and collections.

Without applying VALUE3 and VALUE4, the catalogue contains variants such as:

BTicino [Axolute] H4671M2
BTicino [L/N/NT] LN4671M2
BTicino [Matix] AM5851M2
Legrand [Arteor] 573961
Legrand [Celiane] 067249 / 067556
Arnould [Espace Evolution] 64191 / 64192 / 64391

VALUE3 and VALUE4 therefore provide important commercial discrimination:

VALUE1
  │
  ▼
Common Device model
  │
  ├── Brand / Collection A
  ├── Brand / Collection B
  ├── Brand / Collection C
  │
  └── VALUE3 + VALUE4
             │
             ▼
      Matching commercial
          variant(s)

Even after applying brand and collection, several SKUs can remain.

DIM1 should therefore normally be interpreted as identifying a catalogue Device family and commercial variant set, rather than necessarily identifying one exact SKU.

Catalogue Query

Conceptually, the resolution can be performed with a query of the following form:

SELECT
    b.brand_name,
    l.line_name,
    d.code,
    d.name
FROM AS_ITEM_SYSTEM ais
JOIN EN_ITEM i
    ON i.id_item = ais.id_item
JOIN EN_DEVICE d
    ON d.id_item = i.id_item
JOIN EN_BRAND b
    ON b.id_brand = d.id_brand
JOIN EN_LINE l
    ON l.id_line = d.id_line
WHERE ais.modobj = :VALUE1
  AND b.brand_modobj = :VALUE3
  AND l.line_modobj = :VALUE4;

For:

VALUE1 = 107
VALUE3 = 6
VALUE4 = 8

the result is:

Arnould [Espace Evolution] 64191
Arnould [Espace Evolution] 64192
Arnould [Espace Evolution] 64391

These can be combined for display as:

Arnould [Espace Evolution] 64191 / 64192 / 64391

Standard Device Description

The commercial SKU should be distinguished from the standard Device description.

EN_DEVICE.code provides the SKU:

64391

while EN_DEVICE.name provides the standard Device description:

Flush mounted actuator and free control

When describing the physical Device in diagnostic documentation, EN_DEVICE.name should be preferred as the standard MyHOME Suite-facing Device description.

The complete resolved information can therefore be represented as:

Device:
Flush mounted actuator and free control

Commercial variants:
Arnould [Espace Evolution] 64191 / 64192 / 64391

Identification Model

The complete DIM1 catalogue-resolution model is:

                    DIM1
                     │
       ┌─────────────┼─────────────┬─────────────┐
       │             │             │             │
    VALUE1        VALUE2        VALUE3        VALUE4
       │             │             │             │
       ▼             ▼             ▼             ▼
AS_ITEM_SYSTEM    UNKNOWN       EN_BRAND       EN_LINE
   .modobj                    .brand_modobj   .line_modobj
       │                           │             │
       ▼                           ▼             ▼
    EN_ITEM                     Brand        Collection
       │                           │             │
       └─────────────┬─────────────┴─────────────┘
                     ▼
                  EN_DEVICE
                     │
             ┌───────┴────────┐
             ▼                ▼
           code              name
             │                │
             ▼                ▼
           SKU(s)       Device description

The resulting commercial identity can be rendered as:

Brand [Collection] SKU(s)

Limitations

DIM1 should not automatically be interpreted as a unique SKU identifier.

Several SKUs can share:

  • the same underlying catalogue item;
  • the same brand;
  • the same collection;
  • the same diagnostic DIM1 signature.

Consequently:

DIM1
  │
  ▼
Catalogue identity
  │
  ▼
Brand + Collection + possible SKU(s)

is currently a more accurate model than:

DIM1 → exact SKU

Additional Device information may be required when a unique commercial SKU must be determined.

Summary

DIM1 provides the principal bridge between a live diagnostic Device and the MH Catalogue.

For WHO1001:

VALUE1 → AS_ITEM_SYSTEM.modobj
VALUE2 → UNKNOWN
VALUE3 → EN_BRAND.brand_modobj
VALUE4 → EN_LINE.line_modobj

The known values can be combined to resolve:

Device model
     +
Brand
     +
Collection
     │
     ▼
Matching EN_DEVICE records
     │
     ▼
Brand [Collection] SKU(s)

For:

*#1001*01*1*107*6*6*8##

the MH Catalogue resolves the commercial identity to:

Arnould [Espace Evolution] 64191 / 64192 / 64391

and the standard Device description to:

Flush mounted actuator and free control

VALUE2 remains unknown and is not required for this resolution.

See Also

Clone this wiki locally