Devices can’t be disabled. Only entities. My devices are gone.
Hi, restart from UI just stop server after update. Restart from ssh works fine, no errors in config, nothing in logs… something else to look at?
Anyone can help with the questions about mediabrowser? Or clear out stuff 
1 Like
Did you read this?
Particularly the last paragraph.
After the latest update to 2022.2.5 lovelace loading has become extremely slow for all the tabs but especially the ones with many cards, and especially the ones with cameras.
After the latest update to 2022.2.5, HA is unable to send Wake On Lan Magic Packets. I had to revert back to 2021.12.10 to keep this functionality.
That sounds like something you should open an issue for.
To what device? To a LG TV by any chance? If so check this topic or Github, there is an solution for that.
I am on 2021.2.5 and I can send WOL to my PC and LG Tv.
Still works for me, on Container installation.
Same here, is there a solution to that?
As “known issue” in integrations panel it will be fine to activate or deactivate logs for the integration.
To not have to change it in yaml.
It is an LG TV to be more specific about my issue. Here is my code:
webostv:
host: XXX.XX.X.XXX
name: Game Room TV
turn_on_action:
service: wake_on_lan.send_magic_packet
data:
mac: A8-23-FE-4E-51-D2
it looks like I’m using the same code as your solution. I’m not sure why WOL stopped working for me with this upgrade if it’s working for you 
i’m on latest too, and am using the wak on lan thing too, without problems.
SO its probably something at your side?
The turn on action you need to do that in the automation you are using, not in the config file
From where is that code?
Your configuration?
Get rid of the
‘’’
webostv:
host: XXX.XX.X.XXX
name: Game Room TV
‘’’
and just use the service in the automation
That is in your config I assume, that does not work anymore, delete that and restart HA after that ad the automation like how it explained here, not through YAML but through automations:
EDIT: Sorry @skank you already said almost same thing, I was away for couple minutes while typing, didn’t see your reaction.
1 Like
depending on the device you’re trying to wake, if its a Synology, there’s a fix see https://github.com/home-assistant/core/issues/65688 and https://github.com/home-assistant/core/pull/66125
I did read that. But what and where are “known” devices? And if they are gone how and where do i enable them? It’s not very clear how everything should work now. Besides that they could be gone.
1 Like
I’ve had situations where following an OS uprade, the version listed in supervisor is the old version. All of these types of issues (for me at least) appear to disappear and correct themselves following a restart of the Core). After a restart, the OS 7.3 upgrade finally showed, and I was able to upgrade. Just some bug somewhere, likely. Restart and see if that solves it.
Was that really necessary? Aren’t hostilities already high enough here? 
4 Likes
Thanks Francis for the idea. I use MQTT Explorer a lot previously. I solved my issue by creating a YAML file and telling HA configuration to look at the file. Worked a treat (until HA break that option).