Skip to content
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

Recent: TV Not Turning On, Just "On" Affected #544

Open
shanemcw opened this issue Sep 19, 2024 · 11 comments
Open

Recent: TV Not Turning On, Just "On" Affected #544

shanemcw opened this issue Sep 19, 2024 · 11 comments

Comments

@shanemcw
Copy link

Recently, about a week ago, a controlled TV no longer turns on via the Home app. The TV can be turned off, the inputs changed, etc. via the Home app if it is on, but not "on" if it is off. On the Home app, via Siri on a manual set of the TV to be "on," Home reports that it is on, and automation triggered by the "on" executes, but the TV is not physically on.

Recording this data point in case others find this condition.

@shanemcw
Copy link
Author

It looks like a newly introduced bug in WebOS. In my context, the "turn on with WiFi" setting is "on" in settings (it looks to be specific to just the "on" function), but I can confirm that the official remote app that simulates the remote can also turn off the TV but not back on. So, I confirmed this is not a plugin issue but perhaps a bug preventing general power on control via Home regardless of that setting activated.

@shanemcw
Copy link
Author

WebOS software version 04.50.90

@merdok
Copy link
Owner

merdok commented Sep 19, 2024

I am pretty sure that it has something to do with your network. The turn on command is sent to the TV with the standard Wake on LAN / Wake on WLAN command. That means the TV needs to be in the same network as your homebridge instance and the power saving features on the tv need to be off.

@shanemcw
Copy link
Author

I know, weird right? Confirmed power savings are still off, confirmed is still on same network, been working for over a year, just stopped powering on a week or so ago. Started with scenes—a scene would do everything—including trying to turn the TV on—and automations get the "TV turned on" event, but TV not turned on. Weird the LG Remote iPhone app cannot turn it on either, just turn it off and everything else. Confirmed the "allow other apps to turn on the TV" is still on.

@merdok
Copy link
Owner

merdok commented Sep 20, 2024

Yeah well you have to investigate your local setup and check what could be the cause that the wake on lan packets do not arrive at your tv.

@wondertwins
Copy link
Contributor

I am having this issue as well.

@merdok
Copy link
Owner

merdok commented Nov 29, 2024

@wondertwins the issue will probably be more or less the same in your case. The WOL packets might not arrive at the TV...

@wondertwins
Copy link
Contributor

@merdok yep, it was due to my vpn configuration. Even though I have homebridge setup to use en0 Network Interface, the WOL packets was not getting through.

@wondertwins
Copy link
Contributor

@shanemcw Try setting your broadcast address in advanced settings. I have mine now set to 192.168.1.255 and its working now.

@merdok
Copy link
Owner

merdok commented Nov 30, 2024

Thanks for the update and a possible solution!

@BenS89
Copy link

BenS89 commented Nov 30, 2024

I have the same issue. LG C1 can not be turned on via Homebridge - all other settings work. Turning on via LG App works, so wake-on-lan is working on network layer

Update: My Hombedridge runs on a machine with multiple network interfaces (config was changed by me some days ago). Setting the broadcast address fixed the issue for me. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants