Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Tue, 31 May 2022 11:48:54 GMT

You're welcome!

I'm glad to hear that it worked. Let me know if you have any additional questions regarding this topic left unanswered!

Kind regards,
Andreas

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Tue, 31 May 2022 10:33:59 GMT

HI,

Power cluster is now reporting. I thought its 3 sensors so count will be 3. Thanks for explaining why we need count = 4.

Thanks again for support in this whole process.

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Tue, 31 May 2022 10:15:12 GMT

Hi again,

We did some more investigating into the specs and found a change that should make the sample you sent work properly! If you change B_MULTI_SENSOR_REPORT_ATTR_COUNT from 3 to 4 in zb_multi_sensor.h it should work. The Power Configuration cluster has 2 attributes that are mandatory for reporting, which requires you to increase this count one higher.

This works for us at least, so let me know if this solves your issue!

As for the sniffer trace what we wanted to investigate is the packages with type ZCL: Configure Reporting and Configure Reporting Response to see if the commands went through with success or if they failed setting up the reporting routine as seen in the image (now with arrows and circles). If if would not have been a success, then the status line could contain some information about what have failed with the routine setup.

Kind regards,
Andreas

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Tue, 31 May 2022 07:06:31 GMT

HI,

Please find sniffer result in below screenshot. I am not sure if you can find what you are looking for and I have screenshot the right packet because it is not making much sense to me as this is my first time with sniffer tool

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Mon, 30 May 2022 13:30:26 GMT

Hi Andreas,

I am uploading my project, you can have a look at it. Meanwhile I will also setup wireshark and send its results by tomorrow. I modified multi_sensor example in "nrf5_sdk_for_thread_and_ZigBee_v4.2.0" to be my server and using CLI_agent example of same sdk without modifying it. I am using segger embedded studio for Arm v5.6 (64-bit).

devzone.nordicsemi.com/.../multi_5F00_sensor.rar

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Mon, 30 May 2022 13:06:11 GMT

Hi again and thank you for your patience,

After discussing it with my colleague we came to the conclusion that we might need more information. If you could either set up the Wireshark Sniffer and take a closer look at the ZCL: Configure Reporting Response status to see if it contains any information about what may cause the configure reporting command to fail. It should state something in the status message as to why it fails (screenshot below gives you a hint about what to look for). Else you may also zip your project and upload it here (as long as it does not contain any sensitive information), and we'll have a look with Wireshark to see if we can deduce anything from the trace.

As far as we saw from the Zigbee ZCL spec and your screenshots everything looks correct with the exception that the configure reporting command fails. The power configuration cluster battery information attribute set should be reportable/subscribable, and what you're doing looks to be correct regarding to formatting. The cluster identifier is 0x0001, the battery percentage remaining is 0x0021, and the type of 0x0021 is uint8 (i.e 32 in decimal).

This leads to one new hypothesis, and that is if the cluster somehow have been implemented wrong, but still is readable (which is a far assumption to make). Anyways, if you could supply us with either details about the configure reporting command or Zip and send us your sample, we will take one more look into what may cause this issue!

Kind regards,
Andreas

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Fri, 27 May 2022 11:47:11 GMT

Hi,

Thanks for supplying this additional information. My colleague and I will dig into this when they return to the office on Monday. I believe these attatchments will come in handy.

One more thing that might help is if you are able to generate and attach a sniffer log for us to investigate. The installation/tutorial process can be seen in this guide for Wireshark sniffer for 802.15.4. We will then need the entire pcap file generated if if you get that far. If you don't have the available resources or time to set this up, we'll do with what you've already supplied!

Kind regards,
Andreas

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Thu, 26 May 2022 08:14:44 GMT

HI Andreas,

I tried reading the battery value from read_attr command and I can read it correctly but unfortunately I still cannot subscribe to it. I think I am very close to the solution if you can get some ZIgBee engineer to look at it it would be great. For migration to another SDK is not possible for now.

If you see the below screenshot(1st line) I can bind my power config cluster(0x0001) but cannot subscribe to it. I can subscribe to 0x0402 cluster though. Then if you see 3rd last line zcl attr read f4ce36c29f9d38f6 10 0x0001 0x0104 0x0021. With this command I can read attribute value and it is giving me correct value. The only problem is I cannot subscribe to this cluster and get it to reporting.

Here is my code where I am setting the value of battery may be this can help. May be because it is hard coded value of battery and that why its not reporting? Because temperature and pressure sensor values are changing using sensorsim function but my battery value is fixed(for now). But if this is the case at least I should be able to subscribe to it.

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Wed, 25 May 2022 13:10:14 GMT

Hi,

I'm glad to hear that the case helped somewhat on the way!

I will ask my colleague if they have any idea what may cause this, but the response may be delayed until next week as there is a holiday coming up before the weekend.

Meanwhile you could take a look at the NCS resources if its an option to migrate from nRF5 to NCS

Kind regards,
Andreas

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Wed, 25 May 2022 10:18:12 GMT

HI Andreas,

Thanks for pointing me to this case. Actually by following that case I already tried to add power config cluster and unfortunately I am stuck at exactly same point where the guy Krystof Vydra is stuck.

I added power config cluster to multi sensor application. I can see cluster added and can also get reporting from temperature and power sensor but not from power config cluster.

As you can see in below screenshot power cluster 0x0001 is present in in-cluster list but I cant read value from it.

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Wed, 25 May 2022 08:32:21 GMT

Hi Aqib,

After asking in our ZigBee channel a colleague of me suggested that this similar ZigBee case might be of help with adding the power config cluster. Other than that (and maybe other related cases), there are unfortunately few other guide-related resource than the ZigBee stack API Overview for nRF5 SDK for Thread and ZigBee.

[quote user="AqibK"]If there is no such guide available, is there any other way you suggest[/quote]

Since nRF5 SDK is in maintenance mode, one option is to consider the possibilities of moving from nRF5 SDK to nRF Connect SDK instead. There will be some more learning to do as the SDKs are a bit different from each other, but there exists far better tutorials for nRF Connect SDK, such as this getting started with NCS platform and the Visual Studio Code extension which should help to boost the initial development phase, as well as the three NCS ZigBee tutorials I linked in the previous reply.

Let me know if this is of any help,

Kind regards,
Andreas

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Tue, 24 May 2022 08:32:00 GMT

HI Andreas,

I tried looking into links you provided and also from internet I tried to understand overall ZigBee functionality but unfortunately I still cannot add a power config cluster to my application. I successfully tested multi sensor, light control and CLI samples which comes with SDK but due to complexity of this API structure I am unable to understand how to actually code or modify these samples to my needs.

Can you please point me to some guide which shows step by step process of how to code this functionality or add existing cluster or modify existing cluster. If there is no such guide available, is there any other way you suggest or is it possible to have a direct call with you or any other Nordic engineer for few minutes which can help us in this task?

Regards,

Aqib

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AqibK — Thu, 19 May 2022 12:00:33 GMT

Hi,

Thank you so much for detailed response. I will look into the documents/links you provided. It looks like I will be able to have a good start from these resources. In case I get stuck any some point I will come back here with specific question.

Thanks again

RE: Battery monitoring of end device (door lock) from coordinator (central device) over Zigbee

AHaug — Thu, 19 May 2022 11:50:22 GMT

Hi,

Unfortunally we don't have any guides similar to the Bluetooth guide you're referring to for the ZigBee topic for nRF5 SDK for Thread and ZigBee , except for the documentation available at infocenter.nordicsemi.com.

For nRF5 SDK for Thread and ZigBee we have the ZigBee stack API Overview available, which contains information about the API, but it does not explain to great details how to use it. I believe ZCL Power Configuration Cluster may be what you need for this, but you will have to declare the cluster and set it up properly to use it. The power configuration cluster contains attributes that will give you information about the battery level and percentage remaining.

What you could do is to use this nRF Connect SDK guide about Adding ZCL cluster to application for NCS and compare it to how it is done in nRF5 SDK to get a pointer on how it is set up. There will be some differences, but it should be possible to find where the differences are through comparison. In case you want to investigate ZigBee closer in nRF Connect SDK, we also have this ZigBee quick start guide for NCS. As well as the ZigBee samples for network coordinator, light bulb and light switch which shows you how a signal is sent and read to trigger a light bulb through GPIO pins.

I would recommend that you also obtain the "ZigBee Cluster Library Specification", which is a book resource you will have to source either from the "CSA" - the former ZigBee Alliance or elsewhere. It is a really handy book for ZigBee developers. Chapter 3.3 here states more details about the power configuration cluster.

I know this is not necessarily what you were looking for, as you are developing for nRF5 SDK for Thread and ZigBee, but I hope that this will give you a good push in the right direction.

Please let me know if you have any further questions regarding this topic!

Kind regards,
Andreas