The hardware and sending ir signals are the easy part . Management of it is the challenge
Mapping of commands to signals is one of the biggest hurdles.
If you have a mapping available I could add that quickly.
[edit] to be more specific: what do you want to do with it?
1. sends device specific codes eg LG TV vol up
2. some bytes and YOU give the sequence from your own command data, thats just GPIO on/off.s thats easy
1. requires install and config of "lirc" , thats the easy part.. and besides defining the GPIO for I/O >> setup / definition/ selection of codes from the MANY options available, or you cod use LRIC to learn the codes from pointing you remote at it.. ONLY then does it make sense to use indigo to send / receive codes, that mapping part is somewhat easy, b=ut the M<ANY different codes for the many different remote makes the management difficult to say the least.
All of that requires a lot of manual config and selection ON the RPI
what I can add is
1. define a IR device in plugin ( select RPI & which GPIO used)
2. action: send command to LIRC device (any thing you like ,eg "irsend SEND_ONCE LG_TV KEY_POWER"
3. mange start and stop of LIRC on the RPI,
==> but NOT the config management, activation of the many codes.
by the way you can do "irsend SEND_ONCE LG_TV KEY_POWER" now with send any unix command action in pibeacon,
- Screen Shot 2019-01-27 at 12.03.29.png (23.35 KiB) Viewed 4613 times
but you need to setup all of LIRC.
Karl
Sent from my iPhone using Tapatalk