Bail out of failed reaction?

[Pabla]

Hey Patrick, I have a a few requests for the entity lists in both the entity tab and the entity selector that pops up when making rules.

First request: I was wondering if we could filter the entity list based on certain criteria. Maybe add some filters based on device type, integration (if the HA api exposes this), state etc. Also would be nice if we could sort based on the columns that are already present, ie sort by name, ID or primary value.

Second request: Deciphering between entities that are unavailable/offline and entities that have been deleted on the controller side? Currently they are all shown with a line through them and makes a bit hard to tell which entities are just offline or if they have been deleted and just waiting auto removal. Maybe even the ability to purge these entities so that they don't get in the way.

Third request: Add the ability to select multiple entities at once when adding them to rules, this would save a bit of time when creating long rules that use a long list on entities.

[toggledbits]

@Pabla said in Entity List Feature Requests:

First request: I was wondering if we could filter the entity list based on certain criteria. Maybe add some filters based on device type, integration (if the HA api exposes this), state etc. Also would be nice if we could sort based on the columns that are already present, ie sort by name, ID or primary value.

"Device type" is "not a thing" in Reactor. Capabilities reflect what a device can do, which is Reactor's preferred view of what has otherwise been referred to as type in systems like Vera. Integration has two issues: it's Hass-specific, and I don't know it because the Hass API doesn't expose it. The closest thing is domain, which does not entirely represent the integration for all Hass entities -- some devices an integration will publish have multiple entities, and many of these entities will have domains other than the one original to the integration, for example, Roku has its own domain roku but publishes entities in the sensor and media_player (and other) domains. The domain of the Hass entity is part of the Reactor entity ID, so you can search for it by inclusion in the name filter field (which looks at both name and ID). I can look into sorting as some point, but given the few columns and the ability to filter aggressively, it doesn't seem very high value/ROI.

@Pabla said in Entity List Feature Requests:

Second request: Deciphering between entities that are unavailable/offline and entities that have been deleted on the controller side? Currently they are all shown with a line through them and makes a bit hard to tell which entities are just offline or if they have been deleted and just waiting auto removal. Maybe even the ability to purge these entities so that they don't get in the way.

If a Reactor entity has a line through it on either of these entity lists, that means the entity no longer exists (wasn't advertised by) the source hub/controller. Reactor itself does not show entities that are simply "off line" (i.e. Z-Wave unreachable) with strikethrough, unless it is MIA from the controller's report of inventory. The entity being offline is a completely different thing, and actually Reactor doesn't know or care. If Hass "unpublishes" entities that are only offline, not actually deleted, that's a Hass issue/oddity. The ability to purge deleted entities exists through the purge_dead_entities action that exists for all controllers.

@Pabla said in Entity List Feature Requests:

Third request: Add the ability to select multiple entities at once when adding them to rules, this would save a bit of time when creating long rules that use a long list on entities.

I can add that to the wish list.

[Pabla]

Excellent this makes sense to me! Hopefully we can see the last feature in the coming future