Zigbee End Device uses wrong profile_id when using CLI Zcl cmd

[DaKa]

Hi,

I am using the Zigbee CLI to maintain and control a Zigbee network. The Zigbee stack is running on a BMD340 module.
I added a Ikea Trådfri dimmable light bulb (only stays in the network if I enable legacy mode). Once in the network, I get the active endpoints and a simple descriptor request to get some more information about the device.

Response to active_ep:

src_addr=BC95 ep=1

Response to simple_desc_req:

src_addr=0xBC95 ep=1 profile_id=0xC05E app_dev_id=0x100 app_dev_ver=0x2 in_clusters=0x0000,0x0003,0x0004,0x0005,0x0006,0x0008,0x0B05,0x1000 out_clusters=0x0005,0x0019,0x0020,0x1000

So far, so good.
But then, if I want to use zcl cmd to control the bulb, I am able to control it only if I use the ZHA (0x0104) profile. This is very confusing for me, since the simple descriptor response says that the profile_id of this endpoint is the ZLL (0xc05e) profile.
My question is: Why That? Is it a manufacturer mistake? or I don't understand how Zigbee is supposed to work?

Thanks in advance for your answer,
Damien

[DaKa]

Hello,

Never mind, I found the answer in a ZLL spec. (https://www.nxp.com/docs/en/user-guide/JN-UG-3091.pdf)

Other question:
Is it possible to use the zcl cmd from the CLI to control a device that is using any profile and any "custom" cluster? For example a non-public profile. Or what are the limitation of the zcl cmd?

Best regards,
Damien

[Edvin]

As far as I know, there are no restrictions in the zcl cmd  CLI command. I would be really surprised if there is, because when you type something wrong, it will still execute the command, just without any response (because no node replies to the wrong IDs). As long as the command has the right amount of input parameters, of course.

[DaKa]

Thanks a lot.