Hi,
I love callback constraints feature from AppDaemon, however, there is something that I bumped into that does not allow me to extendedly use it. I use them with the ControllerX, an application that allows you to bind controllers with devices. Callback constraints are used to enable or disable an application depending on the condition, normally a condition involving the state of a light or a media player, so the configuration would look like this:
example_app:
module: XXXX
class: XXXX
constrain_input_boolean: light.light1,on
This works great and I love it, the things is if I want to add another entity constraint I cannot add another condition under the constrain_input_boolean (or at least I could not see in the documentation, this is why I am asking). However, I do the trick of using the constrain_input_select
:
example_app:
module: XXXX
class: XXXX
constrain_input_boolean: light.light1,on
constrain_input_select: light.light2,on
This also works, but the problem is if I want to add another light or other condition, the keys are already taken. I tried to add an array and other things but I could not make it work. Is this something is not implemented on AppDaemon or is there another workaround for this without involving Python code in the applications?
I would also like to thank the contributors of AppDaemons since it is a really cool project and it really saved me from really long YAML configurations with HA automations.
Thanks,
Xavi M.