Hi there - that's about as good as you can get with current functionality - unlike listen_state(), listen_event() is pretty simple, it responds to the named event and hands the data over.

This is partly because I haven't had a more complex usecase - I use custom events myself, but only in a simple way. However, there is no reason I couldn't expand it to handle the usecase of listening for specific attributes as is possible in listen_state() - to be somewhat consistent with listen_state() I would probably do something like:

self.listen_event(self.cycle_scene, 'zwave.scene_activated', attribute="scene_id", value=self.scene_id)

Does that sound like it would work?

FWIW, I have a minimote too but haven't gone through the hassle of setting it up for HA yet, so maybe I will do so so I can test this feature :)

from appdaemon.

That sounds perfect! Thank you very much :D

from appdaemon.

OK, I will add it to the list, but for now you have a working setup :)

from appdaemon.

Got my minimote working and I have added filtering to the listen state call - it has info in the API file but here are a couple of examples of what I ended up with:

Listen for a minimote event activating scene 3:

self.listen_event(self.generic_event, "zwave.scene_activated", scene_id = 3)

Listen for a minimote event activating scene 3 from a specific minimote:

self.listen_event(self.generic_event, "zwave.scene_activated", entity_id = "minimote_31", scene_id = 3)

I am calling these "event filters" and you can use them to filter for any arguments in any event.

I am just about to push the release with this in - 1.3.3.

from appdaemon.

Thank you so much for this! (Sorry for the delay - circling back to automation stuff now).
Looking forward to cleaning up the code I have.

from appdaemon.