Gateway Identification Practical Guide #29
anotherjulien
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A new Practical Guide, Identify an OpenWebNet Gateway, has been added to the Encyclopedia as a specialized instance of Read and Present a Device Configuration.
The guide addresses a recurring problem: reliably determining the catalogue identity of an unknown OpenWebNet gateway from protocol traffic.
The key finding is that
WHO 13 DIMENSION 15cannot always identify a gateway uniquely. In observed captures, both an MH202 and an F454 returnDIM15 = 200. The guide therefore continues identification through diagnosticWHO 1013 DIMENSION 1, which returnsOBJECT_MODEL,N_CONF,BRAND, andLINE.It then shows how to resolve
OBJECT_MODEL,BRAND, andLINEagainstMHCatalogue.db, using the Integration Functions catalogue context, to obtain the correspondingEN_DEVICEcatalogue identity and SKU.The MH202 and F454 captures are included as worked examples, demonstrating how the same
DIM15value is disambiguated byOBJECT_MODEL = 5versusOBJECT_MODEL = 51.The guide also makes the evidence boundaries explicit: it keeps
WHO 13 DIMENSION 15and diagnosticDIMENSION 1.OBJECT_MODELas separate namespaces, does not infer unsupported compatibility behavior, and treats missing diagnostic responses or catalogue matches as unresolved rather than guessing.Relevant Practical Guide navigation and the
WHO 13/ diagnosticDIMENSION 1reference pages were updated to point to the new workflow.All reactions