Deploy preview for PR 4 🛫

project-chip · Jan 30, 2024 · f34c07f · f34c07f
1 parent 181de81
commit f34c07f
Show file tree

Hide file tree

Showing 26 changed files with 302 additions and 302 deletions.
diff --git a/pr-preview/pr-4/404.html b/pr-preview/pr-4/404.html
@@ -1 +1 @@
-<!doctype html><html lang=en class="js csstransforms3d"><head><meta charset=utf-8><meta name=description content><link rel=icon href=/matter-handbook/pr-preview/pr-4/images/favicon.png type=image/png><title>404 Page not found</title><link href=/matter-handbook/pr-preview/pr-4/css/nucleus.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/fontawesome-all.min.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/hybrid.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/featherlight.min.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/perfect-scrollbar.min.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/theme.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/hugo-theme.css?1706623578 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/theme-matter.css?1706623578 rel=stylesheet><style>:root #header+#content>#left>#rlblock_left{display:none!important}p,li,ul{text-align:center}ul{list-style-type:none}</style></head><body data-url=/><section id=body style=margin-left:0><div id=overlay></div><div id=chapter><div id=body-inner><h1>Error</h1><p></p><p>Woops. Looks like this page doesn't exist ¯\_(ツ)_/¯.</p><p></p><p><a href=/matter-handbook/pr-preview/pr-4>Go to homepage</a></p><p><img src=/images/gopher-404.jpg style=width:50% alt="Page not found!"></p></div></div></section></body></html>
+<!doctype html><html lang=en class="js csstransforms3d"><head><meta charset=utf-8><meta name=description content><link rel=icon href=/matter-handbook/pr-preview/pr-4/images/favicon.png type=image/png><title>404 Page not found</title><link href=/matter-handbook/pr-preview/pr-4/css/nucleus.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/fontawesome-all.min.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/hybrid.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/featherlight.min.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/perfect-scrollbar.min.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/theme.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/hugo-theme.css?1706623619 rel=stylesheet><link href=/matter-handbook/pr-preview/pr-4/css/theme-matter.css?1706623619 rel=stylesheet><style>:root #header+#content>#left>#rlblock_left{display:none!important}p,li,ul{text-align:center}ul{list-style-type:none}</style></head><body data-url=/><section id=body style=margin-left:0><div id=overlay></div><div id=chapter><div id=body-inner><h1>Error</h1><p></p><p>Woops. Looks like this page doesn't exist ¯\_(ツ)_/¯.</p><p></p><p><a href=/matter-handbook/pr-preview/pr-4>Go to homepage</a></p><p><img src=/images/gopher-404.jpg style=width:50% alt="Page not found!"></p></div></div></section></body></html>
diff --git a/pr-preview/pr-4/alliance/howwework/index.html b/pr-preview/pr-4/alliance/howwework/index.html
diff --git a/pr-preview/pr-4/alliance/index.html b/pr-preview/pr-4/alliance/index.html
diff --git a/pr-preview/pr-4/alliance/membership/index.html b/pr-preview/pr-4/alliance/membership/index.html
diff --git a/pr-preview/pr-4/alliance/resources/index.html b/pr-preview/pr-4/alliance/resources/index.html
diff --git a/pr-preview/pr-4/alliance/whatwedo/index.html b/pr-preview/pr-4/alliance/whatwedo/index.html
diff --git a/pr-preview/pr-4/categories/index.html b/pr-preview/pr-4/categories/index.html
diff --git a/pr-preview/pr-4/howitworks/attestation/index.html b/pr-preview/pr-4/howitworks/attestation/index.html
diff --git a/pr-preview/pr-4/howitworks/commisioning/index.html b/pr-preview/pr-4/howitworks/commisioning/index.html
diff --git a/pr-preview/pr-4/howitworks/connectivitytransports/index.html b/pr-preview/pr-4/howitworks/connectivitytransports/index.html
diff --git a/pr-preview/pr-4/howitworks/datamodel/index.html b/pr-preview/pr-4/howitworks/datamodel/index.html
diff --git a/pr-preview/pr-4/howitworks/devicetypes/index.html b/pr-preview/pr-4/howitworks/devicetypes/index.html
diff --git a/pr-preview/pr-4/howitworks/discovery/index.html b/pr-preview/pr-4/howitworks/discovery/index.html
diff --git a/pr-preview/pr-4/howitworks/fabric/index.html b/pr-preview/pr-4/howitworks/fabric/index.html
diff --git a/pr-preview/pr-4/howitworks/index.html b/pr-preview/pr-4/howitworks/index.html
diff --git a/pr-preview/pr-4/howitworks/index.xml b/pr-preview/pr-4/howitworks/index.xml
@@ -6,7 +6,7 @@ Lighting On/Off Light Dimmable Light Color Temperature Light Extendded Color Lig
 Devices and Endpoints All Devices, including smartphones and home assistants, are composed of Nodes. A Node is a unique identifiable and addressable resource in a network that a user can perceive as functionally whole. Network communication in Matter originates and terminates at a Node.</description></item><item><title>Connectivity Transports</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/connectivitytransports/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/connectivitytransports/</guid><description>In principle, any IPv6-bearing network is suitable for Matter deployment, subject to supporting a few core IPv6 standards. In the current version of the specification, we focus on three link layer technologies: Ethernet, Wi-Fi and Thread. We restrict the specification to the above so that the specification can suitably cover provisioning of these link layers, and so that the amount of testing in certification is suitably bounded.
 Matter treats networks as shared resources: it makes no stipulation of exclusive network ownership or access.</description></item><item><title>Interaction Model</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/interactionmodel/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/interactionmodel/</guid><description>Concepts The Data Model (DM) of a Node isn&amp;rsquo;t relevant if we can&amp;rsquo;t perform operations on them. The Interaction Model (IM), defines a Node&amp;rsquo;s DM relationship with the DM of other Nodes: a common language for communication between DMs.
 Nodes interact with each other by:
-Reading and Subscribing to Attributes and Events Writing to Attributes Invoking Commands Whenever a Node establishes an encrypted communication sequence with another Node, they constitute an Interaction relationship.</description></item><item><title>Discovery</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</guid><description>Commissionable discovery Commissionable discovery happens before Commissioning and refers to the process of discovering and identifying a commissionable Node. There are three methods through which a commissionable Node may advertise itself:
+Reading and Subscribing to Attributes and Events Writing to Attributes Invoking Commands Whenever a Node establishes an encrypted communication sequence with another Node, they constitute an Interaction relationship.</description></item><item><title>Discovery</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</guid><description>Commissionable discovery Commissionable discovery happens before Commissioning and refers to the process of discovering and identifying a commissionable Node. There are two methods through which a commissionable Node may advertise itself:
 Bluetooth low energy (BLE) DNS-SD on an any IP network the Node is connected to In either method, the commissionable node advertises information as shown in the table below.
 Field Length Required Discriminator 12 bit Yes Vendor ID 16 bit No Product ID 16 bit No Extended data variable No As per the Matter specification, Vendor ID and Product ID are not required but can be included.</description></item><item><title>The Fabric</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/fabric/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/fabric/</guid><description>The Matter spec uses sophisticated methods for encrypting and decrypting information, as well as safe mechanisms for assuring a Node&amp;rsquo;s identity and sharing cryptographic credentials.
 Whenever a set of Devices in a network shares the same security domain, and thus allows secure communication between Nodes, this set is called a Fabric. Devices within a fabric share the same Certificate Authority (CA) top-level certificate (Root of Trust) and a 64-bit identifier named Fabric ID, unique within the context of that CA.</description></item><item><title>Commissioning</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/commisioning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/commisioning/</guid><description>Commissioning in Matter refers to the process of assigning Fabric credentials to a new device or app. The Commissioner is the device or app that does the Commissioning process. The Commissionee is the new device or app that needs to be provisioned into the Fabric.

diff --git a/pr-preview/pr-4/howitworks/interactionmodel/index.html b/pr-preview/pr-4/howitworks/interactionmodel/index.html
diff --git a/pr-preview/pr-4/howitworks/roles/index.html b/pr-preview/pr-4/howitworks/roles/index.html
diff --git a/pr-preview/pr-4/howitworks/security/index.html b/pr-preview/pr-4/howitworks/security/index.html
diff --git a/pr-preview/pr-4/howitworks/thread/index.html b/pr-preview/pr-4/howitworks/thread/index.html
diff --git a/pr-preview/pr-4/howitworks/whatismatter/index.html b/pr-preview/pr-4/howitworks/whatismatter/index.html
diff --git a/pr-preview/pr-4/index.html b/pr-preview/pr-4/index.html
diff --git a/pr-preview/pr-4/index.xml b/pr-preview/pr-4/index.xml
@@ -13,7 +13,7 @@ Devices and Endpoints All Devices, including smartphones and home assistants, ar
 Matter treats networks as shared resources: it makes no stipulation of exclusive network ownership or access.</description></item><item><title>Resources</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/alliance/resources/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/alliance/resources/</guid><description>Resources for Members If you are already a member of the Alliance, here are some helpful links found in Causeway (you&amp;rsquo;ll need to log in with your member credentials).
 New Member Orientation Slides Group Links Matter Working Group How to Join the Matter Working Group and Subgroups (pg. 32-35) Meeting Calendar for Matter Working Groups and Subroups Not seeing a calendar for a specific group? Make sure you’re a member of that group for visibility Subgroups Matter CSG Matter MPSG Matter TSG Tools Collaboration Tools (pg.</description></item><item><title>Interaction Model</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/interactionmodel/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/interactionmodel/</guid><description>Concepts The Data Model (DM) of a Node isn&amp;rsquo;t relevant if we can&amp;rsquo;t perform operations on them. The Interaction Model (IM), defines a Node&amp;rsquo;s DM relationship with the DM of other Nodes: a common language for communication between DMs.
 Nodes interact with each other by:
-Reading and Subscribing to Attributes and Events Writing to Attributes Invoking Commands Whenever a Node establishes an encrypted communication sequence with another Node, they constitute an Interaction relationship.</description></item><item><title>Discovery</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</guid><description>Commissionable discovery Commissionable discovery happens before Commissioning and refers to the process of discovering and identifying a commissionable Node. There are three methods through which a commissionable Node may advertise itself:
+Reading and Subscribing to Attributes and Events Writing to Attributes Invoking Commands Whenever a Node establishes an encrypted communication sequence with another Node, they constitute an Interaction relationship.</description></item><item><title>Discovery</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/discovery/</guid><description>Commissionable discovery Commissionable discovery happens before Commissioning and refers to the process of discovering and identifying a commissionable Node. There are two methods through which a commissionable Node may advertise itself:
 Bluetooth low energy (BLE) DNS-SD on an any IP network the Node is connected to In either method, the commissionable node advertises information as shown in the table below.
 Field Length Required Discriminator 12 bit Yes Vendor ID 16 bit No Product ID 16 bit No Extended data variable No As per the Matter specification, Vendor ID and Product ID are not required but can be included.</description></item><item><title>The Fabric</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/fabric/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/fabric/</guid><description>The Matter spec uses sophisticated methods for encrypting and decrypting information, as well as safe mechanisms for assuring a Node&amp;rsquo;s identity and sharing cryptographic credentials.
 Whenever a set of Devices in a network shares the same security domain, and thus allows secure communication between Nodes, this set is called a Fabric. Devices within a fabric share the same Certificate Authority (CA) top-level certificate (Root of Trust) and a 64-bit identifier named Fabric ID, unique within the context of that CA.</description></item><item><title>Commissioning</title><link>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/commisioning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://project-chip.github.io/matter-handbook/pr-preview/pr-4/howitworks/commisioning/</guid><description>Commissioning in Matter refers to the process of assigning Fabric credentials to a new device or app. The Commissioner is the device or app that does the Commissioning process. The Commissionee is the new device or app that needs to be provisioned into the Fabric.

diff --git a/pr-preview/pr-4/sdk/index.html b/pr-preview/pr-4/sdk/index.html
diff --git a/pr-preview/pr-4/specification/index.html b/pr-preview/pr-4/specification/index.html
diff --git a/pr-preview/pr-4/tags/index.html b/pr-preview/pr-4/tags/index.html