I do have this behavior occasionally after restarting the router or updating HA.
However, please check your automation if the icon is red. This happens to me in my previous post.
I do have this behavior occasionally after restarting the router or updating HA.
However, please check your automation if the icon is red. This happens to me in my previous post.
Hello, have you tried redownloading the blueprint?
Hey there, the important thing is to set the LG connect/mobile app settings to keep the TV awake.
Sadly, for some reason, some models just fail to receive WOL commands reliably, I actually had to get an IR blaster to work around this.
I will try that and report if it still fails.
Thanks
Yes it still fails. I need to duplicate the automation in order to make it work again.
That is weird, I never seen this issue before and it’s quite inconvenient.
All right, first of all I recommend you to delete your automation and create a new one from the blueprint. If the issue keeps happening, then please send the full error log.
Thanks, I already have removed and created the automation when I reinstalled the blueprint.
The log above is complete, I don’t get more when downloading the full log.
Let me know if/how I can get more logs from that.
I think I found something:
When I first start HA after installation and edit the automation while HA still is starting up, I get this error:
Message malformed: Integration 'webostv' does not provide trigger support
After HA is up I can edit the automation without an error.
My guess is that HA marks the automation as defective at first startup.
Note: this only happens when installing HA from scratch, it does not happen from upgrading. I now upgrade HA instead of reinstalling it.
The reason you might be getting this error during installation is because the integration might not be available/configured yet.
I was unable to reproduce your issue over here, so I updated the blueprint to use a different trigger method. Try it out:
This works and doesn’t break at first startup. If there is no downside to the new trigger method it might be safe for updating to everyone.
Sweet, there is a breaking change, but functionality will be the same.
I’ll release it on stable
Thanks a lot!
Please forgive the noob question, but here goes.
I have my LGTVs integrated into HA – check
I can send magic packets via a WOL entity to turn on my TVs – check
I’ve even setup an automation to send the magic packet when the TV is turned on – check again
But, when accessing the TV through a dashboard, there is no way (that I can see) to turn on the TV from a media card. Once the TV is turned on (whether through my physical remote or by turning on the WOL switch), then the media card works great. Just can’t figure out if/how to turn the TV on from the media card to begin with.
I haven’t (yet) implemented this blueprint. Does this blueprint solve my problem? Appreciate any suggestions.
I’ve tried to import this blueprint and the import and configuration works well, when I press the power on button on the multimedia panel the automation correctly execute the job but the tv didn’t power on.
I see in the trace that all the passages are correctly executed.
I’ve also seen to configure a wakeonlan switch
wake_on_lan:
switch:
- platform: wake_on_lan
name: LG_TV_WOL
host: 10.10.2.31
mac: "20:28:BC:CC:02:D4"
broadcast_address: 10.10.2.255
and it works perfectly
what i’ve do wrong? this is my config for the blueprint
alias: LG webOS Smart TV - Turn On Action
description: ""
use_blueprint:
path: cvroque/webostest.yaml
input:
webostv: 726f9b61a56b38781b34f26b96191a5a
webostv_mac: 20:28:BC:CC:02:D4
I’ve found the problem, I’ve multiple lan interfaces on the server and the tv is on the secondary lan and not on the default gateway lan.
You need to manage also the broadcast ip on the configuration to manage this case
Hey there!
The IMPORT BLUEPRINT TO MY HA button up top is leading to a 404 error…
Any idea why or how to go around this?
thanks!
Hey,
You should click on the “My HA” link and you’ll be in an intermediate page, then check the address on Your instance URL. The address might be wrong, causing the redirect to fail.
Alternatively, go straight into HA and import from the URL: https://gist.github.com/cvroque/6780ca0869ef781e9de3b506fd501f78
Thanks for coming back to me, Carlos!
However, I dont think it’s matter of the url of my instance:
If I navigate to http://homeassistant.local:8123, I can access without a problem, but clicking on Open Link shows me a
404: Not Found.
Could it be due to the repository being private on your github account? Trying to wild guess reasons…!
Same thing happening to me.