Enocean release not detected

[BubDev]

SDK 15.2

Mesh SDK 3.1.0

Base Example: Enocean_Switch

Im working on creating an LED dimming firmware that uses a long press on the Enocean remote to dim the LED. It works well most of the time but will miss the release message about 10% of the time. My question is, does the Enocean handler have a low priority level and if a bluetooth mesh message is going on will it ignore the Enocean release message? Could this be because the Enocean remote doesn't successfully send out the BLE message? 

I need to be able to reliably detect a release from the Enocean remote so the dimming will stop.

Any advice will be greatly appreciated.

Thanks

[Simonr]

Hi Brad

What exact Enocean switch are you using, and is it happening on one specific one or does it happen on multiple switches? This case covers an issue that was with one of the older Enocean firmware versions.

I see that most of the Bluetooth switches, if not all, generate 2 or 3 advertising events according to the user manual. You could try using a sniffer to see if and how many packets are sent and would give you a good indication if the packets are sent and/or received at all. The nRFSniffer is great if you have a spare DK or a 51Dongle.

Best regards,

Simon