Support > Remote Buddy Forum > How to create a Custom Action which runs a built-in Kodi action // IOSPIRIT [EN]

Support

All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.

Forum closed

This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview

Author

Thread

User

09.04.2017 06:15:54

How to create a Custom Action which runs a built-in Kodi action

View

This posting is older than 6 months and can contain outdated information.

I'm running Kody 17.1 with the latest RBE. I have created quite a few custom actions but, I can't figure out how to do that with a built-in Kodi action.

For example, Kodi has the built-in action "Seek(##)". I would like to map "Seek10" to a key on my Harmony remote. But, I can't find a way to do it. A single keystroke can't do it (unless I can somehow map "Seek10" to that keystroke. It looks like Kodi is not scriptable (Script Editor can't find a dictionary). There's nothing else I can't find that comes close.

There are a good number of built-in actions for Kodi in RBE. But, they don't include Seek. Kodi keymaps can be edited but, the GUI keymap editor doesn't include the Seek action and my attempts to manually edit the user's keymap file have failed.

So, is it possible to add the Seek(##) action to the standard set supplied with RBE ?

Thanks.

Garry

Last edited: 09.04.2017 06:40:49

These entries from the FAQ may be relevant to this topic:

Configuration

How do I add a new action to a Behaviour - f.ex. an emulated key press or AppleScript? (FAQ015E0153)
1) Open the Remote Buddy Preferences via the pulldown-menu and choose "Mapping".
2) Choose the mapping you want to modify.
3) Select "Custom actions" for the button you want to map to an action of your own.
4) Create the action you need using the appearing editor.

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs