[New device support]: Add manufacturerName _TZE28C1000000_gt5al3bl to GL-SPI-206P definition

Link

https://gledopto.com/h-pd-101.html

Database entry

0x6ce4a4fffeb0c983

Zigbee2MQTT version

2.13.0

External definition

const {definitions} = require('zigbee-herdsman-converters');
const base = definitions.find((d) => d.model === 'GL-SPI-206P');

const definition = {
    ...base,
    fingerprint: [
        ...(base.fingerprint || []),
        {modelID: 'TS0601', manufacturerName: '_TZE28C1000000_gt5al3bl'},
    ],
};

module.exports = [definition];

What does/doesn't work with the external definition?

I was unable to test this locally, as the Home Assistant Zigbee2MQTT add-on has external JavaScript converters disabled by default and there's no config option to enable it.

This device paired under manufacturerName _TZE28C1000000_gt5al3bl (modelID TS0601), which doesn't match the existing GL-SPI-206P fingerprint (_TZE284_gt5al3bl), causing it to fall back to a generic definition exposing only linkquality.

The hardware and packaging is identical to the already-supported GL-SPI-206P (same box, same model number, same manual). This external definition simply adds the additional manufacturerName to the existing fingerprint list, under the assumption the underlying datapoints are identical. I'd appreciate if someone with the ability to test could confirm, or if a maintainer could merge this fingerprint addition directly given the hardware match.

Notes

Related: discussion #30755 and issue #29539, both about the same GL-SPI-206P device under manufacturerName _TZE284_gt5al3bl.

Locate the existing GL-SPI-206P definition and inspect its fingerprint list. Add the reported model and manufacturer pairing, then verify with a compatible Zigbee test that the device exposes the same controls as the existing definition; done means it no longer falls back to linkquality-only handling.