Unable to get actionable notification to trigger
Please make sure your bug isn't already listed on HASS.Agent's issue tracker:
https://lab02research.youtrack.cloud/
There's a list of open bugs & features on the right. On the left you can see what's being worked on, what's planned and what's ready for the next release.
If you're not sure, don't worry, just go ahead and we'll discuss :)
Describe the bug I followed the steps to setup an actionable notification on my Windows 11 machine. However, I can't get the automation to trigger on a "yes" action.
To Reproduce Steps to reproduce the behavior: N/A I setup the notifications via the readthedocs link above
Expected behavior Actionable notifications work.
Screenshots

Misc info (please complete the following information):
- Windows build (ideally screenshot/info of
winver.exeoutput): -
- Windows' UI language: English
- HASS.Agent version: 2022.13.0
Please check what's applicable (multiple answers possible):
- [x] Installed via installer
- [ ] Installed manually
- [x] Problem occurs in HASS.Agent
- [ ] Problem occurs in Satellite Service
Additional context It seems to me the click event on the toast notification is getting dismissed before the "yes" button. I could be wrong though.
Not quite sure what's going wrong. Are there any notable entries in Home Assistant's logs?
@fischgeek I had the exact same problem. Turnes out I got the device_name wrong. It had to be all in caps. I found that out by going into the Developer Tools -> Events and under "Listen to events" I subscribed to "hass_agent_notifications". Then, when I fired the script and clicked "yes", I saw the correct device_name.
Hope that helps
Thanks for that @Hilarious83, could you let me know if that fixes it @fischgeek? I'll update the docs accordingly
I'm skeptical it's case sensitive, but I'll try when I get home. I do wonder if your device name was all caps and you needed to match it. Mine is all lowercase as per the docs.
that's certainly possible. I just copied the devicename from the notify serice where it was in lowercase and wondered why it didn't work. At least you can hopefully narrow it down by listening to the events and see what comes back (if any).
Any update on this @fischgeek?
Sorry. I was on vacation. I'll test as soon as I can.
Old issue but please also make sure the API token is generated on HA admin user.