Open ekt- opened 5 years ago
Isn't it fixed already?
I had a custom component that lacked a services.yaml file, which caused all my automations to break because hass refused to load any of them. I admit I should have read any breaking changes when updating, but I think this is quite a harsh punishment for not complying with the rules, especially when the log refers to the missing services.yaml file was a WARNING.
@rogro82 This issue should be closed as correction is merged.
The issue is still valid in 0.95.4
Hi, the issue is still valid in 0.97.1 Will there be any actions on this or is it necessary to open a new issue?
@Pirol62 I don't understand. With the ne structure of this custom components you shouldn't have the error anymore. Have you installed the latest version ? If yes can you share more context information and logs ?
Hi, sorry I haven't watched the updates on this component. The good message: It's one of the very few components, which have worked stable and as expected from the beginning :-) and so there were no intention to do that. This issue can be closed.
Hi, The issue is still there in 0.101.3!
Starting from HASS 0.92 I think is related to this https://github.com/home-assistant/home-assistant/issues/23197