Sync driver source with working channel-published version

- Revert init.lua to drop GeneralDiagnostics.ActiveHardwareFaults
  subscription that crashed the driver on load
- Use the generic profile filename matter-lock-contact-tamper.yml
  (previous gatelock-matter.yml predated the rename)
- Update fingerprints.yml to reference the renamed profile
- Restore README tamper-alert section to the DoorLockAlarm event path

Author: Econet-Controls-Inc

drivers/EconetControlsInc/bulldog-gatelock/README.md

@@ -23,12 +23,7 @@ The reed switch on GPIO0.28 triggers `sendDoorStateChangeAlarmEvent()` in firmwa
 
 ## Tamper alert
 
-When the keypad's 4-strikes-in-20-seconds brute-force protection trips, the firmware:
-
-1. Adds `kTamperDetected (10)` to `GeneralDiagnostics.ActiveHardwareFaults` on endpoint 0 (also emits the `HardwareFaultChange` event).
-2. Fires a legacy `DoorLockAlarm` event with `alarmCode = kWrongCodeEntryLimit (4)` for backwards compatibility.
-
-The driver subscribes to the `ActiveHardwareFaults` attribute and maps list membership directly to the **tamperAlert** capability — `tampered` while the list contains `10`, `clear` when the firmware removes it (which happens automatically when the lockout window expires). The legacy `DoorLockAlarm` event handler is retained so older firmware builds that only fire the event still surface a `tampered` state.
+When the keypad's 4-strikes-in-20-seconds brute-force protection trips, the firmware fires a `DoorLockAlarm` event with `alarmCode = kWrongCodeEntryLimit (4)`. The driver maps this to the standard **tamperAlert** capability ("tampered" badge in the app). The state stays `tampered` until the driver re-initializes; on init the driver emits `clear`.
 
 ## Prerequisites
 

drivers/EconetControlsInc/bulldog-gatelock/fingerprints.yml

@@ -1,6 +1,6 @@
 matterManufacturer:
   - id: "econet-gatelock"
-    deviceProfileName: gatelock-matter
+    deviceProfileName: matter-lock-contact-tamper
     vendorId: 0x1568        # Econet Controls Inc (5480)
     productId: 0x000A         # 10 (Bulldog GateLock)
     deviceTypes:

…og-gatelock/profiles/gatelock-matter.yml …/profiles/matter-lock-contact-tamper.ymldrivers/EconetControlsInc/bulldog-gatelock/profiles/gatelock-matter.yml renamed to drivers/EconetControlsInc/bulldog-gatelock/profiles/matter-lock-contact-tamper.yml drivers/EconetControlsInc/bulldog-gatelock/profiles/gatelock-matter.yml renamed to drivers/EconetControlsInc/bulldog-gatelock/profiles/matter-lock-contact-tamper.yml

@@ -1,4 +1,4 @@
-name: gatelock-matter
+name: matter-lock-contact-tamper
 components:
   - id: main
     capabilities:

drivers/EconetControlsInc/bulldog-gatelock/src/init.lua

@@ -9,12 +9,10 @@ local MatterDriver = require "st.matter.driver"
 local clusters = require "st.matter.clusters"
 local capabilities = require "st.capabilities"
 
-local DoorLock           = clusters.DoorLock
-local PowerSource        = clusters.PowerSource
-local GeneralDiagnostics = clusters.GeneralDiagnostics
+local DoorLock    = clusters.DoorLock
+local PowerSource = clusters.PowerSource
 
-local UNLATCHED_STATE              = 0x3
-local HARDWARE_FAULT_TAMPER_DETECTED = 10
+local UNLATCHED_STATE = 0x3
 
 ----------------------------------------------------------------------
 -- ATTRIBUTE HANDLERS
@@ -52,38 +50,10 @@ local function battery_percent_handler(driver, device, ib, response)
   end
 end
 
--- GeneralDiagnostics.ActiveHardwareFaults is a list of HardwareFaultEnum values.
--- Firmware adds kTamperDetected (10) when the keypad 4-strike brute-force
--- limit trips and removes it when the lockout expires. Map list membership
--- directly to the tamperAlert capability so the SmartThings UI tracks the
--- attribute's full lifecycle (detected -> clear) instead of just the alarm
--- event edge.
-local function hardware_faults_handler(driver, device, ib, response)
-  local list = ib.data and ib.data.elements
-  local tampered = false
-  if list ~= nil then
-    for _, entry in ipairs(list) do
-      if entry.value == HARDWARE_FAULT_TAMPER_DETECTED then
-        tampered = true
-        break
-      end
-    end
-  end
-  if tampered then
-    device:emit_event(capabilities.tamperAlert.tamper.detected())
-  else
-    device:emit_event(capabilities.tamperAlert.tamper.clear())
-  end
-end
-
 ----------------------------------------------------------------------
 -- EVENT HANDLERS
 ----------------------------------------------------------------------
 
--- Retained for compatibility with firmware that only fires the
--- DoorLockAlarm event (older builds without GeneralDiagnostics tamper
--- reporting). On builds that report both, the attribute handler above
--- supersedes this by also clearing the state.
 local function door_lock_alarm_handler(driver, device, ib, response)
   device:emit_event(capabilities.tamperAlert.tamper.detected())
 end
@@ -137,9 +107,6 @@ local matter_lock_driver = {
       [PowerSource.ID] = {
         [PowerSource.attributes.BatPercentRemaining.ID] = battery_percent_handler,
       },
-      [GeneralDiagnostics.ID] = {
-        [GeneralDiagnostics.attributes.ActiveHardwareFaults.ID] = hardware_faults_handler,
-      },
     },
     event = {
       [DoorLock.ID] = {
@@ -158,9 +125,6 @@ local matter_lock_driver = {
     [capabilities.battery.ID] = {
       PowerSource.attributes.BatPercentRemaining,
     },
-    [capabilities.tamperAlert.ID] = {
-      GeneralDiagnostics.attributes.ActiveHardwareFaults,
-    },
   },
 
   subscribed_events = {