Closed ultratoto14 closed 4 years ago
What was the behavior before? Must have been something similar, perhaps just printed to console. Anyway, we can suppress errors and just make the entities unavailable instead. I was thinking of adding an error
attribute to state_attributes
as well since Home Assistant has very poor support for reporting problems (other than the log, which isn't a very user-friendly way of doing so).
Yes, previously, we just had the status set to unavailable and no exception. It seems also that the startup of ha is delayed, the integration is trying multiple times to get the status before letting the startup continue.
I've noticed the delay start up as well. Not sure why that happens, I thought I "fixed that". Oh, nooow I see... Will deal with that later today.
Ok, so, if a device is unavailable then state attributes are not shown in the UI (which seems logical since the entity is not available, so no info should be present). This however makes it tricky to display any error information. I have an idea though...
I created #57 which should fix this. Would be great if you can try it out!
For the light bulbs, we can have some bulbs that are not logically off but physically off.
In that case, the new way of getting status (by device) produces exception traces in logs: