Thanks both. My limited understanding from reading the blog was that this ‘new way of doing things’ uses a keymap file and I think I already have one of those. I’ll have a check and backup if I can find it then.
So this “new way” mainly concerns the OSMC remote controls. If you don’t have a dongle for one of those remotes plugged in this new custom keymap is not loaded. If you use a keyboard, or another remote or controller that presents itself to Kodi as a keyboard then there may be some interaction which you can mitigate by turning off the custom map as outlined [here].
If you have existing keymaps your using in your userdata folder (including what is created by the Keymap Editor add-on) these are not deleted, modified, or disabled. Any existing keymaps are actually loaded after our new custom map so your tweaks will not only stay in place, they will also affect the OSMC remote as well.
I know! I reset the hub/remote’s profile from the iPhone app intentionally as I wanted to eliminate the harmony hub being the problem when trying to connect to Vero via Bluetooth.
Also, looks like I spoke too soon. Successfully paired the hub with vero via Bluetooth earlier, all looked good. Rebooted vero just now and the Bluetooth pairing has disappeared. Repaired again, connected via Bluetooth, rebooted, and same again…Bluetooth profile on vero has disappeared.
As suggested previously I should now probably upload a log, yes? Try and pair again via Bluetooth, enable debug logging, reboot and upload log? (Sorry, bit of a novice with this stuff).
Mar 26 16:42:09 osmc hciattach: Initialization timed out.
Mar 26 16:42:09 osmc hciattach: bcm43xx_init
Mar 26 16:42:09 osmc hciattach: Flash firmware /etc/firmware/BCM4345C0.hcd
Mar 26 16:42:09 osmc systemd: sdio-bt-firmware.service: Control process exited, code=exited status=1
Mar 26 16:42:09 osmc systemd: Failed to start Vero3 Bluetooth support.
Mar 26 16:42:09 osmc systemd: Startup finished in 3.491s (kernel) + 32.717s (userspace) = 36.208s.
Mar 26 16:42:09 osmc systemd: sdio-bt-firmware.service: Unit entered failed state.
Mar 26 16:42:09 osmc systemd: sdio-bt-firmware.service: Failed with result 'exit-code'.
Interesting. Thanks for the response. I do have a keyboard somewhere but I’m an absolute novice with regards to this. If I plugged a keyboard in, how would I access the command line? And is this all one command? Need to brave a supermarket as the cupboards are bare but will try when I get back. Thanks.