<?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>FAILURE response when reading RebootCount in GeneralDiagnosticsCluster</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126680/failure-response-when-reading-rebootcount-in-generaldiagnosticscluster</link><description>Hi, The RebootCount attribute of the GeneralDiagnosticsCluster is returning a FAILURE response. 
 This issue is causing failures in Matter test cases TC-ACE-2.1. CONFIG_CHIP_LAST_FABRIC_REMOVED_ERASE_ONLY is required. What kind of response is possible</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 07 Feb 2026 00:16:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126680/failure-response-when-reading-rebootcount-in-generaldiagnosticscluster" /><item><title>RE: FAILURE response when reading RebootCount in GeneralDiagnosticsCluster</title><link>https://devzone.nordicsemi.com/thread/560577?ContentTypeID=1</link><pubDate>Sat, 07 Feb 2026 00:16:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e6996d0-b262-467b-8c43-0175e63905bd</guid><dc:creator>chiba</dc:creator><description>&lt;p&gt;Thank you, your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FAILURE response when reading RebootCount in GeneralDiagnosticsCluster</title><link>https://devzone.nordicsemi.com/thread/560523?ContentTypeID=1</link><pubDate>Fri, 06 Feb 2026 09:21:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0698373-1228-4644-97a0-db1139096355</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It seems like it is in fact a bug. When the last fabric is removed, the factory reset is essentially performed. Since we remove all of the data, we also remove the reboot count variable - but we do not reboot ourselves due to KConfig, and we don&amp;#39;t re-initialize the setting. Since the setting does not exist, the error is returned.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The solution is to either reboot the board once (the reboot count will be re-initialized on the reboot), or change the implementation of the last fabric removal:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;diff --git a/samples/matter/common/src/app/fabric_table_delegate.h b/samples/matter/common/src/app/fabric_table_delegate.h
index 5e914cd4cf..b9dc2d8327 100644
--- a/samples/matter/common/src/app/fabric_table_delegate.h
+++ b/samples/matter/common/src/app/fabric_table_delegate.h
@@ -60,6 +60,8 @@ private:
                                chip::DeviceLayer::PersistedStorage::KeyValueStoreMgrImpl().DoFactoryReset();
                                /* Erase Network credentials and disconnect */
                                chip::DeviceLayer::ConnectivityMgr().ErasePersistentInfo();
+                               /* Make sure Reboot Count is set to 1 */
+                               chip::DeviceLayer::ConfigurationMgr().StoreRebootCount(1);
#ifdef CONFIG_CHIP_WIFI
                                chip::DeviceLayer::WiFiManager::Instance().Disconnect();
                                chip::DeviceLayer::ConnectivityMgr().ClearWiFiStationProvision();&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;The above change works for me (the person looking into this from the Matter Team), and I don&amp;#39;t see the error anymore. Though the reboot count is reset to 1. The user might read it before ErasePersistentInfo() and set it again to the same value if they prefer.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;There is a task started internally to fix this in a future release, but I do not have details on exactly how it will be implemented.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FAILURE response when reading RebootCount in GeneralDiagnosticsCluster</title><link>https://devzone.nordicsemi.com/thread/559651?ContentTypeID=1</link><pubDate>Tue, 27 Jan 2026 09:48:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:996f4784-efe6-4928-8d6a-ee6c99901fee</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Sorry for the late reply. I need to run this by our Matter team. I will get back to you as soon as I know more.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>