Quote Originally Posted by chunter2 View Post
I too am trying to figure out how to use a blaster with ir-keytable. With lirc I had a blaster section in the lircd.conf file that was used with a channel change script that mythtv would run when it would start a recording on my satellite box. The channel number would be passed to the script which would use irsend to "blast" each number. How would this work with ir-keytable only?

This is part of the problem with using ir-keytable and ditching lirc completely. At least with any instructions I have seen so far, ir-keytable only offers a subset of the functionality of the original LIRC. Three things it does not appear to offer, or that no one has explained how to do:

1. Ease of setup by picking your remote (and IR sender, if you are using one) from a list, without having to mess with or modify config files (sadly this has been lost in the most recent version of LIRC).
2. Ability to use for purposes outside a specific program by using a .lircrc (or equivalent) file. For example if you are running a desktop version of Ubuntu, how do you launch your media program (Kodi or MythTV) using only the remote? With LIRC you are not limited to controlling only certain programs; with a little bit of bash scripting skill you can control damn near anything from the remote (I have actually used it to toggle power to a lamp, by sending a command to a Raspberry Pi power control device elsewhere on the local network). If there is a way to do this in ir-keytable, nobody has bothered to explain it as far as I have seen.
3. The blasting ability you mention, using the irsend command - see http://www.piddlerintheroot.com/ir-blaster-lirc/ and/or https://translate.google.com/transla...-text=&act=url (English translation by Google) for examples of how this can be used.

Also there is the problem that certain keys on the remote just don't seem to work as they should for some people when using ir-keytable.

For now, as explained in other threads, it is still possible to revert to an older version of LIRC (for example see https://twosortoftechguys.wordpress....-ubuntu-18-04/) and that solves all of these issues. But at some point that solution may no longer be workable, unless some programmer decides to fork and rename and maintain the former (0.9.x) version of LIRC, which is something I'd truly love to see, because for many users (including myself) the former version of LIRC has been the only thing that consistently works and works well, provided you don't upgrade to that gahdawful 1.x version that's offered in the more recent Ubuntu repos. Really wish they would add lirc-classic to the Ubuntu repo (that being the version of LIRC that's in the Ubuntu 16.04 repo).