Homebrewn device - Inconsistent data in Zigbee2Mqtt & Missing Endpoint in Homeassistant

[mxf14]

Dear Forum,

I did create a custom Zigbee device based on ESP32-C6. It has 2 endpoints: 1x binary input (door bell) & 1x binary output (door opener).
The device pairs well with Zigbee2Mqtt and shows up with a pretty good auto-generated converter. Data on the "Exposed" page updates and can be updated as well (for the output). So far so good.

The issues I got are that ...

1. Vendor name and device model are stored in the database but do not show up on the Zigbee2Mqtt page

Database entry:
{"id":38,"type":"EndDevice","ieeeAddr":"0x1051dbfffe1aaff8","nwkAddr":16338,"manufId":4660,"epList":[10,11],"endpoints":{"10":{"profId":260,"epId":10,"devId":12,"inClusterList":[0,3,16],"outClusterList":[],"clusters":{"genBasic":{"attributes":{"modelId":"DoorModule","manufacturerName":"Mx","powerSource":0,"zclVersion":8}},"genBinaryOutput":{"attributes":{"description":"Buzzer","presentValue":0,"statusFlags":0}}},"binds":[{"cluster":16,"type":"endpoint","deviceIeeeAddress":"0x00124b002e1e8b98","endpointID":1}],"configuredReportings":[{"cluster":16,"attrId":85,"minRepIntval":1,"maxRepIntval":10}],"meta":{}},"11":{"profId":260,"epId":11,"devId":12,"inClusterList":[0,3,15],"outClusterList":[],"clusters":{"genBasic":{"attributes":{"powerSource":0,"zclVersion":8}},"genBinaryInput":{"attributes":{"description":"Door Bell","presentValue":0,"statusFlags":0}}},"binds":[{"cluster":15,"type":"endpoint","deviceIeeeAddress":"0x00124b002e1e8b98","endpointID":1}],"configuredReportings":[{"cluster":15,"attrId":85,"minRepIntval":1,"maxRepIntval":10}],"meta":{}}},"zclVersion":8,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":332242049},"lastSeen":1772314876362}

I created a custom converter based on the auto-generated one and stored it in "/opt/zigbee2mqtt/external_converters/mx_doorcontrol.mjs". My guess is that it did not get loaded, probably for the same reason as why vendor and model are "unknown".

The unapplied converter:
`import * as m from 'zigbee-herdsman-converters/lib/modernExtend';

export default {
zigbeeModel: [''],
model: 'DoorModule',
vendor: 'Mx',
description: 'Door bell and opener handling',
extend: [m.deviceEndpoints({"endpoints":{"Buzzer":10,"DoorBell":11}}), m.binary({"name":"Buzzer","cluster":"genBinaryOutput","attribute":"presentValue","reporting":{"min":"MIN","max":"MAX","change":1},"valueOn":["Buzz",1],"valueOff":["NoBuzz",0],"description":"Door Opener","access":"ALL","endpointName":"Buzzer"}), m.binary({"name":"Door Bell","cluster":"genBinaryInput","attribute":"presentValue","reporting":{"min":"MIN","max":"MAX","change":1},"valueOn":["DingDong",1],"valueOff":["NoDingDong",0],"description":"Door Bell Status","access":"STATE_GET","endpointName":"DoorBell"})],
};
`

2. Homeassistant does not show the binary input (door bell)

Home assistant shows the door opener entity, but not the door bell:

Zigbee2Mqtt shows (and updates) both:

I know there are a lot of questions. But I would be glad about any help.

Thanks for the great work to the community!

[andrei-lazarov]

Check the logs when Z2M boots to see if the converter is loaded or not.
Actually it renames it automatically with .invalid when it fails to load.

1. Stop Z2M
2. Manually edit database.db
3. Start Z2M

Update database.db manually with the model and manuf at the top level, not inside cluster attributes:
{"id":38,"type":"EndDevice","ieeeAddr":"0x1051dbfffe1aaff8","nwkAddr":16338,"manufId":4660, "manufName":"Mx","powerSource":"Mains (single phase)","modelId":"DoorModule", "epList":[10,11],"endpoints":{"10"...

See if that helps.

[mxf14]

Hello
Thanks for the hints.

I changed the database.db while Z2M down and moved manufacturer and model. But when starting up again the database entry changes back to what it was previously.

The log file shows no errors, only a few unrelated ping warnings. The only entry related to the doormodule device shows this [2026-03-01 21:31:34] info: z2m: DoorModule (0x1051dbfffe1aaff8): Not supported (EndDevice)