For me it is mostly the driver Zigbee Motion Sensor. I just started logging to a txt file and I will let it run for several hours and then send it to you. How would you like me to send it?
This is a serious issue, affecting many people. I’m hoping you folks actually look into this. I am presently sharing Hub access with the ST support team, so they may access it to look into this.
Everyone who is having this issue, especially those of you that are saying their batteries are only lasting days now instead of months, need to follow @Ivan_Luis_Falleau instructions and send him the logcat output from the driver that the devices are using. Sharing Hub access with the ST support team is not enough, they need the logcat output to see what is causing the problem.
If you add “> textfile.txt” at the end of the logcat command it will log the output to a text file in the current directory so it will be easy to send to Ivan. See example below. Let this process run for 3 to 4 hours and all the output will be stored in the file.
If you dont have Command line setup then see the link by @JDRoberts below.
If you still cant figure it out then let me know and I will try to explain it further.
Also note that after you run the command “smartthings edge:drivers:logcat > batterydraincli.txt” there will be no output in the command line window, everything will be directed to the text file. You will have to open the text file and look for the driver number you want to log and then type that in the command line window and hit enter and then you will see the messages logging to the file.
Shouldn’t the driver id be included? Otherwise that’s going to be a huge file. Also, is the battery capability reported out? I’m curious to know since the app doesn’t show battery reports in history.
The command should look like this once all the info is provided in in CLI. The driver id below is for the Zigbee Motion Sensor edge driver.
Yes, the driver number can be included if you already know what it is or you can just look in the text file that is output and find the driver number and then type that number in the command line window and hit enter. Without typing the driver number and hitting enter its not going to log anything.
The purpose is not to log the battery capability but to show if there is to much polling of the device and it killing the battery because of it.
Yes, me as well. I have been logging my battery changes in Excel since early 2022 and a lot of my Iris multipurpose sensors that were getting about 500 days between changes are now only getting 90 to 100 days. Other people are reporting their batteries lasting for less than a month! I noticed a huge increase in messages while running logcat in mid-September.
Also, I’m thinking that this maybe causing all the Zigbee problems people seem to be having as of late.
I noticed the sudden drop after fitting new batteries to older model motion sensors. For the sensor at around 20C ambient its reported 33% for a while now, the other that’s under 15C reports 0% although it continues to function - the latter would have fewer events needing reporting. A remove, reset, and re-add improved it a little for a few days only. The sensors have been running for a long time with a good interval between batteries - until recently.
Yesterday my Hub’s beta firmware was updated to 52.1.
The zigbee stack was updated from version 5.6.4 to version 6.0.3
Today I am observing the logs of the drivers of devices that use battery, zigbee Contac Mc, zigbee Motion Sensor Mc, Zigbee Temp Sensor and Child Thermostat Mc, Zigbee Smoke/CO Detector Mc that I have with devices working.
What I mentioned about the systematic sending of reports from the Basic cluster, generic body seems to have disappeared.
After several hours of logs, periodic reports status and activation reports have been received and no message has been received from the Basic cluster in any driver.
This can be good news for improving battery consumption in zigbee devices.
I don’t know if they have to do with this new version of the zigbee stack version 6.0.3, the beta version 52.1 notes do not say that they have changed
I sure hope so because I just replaced a battery on ST’s multisensor yesterday that was drained in just 2 days. So far that device is still at 97% 14 hours later, which is good news compared to a couple days ago.
I have 3 multipurpose sensors (aeotec, Samjin) with my zigbee Contact Mc driver and with periodic temperature reports in 60 minutes and 1°c and periodic Contact status reports in 3600sec, instead of 300sec, which is the default interval.
It sure is! The battery that was in it for almost 2 years finally needed replaced, and the new one drained in just those two days. It “could” have been a bad battery, but it reported 100% right away for a few hours, and then it started draining that fast with 24 hours of being installed.
But…
As soon as I posted that I looked at the device again just now, and it’s at 90% and reporting temperature changes every minute. Based on that level of reporting, I don’t expect the battery to last too much longer. I’ll wait to see what happens by this evening, and then I’ll switch over to your driver.
I’m seeing this with a zwave ecolink contact sensor in my shed (with other zwave mains powered devices within 20-30 ft). Replaced the battery with new Energizer Lithium on 12/29 and last status reported to Smarthings was on 1/3. Battery showed 61% on 1/1. This is probably the 3rd or 4th battery replacement in as many months where prior to that, I would usually get at least a year. Figured the first few times it was a bad battery, but keep seeing others with similar issues recently.
That sensor is exposed to constant temperature changes.
I would configure it like I have the one on my garage door, temperature reports every 1 hour or changes of 3°c (5.4°F) at least
Mariano, I apologize if you’ve covered some of these things before, but I’m switching all my Zigbee devices to your drivers. I want to make sure I understand the settings to optimize for reducing battery drain, minimizing Zigbee traffic, and taking advantage of the new Battery virtual device. I have tested all the devices with the drivers, and they work as expected. Also, I know I was able to send you a donation last year, and I want to send it again, but I can no longer find it on your Github page. Please send me the link again! I insist, most of my smart home runs on your drivers, and I want to compensate you for your efforts!
I am changing all of my Iris Multipurpose sensors (IL07) to Zigbee Motion MC. Can I just change the driver, or do I need to remove and pair each one again? I should change the motion sensor report interval to 3600, temperature report interval to 60, and the temperature reportable change to 100. This will still give me motion alerts in real-time, temperature every hour, and an update if it changes by 1°F?
I am changing all of my SmartThings Multipurpose sensors (Samjin) to Zigbee Contact MC. Can I just change the driver, or do I need to remove and pair each one again? I should change the contact sensor report interval to 3600, temperature report interval to 60, and the temperature reportable change to 100. This will still give me open/close and vibration alerts in real-time, temperature every hour, and an update if it changes by 1°F?
I am changing all of my Iris Water Leak sensors (moisturev4) to Zigbee Moisture Sensor MC. Can I just change the driver, or do I need to remove and pair each one again? I should change the temperature report interval to 60, and the temperature reportable change to 100. This will still give me leak alerts in real-time, temperature every hour, and an update if it changes by 1°F.
