Koenkk / Koenkk/zigbee2mqtt

[Support Request] Fortezza FZE01BK (TY0A01) Smart Lock - DP8 sends "LOCK"/"UNLOCK" strings

Open
#32,659 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.7k
Forks
2k
Avg merge
18h 55m
Merged PRs (30d)
35

Description

Is your feature request related to a problem? Please describe

Yes. The Fortezza FZE01BK smart lock is a Tuya device (model TY0A01) that works with Zigbee but currently has no converter in Zigbee2MQTT. The device is detected and recognized, but DP 8 (lock state) sends "LOCK"/"UNLOCK" strings that Zigbee2MQTT cannot convert, causing errors. Without support, users cannot control or monitor the lock state through Zigbee2MQTT.

Describe the solution you'd like

Create a converter for Fortezza FZE01BK that:

  1. Maps DP 8 values: "LOCK" → locked state, "UNLOCK" → unlocked state
  2. Captures battery level from DP 10
  3. Supports door status monitoring from DP 47
  4. Supports lock motor state from DP 57

Current external converter working but incomplete:

  • Device fingerprint: modelID 'TY0A01', manufacturerName '_TYST12_udaoihrc'
  • fromZigbee: tuya.fz.datapoints, fz.battery
  • Exposes: lock, battery
  • Issue: DP 8 sends "LOCK"/"UNLOCK" strings but no valueConverter maps these correctly

A valueConverter that handles string-based lock states (not just 0/1) would resolve this.

Describe alternatives you've considered
  1. Using WiFi app (Geonav) - requires Geonav hub which is not available and expensive
  2. Switching to another smart lock brand with official Zigbee support (Aqara, Xiaomi) - would require replacing the device
  3. Creating a custom valueConverter locally - attempted but requires understanding of Zigbee2MQTT internals and string-to-state mapping

Zigbee2MQTT support would be the ideal solution as the device is already detected and functional.

Additional context

Technical Details

Device Information:

  • Model: Fortezza FZE01BK
  • Zigbee Model: TY0A01
  • Manufacturer: _TYST12_udaoihrc
  • Power: 4xAA Battery
  • Endpoints: 1

Fingerprint:

{
    "modelID": "TY0A01",
    "manufacturerName": "_TYST12_udaoihrc"
}

Current Working Converter

External converter currently working:

  • Detects device correctly
  • Exposes battery and lock entities
  • Carregamento sem erros no Zigbee2MQTT 2.12.1

Error Logs

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied external converter and the existing tuya.fz.datapoints and fz.battery entry points. Add support for the TY0A01 fingerprint, string-valued DP 8 lock states, and the requested DP 10, 47, and 57 datapoints; done means the lock, battery, door status, and motor state are exposed without conversion errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.