rustic wadi
Well I'm not actually new to HA, I have been using it for about 1.5 years now but I am new to Discord, thus I am using the #New to HA tag so I don't upset anyone, well I probably will anyways, ohh well..
The attached error from HA has occurred for me a few times over the last 1.5 years. It occurs when an HA entity is no longer and usually unexpectedly available to HA (as many of you know). In this case my Toshiba (Amazon Fire) TV went to sleep and then entity disappeared to Home Assistant.
Yes I should probably have a condition to make sure the entity is available but come on, I dont want to condition every single notification in every automation I have, this is an absurd way to handle entities.
The problem is obvious, the TV is causing the issue, I am not contending the issue lies with HA at all, however as a programmer I find that Home Assistant not running the rest of my automation because one unimportant notification entity is very illogical. HA should just skip it and keep going in my opinion.
Yes warn me of the problem, this is very useful and good but at the same time don't break the entire automation, this is bad.
Who decided it is a good idea to just break an entire automation because one unimportant entity is not available? This is what I observed today. How can we get this fixed?
and yes - in my opinion this is also poor design. This is where people will get upset at me. Go ahead, get upset, I don't care. Accept criticism and make HA better and don't waste time arguing would be my suggestion to you if you are about to bang a reply to me telling me _____ ..
Thank you in advance to all of the other people that will offer suggestions that love HA as much as I do and try to help. Much appreciated!
dim apex