Webhook heavily delayed

josef.krinzinger

Hi!

currently playing around with Home Assistant and successfully registered the Webhook. 
But the webhook events are received around 3 minutes after the doorbell was triggered, which is absolutely unacceptable for a doorbell. 

I tested my webhook url from external manually and the average response time was 300ms for the call.
So i'm pretty sure the issues is not on my side. 

Anything i can do to debug this? Is this a known/accepted issue of the API?  
 

3

Comments

31 comments

Date Votes
  • Comment author
    Leslie Community moderator Master (Platinum)
    • Edited

    Hello heinigerd,

    Thanks a lot for this precise feedback. I forwarded it to the teams and they found your information very interesting. Your usecases will be tested with the new webhook service

    To answer your questions : 

    1. What is causing the inconsistent webhook delivery delays for security events?

    I'll answer both 1. and 3. questions : in a nutshell, the current webhook infrastructure is not robust enough to handle an increasing number of requests. Some scale-ups were done to avoid the problem with our native apps notifications, but it's expensive. So, it was decided to perform a total rework in order to fit with the current needs

    2. Why does a second app (with valid scopes and home access) not receive any security webhooks at all?

    It's surely a bug, there is no will on our side to block this. It's planned to include tests for this on the new service, but no fix will be done on the current one

    4. Is the webhook refactoring project (mentioned by Netatmo in September 2024) still in progress, and when can we expect improvements?

    The deadline for this project is planned for this summer. It's a big work and many tests are required

    5. Are there any best practices to ensure faster webhook delivery?

    Unfortunaly with the current service, no

     

    Have a good day,

    Leslie - Community Manager

    0

Please sign in to leave a comment.