Initial support for Xiaomi Aqara T1 Cube

[manup]

Note: This PR requires a newer firmware, since the device only exposes required endpoints when the coordinator Node Descriptor has the Xiaomi manufacturer code set to 0x115F: deCONZ_ConBeeII_0x266b0700.bin.GCF

The PR contains a fix to query Basic Cluster attributes like manufacturer name for newer Xiaomi Zigbee 3.0 devices.
The Xiaomi Aqara T1 Cube exposes the same API and button events as the older Xiaomi Aqara Cube does.

{
   "1": {
    "config": {
        "battery": 100,
        "on": true,
        "reachable": true,
        "temperature": 2500
    },
    "ep": 2,
    "etag": "2c4057c509efa2d9e42d30a5697331d6",
    "lastseen": "2021-04-29T23:26Z",
    "manufacturername": "LUMI",
    "mode": 1,
    "modelid": "lumi.remote.cagl01",
    "name": "Mi Magic Cube",
    "state": {
        "buttonevent": 1003,
        "gesture": 3,
        "lastupdated": "2021-04-29T23:26:02.467"
    },
    "swversion": "20200327",
    "type": "ZHASwitch",
    "uniqueid": "04:cf:8c:df:3c:80:0d:1e-02-0012"
  },
  "2": {
    "config": {
        "battery": 100,
        "on": true,
        "reachable": true,
        "temperature": 2500
    },
    "ep": 3,
    "etag": "aa413cc38589fbb8c94c1b83867ea437",
    "lastseen": "2021-04-29T23:26Z",
    "manufacturername": "LUMI",
    "mode": 1,
    "modelid": "lumi.remote.cagl01",
    "name": "Mi Magic Cube",
    "state": {
        "buttonevent": -6828,
        "gesture": 8,
        "lastupdated": "2021-04-29T23:26:58.391"
    },
    "swversion": "20200327",
    "type": "ZHASwitch",
    "uniqueid": "04:cf:8c:df:3c:80:0d:1e-03-000c"
  }
}

[Smanar]

So it mean the "magic" will be in the firmware, and not in the API ?

[manup]

So it mean the "magic" will be in the firmware, and not in the API ?

Yes at least as initial approach I'd like to hard code the Node Descriptor response for Xiaomi in the firmware based on MAC prefix. This has the advantage that other projects like zigbee2mqtt and ZHA/zigpy which have adapters for the deCONZ serial protocol don't need to worry about this.

Later on the serial protocol will be configurable to let the firmware not send the Node Descriptor response and instead let the application like deCONZ handle this to gain more freedom.