Best remote for flirc6/11/2023 ![]() Listen for events from “keyboard_remote_command_received” and press the individual buttons. Go to the Developer Tools and then the Events tab. To do so, you need to obtain the “key_code” for each programmed button. Now you can make automations capable of anything your Home Assistant can do from the press of a button. Once you see it’s recognized, add the following to your configuration.yaml and restart: keyboard_remote: First, confirm it is recognized by Home Assistant by looking in the Supervisor’s Hardware tab. Now the Flirc can be set up in Home Assistant using the Keyboard Remote integration. Once you have recorded all the keys you want, you unplug the device from your computer and plug it into your Home Assistant box. You do not need to remember which buttons are mapped to which keys because they will later be identified in Home Assistant by watching the event log. Next, click on a key, and it will ask you to press the corresponding button on the remote. I think selecting a standard keyboard makes the most sense to maximize the number of programmable keys. ![]() There are a number of virtual keyboard or remotes you can select. So let’s walk through how this would be set up.įirst, download the software from the website and plug in the USB device. Except, instead of interacting by physically pressing keys, the key is “pressed” when it detects the corresponding infrared frequency. Those codes are saved on the device itself, so it can be moved to your Home Assistant Operating System box and will be seen as just an ordinary keyboard. The software lets you assign buttons to a virtual keyboard by selecting individual keys and firing your remote at it. First, you plug it into a PC, Mac, or Linux machine. This reply was modified 5 years, 10 months ago by relgi.The amazing thing about this device is its simplicity. The script name is fb.sh and that is the crontab /home/pi/fb.sh # Nur asuführen wenn jivelite im AutostartĪutostart=$(grap -a „jivelite=1“ /opt/max2play/autostartconf | wc -l)Įcho „Jivelite nicht im Autostart – irxevent wird nicht gestartet!“Įcho ‚DISPLAY=:0 irxevent -d /home/pi/lircrc‘Įcho’DISPLAY=:0 irxevent -d /home/pi/lircrc‘ # Short-Description: Starts & Stops fb.sh I try it as a script whit crontab like follow: My Problem is, to do that string anywhere in the boot sequence. ![]() This reply was modified 7 years, 4 months ago by Bort.Įverything with my remote control works fine, if I wrote in the shell of the remote session this:īut after a reboot of the Raspberry PI3, I have to do it every time again. via irw) – otherwise thee nf may be not correct… irxevent /etc/lirc/lircrcĪlways check lircd for running correctly (e.g. Instead of jivelite you may use CurrentWindow as target for the keyboard emulation and control even other applications with the mapped keys in the lircrc.ģ.) On startup you need a script which waits for the successfull start of lircd and jivelite to start finally irxevent e.g. # jivelite second power off for display backlight 'q' ![]() ![]() Or for multiple keyboard action just double the block: # Remote: big green button Since Jive Lite has no native IR/lirc support, I had to use irxevent:ġ.) complete nf for all keys you wanted to use (for such a much-used remote like the XBOX one just download it somewhere -))Ģ.) take the whole needed mapping from IR-keys to the keyboard control of jive lite (reference: a) in the lircrc config file I’ve nearly the same configuration (7″ touch + jive lite + + XBOX one remote clone) for both of my kids very stable and nearly indestructible.Īt first I played around with some default key mappings like „KEY_RIGHT“ this worked – but the remote has a lot of more keys □ ![]()
0 Comments
Leave a Reply. |