SupaCEC - A utility to switch TV inputs when a controller is connected
-
Ah yes sorry, didn't had much time the few past days.
The udev rule was quite simple :
ACTION=="add", SUBSYSTEM=="input", RUN+="echo 'as' | cec-client -s -d 1"Unfortunately, the RUN primitive of udev rules seems not to apply since systemd.
I wasted an entire evening to understand that by testing :)
Then I found this thread :
https://retropie.org.uk/forum/topic/3335/anyone-familiar-with-udev-rulesIt should be possible to circumvent this via the use of a systemd daemon script.
Maybe @mediamogul can help us on this one, as he faced the same issu ?
-
@Sano said in SupaCEC - A utility to switch TV inputs when a controller is connected:
ACTION=="add", SUBSYSTEM=="input", RUN+="echo 'as' | cec-client -s -d 1"
No, I think the problem is that udev doesn't parse pipe or redirects as it doesn't run a shell but passes arguments literally. If you use "/bin/sh -c 'commands'" it should process pipes and redirections correctly.
-
Thanks, but I also tried to call a simple shell script with the command line and, it was not working either...
So seeing @mediamogul post I thought udev/systemd was indeed the problem... -
Yes, it's not working, but I did try: "/usr/bin/touch ~/test", and it worked, so the RUN argument is not fully deprecated.
There are existing udev scripts in retropie that run commands directly, and I even added my own to control disk spindown via smartctl, so it does work... I'm betting the problem is the pipe.
-
@psyke83
Roger that, but why my call to a (working) sh script didn't work ?
And why does a simple touch works ? Strange AF...Plus there are a lot of this kind of docs highlighting the need of a systemd script in order to launch anything... https://fixmynix.com/run-shell-scripts-from-udev-rules/
-
I got it to work like so:
ACTION=="add", SUBSYSTEM=="input", RUN+="sh -c /home/pi/waketv.sh"
waketv.sh:
#!/bin/sh
/bin/sh -c 'echo 'as' | cec-client -s -d 1'I'll see if there's a way to make the pipe work without relying on a script.
-
@psyke83
Congrats !
That said, even with your syntax I can't make it work on my setup :(
Maybe something is messed up on my RPi... -
Maybe @mediamogul can help us on this one, as he faced the same issu ?
Sorry, I'm just now seeing this. Unfortunately, I was never able to get further than what was posted in that original thread. I'm glad it's being revisited and that there might be a working option.
-
This should work:
ACTION=="add", SUBSYSTEM=="input", RUN+="/bin/bash -c 'echo 'as' | cec-client -s -d 1'"
I actually tested this (as someone else is using the tv):
ACTION=="add", SUBSYSTEM=="input", RUN+="/bin/bash -c 'echo test | tee /dev/kmsg'"For some reason, "test" is echoed three times to the kernel log & I'm not certain precisely why...
-
@psyke83 said in SupaCEC - A utility to switch TV inputs when a controller is connected:
This should work:
ACTION=="add", SUBSYSTEM=="input", RUN+="/bin/bash -c 'echo 'as' | cec-client -s -d 1'"
Sorry, still no luck :(
But thanks a lot for trying !For some reason, "test" is echoed three times to the kernel log & I'm not certain precisely why...
That I know :)
just run ansudo udevadm monitor -ebefore pluging anything
It's just the kernel and udev adding the new device, link, driver,... (depends on the device)
Easy to filter in the rules, if only the RUN primitive could work as intented...@mediamogul thanks for reading and answering anyway. Hope we'll find a clean solution. @psyke83 seems to be the man.
-
@Sano said in SupaCEC - A utility to switch TV inputs when a controller is connected:
ACTION=="add", SUBSYSTEM=="input", RUN+="/bin/bash -c 'echo 'as' | cec-client -s -d 1'"
OK, I commandeered the TV to test and can confirm it didn't work ;). However, the pipe is working via the tee command, so the problem might be due to the cec-client being called three times in succession. Can you try refining the rule and testing? Also test "tee >/dev/kmsg" just to make sure there's no difference in configuration between our systems.
Edit: also, try specifying the path of cec-client in the command just in case the PATH is not initialized properly.
-
OK, this definitely works! ;)
ACTION=="add", SUBSYSTEM=="input", RUN+="/bin/bash -c 'echo as | /usr/bin/cec-client -s -d 1'"
The problem was either the nested apostrophes or missing PATH. I don't want to annoy the person watching the tv, so you'll need to test, but the above line worked for me. I assume it executed the command three times, however, so refining is a good idea.
This filter works for my DS3 controller causing it to execute once:
ACTION=="add", SUBSYSTEM=="input", KERNEL=="js[0-9]*", RUN+="/bin/bash -c 'echo as | /usr/bin/cec-client -s -d 1'" -
Ok finally found a simple solution working here, if anybody could test :
First install cec-utils :
sudo apt-get install cec-utilsCreate a /etc/udev/rules.d/10-cec.rules with this line:
ACTION=="add", KERNEL=="js0", SUBSYSTEM=="input", RUN+="/bin/bash -c '/bin/echo as | /usr/bin/cec-client -s -d 1'"Note the rule will match only for the first controller (js0) and execute only once, and also note the full path to binaries.
Reload udev rules :
sudo udevadm control --reload-rulesWhen you plug the first controller, the tv should switch to retropie.
I tested it with (wireless) PS3 controller and USB arcade stick.@psyke83
I was so concentrated testing things that I missed your post. Congrats, you found it first :)
The good thing is we both came to the same conclusions. -
Awesome @Sano and @psyke83! I haven't had a chance to test this yet, but I like where this was headed and wanted to formalize something. I'll hopefully test it tonight, in the meantime if anyone wants to look it over https://github.com/superterran/SupaCEC/tree/refactoring-to-udev-rule
-
The script seems to work fine* - except for unnecessary sudo invocations - on my DS3 controller. The previous test only switched to the Pi when the tv was off, but yours will also switch HDMI inputs when the tv is on.
- until you merge changes to the master branch, users need to specify the "refactoring-to-udev-rule" branch both in the curl instruction and manually appended to the gitPullOrClone line.
Edit: hmm, the first test worked, but second test after waiting for controller to timeout didn't switch inputs.
-
I've done further testing and come to the conclusion that cec-client only works reliably when a single command is invoked.
Your script appears to send the two commands simultaneously per line - the "pause" & switch source command, but both of your rules match my DualShock 3, which means it's 4 commands being sent at once.
The behaviour is unpredictable with your version; sometimes the tv will switch source and sometimes not. With my simpler version, it works more reliably, but it doesn't always work, especially after first boot. I have Kodi configured to start on boot, so it may be interfering somehow.
ACTION=="add", SUBSYSTEM=="input", KERNEL=="js[0-9]*", RUN+="/bin/bash -c 'echo as | /usr/bin/cec-client -s -d 1'"
-
@meleu :
(Screaming like a movie character with fists toward the sky)
Nooooooo ! Whyyyyyyy ? -
@Sano yo! Whats up doc?! :-)
-
@meleu It's my new (totally natural and not overacting) reaction to a downvote :)
I wish we had PM here...
Sorry ! -
@Sano OMG dude! Sorry! It was an accident (I was on the Android phone). You deserve an upvote!
I'm looking for a free time to join this conversation/development here. I'm interested!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.