Yale Doorman V2N with YMZB-100 EVA Zigbee module: Only linkquality exposed, no lock features in Zigbee2MQTT

Hi all,

I have a Yale Doorman V2N with the EVA Zigbee module and I’m trying to get it working locally with Zigbee2MQTT (and Home Assistant). I want to avoid using the cloud for my lock.

Here’s everything I’ve tried so far:

Pairing and Interview

The module pairs with Zigbee2MQTT and the interview completes successfully.

However, only linkquality is exposed—no lock, battery, PIN code, or other features.

The device does not report a modelID or manufacturerName in the logs during or after interview.

The logs just show:

Interviewing ‘0x680ae2fffe6baac8’

Successfully interviewed ‘0x680ae2fffe6baac8’

and then only linkquality is available in the state.

Custom Converter Attempts

I created a custom converter (yale_doorman.js) and tried:

Matching by IEEE address (fingerprint: [{ieeeAddr: ‘0x680ae2fffe6baac8’}])

Using a generic fingerprint (by type, endpoint, clusters)

Removing the fingerprint entirely (so the converter would match any device)

I included all relevant fromZigbee/toZigbee converters and exposes (lock, battery, pin code, etc.).

No matter what, only linkquality is exposed.

Other Troubleshooting

I tried waking up the lock (physically interacting with it) before and after pairing.

I tried re-pairing multiple times and restarting Zigbee2MQTT.

I checked the logs for any mention of modelID, manufacturerName, or clusters—nothing is reported.

I tried pairing with ZHA (Home Assistant’s Zigbee integration), but the result was the same: the lock is either not recognized or only exposes linkquality.

I checked for firmware updates for the lock/module—none available.

I found that the module works with the Futurehome hub (as described here), but I do not want to buy a new hub just for this.

What I See Under Exposes (Zigbee2MQTT)

Battery: Remaining battery in % (N/A%)

State: State of the lock

Lock state: Actual state of the lock (N/A)

Pin code: User, User type, User enabled, PIN code

Action source name: Source of the triggered action on the lock (N/A)

Action user: ID of user that triggered the action on the lock (N/A)

Auto relock time: The number of seconds to wait after unlocking a lock before it automatically locks again. 0=disabled

Sound volume: Sound volume of the lock

Action: Triggered action (e.g. a button click) (N/A)

Linkquality: Link quality (signal strength) (e.g. 102lqi)

Willing to Provide a Zigbee Sniffer Log

I am willing to buy a CC2531 USB stick and provide a Zigbee sniffer log if that would help with debugging or adding support.

Please let me know if you need a specific capture (e.g., during pairing/interview) and I will follow your instructions.

What I’m Looking For

Is there any way to get more debug information or a fingerprint for this device?

Would using a Zigbee sniffer help, or is there a way to enable more verbose logging in Zigbee2MQTT to capture the device’s clusters or attributes?

Has anyone managed to get this module working with Zigbee2MQTT or ZHA, or is there a custom handler/converter available?

Any advice or next steps would be greatly appreciated!

Thank you for your help!