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

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 30/07/2024 16:06, R.Wieser wrote:

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.

I've had a similar problem with the pi4 and an hdmi monitor. The monitor
is connected via one of those multi-input automatic switches: it won't
switch away when the pi is shut down - the pi4 needs to be powered down
too. Have you tried powering down your pi? - does it switch then?

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

--
Mike Scott
Harlow, England

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

R.Wieser wrote:

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 a look what commands you can send to the TV using cec-client

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

R.Wieser wrote:

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.

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 to make him switch
back when there is no signal on input x. If you don't have a setting for
this behaviour you need a different switch.

-jw-
--
And now for something completely different...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

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.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Mike,

I've had a similar problem with the pi4 and an hdmi monitor.

Thats the name I forgot, HDMI. The RPi 3 is connected to the TV using HDMI.

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.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

"R.Wieser" <address@is.invalid> wrote:

:-) 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 ?

It might be worth trying "vcgencmd display_power 0" at that point,
which I think effectively stops the HDMI output, just in case the TV
happens to treat that differently. I sometimes use that with a monitor
to do something similar. (You could try that out without turning off
the Pi of course, and it's "vcgencmd display_power 1" to get the
picture back.)

-Rus.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Chris,

why not use the remote to switch it over?

What do you think I've been doing all this time ? Buying a new TV every
time so I could go back to watching to whats on cable ? Thats a bit
expensive. :-)

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

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. And when I do I get a "no signal" message on my TV, confirming it.

2) looking at a black screen while trying to figure out if the RPi really
did shut down isn't really a situation I want to find myself in.

Being able to instruct the TV to switch away from the RPi gives the best of both worlds. In doubt I than can have the TV switch back to the RPi and
check if it really shut down.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

R.Wieser wrote:

:-) 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 ?

You might want to try the vgencmd thing Russell suggested, but other
than that...

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.

Sorry, I was mixing things up with my own setup here. Basically why I
got an HDMI switch although my TV has plenty input is exaxtly the
behaviour I described: whatever I turn on makes the switch go to this
new source, when I turn it off it goes back to what was playing before.
TVs don't do that, (most) switches do and with some switches the
behaviour can even be configured. So I have four HDMI devices all
connected to the switch and one HDMI cable from the switch to the TV.

-jw-
--
And now for something completely different...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Joerg,

You might want to try the vgencmd thing Russell suggested, but
other than that...

Andy Burns suggested something called "cec-client".

Sorry, I was mixing things up with my own setup here.

:-) I already assumed that that was the case.

Basically why I got an HDMI switch although my TV has plenty
input

[snip]

Hmmm... thats something I need to keep under consideration. Thanks.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

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. Tackeling one but at the same time creating the next ain't it.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 31/07/2024 08:28, Joerg Walther wrote:

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.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

mm0fmf,

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.

You forget to mention the part where I, /way/ to often, have to tell poster that what they offer isn't what I specifically asked for in the first post -
or worse, offering work-arounds which I already mentioned in that first post and not wanted to use.

... and than try to make it sound as if its all my fault, and sometimes as a result, as with you, bear a (life-long?) grudge.

Kid, I've encountered too many "helpfull" people who just skipped the
question and pretty-much demanded that I should accept their work-arounds as *the* solution. Others who claimed all kinds of things, but could, when pressed for it, not come up with any kind of substanciation, let alone
proof, for any of it.

Its also remarkable (not really) that you make a claim of wrongdoing, but am not supporting that claim in any way. Nothing by anything in this thread,
not by linking to any other one*. I know, I know. Putting your mouth where your money is is /dangerous/, as you could be proven wrong (like the last time?). :-)

* just a "go find yourself what the proof of my claim is" dismissing handwaving. Something rather dishonest those "knights of claim-a-lot" seem
to grocer in ...

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Wed, 31 Jul 2024 12:10:07 +0200, R.Wieser wrote:

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.

You don’t know how to use SSH?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Wed, 31 Jul 2024 09:14:46 +0200, R.Wieser wrote:

:-) And how would I be able to see what I was typing, with HDMI having
been switched off ?

SSH?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Lawrence,

You don't know how to use SSH?

:-) SSH is just part of the equation.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Thu, 1 Aug 2024 08:59:54 +0200, R.Wieser wrote:

Lawrence,

You don't know how to use SSH?

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?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Lawrence,

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?

You think so ? I think that without the other parts of the equation installing SSH is as usefull as a plane without wings.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

"R.Wieser" <address@is.invalid> wrote:

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 ?

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

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.

Well, yes, there is that. :-)

-Rus.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Russel,

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

That would indeed be a way to test if vcgencmd command works.

Though the problem is its suggested use, not the command itself.

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. :-)

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).

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Lawrence,

Turning off your monitor on the remote machine? SSH works fine in
that situation.

What are you talking about ? A "remote machine" ? This is about my RPi
and the TV its connected to, with both being located directly next to each other. Nothing "remote" about that.

Also, I think I made quite clear that I *didn't* want my TV to be turned
off. Just for it to switch to its previous inputs when the RPi is shut
down.

As it looks as if we are not quite understanding each other maybe you could explain how your "SSH" suggestion is supposed to work ?

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

"R.Wieser" <address@is.invalid> wrote:

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).

I understand your position, and you're almost certainly right. I have
to admit, I hadn't previously realised the full implications of this
thread as a whole.

-Rus.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

R.Wieser wrote:

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).

I just asked ChatGPT if it knew an answer, and it did (not that I am
certain if it works):

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), a feature available through HDMI that
allows devices to communicate with each other and exchange basic control commands.

Here’s how you can do it:

Check if the TV supports CEC: Not all TVs support CEC, and it may be
branded under different names like "Anynet+" (Samsung), "BRAVIA Sync"
(Sony), "Simplink" (LG), etc.

Install CEC tools: On the Raspberry Pi, you can install the cec-utils
package, which includes a tool called cec-client. This tool allows you
to send CEC commands.

bash
Code kopieren
sudo apt-get update
sudo apt-get install cec-utils
Send CEC commands: You can use cec-client to send various commands to
the TV. For example, to instruct the TV to switch to a different HDMI
input, you can use specific CEC commands.

Create a script: You can create a simple script that sends the CEC
command when the Raspberry Pi is about to shut down. For example:

bash
Code kopieren
#!/bin/bash
echo "as" | cec-client -s
The command echo "as" | cec-client -s tells the CEC client to switch the
active HDMI source.

Execute the script on shutdown: To automatically run the script when the Raspberry Pi shuts down, you can add it to the /etc/rc.local file or
create a Systemd service.

Keep in mind that the exact commands and setup may vary depending on
your TV model and the supported CEC functions. It's a good idea to refer
to your TV's manual for specific information about its CEC support.

-jw-
--
And now for something completely different...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Joerg,

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), a feature available through HDMI that
allows devices to communicate with each other and exchange basic control commands.

[snip]

Thank you for that extensive answer. Andy Burns also mentioned that "cec-client" program, but having a bit more info about it is always good.

By the way, I'm curious :

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 ?

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Joerg,

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),

A partial success. After having installed the cec-client software I was
able to do a scan and switch the TV off (meaning : the TV does respond to
CEC commands).

However, the "as" argument didn't seem to do anything.

I also tried a few "tx" arguments (found on the Web) with the TV (0.0.0.0)
as the target but could not evoke a back-to-tuner-input response either.

Any idea(s) ?

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

T24gMDIvMDgvMjAyNCAyMToyOCwgZHJ1Y2sgd3JvdGU6DQo+IE9uIDMwLzA3LzIwMjQgMTc6 NDYsIFIuV2llc2VyIHdyb3RlOg0KPj4gQW5keSwNCj4+DQo+Pj4gSGF2ZSBhIGxvb2sgd2hh dCBjb21tYW5kcyB5b3UgY2FuIHNlbmQgdG8gdGhlIFRWIHVzaW5nIGNlYy1jbGllbnQNCj4+ DQo+PiBBICJjZWMtY2xpZW50IiB5b3Ugc2F5ID/CoMKgIEknbGwgaGF2ZSB0byBsb29rIGZv ciBpdC4NCj4gDQo+IGFwdCBpbnN0YWxsIGNlYy1jbGllbnQNCg0KT29wcywgdGhhdCBzaG91 bGQgYmUgY2VjLXV0aWxzDQoNCj4gWW91J2xsIHRoZW4gbmVlZCB0byBmaW5kIHRoZSBjb21t YW5kcyBjaGFuZ2UgdGhlIHNvdXJjZSwgd2hpY2ggd2lsbCANCj4gZGVwZW5kIG9uIHlvdXIg VFYuIFBhZ2VzIHN1Y2ggYXMgdGhpcyBtYXkgaGVscA0KPiANCj4gaHR0cHM6Ly9zdGFja292 ZXJmbG93LmNvbS9xdWVzdGlvbnMvMTc1MDY1MTUvc2V0LWFjdGl2ZS1zb3VyY2UtdG8tdHYt d2l0aC1jZWMtY2xpZW50DQo+IA0KPiAtLS1kcnVjaw0KDQo=

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 30/07/2024 17:46, R.Wieser wrote:

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.

apt install cec-client

You'll then need to find the commands change the source, which will
depend on your TV. Pages such as this may help

https://stackoverflow.com/questions/17506515/set-active-source-to-tv-with-cec-client

---druck

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Fri, 2 Aug 2024 09:48:00 +0200, R.Wieser wrote:

Lawrence,

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.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Andy,

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>

Thanks. I have seen it mentioned elsewhere a few times too.

But to go hunt for something that /may/ be in there while not even being
sure if I would be able to recognise it if it would slap me in the face
isn't quite my cup of tea I'm afraid.

I'll just keep googeling for a while, and, nonwithstanding how well I could
use it, drop the whole thing if nothing turns up.

Maybe my (oldish) Philips TV simply isn't able to do it ... :-(

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Joerg,

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".

Thanks.

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").

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

"R.Wieser" wrote:

I have no idea what you are saying here. I'm supposed to be "SSHing" ?

I think the whole "SSH distraction" arose when someone suggested a
command which would disable the HDMI output, then a command to undo it,
and someone 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

Sorry I've not go the patience to go back and read the thread to see who
the various "someones" were ...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

R.Wieser wrote:

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").

The less info there is available online on any given subject the more
likely it is that the machine is going to make up information because in
its very depths it is supposed to keep up some chatty behaviour.

-jw-
--
And now for something completely different...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Andy,

I have no idea what you are saying here. I'm supposed to be "SSHing" ?

I think the whole "SSH distraction" arose when

I, the OP, was

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,

I seem to have a couple of years of experience with myself (duh :-) ), and
have noticed that I am /very/ likely to make typos when trying to do that.
Even to lauhghable proportions when I'm tired.

But thats not the point.

but then someone suggested you could SSH to the Pi from somewhere else to type the command to re-enable the screen

The one suggesting it was Lawrence. And his whole suggestion was exactly
four characters, "SSH?". IOW, not having /any/ of the info you, in the
above, have provided (and he still hasn't by the way).

After which I wrote that that would be solving one problem but by it
creating another.

Based on his responses I had to conclude that Lawrence has absolutily no
idea what I'm talking about, so I asked him to explain his solution. Hey, perhaps his SSH solution is different from the one I know, and cannot ever be(come) a problem.

I'm still waiting for that explanation though, as no matter how strongly I indicated I need some he refuses to supply it. All he's posted is a few
words which start with "SSH" - without any explanation to them - and a few iterations of "remote machine" - again, without a sliver of explanation of
what it is or how its supposed to be used.


So yes, there is a distraction going on, but it isn't the "SSH?" suggestion
one itself (it might have worked in quite a few circumstances). Its
Lawrence there verbally dancing around, trying to evade having to say
anything at all. Why ? Only he knows.

... 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.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Joerg,

its very depths it is supposed to keep up some chatty behaviour.

And there is that ofcourse.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 2024-08-03 13:34, R.Wieser wrote:

... 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

ssh pi@the-ip-of-the-pi

provide the password at the prompt.

Now you have ssh()ed to the pi.
You have a terminal session in the pi.

now execute the commands and be done with it



--
/Björn

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Björn,

... 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

So would I.

But in my particular case that would be a problem.

And I'm not talking about that I would need to keep a 'puter at ready just
to be able to check that the RPi shut down correctly.

Though the problem I referred to would make moot of that.

Than again, if someone would have realized (or just asked for!) the problem
I referred to (s)he might have been able to suggest another way to talk to
the RPi. Which would un-moot the "keep a 'puter at ready" issue. :-)

Remark:

Although I would like to see someone figuring out/realizing what my "but at
the same time creating the next" problem is (hint, the cause has been quoted here), I hope that everyone here realizes that this whole "disable HDMI
output" subthread is moot, as, as already mentioned, it doesn't do anything
for me in regard to my initial question, having the TV switch away from the
RPi when the latter is shut down.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)