![]() I've read in a few other places that powered usb hubs sometimes make a difference when having issues with usb devices as well. Would you suggest something with even more amps? What I'm using is just a generic cell phone charger from an Android phone, not the "official" RPi power supply cable you can purchase. ![]() It is 5V and 700mA as specified on the website. I checked my power supply against the RPi requirements. The device seems to show up when usb devices are queried about 50% of the time. I grabbed the remote and hammered the up/down arrows and noticed that when the device does appear using the lsusb command I can get the menu to move up/down, but only once out of every 50 or so presses. The weird thing was I can run the command twice within seconds of each other and sometimes the devices is there and other times it isn't. The lsusb command did show the device (I'm assuming it is the one showing up as "Clay Logic" as that does not exist when FLIRC is not plugged in). Fswitch_onĮdit: I see you edited the post but the syntax is still wrong.Thanks to kramer and Chris! for their replies. It could also be security (disable authentication on local network), protected switch or something like that. conf file (there are also some extra spaces on your example but perhaps those are because of some copy/paste issue? ) I think it's case sensitive so the string you have there will not work like that but I'm not sure if you just wrote something there and have the correct format in the. I would first verify it ( = http: // url: port / json.htm? Type = Command & param = Switch light & idx = IDXofNEOplug & switchcmd = On) works in the browser. I get the error message in Domoticz saying Invalid ON Action! Harlov wrote:I think I have got it working with savings in /etc/triggerhappy/triggers.d/ but when I need to type in DomoticzĮV_KEY KEY_PLAYPAUSE 1 curl -s "http: // url: port / json.htm? Type = Command & param = Switch light & idx = IDXofNEOplug & switchcmd = On" Log_daemon_msg "Restarting $DESC" "$NAME"ġ) log_end_msg 1 # Old process is still runningĮcho "Usage: $SCRIPTNAME " >&2 Status_of_proc "$DAEMON" "$NAME" & exit 0 || exit $? & log_daemon_msg "Stopping $DESC" "$NAME" & log_daemon_msg "Starting $DESC " "$NAME"Ġ|1) & log_end_msg 0 Ģ) & log_end_msg 1 Start-stop-daemon -stop -signal 1 -quiet -pidfile $PIDFILE -name $NAME # restarting (for example, when it is sent a SIGHUP), # If the daemon can reload its configuration without Flirc not working as expected with Raspberry Pi Windows. ![]() # Function that sends a SIGHUP to the daemon/service # Many daemons don't delete their pidfiles when they exit. Start-stop-daemon -stop -quiet -retry=TERM/30/KILL/5 -pidfile $PIDFILE -name $NAME Start-stop-daemon -start -quiet -pidfile $PIDFILE -exec $DAEMON - \ Start-stop-daemon -start -quiet -pidfile $PIDFILE -exec $DAEMON -test > /dev/null \ # Function that starts the daemon/service # Depend on lsb-base (>= 3.0-6) to ensure that this file is present. # Load the VERBOSE setting and other rcS variables # Read configuration variable file if it is present As an aside before we continue on with the tutorial, FLIRC also makes a really awesome Raspberry Pi 2 / B+ case (16) that features an integrated aluminum-body heat sink if you're looking for a good media center case for your Pi it's not just good looking it's also quite efficient at keeping your board cool. # Short-Description: triggerhappy hotkey daemonĭAEMON_ARGS="-daemon -triggers /etc/triggerhappy/triggers.d/ -socket /var/run/thd.socket -pidfile $PIDFILE -user nobody /dev/input/event*" Logitech Harmony: This can refer to any logitech powered harmony remote control Inteset Remote: A remote control branded by inteset, a flirc partner. uname -a Linux ubuntu 5.4.0-1042-raspi 46-Ubuntu SMP PREEMPT Fri Jul 30 00:35: aarch64 aarch64 aarch64 GNU/Linux lsbrelease -a No LSB modules are available. This is primarily for advanced users and is installed alongside the GUI. just in case you don't have it, the content of the triggerhappy file in /etc/init.d/ is: I installed Ubuntu Server 20.04.2 LTS for Raspberry Pi on my Raspberry Pi 3 B+. thd.1.html) thd -dump /dev/input/event* which dumps all events processable by thd to the console (useful to find out the correct event name for a specific key). by running cat /etc/init.d/triggerhappy - if you are running Jessie it might be something else). Just check that you have a file called "triggerhappy" in /etc/init.d/ (check it e.g. Well, in my Raspbian Wheezy it was running automatically by default, no need to install or do anything. What I do not understand is how to start Trigger Happy (thd). Harlov wrote:I thank you very much for this
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |