Nodon Octan remote does not register concurrent button presses

[bazyr]

Hi all

I have recently had to completely reset and re-set up my Homeseer/Z-wave network. Previously, I had a pair of Nodon Octan remotes which would cycle through a number of scenes with a button press (using Events). This worked well.

Now, I notice that the Homeseer only recognises the first press of any button. It won't log the second, third, fourth etc... I have to press another button (which appears in the log fine), then go back to the first button for it to register again.

For instance, if I press: 1, 1, 2, 3
Homeseer sees: 1, 2, 3

If I press: 1,1,1,1,4,4
Homeseer sees: 1,4

What's going on? How can I get Homeseer to see concurrent presses of the same button? I doubt it's anything to do with the remotes themselves, as they previously worked this way fine.

Current Date/Time: 8/3/2018 9:04:00 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.435
Linux version: Linux hometrollerSEL 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 0 Days 0 Hours 6 Minutes 36 Seconds
IP Address: 192.168.86.240
Number of Devices: 275
Number of Events: 10
Available Threads: 199
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:

Enabled Plug-Ins
3.0.0.21: Chromecast
0.0.0.5: Nanoleaf 3P
3.0.0.31: Nest
3.0.1.190: Z-Wave

[zwolfpack]

Make sure the trigger uses 'had its value set' not 'changes and becomes'. The value doesn't change on successive presses of the same button.

[bazyr]

Thanks zwolfpack -- that seems to work!