This code used to work: - id: '1679873069852' alias: Notification - Water Leak - Kitchen sink description: '' triggers: - type: moist device_id: ffc7d99ac2bbbc8ebcc955d5e1b86618 entity_id: 5c18c7a0fe5dd3a79e95dd394f8d298f domain: binary_sensor trigger: device conditions: […

[image] exx: device_id: ffc7d99ac2bbbc8ebcc955d5e1b86618 Im guessing that’s probably your issue right there. device_id: ffc7d99ac2bbbc8ebcc955d5e1b86618 If you just switched coordinators and integrations, then there’s a HIGHLY likely chance your device_id has changed. If you have the automat…

[image] mmstano: there’s a HIGHLY likely chance your device_id has changed @exx [image] Why and how to avoid device_ids in automations and scripts Community Guides Background When you start writing automations, a device trigger seems the obvious choice. Everybody …

[image] exx: I’m at a loss here. Was there a breaking change I missed somewhere? :frowning: All the examples in the actionable notification docs show action and title values surrounded in quotes. Try changing this: actions: - action: TURN_WATER_ON title: Turn water on…

[image] mmstano: Im guessing that’s probably your issue right there. device_id: ffc7d99ac2bbbc8ebcc955d5e1b86618 I did do that already, that’s how the device-I’d got in there. I would never bother to look that nonsense up to manually put that in my yaml. Lol That aside though, in the interes…

I’ll give that a try, thanks! Need to do some more work on the zigbee network first. Now that it’s had a chance to “bake” for a few days, I’m finding that some of my devices are reporting. Maybe need to add another router or two to increase signal levels. I have 8 or 10 battery powered devices that…

Issue with actionable notifications and wait for trigger?

Configuration

parautenbach (Pieter Rautenbach) January 11, 2026, 6:06am 3

@exx

(And already the second time I’m posting this today.)