Hi,
I upgraded to HASSIO from an older hassbian install. After struggling initially to get up and running, I managed to get most of my old config transferred to lovelace. I just cant get the WOL switch to work though. Calling the WOL service does turn on the PC, but for some reason the component always says not available,… Do you need to configure something else in HASSIO to get WOL to work?
Running the HASSIO on a PI3.
are you using WOL switch or WOL the service?
Is this just an issue of it not showing in the front end?
I was using the WOL Switch, but also enabled the WOL service the last time I was trying to get this to work (so I could test if the MAC address was working). It was working 100% on the old HASSBIAN, but in HASSIO/Lovelace I just get a message that the component is not available…
Where are you getting this message? In a yellow/red box in lovelace or in the error log?
In a yellow box in lovelace…
double check the entitiy_id you have entered in lovelace.
Go to the developer panel and in the states tab search for your switch entity ID for your WOL component. Copy and paste that into your lovelace config.
If you cannot find your WOL switch in the states panel then the WOL switch likely didn’t load, you need to check the error log to see the cause of this.
Ok, after checking the states I noticed the WOL switches was not showing up at akk… Deleted them from the config, restarted HA. Then I created them from scratch - rebooted and they showed up. Not sure why they weren’t showing up in the first place, but after removing them and re-booting they are now showing up and working correctly…
So I ran into a bit of a problem again. The switch was working perfectly for a while but yesterday I noticed the state no longer updates. So the PC turns on with the switch but HA shows it as off. This is for a windows 10 PC, my other WOL switch for the media Server (Ubuntu) works as expected with the state showing as on once the PC boots…
Any reason why the windows 10 PC state will no longer update? Nothing changed on the config and the IP address has also not changed…
Ok, so I had time this weekend and debugged this issue. Turns out my Avast updated and set the LAN connection to Public - Firewall was blocking the wol state detection from HassIO… Setting it to private solved this issue…