Following issues…
In Home Assistant App, I have a button to ‘start’ our Smart TV. It actually does a ‘wake on LAN’; but a wake on LAN is slow… like up to 10 seconds.
My users at home don’t have that patience… And the fact that is no ‘please wait, tv is about to start…’, makes it even less ‘user friendly’. In some way I can understand them.
What would be options to give them feedback in the HA app that the TV is indeed about to wake up.
At the moment it just a switch that a user pushes to launch the TV. An automation will trigger the wake on LAN and put the switch back to his original value…
Something is wrong if WOL is not instant. 10 seconds is far too long. My WOL automation takes way less than a second. Rather than trying to put a fix in place it would probably be better to find out why your automation takes 10 seconds to run.
the TV has a red light that turns off when it turns on… But as said that takes 10 seconds before something happend. In the mean time a user has no real idea if he has now pushed the wake up button, of the TV is reacting or not…
so some feedback to the user from the APP GUI would be nice… (versus the experience where using the TV remove gives instant feedback on the TV).
On my TV (an Android) like yours there is a red light which goes off when you press the standby button on the remote. That red light will be on in two situations:
The TV has just been powered on. In this case pressing the standby button starts it and you get the usual manufacturer logo for about 10 seconds to show this.
The TV is on standby having been playing earlier. If this is the case the launcher screen appears immediately.
Not clear which is happening in your case. Presumably the device is powered, otherwise WOL wouldn’t work, but if it has to go through its start-up procedure I’m surprised there isn’t some kind of display from the TV itself to show this is happening.
It is a Philips 55OLED706/12: it is the behaviour it has after a WOL…
And a device waiting for WOL, is basically a device where only the network card is active…
A WOl on this TV just turns on the ‘computer’ of the TV, not the screen. For the screen to turn on you need a second command. See also my next reaction.
The IR remote does indeed both.
I ‘fixed’ is now by having the button stay on until the TV IP address becomes active.
And an automation turns the screen to the home screen when the IP is active.
One small catch: the TV wakes up everyday: I assume to check for ‘updates’. The automation also turns on the TV at that moment… So the automation now also has a condition that ‘wake up’ button needs to be pressed.