display-on.sh wakes monitor up to wrong tty about chilipie-kiosk HOT 13 CLOSED

OK, seems like there's definitely something fishy with the scripts, since you're not the only one seeing this!

Let me know if you manage to fix this somehow, and we'll be happy to test & merge upstream!

from chilipie-kiosk.

Did you ever get to the bottom of this @xfakt-pj?

from chilipie-kiosk.

No, I'm afraid we just went with the workaround.

from chilipie-kiosk.

OK, I'll try to look into this when preparing the next release.

from chilipie-kiosk.

Great, would be much appreciated. I think I can find some time to test that new release ;)

from chilipie-kiosk.

@xfakt-pj there's a new RC available for download!

from chilipie-kiosk.

The v2.1.0 release was thoroughly tested for this, and we were unfortunately unable to reproduce this.

I'm not saying I don't believe you, but I'm saying I don't know what to do about this without a way to reproduce, sorry!

Feel free to reopen if you have more info on this.

from chilipie-kiosk.

Sure, no worries. Didn't have the time to test the RC yet. I will get back to this when upgrading the current dashboards.

from chilipie-kiosk.

Issue seems to persist after updating to v2.1.0. I have attached my crontab in the hope that it might prove to be useful somewhere down the line.

Considering the workaround I stated in the OP and the fact that you can not reproduce this I currently have no leads as where to start debugging this. But lets keep this here for future reference.

Can we keep the issue open in case somebody else comes across the issue? @jareware

from chilipie-kiosk.

I have the same issue also, the morning "display-on.sh" is opening on the raspi-config tty.
The reboot workaround also works, but it's not super clean :)

from chilipie-kiosk.

Odd. My guess would be that the display-on.sh script cycling the tty misbehave somehow. (They're there because without them some displays would not come back on. HDMI is a mess. 😒)

@xfakt-pj, @jendib, if you want to try something, you can remove the chvt commands from ~/display-on.sh and see if it changes anything.

And please report back if you do! 😃

from chilipie-kiosk.

I just try this solution and works great for mi, see if it works for you.
-Instead of removing signal to the display I send a "stand by" command to TV using CEC.
This are the steps:

Install :
sudo apt-get install cec-utils

TV ON
echo "on 0" | cec-client -s
TV OFF (stand by)
echo "standby 0" | cec-client -s

Also I can "Force" to keep display on specific HDMI ( INPUT 1 ) Input by running this on a cron.

HDMI INPUT 3
echo "tx 4F:82:30:00" | cec-client -s
HDMI InTUP 1
echo "tx 4F:82:10:00" | cec-client -s

*or maybe switch from one to another input every given time also in a cron.

CEC have much more benefits Raspbery can also receive instructions from TV remote control (depending on the TV model)

or maybe with a local "api server" or websocket can even control TV from web.

Any more info or suggestions are welcome.

from chilipie-kiosk.

Great set of tips!

The biggest issue with CEC seems to be that even if something works on one TV, there's 0 guarantees it'll work on another TV, even from the same manufacturer.

from chilipie-kiosk.