From 35e5c0de3020d7f7e2d5f935a6351e3dd9759052 Mon Sep 17 00:00:00 2001
From: Sarthak Shaha <sarthak.shaha@silabs.com>
Date: Mon, 26 Feb 2024 15:24:29 -0500
Subject: [PATCH] reverted changes to time-fromat-localization clusters xml

---
 .../zcl/data-model/chip/time-format-localization-cluster.xml     | 1 -
 1 file changed, 1 deletion(-)

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 3753c758df279e..39ba6d316712e3 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,7 +55,6 @@ 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>