-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test works but TV will not power off on normal shutdown #226
Comments
I will also add that I have 3 physical monitors, the other 2 are connected via display port. Not sure if that is relevant or not but thought it was worth mentioning. Thanks again! |
Hi @catsncode can you try enabling persistent connections please (device onfigutation). If that does not work please paste a log and I will have a look |
Sorry for the delay, my machine was down for a bit. Now I can test again. Persistent connections was already checked. I just tried it and it worked fine... If it starts acting up again, I'll post the log. Thanks! |
@JPersson77 I seem to have this same issue. TV does not turn off on system shut down. I don't know what test mode is and where to use it, so cannot tell if that works. Also, what does it mean to "enable persistent connections please (device configutation)". Which device, which app, which software, which system. On TV, on PC? |
hi @Kingston1 the test function is in the drop down menu of main UI page: the persistent connections are enabled in the app's configuration page for the TV: |
@JPersson77 well argh. My mistake. I was using a seriously old version. I installed the latest (4.0.5) and everything works flawlessly with default settings, through both Wifi and LAN. But to my defence, I landed on this app through a very prominent Google search result, which is pointing to that seriously ancient version: https://www.reddit.com/r/OLED_Gaming/comments/vlx8nz/turn_lg_oled_onoff_automatically_via_pc/ I was stupid and assumed the link was legit. I don't have reddit account but someone should get that person to link to the releases page instead. Thanks for your flawless software though! |
After that 1 time it worked, it has failed to work after that every time. I've probably shutdown around 15 times as I'm testing some other stuff on the machine. Here is a clean debug log I took that shows a shutdown and startup. The power on always works, but it's very slow. Is there any way to speed it up? Thanks again! |
Hi @catsncode you are right that comms seem slow and it seem to be causing problems. Usually a response from the TV is immediate but I can see seconds long delays. First, try and pull the power plug on all network equipment, the PC and the TV, including access points, routers, switches etc. I have seen that help more than ten times probably. Then make sure shutdown timing is set to delayed and that persistent connections are enabled. Fingers crossed... |
I would have thought to put shutdown timing to early since the PC is powering off before the TV is shutting off. It is still not working. The power on works like a champ every time (unless the TV is somehow doing that itself when it sees the hdmi signal?) I haven't rebooted the router yet because I'm worried it could mess some other things up. The TV's assigned IP has not changed so I'm not sure what rebooting would accomplish as I think it would still assign it the same one. Thanks! |
Hi again, the reason I suggest to power cycle all network equipment, PC and TV is because something is/seem to be causing delays in the network communications and this was the solution for a few people with similar issues. |
Hi @catsncode any updates on the above? |
Thanks for checking in. I've definitely tried power cycling but still have
the same issue. Power on works pretty much every time, but not the power
off. It's so weird that the test mode works fine. So my current solution
is to just let the screen timeout after 15 minutes, which works but is not
ideal. Thanks!
…On Tue, Nov 12, 2024 at 4:02 AM JPersson77 ***@***.***> wrote:
Hi @catsncode <https://github.com/catsncode> any updates on the above?
—
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPZV4VSLAUJ7WWICS7KHUT2AG735AVCNFSM6AAAAABK2LSEDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZHE2TQNJSGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks, if you are using wireless can you please try using a cable? Or vice versa. From the logs it looks like slow/delayed communications on the LAN |
Sadly I can't access my virtual pinball PC to plug in ethernet without
removing the TV. It was a bad design choice, hah. I'm sure I will
eventually have to do that and when I do I'll give it a try. Or if I can
find a USB to ethernet adapter I can try it as I do have usb access to the
pc. I would not be able to use wired ethernet as a solution though.
Would it be possible to at some point put in a config option for cases like
mine where it could wait a super long time or something? If the TV turned
off even after a full minute, that would be great. Maybe a number of
seconds value, I don't know.
Thanks for the help!
…On Thu, Nov 14, 2024 at 2:21 AM JPersson77 ***@***.***> wrote:
Thanks, if you are using wireless can you please try using a cable? Or
vice versa. From the logs it looks like slow/delayed communications on the
LAN
—
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPZV4R7QY3JSVUU6DZ4VYD2ARFQPAVCNFSM6AAAAABK2LSEDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZVGU4TKNRYGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
hi again @catsncode just checking in if there is any progress on the issue. I don't think it will solve your issue to enforce longer network timeouts unfortunately. |
Thanks for checking in. No, I think you wanted me to try using wired
ethernet, but I haven't had to open up the virtual pinball machine yet and
probably don't want to buy a usb ethernet just for that purpose. I'm ok
with my current solution of having the screen timeout after 15 minutes. At
least it is turning on fine which is the most important thing. I'll let
you know when I'm able to try wired ethernet. Let me know if you ever want
to try something via a debug build or something. Thanks!
…On Sun, Dec 22, 2024 at 3:53 AM JPersson77 ***@***.***> wrote:
hi again @catsncode <https://github.com/catsncode> just checking in if
there is any progress on the issue. I don't think it will solve your issue
to enforce longer network timeouts unfortunately.
—
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPZV4VVKHNVZEJPF6UE46L2GZ4W5AVCNFSM6AAAAABK2LSEDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGM4DCOJQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for this amazing and helpful code!
Power on is working, but I just can't get it to power off even though the test mode works fine. I have tried, early and delayed. I checked the error log and it says:
"Did not receive the anticipated event subscription call back prior to shutting down unable to determine if system is shutting down or restarting!"
Any ideas on how I can troubleshoot? This is a windows 11 machine with a C2 TV on hdmi 2. I had some weird issues with interference or something on hdmi 1, which is why I switched to 2. I have also tried setting the TV to always on mode but it did not help.
Thanks!
The text was updated successfully, but these errors were encountered: