EnOcean Switch Demo

[tealtech]

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 into commissioning mode but the nrf52 fails to acknowledge any commissioning telegrams. Out of commissioning mode I can see the BLE advertising packets from the ptm215b during normal operation, and these aren't present after the 'long-short-long' commissioning sequence, which suggests that the ptm215b is sending commissioning telegrams ok. 

How can I tell whether the nrf52 is receiving the commissioning telegrams?

Are there any known issues with this example? I'm using Segger toolchain.

[supershirobon]

I am having the exact same problem, and I've confirmed from reading the NFC Tag that the 'Disable Radio Commissioning" flag is not set, so I'm lead to believe the example is faulty.

[tealtech]

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'd.

How are you reading the PTM215B NFC tag? Is it an App?

[tealtech]

I managed to use NXP's 'Tag Writer' App to read the Enocean NFC tag, and also confirmed that the 'Disable Radio Commissioning' 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.  Should I be able to see commissioning packets in nRF Connect?  The PTM215B data sheet suggests that the commissioning telegram is a BLE advertising packet?

[Bjørn Kvaale]

I have asked about this internally & will update this thread when I know more. I guess you have followed the testing documentation on the infocenter, correct?

[tealtech]

I have been in contact with Enocean regarding this issue.  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.  This has been corrected in the latest firmware.  Hopefully they can provide a workaround or a replacement switch.  As soon as I can verify all of this I'll let you know.

[Bjørn Kvaale]

Ahh, ok. So this could be an issue on the enocean side & not on the Nordic side? We will take a look at the issue on our side too & verify.

[tealtech]

I can confirm that the issue was with the Enocean switch firmware.  I tested a new switch with the latest firmware and it all works OK.