Config check needs to get more clear

Config check can be rather unhelpful. It doesn’t point to the correct file (if you have an error in, say, customize.yaml, it doesn’t point to that, but to configuration.yaml). What does this even tell me?

I didn’t even make any changes to config.yaml. What do I do with this?

The same goes for notifications. “Config error, see logs” isn’t very helpful as there are errors that don’t spawn a notifications, and I have no way of telling what’s the notification concerning. Thanks!

Your wake on lan switch config is invalid.

But why? It worked even an hour ago, I didn’t touch anything AND the switch itself works (it wakes the PC up). I really don’t know what to do with this. Thanks for your answer.

Paste your switch config here.

I restarted Hassio once more, now it says

The following integrations and platforms could not be set up:

* [sensor.template](https://www.home-assistant.io/integrations/template)
* [sensor.mqtt](https://www.home-assistant.io/integrations/mqtt)

and the original error is gone. I’m not editing any file. I’m completely perplexed.

The original error is gone because the switch no longer exists. The platform it relies on could not be set up because your config is invalid.

You’ve deleted the switch: key, so all your switches are now under the sensor: key which is invalid.

I must’ve been sleep-editing the config.yaml, I don’t remember doing it at all in a couple of days. Mea culpa, problem solved, thanks!

My original point kinda still stands though, shouldn’t there be at least the line where the error occurs instead of “see ?, line ?”?

The reason you get that is because you import other files in to the config file.
So when the config check is done (I assume) all is in one file so line numbers are not correct anymore.

What you can do is to instead of including the separate files is to copy paste it in to the config just to do the config check.
That way you should get a correct error message.

I’d probably need to remove the !includes too, right? Seems like a error-prone process. thanks!

Yes or just comment it out.