<?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>[BUG] lwm2m firmware update result is not set, firmware update state is set instead</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/86355/bug-lwm2m-firmware-update-result-is-not-set-firmware-update-state-is-set-instead</link><description>Hi, 
 I have just bumped the NCS I am using for my project to version 1.9.1. After this update, I found a bug in the Zephyr code. 
 On line 214 of zephyr/subsys/net/lib/lwm2m/lwm2m_obj_firmware.c: 
 
 The number &amp;quot;3&amp;quot; should be a number &amp;quot;5&amp;quot;. This means</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 29 Mar 2022 11:34:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/86355/bug-lwm2m-firmware-update-result-is-not-set-firmware-update-state-is-set-instead" /><item><title>RE: [BUG] lwm2m firmware update result is not set, firmware update state is set instead</title><link>https://devzone.nordicsemi.com/thread/360511?ContentTypeID=1</link><pubDate>Tue, 29 Mar 2022 11:34:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1e595d5-4c68-4675-aa1c-e31f6f6645ab</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
[quote user=""]I know this is a Zephyr issue, I will maybe do a PR to fix this.[/quote]
&lt;p&gt;Yes, that is correct. This is a Zephyr library.&lt;/p&gt;
[quote user=""]I saw that this is fixed in&amp;nbsp;c2550d56c8163fc230334cefcaa7b8f0c4565936. I will cherry-pick this fix for now, but when is the plan that it will be released a fix for this as part of NCS?[/quote]
&lt;p&gt;The fix should be available in the main branch, and will be included in the next release.&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>