Zigbee brightness cluster attribute and cluster

RE: Zigbee brightness cluster attribute and cluster

AHaug — Tue, 09 Aug 2022 10:06:48 GMT

Hi,

Yeah, I don't expect you to change version mid developing at all.

I've created an internal inquiry to see if we are able to create a PR that fixes this, but I can't say when and if this inquiry will be fixed. I'll let you know as soon as I know more.

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Fri, 05 Aug 2022 13:59:40 GMT

If you have the Coordinator design running on your eval board it may be easier to just try it. It's very obvious error.

It's a bit complicated for us right now to jump to new version as we are in middle of writing code to parse messages.
Thx, Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Fri, 05 Aug 2022 13:11:49 GMT

I will have to dig up and see if I can find anything about a change in the newer version and to verify that its a version error. Our ZigBee developers believe it might have been fixed in a newer version of NCS and that the error you're seeing is related to older versions.

I'll get back to you on monday.

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Thu, 04 Aug 2022 15:21:57 GMT

Andreas,
No I have not. Can you confirm that was a change in v2.0 ?

I don't mind moving to a newer version NCS once in a while, however doing this we have to regression test everything we know works in v1.9 since behavior is always a bit different.

Thanks,
Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Thu, 04 Aug 2022 14:03:06 GMT

Hi Jorgen,

Apologies for the long response time. Have you checked if the error with the request pool is present in NCS v2.0.0 as well?

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Tue, 26 Jul 2022 15:04:41 GMT

Andreas,
No problem we have other things to work on .
I believe once first error is generated it does not matter if I step down when at high limit or if I'm at low limit and step up. I will confirm this.
( "waiting" does not help)
Thx, Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Tue, 26 Jul 2022 13:59:32 GMT

Hi Jorgen,

I will see if I can dig up an explaination to this, however it might take some time (again due to vacation).

My immediate thought is that the request pool only either has room for a given amount of orders (fixed bit number of orders can be held at a given time), or that the limit has been overstepped. Does the error clear if you step down after reaching the upper limit?

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Sat, 23 Jul 2022 20:16:40 GMT

Thanks Andreas,

I was able to step up and down now!

If I step too many times down or up and device is all the way to it's upper or lower limit already I get error msg saying="request pool is full, wait a little".

Can you tell me what causes this error?

I should not have to keep track of where I am on the step scale for a device, right?
It should just reject or do nothing if I keep stepping beyond full/lowest brightness, please confirm.

The "request pool..." error does not clear unless I push reset on eval brd and then I have to restart stack.
So it's probably related to Nordic FW.
Is there a way to clear this message with command?

Thanks again!
Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Mon, 18 Jul 2022 09:13:47 GMT

Hi again Jorgen,

I took another look into the ZigBee Cluster Library (version 7) and found something that I hope will clarify how to use the command

For the step command: zcl cmd 0x8041 10 0x0008 0x02 -l 00A01400

we have that the long payload 00A01400 is formated as 0x00 0xA0 0x14 0x00.

Here 0x00 = "step mode" which says to step up

0xA0 = "step size", which is to be changed by 160 (0xA0 = 160)
0x14 = "transition time", which is stated as "The Transition time field specifies the time that SHALL be taken to perform the step, in tenths of a seconds
0x00 = "option", which is just 0 since its not used

These can be seen in chapter 5.2.2.3.6 in the specification

I hope this clarifies this command for you!

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Fri, 15 Jul 2022 13:47:37 GMT

Thanks Andreas!

Examples would be great on the payload format for lighting in general with short explanation of range parameters.
It would save a lot of dev time....:)

Since lighting control is such a common requirement an appnote with examples on this topic would be extremely useful or even a "real" lighting controller design example.
There are many ways to dim a light and change color etc.
Some implementations (step vs. move to level as example) has impact on real-time response as well as flooding network with messages and instead using broadcast group etc. depending on how many lightbulbs are on the network.
Just some food for thought...

Cheers, Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Thu, 14 Jul 2022 13:58:24 GMT

Hi Jorgen,

I will see if I can test this myself either tomorrow or on Monday. The commands were fetched from an internal course a way back and they might have changed in newer SDKs

[quote user="JorgenM"]How is 160 level represented in the payload?[/quote]

160 should be represented by A0 in the payload, but I see now that it is not as clear as it might have been. However, there are a part of that payload that has data that are not 160. I will have to look into what the other bytes in the long payload is.

[quote user="JorgenM"]What table is this defined in in the Cluster doc?[/quote]

I will also find this again and supply it to you

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Wed, 13 Jul 2022 15:33:40 GMT

Hi Andreas,
Yes your command worked but haven't been able to get others to work like "step up" or "move to level".
Is it possible for you to elaborate on the payload in your example

zcl cmd 0x8041 10 0x0008 0x02 -l 00A01400

"currentLevel" being "160" ? What is the range of current level attribute?
How is 160 level represented in the payload?
What table is this defined in in the Cluster doc?

If I use "move to Level" command 0x00 what is the range? An example on this would be great.

I think I'm entering the wrong payload parameters.

Thanks, Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Tue, 12 Jul 2022 13:01:49 GMT

Hi Jorgen,

How is the progress going? Did the commands I posted work, and can we close this ticket? If not, please let me know if you have any additional questions regarding this specific ticket!

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Thu, 07 Jul 2022 18:30:41 GMT

Continued..
Yes I meant the "light switch" example you are referring to above.
You assume correct. I can retrieve node ID's, clusters number of endpoints etc. as per screenshot I sent.
Thanks for your help!

Jorgen

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Thu, 07 Jul 2022 17:56:11 GMT

Thanks Andreas!
Yes looks like I missed the payload format. I will have to decipher this a bit.

zcl cmd 0x8041 10 0x0008 0x02 -l 00A01400

I will try this.

Thanks, Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Thu, 07 Jul 2022 14:11:38 GMT

Hi,

I see you have the ZigBee Cluster Specification available, so I will also be using some snippets from the ZCL Spec V7 in my example below. I am also making an assumption that you know your devices ID and how to find their addresses and the correct end point values, so if I am assuming wrong on this, please correct me!

[quote user="JorgenM"] Nordic zigbee light bulb controller example[/quote]

By this, do you mean the the light switch sample?

[quote user="JorgenM"]I assume it's not the same as "level" cluster which is 0x0800 as per below.[/quote]

The level control attribute id is correct (0x0800) as per ZigBee Cluster Library Specification 7 states, but the command to change the value of the light is another command

[quote user=""]#1 Based on below cluster info etc. can you give example of ZCL commend format to set brightness to 50%?[/quote]

Here is a few examples of how to "mock" a light switch with commands:

Off command with example:

zcl cmd [-d] <h:dst_addr> <d:ep> <h:cluster> [-p h:profile] <cmd_ID> [-l h:payload]
zcl cmd -d 0x8041 10 0x0006 0x00

Step command (dimmer function):

zcl cmd [-d] <h:dst_addr> <d:ep> <h:cluster> [-p h:profile] <cmd_ID> [-l h:payload]
- for clarity: "-l" in [-l h:payload] = lower case L
zcl cmd 0x8041 10 0x0008 0x02 -l 00A01400

This example is sent to the device at address 0x8041, at the endpoint 10 (light bulb), and utilizes the ZigBee Home Automation Profile (0x0104) by default. When it is recived by the bulb, it should gradually increase the value of CurrentLevel attribute by 160 over 2 seconds

[quote user=""]We can use "move to level" to 50%. I believe range is 0x000 - 0xfe if I read it right?[/quote]

So to do this, you need to replace the cmd_ID in the example above from step (0x02) to "move to level 0x00. I am not 100% certain about the range, but my current best guess is that it is a long hexadecimal number. I will see if I can find someone who can verify this for me, but try with the same range you were trying the previous command with

[quote user=""]

#2 Can you me show ZCL command example of how to read this?

From Nordic doc:
zcl attr read h:dst_addr d:ep h:cluster [-c] h:profile h:attr_id

[/quote]

In my sample, sending the command "zcl attr_read 0x8041 10 0x0006 0x0104 0x0000" returns ID: 0 Type: 10 Value: True, so I think you just misinput the order of the parameters based on your screen shot.

Let me know if this clarifies things for you or answers your questions!

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Wed, 06 Jul 2022 18:32:48 GMT

Hi Andreas, It's just a generic Zigbee HA1.2 RGB light bulb with dimming and color control.
The Nordic zigbee light bulb controller example is a eval board "light switch" so it doesn't show actual codes that are sent.
At least I could not find it...?
I think I'm not sending the correct attr_id
In fact I'm not sure where I can find the att_id , for "level" (dimming) as example.

I assume it's not the same as "level" cluster which is 0x0800 as per below.

An example of the just the command would be great.

Thanks!
Jorgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Wed, 06 Jul 2022 17:36:22 GMT

Hi Jorgen,

Is the light bulb application based on a sample application or is the firmware written from scratch? And is the RGB bulb a specific device, or just a bulb that is ZigBee-compatible?

[quote user=""]#1 Based on below cluster info etc. can you give example of ZCL commend format to set brightness to 50%?[/quote]

If you have not seen the zigbee samples already I believe the light bulb sample is a dimmable ZigBee device which might contain the functionality you are looking for. And I will take a look and see if I have a sample available tomorrow morning

[quote user=""]#2 Can you me show ZCL command example of how to read this?[/quote]

I believe I also have a sample for this, but I will need to find it first

Kind regards,
Andreas

RE: Zigbee brightness cluster attribute and cluster

JorgenM — Fri, 01 Jul 2022 13:31:52 GMT

Hi Andreas,

No problem. Thanks for letting me know.

Jörgen

RE: Zigbee brightness cluster attribute and cluster

AHaug — Fri, 01 Jul 2022 12:05:33 GMT

Hi Jorgen,

I've also replied this to the other case you've posted that I'm working on, but I'm writing it here as well! This is just a note that I've picked up your case and will begin investigating it. However due to summer holidays here in Norway we are currently running with a reduced support staff, so the reply time might be longer than normal. I hope I can get back to you during early next week with more answers.

Kind regards,
Andreas