Home Assistant's automation editor gains forms for checking a Z-Wave device's status, configuration settings and reported values before an automation continues. The conditions can test whether any or all selected devices match, using named states instead of requiring their underlying numbers.
Raman Gupta's work follows the visual Z-Wave event and value-change triggers introduced earlier this week. Together, the changes bring both starting an automation and checking its prerequisites into the editor's forms. Existing per-device conditions remain supported.
The forms also catch mistakes before an automation runs: saving fails if none of the selected devices has the requested setting or value. An empty selection never counts as a successful match.