Hi Steve,
I want to thank you again for doggedly continuing to help me. I'm giving up at this point, not because it can't be done, but because the thing you said about clicking on the interface made me realise this isn't a good solution for my specific use case.
Basically, if it requires an interface click before it will work, then it is not a suitable solution for critical notifications eg people breaking into the tractor shed again. The consequences of not receiving a notification because a click hadn't clicked is too high for me, so I'm going to pursue using the audio out of whatever pi zero.
I have several old ones, and this is a good use: a sensor node with voice notifications. I can make it pretty.
But, @Steve-Mcl, I also want to thank you generally because of all that I learned from you. The big ones were:
- a better understanding of how http endpoints work and can be called. I think this will be extremely helpful knowledge in other contexts. Dangi ka matha.
- cache busting. Wow! very valuable and a wonderful surprise as a concept.
I invite anyone who solves this in an easy way to share their solution. I will post the Piper tutorial in the next few days, my hands are very full. Working on a 500L compressor I retrieved from the store because I have a tractor with a flat tyre.
The conversation went like this:
"Why does this sound like it's full of water?"
"It always sounds like that."
"I see. So when did you last drain the tank?"
"Drain the tank?"
"There's water in it, when did you last drain it?"
"You're supposed to drain it? How?"
They've been using it for five years.
Anyway thanks again. I'll post my solution with flow when I figure it out.
And @E1cid, your idea of putting the Piper call inside the endpoint was super interesting, and very much cooler than what I had going on, and I'm stealing it. You have a nice brain.