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?  
 

0

Comentarios

8 comentarios

  • Comment author
    stefan

    Hi, same issue here. I even had to wait more than 5 minutes yesterday. The problem exists since about two month. Before the notifications came within a few seconds. Now i have to wait at least 1 minute

    0
  • Comment author
    joost.samsom

    Same issue here. Annoying!

    0
  • Comment author
    jeanvictor.bourbon

    Same here. Was thinking was coming from my infra. Glad to see I’m not an isolated case

    0
  • Comment author
    netatmo-presence
    • Editado

    Same here since 5th May in the morning.
    Often a delay between 1-2 minutes! … I also noticed that the JSON payload is incomplete for humans and vehicles, only for pets it is complete.

    I already informed Netatmo but for now without much useful replies.

    My 2 presence outdoor cameras are pretty useless if I can react on an event which is 1-2 minutes old 🤮

    In the worst-case scenario, the burglar will be gone by then.

    If they don’t fix it, I have to buy some new outdoor cameras, but from INSTAR for example. Those devices support local LAN access with MQTT, pretty much better than this stuff from Netatmo.

    2
  • Comment author
    gustavsen

    Same issue here. I have tried two different webhook setups, and they are both virtually useless with these delays.

    0
  • Comment author
    netatmo-presence

    well, Netatmo doesn't give a shit on it 🤮

    It's time to switch to something that works and kick those Netatmo devices out of my house.

    0
  • Comment author
    Leslie Community moderator

    Hello all,

    Sorry for the late answer, it took time for the teams to investigate and perform tests. We indeed noticed delays on the 3rd party webhooks component. Despite a huge scale-up of the service, the situation is not better

    There is a ongoing rework project for webhooks (including the ones sent from our native apps) to improve the stability. Unfortunately, I don't have more information about an availability date for this

    Have a good day,

    Leslie - Community Manager

    2
  • Comment author
    simon

    Same problem here. Hope you can fix this soon.


    1

Iniciar sesión para dejar un comentario.