I’m glad it’s being recognized as an active MIDI input/output.
While troubleshooting first close any other DAWs or music apps you might have open, as there could be some kind of weird auto-mapping going on with nanoKONTROL2 potentially disrupting the connection with Sensory.
Next make sure that the nanoKONTROL2 is only selected as an input and that it is deselected as an output. Deselect any other active MIDI inputs and outputs while you are testing the nanoKONTROL2.
Now try mapping the buttons to parameters in Sensory by following the steps on this page: https://help.sunhou.se/howto/switch-kits-with-a-midi-device.html
After you’ve got it working with all other music apps and DAWs closed, then, one-by-one, you can begin to turn on all of the other things that you run in conjunction with SP and see if/where the connection gets interrupted (and change the setting in the program that is causing the issue).
Let us know how it works out, and, if you are still having trouble, send us an email at email@example.com including a short video of Sensory’s IO window and attempting to map keys/knobs of the controller to parameters in Sensory.