From ed0d97edcbbc1407470fab0c6c5e320b0cc37866 Mon Sep 17 00:00:00 2001
From: Sarthak Shaha <sarthak.shaha@silabs.com>
Date: Thu, 25 Jan 2024 13:32:55 +0530
Subject: [PATCH] added gloablattributes to
 time-format-localization-cluster.xml

---
 examples/lock-app/lock-common/lock-app.matter                   | 2 +-
 .../zcl/data-model/chip/time-format-localization-cluster.xml    | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/examples/lock-app/lock-common/lock-app.matter b/examples/lock-app/lock-common/lock-app.matter
index fa6051ccc45e01..c0346f9db944ad 100644
--- a/examples/lock-app/lock-common/lock-app.matter
+++ b/examples/lock-app/lock-common/lock-app.matter
@@ -432,7 +432,7 @@ cluster LocalizationConfiguration = 43 {
       or audibly convey time information need a mechanism by which they can be configured to use a
       user’s preferred format. */
 cluster TimeFormatLocalization = 44 {
-  revision 1; // NOTE: Default/not specifically set
+  revision 2;
 
   enum CalendarTypeEnum : enum8 {
     kBuddhist = 0;
diff --git a/src/app/zap-templates/zcl/data-model/chip/time-format-localization-cluster.xml b/src/app/zap-templates/zcl/data-model/chip/time-format-localization-cluster.xml
index 39ba6d316712e3..3753c758df279e 100644
--- a/src/app/zap-templates/zcl/data-model/chip/time-format-localization-cluster.xml
+++ b/src/app/zap-templates/zcl/data-model/chip/time-format-localization-cluster.xml
@@ -55,6 +55,7 @@ limitations under the License.
       may have differing preferences for how dates and times are conveyed. As such, Nodes that visually
       or audibly convey time information need a mechanism by which they can be configured to use a
       user’s preferred format.</description>
+    <globalAttribute side="either" code="0xFFFD" value="2"/>    
     <!-- Base data types -->
     <attribute side="server" code="0x00" define="HOUR_FORMAT" type="HourFormatEnum" writable="true" optional="false">
         <description>HourFormat</description>