Please explain meta, endpoint and configure

[daestx]

When creating a converter.js file from PTVO tool, it contains following code:

meta: {
    multiEndpoint: true,

},
endpoint: (device) => {
    return {
        l1: 1, action: 1, l2: 2,
    };
},
configure: async (device, coordinatorEndpoint, logger) => {
  const endpoint = device.getEndpoint(1);
  await endpoint.read('genBasic', ['modelId', 'swBuildId', 'powerSource']);
},

For me it is currently not clear what it is used for. Is this section needed when sending data via Zigbee to the device? Currently my device is just sending data. I stripped this section from my code and I see no difference.

Please explain

[ncolomer]

Hello @daestx,

Reading from the many examples you can find in the many converter examples here + self deduction and testing:

• meta.multiEndpoint: true should be defined as soon as your device has several endpoints to generate definition
• endpoint is required to declare the endpoints in use for the device
• configure is a hook when device is (first?) discovered. It allows one to to configure things like preliminary read/write or bind reporting.

Need to admit I asked myself all same questions. It's a pain this lib is not documented... but at least you have many examples to learn from + access to the codebase.

Also note your issue would probably better sit in Koenkk/zigbee-herdsman-converters repo rather than this one. I think PTVO provides converter(s) as a courtesy only for their users.