Fixed/Improved Paulmann Amaris LED panels

[samuel-p]

I recently bought the Amaris LED panel 798.10. Unfortunately, the panel did not work straight away.

The lamp was initialized with the wrong model (948.47/29165) in Zigbee2MQTT. As a result, an incorrect color_temp range was displayed in Home Assistant and the lamp occasionally flickered.

After the corresponding adjustments from this PR, the lamp was correctly identified and has been working without any problems ever since. The data from extend were generated by the external definition function.

Zigbee2MQTT is really new to me, so I'm not sure if I've done everything right here. I just wanted to make my changes available to the public.

[samuel-p]

Probably it just works because I used the same fingerprint, as the device which was wrongly detected. I have no idea how the identification of the devices works. So it would be awesome id someone has a hint for me, on how to fix that.

[Koenkk]

Could you provide the data/database.db entry of your device?

[samuel-p]

Sure, here you go:

{
  "id": 2,
  "type": "Router",
  "ieeeAddr": "0x00158d000877755b",
  "nwkAddr": 26911,
  "manufId": 4632,
  "manufName": "Paulmann Licht GmbH",
  "powerSource": "Mains (single phase)",
  "modelId": "RGBW",
  "epList": [
    1,
    242
  ],
  "endpoints": {
    "1": {
      "profId": 260,
      "epId": 1,
      "devId": 269,
      "inClusterList": [
        0,
        4,
        3,
        6,
        8,
        5,
        768,
        4096
      ],
      "outClusterList": [
        25
      ],
      "clusters": {
        "genBasic": {
          "attributes": {
            "modelId": "RGBW",
            "manufacturerName": "Paulmann Licht GmbH",
            "powerSource": 1,
            "zclVersion": 3,
            "appVersion": 19,
            "stackVersion": 1,
            "hwVersion": 16,
            "dateCode": "20190515",
            "swBuildId": "1400-0001"
          }
        },
        "lightingColorCtrl": {
          "attributes": {
            "colorCapabilities": 31,
            "colorTempPhysicalMin": 153,
            "colorTempPhysicalMax": 370,
            "colorMode": 2,
            "currentX": 21011,
            "currentY": 21754,
            "enhancedCurrentHue": 31369,
            "currentSaturation": 20,
            "colorTemperature": 161
          }
        },
        "genLevelCtrl": {
          "attributes": {
            "currentLevel": 254
          }
        },
        "genOnOff": {
          "attributes": {
            "onOff": 1
          }
        }
      },
      "binds": [],
      "configuredReportings": [],
      "meta": {
        "onLevelSupported": false
      }
    },
    "242": {
      "profId": 41440,
      "epId": 242,
      "devId": 97,
      "inClusterList": [
        33
      ],
      "outClusterList": [
        33
      ],
      "clusters": {},
      "binds": [],
      "configuredReportings": [],
      "meta": {}
    }
  },
  "appVersion": 19,
  "stackVersion": 1,
  "hwVersion": 16,
  "dateCode": "20190515",
  "swBuildId": "1400-0001",
  "zclVersion": 3,
  "interviewCompleted": true,
  "meta": {
    "configured": 1324213189
  },
  "lastSeen": 1712602927663
}

Thanks for your quick response.

[Koenkk]

This device uses the same fingerprint as 948.47/29165 so we cannot distinguish them. You can add the enhancedHue to 948.47/29165, then only the color temp range is too high (but just make sure you don't set it out of the range)