Netatmo webhooks delay

francisco

Last year when we implemented the Netatmo Doorbell, the webhooks were sent just after pressing the button (NDB-incoming_call).

In the recent months the webhooks started to take a long time to arrive: 15 to 40 seconds. Making our doorbell take a very long timr to ring.

We have debugged every possible variable, but unfortunately it seems like a problem from Netamo:

  • We have ensured the doorbell has good wifi coverage.
  • We have purchased and are using the Netatmo official power supply.
  • We have re-installed the application and reset tokens.
  • We have ensured our API is instantaneously reachable from anywhere in the world.
  • We have reduced data/footage retention to the minimum.

 

Before, when we got the webhook, most of the times the image was not even available in the Azure Blob Storage. We even have a routine in our API that does something to the image when it become available. We can actually tell that before, it was quite common to wait a few seconds for the image to become ready, while now, most of the times when we receive the webhook the image has finished uploading.

Did you change anything on your side to wait for the image before sending the webhook? If so, can we enable the webhook to fire instantaneously even if the image is not available?

Thank you in advance.

1

Comments

3 comments

Date Votes
  • Comment author
    francisco

    Update:

    We had a few really bad days last week. But more recently it seems that it has improved quite a bit.

    We had two doorbell disconnects during the weekend early mornings. Hopefully it was an update on your side. Or maybe we are just getting superstitious because your service sometimes works okay, other times not so well.

    Hopefully it continues working well, without problems in the near future. Just made a test and we received the notification in less than 6 seconds, which is quite good for us. Obviously less than 2 or 3s would be ideal.

    I still have some open questions:

    • Would it be possible to get the POST directly from the doorbell or find a way to replace your cloud?
      This will be specially relevant when you discontinue your service.
    • Ar you waiting for the image to be available before sending the request? If so, do you intend to revert that or allow us to disable that feature?

    Thank you.

     

    CC: @Leslie

    - Related thread
    - Related blogpost for you to see what we are doing with these webhooks.

    0
  • Comment author
    Leslie Community moderator

    Hi Francisco,

    We pushed a fix concerning the webhook delays on Friday 20 September. We waited 1 week to see the user's feedbacks and check logs, and good news : it seems to have significantly reduced the sending time

    Concerning your questions : 

    • Would it be possible to get the POST directly from the doorbell or find a way to replace your cloud? <= unfortunately no. Everything is Cloud-based so it must necessarily go through our servers
    • Ar you waiting for the image to be available before sending the request? If so, do you intend to revert that or allow us to disable that feature? <= No, we don't wait for the thumbnail availability before sending the request. The developers are working on an improvement of the webhooks logic for the end of this year, so it should improve the response times

     

    Have a good day,

    Leslie - Community Manager

    1
  • Comment author
    francisco

    Thank you for your answer. This is great!

    0

Please sign in to leave a comment.