Well - if your devices end up the same as for me and for others who have posted in this thread, then you probably have changed the keymap of your built-in keyboard. If that's gone funny now you should be able to get it back to normal by rebooting -- the setxkbmap command should not have any permanent effects.

While I haven't gotten anything to work so far, it's pretty clear to me that the number following the "-device" option must be the ID of the bluetooth keyboard. If the bluetooth keyboard doesn't show up as a device, we don't have a handle for specifying that we want to alter the keymap for that device.

Best regards, Jan