Hello all,
I've got a RPi 3 which I use to view YouTube stuff on a TV. Although the
TV automatically switches to the RPi when the latter is switched on, it doesn't switch back when the RPI is shut down.
Question : is anyone know of a program which will release the TV (so it can switch back to whatever it was displaying before, as it happens with my DVR) ?
Regards,
Rudy Wieser
I've got a RPi 3 which I use to view YouTube stuff on a TV. Although the
TV automatically switches to the RPi when the latter is switched on, it doesn't switch back when the RPI is shut down.
Question : is anyone know of a program which will release the TV (so it can switch back to whatever it was displaying before, as it happens with my DVR) ?
Have you tried powering down your pi? - does it switch then?
Yep, nope (I just repeated the test to be sure I did). The TV just keeps >showing a "no signal" message.
Have a look what commands you can send to the TV using cec-client
I've had a similar problem with the pi4 and an hdmi monitor.
Have you tried powering down your pi? - does it switch then?
Then there is nothing you can do about the pi, it's turned off.
So you must check if there is a setting on your HDMI switch
Joerg,
Then there is nothing you can do about the pi, it's turned off.
:-) There is a moment before its shut down and powered off that its still running. That would be a splendid moment to have the RPi tell the TV that
it should switch its inputs away from the RPi, don't you think ?
So you must check if there is a setting on your HDMI switch
What switch ? You mean the one thats part of the TV ? That one doesn't
have a settings panel I'm afraid.
Regards,
Rudy Wieser
:-) There is a moment before its shut down and powered off that its still running. That would be a splendid moment to have the RPi tell the TV that
it should switch its inputs away from the RPi, don't you think ?
why not use the remote to switch it over?
It might be worth trying "vcgencmd display_power 0" at that...
point,which I think effectively stops the HDMI output,
it's "vcgencmd display_power 1" to get the picture back
:-) There is a moment before its shut down and powered off that its still >running. That would be a splendid moment to have the RPi tell the TV that
it should switch its inputs away from the RPi, don't you think ?
So you must check if there is a setting on your HDMI switch
What switch ? You mean the one thats part of the TV ? That one doesn't
have a settings panel I'm afraid.
You might want to try the vgencmd thing Russell suggested, but
other than that...
Sorry, I was mixing things up with my own setup here.
Basically why I got an HDMI switch although my TV has plenty[snip]
input
:-) And how would I be able to see what I was typing, with HDMI having
been switched off ?
SSH?
You might want to try the vgencmd thing Russell suggested, but other
than that...
This SRB: Standard Rudy Behaviour
Look up his previous questions and replies in the archives. He'll ask a question, people make suggestions, he'll not find any of the suggestions acceptable or there'll be extra information provided after the suggestions that makes the situation different. And it goes on for a while. Lather, rinse, repeat.
Lawrence,
:-) And how would I be able to see what I was typing, with HDMI
having been switched off ?
SSH?
The idea is to *solve* the problem.
:-) And how would I be able to see what I was typing, with HDMI having
been switched off ?
You don't know how to use SSH?
Lawrence,
You don't know how to use SSH?
SSH is just part of the equation.
SSH is just part of the equation.
That's a back down from your previous position that it would only make
the problem worse, then?
Russel,
It might be worth trying "vcgencmd display_power 0" at that...
point,which I think effectively stops the HDMI output,
it's "vcgencmd display_power 1" to get the picture back
:-) And how would I be able to see what I was typing, with HDMI having been switched off ?
Yes, I also thought of such a solution. But :
1) It looks like that shutting- and powering-down the RPi should be "rather effective" in stopping the HDMI output.
... without the other parts of the equation ...
I suppose you could use a command like this just to try it out
briefly with no need for further typing:
vcgencmd display_power 0;sleep 10;vcgencmd display_power 1
1) It looks like that shutting- and powering-down the RPi should
be "rather effective" in stopping the HDMI output.
Well, yes, there is that. :-)
Turning off your monitor on the remote machine? SSH works fine in
that situation.
Although you did not mention it, I take it you picked up on that just disabeling HDMI output doesn't cause my TV to switch back to its previous input. Which means that that vcgencmd doesn't seem to be the sought-for solution (and nullifies the need to test it).
Although you did not mention it, I take it you picked up on that just >disabeling HDMI output doesn't cause my TV to switch back to its previous >input. Which means that that vcgencmd doesn't seem to be the sought-for >solution (and nullifies the need to test it).
Yes, it is possible for a Raspberry Pi to send a signal to a TV to[snip]
switch the HDMI input before shutting down. This can be done using CEC (Consumer Electronics Control), a feature available through HDMI that
allows devices to communicate with each other and exchange basic control commands.
I just asked ChatGPT if it knew an answer,
Yes, it is possible for a Raspberry Pi to send a signal to a TV to
switch the HDMI input before shutting down. This can be done using
CEC (Consumer Electronics Control),
Andy,
Have a look what commands you can send to the TV using cec-client
A "cec-client" you say ? I'll have to look for it.
Lawrence,
Turning off your monitor on the remote machine? SSH works fine in
that situation.
What are you talking about ? A "remote machine" ?
You'll then need to find the commands change the source
I just asked ChatGPT if it knew an answer,
was that the first answer it gave, or did you have to hit "refresh" a couple >of times ?
Turning off your monitor on the remote machine? SSH works fine in
that situation.
What are you talking about ? A "remote machine" ?
The one you are SSHing to.
A "cec-client" you say ? I'll have to look for it.
apt install cec-client
You'll then need to find the commands change the source, which will depend[snip]
on your TV. Pages such as this may help
You'll then need to find the commands change the source
The answer may be buried here ... but buried quite deep ...
<https://www.cec-o-matic.com>
I just asked ChatGPT if it knew an answer,
was that the first answer it gave, or did you have to hit "refresh" a >>couple of times ?
The first answer, which appeared immediately, was in German, so as a
second I just said "Now the whole thing in English".
I have no idea what you are saying here. I'm supposed to be "SSHing" ?
Though I was curious if it perhaps gave responses which where not quite as >usable (rubbish perhaps?) as the one you posted (I heard about an AI's >capacity to "halucinate").
I have no idea what you are saying here. I'm supposed to be "SSHing" ?
I think the whole "SSH distraction" arose when
wondered how you'd type a command when you couldn't see what you were...
typing because the screen would be black ...
I think most people could manage to type a command "blind" to re-enable
the screen,
but then someone suggested you could SSH to the Pi from somewhere else to type the command to re-enable the screen
its very depths it is supposed to keep up some chatty behaviour.
... Though my guess is that he doesn't actually know much of anything about it. Just some "big words" he tried to impress me with.
... Though my guess is that he doesn't actually know much of anything
about
it. Just some "big words" he tried to impress me with.
Most people on this list would interpret 'SSH?' as
since the pi likely has a ssh-deamon running, from another commputer ssh
to the pi
so get the ip of the pi, and connect another pc to the same network and
type
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 14 |
Nodes: | 6 (0 / 6) |
Uptime: | 231:29:12 |
Calls: | 55 |
Calls today: | 1 |
Files: | 50,127 |
D/L today: |
29 files (3,538K bytes) |
Messages: | 275,360 |