<?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>EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39578/enocean-switch-demo</link><description>I have successfully built and run the mesh examples 2.2.0, on several nrf52832dk boards with the exception of the EnOcean Switch example. 
 I can successfully build and launch the example, but it fails to commission the PTM215B switch. I can put the switch</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 29 Oct 2018 20:47:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39578/enocean-switch-demo" /><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/154963?ContentTypeID=1</link><pubDate>Mon, 29 Oct 2018 20:47:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c156de2-aeb8-417d-9084-8aa797cc2930</guid><dc:creator>tealtech</dc:creator><description>&lt;p&gt;I can confirm that the issue was with the Enocean switch firmware.&amp;nbsp; I tested a new switch with the latest firmware and it all works OK.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/153995?ContentTypeID=1</link><pubDate>Tue, 23 Oct 2018 08:28:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5249d2f9-1592-47f7-86c0-aeb40f833f94</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Ahh, ok. So this could be an issue on the enocean side &amp;amp; not on the Nordic side? We will take a look at the issue on our side too &amp;amp; verify.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/153908?ContentTypeID=1</link><pubDate>Mon, 22 Oct 2018 17:55:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb05a883-9bb7-4b9c-93d4-1d59a63d8fe4</guid><dc:creator>tealtech</dc:creator><description>&lt;p&gt;I have been in contact with Enocean regarding this issue.&amp;nbsp; It appears that there is a known issue with a firmware release which transmits an incorrect packet length during the radio based commissioning process, causing the packet to be rejected.&amp;nbsp; This has been corrected in the latest firmware.&amp;nbsp; Hopefully they can provide a workaround or a replacement switch.&amp;nbsp; As soon as I can verify all of this I&amp;#39;ll let you know.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/153805?ContentTypeID=1</link><pubDate>Mon, 22 Oct 2018 12:31:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a39f98ac-c3d9-4840-9bfd-b6b6e2809937</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;I have asked about this internally &amp;amp; will update this thread when I know more.&amp;nbsp;I guess you have followed the&amp;nbsp;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v2.2.0/md_examples_enocean_switch_README.html?cp=4_1_0_4_2"&gt;testing documentation&lt;/a&gt; on the infocenter, correct?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/153726?ContentTypeID=1</link><pubDate>Sun, 21 Oct 2018 18:28:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e030fc91-8e03-4e5e-88d2-c573b5b9eeb6</guid><dc:creator>tealtech</dc:creator><description>&lt;p&gt;I managed to use NXP&amp;#39;s &amp;#39;Tag Writer&amp;#39; App to read the Enocean NFC tag, and also confirmed that the &amp;#39;Disable Radio Commissioning&amp;#39; flag was not set. I also modified the parsing function to capture any telegrams containing the Enocean manufacturers code, but nothing is captured during commissioning.&amp;nbsp; Should I be able to see commissioning packets in nRF Connect?&amp;nbsp; The PTM215B data sheet suggests that the commissioning telegram is a BLE advertising packet?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/153712?ContentTypeID=1</link><pubDate>Sat, 20 Oct 2018 15:37:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:604043e3-5667-4aa1-a7a0-cf5061df6872</guid><dc:creator>tealtech</dc:creator><description>&lt;p&gt;I have found the packet-parse() function in enocean.c and confirmed the receipt of standard data telegrams but commissioning packets never seem to be rx&amp;#39;d.&lt;/p&gt;
&lt;p&gt;How are you reading the PTM215B NFC tag? Is it an App?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: EnOcean Switch Demo</title><link>https://devzone.nordicsemi.com/thread/153531?ContentTypeID=1</link><pubDate>Thu, 18 Oct 2018 19:51:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94faae3c-e488-4574-8329-30f90106b4df</guid><dc:creator>supershirobon</dc:creator><description>&lt;p&gt;I am having the exact same problem, and I&amp;#39;ve confirmed from reading the NFC Tag that the &amp;#39;Disable Radio Commissioning&amp;quot; flag is not set, so I&amp;#39;m lead to believe the example is faulty.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>