AIO is triggering multiple times, should be once...

[shadow wren]

I have an action set up for a value from a feed to be sent to a webhook once per day at noon. In my experiments, the data is being sent multiple times, not just once. It is behaving as if it requires some sort of ACK which it is not getting.

After submitting the action, and returning to it later, it seems changed.

But, I programmed it to "Every day at" not "Every n hour(s)".

This page makes no sense, and my efforts to program it to a once per day trigger have been futile. Can anyone shed some light on this?

[shadow wren]

I believe that Adafruit IO is sending a webhook to Discord, and not getting a "response", even though on the Discord side, it is working fine. Then AIO retries five times and stops the Action.

What am I doing wrong?

[obsidian holly]

@terse mirage any ideas?

@shadow wren the date/time should be working as expected. I've pinged Loren who may be able to shed more light.
You can also do more testing using another webhook address like httpbin.org where you can post to http://httpbin.org/post

or better yet https://webhook-test.com

[shadow wren]

Ooooh... thank you for webhook tester... I will try that.

[terse mirage]

just seeing this. @shadow wren it sounds like there are 2 issues:

• webhook form won't stay at "once per day"
• webhooks aren't successfully resolving on the IO side, and thus auto-retry 5 times, despite actually being successful on the hook side
  is that right?

[shadow wren]

Hi, @terse mirage (which happens to be my middle name)

I think you grok that correctly. But, the first might be a misunderstanding of the Action form. And I do think there needs to be additional clarifying words on that form.

But, I have done some experiments with respect to the second point, and have some data to share. I set up two Actions to fire a webhook upon change in value of a Slider on my Dashboard. One Action fires to a Discord channel. The other Action fires to webhood-test.com, as above. After five actuations, where both actions work fine, Discord stops working and the test site continues happily. AIO sends me an email stating, "Your trigger with id XXXXX has been paused due to too many failures."

So, I conclude some interaction between Discord and AIO is not working correctly. Possibly, there is a throttle on Discord. However, note that I originally detected this failure with three sensors posting to Discord once per hour. After five hours, they fail. I cannot imagine a throttle that would be unhappy with that.

[obsidian holly]

please feel free to suggest additional wording or information you'd appreciate on the action form. it may help drive future revisions

[shadow wren]

I would be honored to contribute. I will give it a brain cell.

[terse mirage]

After five actuations... discord stops working
stops working on both sides, like the notifications don't come through in the actual Discord channel either? or IO just thinks it's not working but they appear correctly?

i do see the Action form issue! oof not a fan of that form.

also @shadow wren are you seeing the actual error on those webhooks? can see the last response by clicking the little blue i

[shadow wren]

I suspect "empty response" is the issue.

[obsidian holly]

Yeah we're tweaking the knobs and warming up the steam kettle to bring a patch online, should accept more Http status codes now (soon)

[terse mirage]

indeed, we were being naive about response statuses, really glad you caught and reported this!

ok @shadow wren i just deployed a fix for that particular issue, i think your discord hooks will not break after 5 sends now

thanks for the interesting note about our names! i swear i met not one male Loren with that spelling for the first 20 years of my life, but in the last 5 years or so i've bumped into quite a few.

[shadow wren]

Ooooh.... will test now! Thank you for fast bits.

Hey, I can't break it!! Nice work!!

What was the nature of the fix, @terse mirage ?

I also note that webhook-test responds with Status:200, and Discord responds with Status:204.

[terse mirage]

yeah we were only looking for 200 or something

expanded it to all 200-299 codes 🤦‍♂️

[shadow wren]

Ha. That sounds logical. Well, I am a happy camper with the fix.

[obsidian holly]

Appreciate the feedback, would have probably gone unnoticed otherwise!

[shadow wren]

I am nothing if not willing to share my opinion with others. LOL.

So, on another form...

I am trying to say "every day at noon execute this".

But I have to select time period as "hourly", then choose "Every day at 12:00"... which makes no sense to me.

Very confusilating.

[terse mirage]

yep, very bad form

i think we grabbed some kind of jquery cron manager thingie and it's just old and not terribly compatible with everything else

big changes afoot for that whole subsystem, will keep you in mind for testing it when we're close

[shadow wren]

Cool. I will be happy to bang on it. I am liking AIO in general!!

[shadow wren]

@terse mirage I mention you in a video on YouTube. Search "PFG.Live 2023-1119". 🤓👍

[terse mirage]

oh that's really cool! thanks for telling the whole story and all the kind words.