Difference between revisions of "Mesh Network"
From AMTech WikiDocs
(→Mesh Validations) |
|||
| Line 4: | Line 4: | ||
A set of stpg instances form a valid mesh if the following conditions are met: | A set of stpg instances form a valid mesh if the following conditions are met: | ||
| − | * | + | * All instances must be valid for its metadata |
| − | * Mesh id | + | * Mesh id unique for templates in tenant (networkId property in the sc json) |
* there must be a single root node (mode=1 or mode=3 in the sc json) | * there must be a single root node (mode=1 or mode=3 in the sc json) | ||
* all instances must have the same mesh id (meshId property in the sc json) | * all instances must have the same mesh id (meshId property in the sc json) | ||
* all instances must have the same channel | * all instances must have the same channel | ||
* if using encryption, all instances must have the same seed | * if using encryption, all instances must have the same seed | ||
Latest revision as of 15:09, 19 November 2020
A Mesh network is composed of a root and multiple nodes, all thing instances of the type stpg (Smart Tracker Proximity Gateway)
Mesh Validations
A set of stpg instances form a valid mesh if the following conditions are met:
- All instances must be valid for its metadata
- Mesh id unique for templates in tenant (networkId property in the sc json)
- there must be a single root node (mode=1 or mode=3 in the sc json)
- all instances must have the same mesh id (meshId property in the sc json)
- all instances must have the same channel
- if using encryption, all instances must have the same seed
