Replies: 1 comment 1 reply
-
Did something change in C1? On my CX 2020, system.power_off() works like a Power Off API, not like a toggle. Part of the reason is because once the first power_off is called, the underlying connection is shutdown and further calls don't work. Are you saying the TV still maintains the websocket connection even after powering off (like it's some sort of soft power off)? Typically, the way it works with my TV (and in that of few others) is:
Can someone else confirm? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have C1 in PC use. Cause it's tv, it doesn't start/turn off with PC.
I try to simulate monitor behaviour via Windows Task Scheduler.
I can turn TV off (system.power_off) via Task Scheduler when idle is triggered, but it seems that system.power_off is toggle switch, because Windows triggers idle again and it turns TV on again. Yes, system.power_off command starts my TV when it’s turned off. To solve this, I tried to determine when TV is on or off, like fetching app list (app.list_apps) or read tv info (system.info) or send input (inp.up)… but responds were same when TV was on or off.
Is there true system.power_off() and system.power_on() commands? Or something to try to determine is tv on or off?
There are many problems to solve. Sadly Windows doesn't log sleep, and seems script is too slow to execute when PC powered off (event id 1074). Dirty solution would be to use Raspi to ping PC and turn tv on/off or something like that.
Beta Was this translation helpful? Give feedback.
All reactions