Closed sti0 closed 4 months ago
I don't know about this one. Infeasible status are difficult to catch because there could a huge amount of reasons for a failing optimization. You happend to stump on the only case that is actually catched and where a warning message is issued.
Today when a optimization result is infeasible we may get a warning in the container / addon log.
This warning is not accessable by web ui or the
sensor.optim_status
sensor entity.Therefore I would suggest to add the reason of a infeasible optimization result as an additional attribute to
sensor.optim_status
. This then could be used in automations, alerts and notifications. Furthermore it should be displayed in the Web UI as well.