Yah. Thus why I threw it out there as “AI”. It hallucinates a large chunk of the time in my “professional” use of it where I’m always calling something into question and it “suddenly agrees” - but it does spit out a bit of usefull stuff now and then.
I’ll take a look. I’ve actually got 3 sites and this site has identity turned on but not really vetted yet. All local users, so the output provided covers standalone.
Happy to get back to you on this after I confirm. I just took the overly cautious tact of not exposing IDs on my running system. I’ll iterate a bunch more over some time and let you know.
I actually am using webhooks to trigger a door unlock via api (and have a side request Feature Request: Pass LOG MESSAGE with Webhook calls to allow webhooks to pass an entry to syslog for the purposes of logging the long ID) You’ve correctly called out that people will want to know what the triggered ID is… I’ll work on finding a way for you.
I guess even if we were to do nothing more than dump out the ID of the triggered event, knowing a legit event happened and treating it as a “button press” could at least move this into the native support and log the ID.
I’ll set up and play with the AI-dreampt-up stuff and see how much is real.