Well … I’ve got a hunch, but I will need to continue monitoring and further test some things out with my setup. I turned on TRACE level logging for the alarm decoder binding, and didn’t see much extra info. It looked as though everything was operating as expected. Can see all the zone info properly, can see the details display messages, everything looked good. But key presses just were not fully translating.
I went to bed last night, this afternoon ran some more tests. Was still not getting anything. So I decided to fire up minicom and watch the output to see if I could do at the same time as OH so I could see if data was going across at all. Two terminal windows, one inside Karaf console, other in minicom. Used the test keypad, and suddenly the keypresses were making it across. System started arming, and disarming, but some messages got wonky - probably because the binding and minicom were trying to read the output and I was inundating the system with presses. Now I exited minicom with no reset, continued testing, working. Entered minicom again and exited with a reset. Keypress still working.
My hunch, is that somehow the AD2USB device was not getting started? Somehow in the process of OH startup perhaps, the serial port wasn’t being first initialized to allow the transfer of data across? I’m going to try restarting the system at some point that is hooked up to see what happens.
The only downside I have at this point, is I’m relegated to multiple updates to the item with each number press required, vs being able to parse a whole string across to the keypad. Any way this could be achieved differently @Bernd_Pfrommer? And I will leave my logs on trace for now so I can see what I may get if it faults up again on me and post it here.