Rene Tode

after the release from AD 4 we are going to work on upgrading dashboard. 1 of the things we plan to do is give every widgettype options like navigate and...

this would be a very complicated widget and the user needs to create complicated settings. i dont think this will be something we will create as default option, but you...

why use listen_event at all? just use: ``` class RollerBlinds(hass.Hass): def initialize(self): self.listen_state(self.event_recieved, "input_select.the_one_you_use", attribute="event_type", new="roller_blinds") def event_received(self, entity, attribute, old, new, kwargs): self.log("event_type from input_select changed to rollerblinds") ```...

when the attribute never changes, then how would you get a response, and why would you want to listen to it? hmm, i think now i get what you tried...

to filter callbacks we have constraints. in this case you want a custom constraint, that checks if an certain attribute has a certain value. https://appdaemon.readthedocs.io/en/latest/APPGUIDE.html#callback-constraints so the option exists, only...

custom constraint. https://appdaemon.readthedocs.io/en/latest/APPGUIDE.html#custom-constraints and we are talking about adding more default options for constraints.

with a custom constraint you create a function that gives back true or false based on the given input. by adding a listen_state for all input_selects (which you can get...

because that way the callback wont even be started. all a matter of choices. but in AD 4 you will see the difference between a callback that is returned inside...

you are right. selecting before gets rid of the need for the constraint. allthough the constraint could get have other options as well. indeed for everything are several ways to...

> Hopefully HA will be more accommodating to AD created entities and attributes in the future dont count on it. i deal with that problem for over 2 years now....