<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strange power consumption of Matter Window Covering</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/104994/strange-power-consumption-of-matter-window-covering</link><description>Hello DevZone, 
 I met a strange problem strange power consumption of Matter Window Covering example (with release build). 
 
 Hardware: 52840DK v3.0.1 
 Software: NCS v2.4.2 
 Configuration: `prj_release.conf` 
 
 The problem is: when I pushed button</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Oct 2023 02:33:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/104994/strange-power-consumption-of-matter-window-covering" /><item><title>RE: Strange power consumption of Matter Window Covering</title><link>https://devzone.nordicsemi.com/thread/452688?ContentTypeID=1</link><pubDate>Fri, 27 Oct 2023 02:33:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ea636e5-d6cf-4adb-9e35-bfafd0a5b9ff</guid><dc:creator>Jayant Tang</dc:creator><description>&lt;p&gt;Yes, pressing button 2 once or pressing the button 3 19 more times will stop the PWM. I have modified the `&lt;span&gt;PositionToBrightness()&lt;/span&gt;` function, to set the brightness to only 0% or 100%. And this can be fixed.&lt;/p&gt;
&lt;p&gt;I can also remove the code and DeviceTree node of PWM.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;By the way, I think it&amp;#39;s a good idea to ask the developers to change the LED behavior in release mode, because the position is not always 100% or 0%, especially when using Apple Home to control this device. This power consumption is very confusing for the new customers who is not familiar with our product.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jayant&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange power consumption of Matter Window Covering</title><link>https://devzone.nordicsemi.com/thread/452564?ContentTypeID=1</link><pubDate>Thu, 26 Oct 2023 12:52:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8c7778fe-67c1-4d32-ac17-3cb1679be0a4</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;So the PWM is left running after button 3 is pressed once to keep the &amp;quot;window covering&amp;quot; at 95%? If that&amp;#39;s it I would assume either pressing button 2 once to get it back to 100% or button 3 19 more times to get it fully closed should stop the PWM, no? You could also try to modify the sample to make one button press close the window covering fully I guess. I can ask the developers if this is the intended behavior and that the current consumption in fact should increase whenever the window isn&amp;#39;t fully opened or closed.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange power consumption of Matter Window Covering</title><link>https://devzone.nordicsemi.com/thread/452408?ContentTypeID=1</link><pubDate>Thu, 26 Oct 2023 05:29:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ad2a0d9-2d98-485e-ae74-bddda2821674</guid><dc:creator>Jayant Tang</dc:creator><description>&lt;p&gt;Hi Simon&lt;/p&gt;
&lt;p&gt;I tested both standalone and commissioned. The result is the same.&lt;/p&gt;
&lt;p&gt;What you said about HFCLK is right. I just found out that this is not a problem. The real reason is that the LED2 will be lighted up with PWM when the window covering is not 100% opened or 0% closed.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s related to Button 3, because the default state is 100% opened, and pressing Button 3&amp;nbsp;will close the window covering by a step of 5%.&lt;/p&gt;
&lt;p&gt;The power consumption will not disappear after reset, I think it&amp;#39;s because the example saved the position to the flash.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jayant&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange power consumption of Matter Window Covering</title><link>https://devzone.nordicsemi.com/thread/452158?ContentTypeID=1</link><pubDate>Wed, 25 Oct 2023 07:46:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:743e8794-5749-4d3b-bf2c-3db65e9b63ad</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Are you testing the device standalone or also commissioning it when seeing this issue. I think what&amp;#39;s happening is that button 3 enables the HF clock for some reason, and doesn&amp;#39;t turn it off. From the documentation I&amp;#39;m not able to see why this should be, as it should just change the level of one LED one step. Do you see LED2/3 being changed when pressing button 3 as expected?&lt;/p&gt;
&lt;p&gt;Do you have the log from the debug mode then. Since the HF clock is already running by default to do logging in the debug build I think that&amp;#39;s why you don&amp;#39;t see the current increase in the debug build, but I assume the behavior is the same.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>